274 KB
26 KB
21 KB
123 KB
122 KB
122 KB
122 KB
134 KB
The commands added to the server properties->script menu are only executed once when the connection is first made. After that, subsequent reconnects will not execute these commands. We need to look into a way to always execute these commands when connecting and reconnecting. Look at ConnectionProperties->getConnectionPrivate. Search for ConnectionUtil.executePostConnectionScript.
There should also be a configurable parameter added into Options->General with the default being off so that current users don't have behavioral changes.
Hi Tom,
We followed the steps but we are not able to reproduce the issue. We checked the logs attached in the issue description as well, it is mentioned connection timeout in the logs.
Can you please help if we are missing something.
Thanks
Darpan
Hi Tom,
We followed the steps but we are not able to reproduce the issue. We checked the logs attached in the issue description as well, it is mentioned connection timeout in the logs.
Can you please help if we are missing something.
Thanks
Darpan
Hi Darpan,
Here are the steps to follow...
1) Use the DB2 LUW 172.24.1.8 v11.1 connection. Open the server properties->script window and add some script. See here. Save it.
2) Now right click on the connection and open a QA window. See here. Notice the schema is set to TOM.
3) Change the schema in the QA window. See here.
4) Disconnect the connection. See here. Emulates the customer losing the connection(timing out).
5) Reconnect the connection. See here.
6) Notice the schema after the reconnect. See here. It should be TOM but since the server properties->script was never executed, the schema was not changed.
Hope that helps,
Tom
Hi Darpan,
Here are the steps to follow...
1) Use the DB2 LUW 172.24.1.8 v11.1 connection. Open the server properties->script window and add some script. See here. Save it.
2) Now right click on the connection and open a QA window. See here. Notice the schema is set to TOM.
3) Change the schema in the QA window. See here.
4) Disconnect the connection. See here. Emulates the customer losing the connection(timing out).
5) Reconnect the connection. See here.
6) Notice the schema after the reconnect. See here. It should be TOM but since the server properties->script was never executed, the schema was not changed.
Hope that helps,
Tom
Hello Tom,
Thanks for the steps to reproduce the issue.
Now we are able to generate the issue and start looking into it.
Thanks,
Rajat
Hello Tom,
Thanks for the steps to reproduce the issue.
Now we are able to generate the issue and start looking into it.
Thanks,
Rajat
Hi Tom,
We checked the flow of the code and we found that the query in Script column is getting executed during after the reconnect from ConnectionUtil.executePostConnectionScript. After that, the schema is being set to the selected one. This is the flow that we found -
This is the required behavior because if we change this, in that case when the user reconnects and we haven't used and "SET SCHEMA" query in the script, it will not use the schema used by the user initially, but it will change the schema to some default schema which is not the required behavior.
We need confirmation on how should we proceed further. Should we use the schema in the script column or should we use the schema selected by the user?
Thanks
Darpan
Hi Tom,
We checked the flow of the code and we found that the query in Script column is getting executed during after the reconnect from ConnectionUtil.executePostConnectionScript. After that, the schema is being set to the selected one. This is the flow that we found -
This is the required behavior because if we change this, in that case when the user reconnects and we haven't used and "SET SCHEMA" query in the script, it will not use the schema used by the user initially, but it will change the schema to some default schema which is not the required behavior.
We need confirmation on how should we proceed further. Should we use the schema in the script column or should we use the schema selected by the user?
Thanks
Darpan
Hi Darpan,
I will take another look at this and get back to you.
Thanks,
Tom
Hi Darpan,
I will take another look at this and get back to you.
Thanks,
Tom
Hi Darpan,
Don't do anymore work on this.
Thanks,
Tom
Hi Darpan,
Don't do anymore work on this.
Thanks,
Tom
Issue #15604 |
Closed |
Invalid |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
The commands added to the server properties->script menu are only executed once when the connection is first made. After that, subsequent reconnects will not execute these commands. We need to look into a way to always execute these commands when connecting and reconnecting. Look at ConnectionProperties->getConnectionPrivate. Search for ConnectionUtil.executePostConnectionScript.
There should also be a configurable parameter added into Options->General with the default being off so that current users don't have behavioral changes.