• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Devaka Cooray
  • Jeanne Boyarsky
  • Bear Bibeault
  • Junilu Lacar
  • Paul Clapham
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • salvin francis
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

Getting wlthint3client.jar file error while doing load testing for jms client  RSS feed

Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Hi All,

I have a jms client program that using wlthint3client.jar file to send jms message from jboss serever to weblogic server. This program is tested and running fine with low load condition, but its failing with heavy load condition system is going to unresponsive state.

I am getting below messages in thread dump file collected when the system underdone with heavy load condition.

"ExecuteThread: '0' for queue: 'JmsAsyncQueue'" daemon prio=10 tid=0x00007f48ac493800 nid=0x2201 in Object.wait() [0x00007f48e67ed000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x000000072a6659e8> (a weblogic.kernel.ServerExecuteThread)
at java.lang.Object.wait(Object.java:503)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
- locked <0x000000072a6659e8> (a weblogic.kernel.ServerExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)

Locked ownable synchronizers:
- None

"weblogic.transaction.TxTimer: '1'" daemon prio=10 tid=0x00007f48ac434000 nid=0x2200 in Object.wait() [0x00007f48e68ee000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x000000072ae08cb8> (a weblogic.transaction.internal.GenericTimer)
at weblogic.transaction.internal.GenericTimer.run(GenericTimer.java:15)
- locked <0x000000072ae08cb8> (a weblogic.transaction.internal.GenericTimer)
at java.lang.Thread.run(Thread.java:724)

Locked ownable synchronizers:
- None

"weblogic.timers.TimerThread" daemon prio=10 tid=0x00007f48ac44f000 nid=0x21ff waiting for monitor entry [0x00007f48e69ef000]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x000000072a6602b0> (a weblogic.timers.internal.TimerThread)
at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:262)
- locked <0x000000072a6602b0> (a weblogic.timers.internal.TimerThread)

Locked ownable synchronizers:
- None

"ExecuteThread: '4' for queue: 'default'" daemon prio=10 tid=0x00007f48ac2eb800 nid=0x21fe runnable [0x00007f48e6af0000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:870)
- locked <0x000000073df1f1c8> (a java.net.Socket)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:830)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:339)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

Locked ownable synchronizers:

I am able to understand that this problem is happening due to wlthint3client.jar but i do not have any clue why its happening.

Can anybody help me on this issue.


Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try removing wlthint3client.jar and restart server.
Refer https://docs.oracle.com/cd/E21764_01/web.1111/e13717/wlthint3client.htm#SACLT379 for more details.
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!