Support Article
Getting WAS hung threads
SA-26683
Summary
After migrating to test environment, PRPC application throws hung threads after any user interaction.
User have below configuration :
- Windows Server 2008 R2
- Websphere 7.0
- DB2/AIX64 SLQ9073
Error Messages
Thread[WebContainer : 7,5,main]
java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:981)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1352)
at java.net.InetAddress.getAllByName0(InetAddress.java:1300)
at java.net.InetAddress.getAllByName(InetAddress.java:1229)
at java.net.InetAddress.getAllByName(InetAddress.java:1151)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$Lookup.<init>(TDNetworkIOIF.java:182)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.connectToHost(TDNetworkIOIF.java:297)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.createSocketConnection(TDNetworkIOIF.java:130)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.<init>(TDNetworkIOIF.java:116)
at com.teradata.jdbc.jdbc_4.TDSession.getIO(TDSession.java:580)
at com.teradata.jdbc.jdbc.GenericLogonController.run(GenericLogonController.java:95)
at com.teradata.jdbc.jdbc_4.TDSession.<init>(TDSession.java:209)
at com.teradata.jdbc.jdk6.JDK6ConnectionFactory.constructConnection(JDK6ConnectionFactory.java:22)
at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:130)
at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:120)
at com.teradata.jdbc.TeraDataSourceBase.createNewConnection(TeraDataSourceBase.java:672)
at com.teradata.jdbc.TeraPooledConnection.getConnection(TeraPooledConnection.java:120)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getConnection(WSRdbDataSource.java:2788)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getGoodConnection(WSManagedConnectionFactoryImpl.java:3614)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1819)
at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:2086)
at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1761)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2636)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1064)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:701)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:668)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:635)
at com.pega.pegarules.data.internal.access.DataSourceManager.getConnection(DataSourceManager.java:321)
at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.activate(DatabaseConnectionImpl.java:1344)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1312)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:977)
at com.pega.pegarules.data.internal.access.ThreadConnectionStoreImpl.getConnection(ThreadConnectionStoreImpl.java:389)
at com.pega.pegarules.data.internal.access.DatabaseInformationMapImpl.lookupDBInfo(DatabaseInformationMapImpl.java:319)
at com.pega.pegarules.data.internal.access.DatabaseInformationMapImpl.get(DatabaseInformationMapImpl.java:267)
at com.pega.pegarules.data.internal.access.DatabaseImpl.getDBInfo(DatabaseImpl.java:7328)
at com.pega.pegarules.data.internal.access.RuleResolver.getRuleCandidateIterator(RuleResolver.java:1925)
at com.pega.pegarules.data.internal.access.RuleResolver.lookupFirstLevelCandidates(RuleResolver.java:2093)
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1801)
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1720)
at com.pega.pegarules.data.internal.access.RuleResolver.openDefaultRule(RuleResolver.java:1663)
at com.pega.pegarules.data.internal.access.DatabaseImpl.openDefault(DatabaseImpl.java:4771)
Steps to Reproduce
Unknown
Root Cause
From the Systemout logs below details has been observed .
[8/8/16 1:32:42:197 EDT] 00000017 DSConfigurati W DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'portNumber' does not exist on the DataSource class com.teradata.jdbc.TeraConnectionPoolDataSource.
Users database team announced that they were “implementing a gateway Efix on Teradata appliance for monitoring and with this “client Teradata JDBC versions should be at least 14.00.00.12 version” and they are using version 13. With the old drivers, it was causing a thread dump and all connection pools stopped working.
Resolution
Teradata JDBC driver version has been updated to 14.00.00.12 version.
Published September 1, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.