Question
Tata Consultancy Services
IN
Last activity: 4 Feb 2018 2:06 EST
Issues with PEGA 7.1.5 on WAS 8.5.5.10 version
Hi Team
i am trying to install PEGA 7.1.5 on WAS Proprietary information hidden version, My installation seems to be successfull but application is not coming up. Any idea you can get from the logs will be helpful. As i dont see any upright errors
Pegasystems Inc.
IN
HI,
Could see below errors from the logs
[2/4/18 2:25:18:653 UTC] 00000054 ThreadMonitor W WSVR0605W: Thread "d7abfd86693d" (00000041) has been active for 713109 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at com.ibm.db2.jcc.t4.y.b(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.v(Unknown Source)
at com.ibm.db2.jcc.t4.cb.c(Unknown Source)
at com.ibm.db2.jcc.t4.q.a(Unknown Source)
at com.ibm.db2.jcc.t4.h.readFetch_(Unknown Source)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.b(Unknown Source)
at com.ibm.db2.jcc.t4.c.b(Unknown Source)
at com.ibm.db2.jcc.am.kc.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
HI,
Could see below errors from the logs
[2/4/18 2:25:18:653 UTC] 00000054 ThreadMonitor W WSVR0605W: Thread "d7abfd86693d" (00000041) has been active for 713109 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at com.ibm.db2.jcc.t4.y.b(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.v(Unknown Source)
at com.ibm.db2.jcc.t4.cb.c(Unknown Source)
at com.ibm.db2.jcc.t4.q.a(Unknown Source)
at com.ibm.db2.jcc.t4.h.readFetch_(Unknown Source)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.b(Unknown Source)
at com.ibm.db2.jcc.t4.c.b(Unknown Source)
at com.ibm.db2.jcc.am.kc.a(Unknown Source)
at com.ibm.db2.jcc.t4.c.a(Unknown Source)
at com.ibm.db2.jcc.am.ResultSet.nextX(Unknown Source)
at com.ibm.db2.jcc.am.ResultSet.next(Unknown Source)
at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next(WSJdbcResultSet.java:3114)
at com.pega.pegarules.data.internal.access.DatabaseResultSet.next(DatabaseResultSet.java:452)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl.readClassDefinitions(ClassMapImpl.java:7023)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl.init(ClassMapImpl.java:2142)
at com.pega.pegarules.data.internal.access.DatabaseImpl.<init>(DatabaseImpl.java:1683)
at com.pega.pegarules.data.internal.access.DatabaseImpl.newDatabaseImpl(DatabaseImpl.java:1592)
at com.pega.pegarules.data.internal.access.DatabaseImpl.newDatabaseImpl(DatabaseImpl.java:1587)
at com.pega.pegarules.data.internal.PRDataProviderImpl.ctorDatabaseImpl(PRDataProviderImpl.java:744)
Check if any database sessions are locked up and not releasing the locks ,let us know if you find any threadumps in the pegarules log file to check for the root trace of that .
You can have a look at below article for reference
http://www-01.ibm.com/support/docview.wss?uid=swg21314783
Thanks,
Arun