JDBC pools(Functional Alias restart)

, ,
1

Hi All,:o
As we aware of restart of Functional Alias in JDBC pools whenever the webMethods IS is restarted for DB connectivity.

we are facing DB connectivity problem when we restart SERVER1 so we are restarting all the functional alias in JDBC pools. Then the DB connection is working fine.

But there is no problem with DB connectivity though we restarted SERVER2.

Can anyone provide the information and explain why it is occurring.Though both the servers have the same configurations with no difference.

Thanks in Advance for your Clarification.:happy:

2

Raj,

Could you provide more detail like the version of JDBC adapter and IS and configuration settings of JDBC Adapter?

3

And the error? “DB connectivity problem” isn’t quite precise enough.

4

Hi Talha,
JDBC Adapter version 6.0.3 (SERVER1 & SERVER2)

        IS 6.5 and configuration is also same for both the server.

        Oracle DB
5

Hi Talha,
Please find the detailed information of my system

WM IS1 and DB1 are on same server1 (BOX) similarly WM IS2 and DB2 are on other server2 (BOX).

we are just restarting only WM IS, no changes/restart are done at DB or Server(Box).

After restating WM IS1 there is no problem with DB1 connectivity but when we restarted WM IS2 its not connecting to DB2 unless or until we restart the functional Alias in JDBC pools.

So we need the clarification why it is differing though all the settings and configurations are same for both the WM IS SERVERs :frowning:

6

Raj could you also provide the JDBC Adpater configuration, the DB version and error detail as Rob requested.

7

Cannot connect to the database with DataSource class “oracle.jdbc.pool.OracleDataSource”.

Io exception: The Network Adapter could not establish the connection

[ART.114.13] Adapter Runtime: Error occurred while Adapter Runtime was loading adapter type “JDBCAdapter”.

[ART.114.9] Adapter Runtime: Error(s) while registering adapter type JDBCAdapter.

JDBCConnectionManager: initialization failed for TN functional alias, check configuration.
JDBCConnectionManager: initialization failed for Xref functional alias, check configuration.
JDBCConnectionManager: initialization failed for ProcessAudit functional alias, check configuration.
JDBCConnectionManager: initialization failed for DocumentHistory functional alias, check configuration.
JDBCConnectionManager: initialization failed for ISCoreAudit functional alias, check configuration.
JDBCConnectionManager: initialization failed for Staging functional alias, check configuration.
JDBCConnectionManager: initialization failed for Reporting functional alias, check configuration.

Exception while deleting expired uuids: com.wm.app.b2b.server.indoubtresolver.exceptions.ConnectionException: ] Unable to get Connection
Unable to get JDBC Connection to the database.

Hi All Can you give the resolution to our problem as it is critical for US!!!

8

If it’s critical, you should open a ticket with webMethods support.

From looking at the description of the problem, I don’t know why something would work perfectly on one server and not work on another if they were indeed identical. My guess is that they are not identically setup (either the ISes or the DBs.)

Although I don’t think it will help much in this case since you’re seeing this problem after a server restart, try setting the minimum number of connections to 0.

  • Percio
9

To reiterate what Percio said: If it is critical, you should open a service request with webMethods tech support.

The error message indicates that the DB server you’re trying to reach isn’t reachable. Are firewalls a factor? Is there a typo in a server name?

One more time: please post your adapter connection configurations!

10

Hi All,
Thanks for all your Support & Advice, we got the solution!! We have configured DB2 driver instead of Oracle driver in Pool alias for one of the server.

But one thing we are not clear though we have configured DB2 driver in Pool alias how it is able to connect Oracle DB after restarting Functional Alias.

Can we connect through DB2 driver to oracle DB and similarly Oracle driver to IBM DB2 DB by using Jar files of one another.