Closed NilukaSripalim closed 1 week ago
@UdeshAthukorala FYI
The JSON file related to the specific branding preference is being saved in the database as BLOB objects. In DB2 database, the datasource will dynamically determines the most efficient mode to return BLOB or XML data. This step is based on the size of the LOBs or XML objects.
The DB2 JDBC drivers have a parameter named progressiveStreaming
to decide how such objects should be returned. If the value is not set or if the value is set to 1, the driver will not load the LOB data into memory all at once, but will instead load it in small chunks as you access the data. This will not be suitable for our implementation. Hence, this parameter has to be specified in the connection string as progressiveStreaming=2
which will disable the progressive streaming.
Since, this doesn't require any code changes, the relevant instructions should be mentioned in the documentation.
Sample configuration to be added to the deployment.toml
type = "db2"
url = "jdbc:db2://localhost:50000/isrc11:progressiveStreaming=2;"
username = "db2inst1"
password = "password"
driver = "com.ibm.db2.jcc.DB2Driver"
[1] https://www.ibm.com/docs/en/db2/11.5?topic=pdsdjs-common-data-server-driver-jdbc-sqlj-properties-all-database-products#:~:text=property%20is%20int.-,progressiveStreaming,-Specifies%20whether%20the [2] https://www.ibm.com/docs/en/db2/11.5?topic=keywords-progressivestreaming [3] https://stackoverflow.com/questions/22659970/lob-is-closed-errorcode-4470-sqlstate-null
https://github.com/wso2/product-is/assets/50801227/b7d42072-1ff1-4210-8325-ddee573fbda8
We can add the connection string parameter through the infer.json file. So, it is not required to add it through deployment.toml. Hence it is not required to mention in the documentation as well.
Functional part is tested and verified, but untill docs update, will keep this issue in an open state
This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!
Describe the issue: Issue while attempting to set up branding "Design" in Console with a DB2 database. The UI displays the following error message:
wso2carbon.log
https://github.com/wso2/product-is/assets/39120228/89f4a2d3-94f8-4866-aca7-b48900379ead
How to reproduce: Configure DB2 database in toml. Log in to the console. Navigate to the branding "Design" section. Attempt to update or modify branding preferences. Observe the error message in the UI.
Expected behavior:
Certainly! Here's a template for a Git issue:
Issue Title: Unable to Setup Branding "Design" with DB2 Database
Description:
I am encountering difficulties while attempting to set up branding "Design" in WSO2 Identity Server with a DB2 database. The UI displays the following error message:
rust Copy code Update Error: An error occurred while updating the Branding preferences for carbon.super. Steps to Reproduce:
Configure WSO2 Identity Server to use a DB2 database. Log in to the Identity Server management console. Navigate to the branding "Design" section. Attempt to update or modify branding preferences. Observe the error message in the UI. Expected Behavior:
The branding "Design" should be set up successfully without encountering any errors related to the database, and the UI should reflect the changes made.
Environment information (Please complete the following information; remove any unnecessary fields) :