Results 1 to 3 of 3

Thread: Stuck threads in weblogic

  1. #1
    Join Date
    Jun 2011
    Posts
    29

    Default Stuck threads in weblogic

    Hi

    We are facing below error frequently in our appliocation:
    Code:
    "[STUCK] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" id=2247 idx=0x264 tid=1248 prio=1 alive, waiting, native_blocked, daemon
        -- Waiting for notification on: java/lang/Object@0xb8f39ee0[fat lock]
        at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
        at java/lang/Object.wait(J)V(Native Method)
        at java/lang/Object.wait(Object.java:485)
        at org/springframework/integration/store/MessageGroupQueue.put(MessageGroupQueue.java:178)
        ^-- Lock released while waiting: java/lang/Object@0xb8f39ee0[fat lock]
        at org/springframework/integration/store/MessageGroupQueue.put(MessageGroupQueue.java:37)
        at org/springframework/integration/channel/QueueChannel.doSend(QueueChannel.java:79)
        at org/springframework/integration/channel/AbstractMessageChannel.send(AbstractMessageChannel.java:157)[optimized]
        at org/springframework/integration/channel/AbstractMessageChannel.send(AbstractMessageChannel.java:128)
    Here is the set-up:
    1. A jdbc message store backed queue
    2. A particular request puts about 10-15 messages continuously to the queue.
    3. We have jdbc batched all the transactions.

    Could you please help me with this error?

  2. #2
    Join Date
    Jan 2008
    Location
    Mohnton, PA USA (that's near Philadelphia)
    Posts
    2,148

    Default

    Could you please provide more information as to what triggers this error? In other words what happens in your application to force this error. We can't fix it unless it is reproducible and i want to get some idea how to reproduce it.

  3. #3
    Join Date
    Jun 2011
    Posts
    29

    Default

    Thanks Oleg for your reply.

    Our application generates about 50 different events.
    We use the following configuration for each event:
    1. Queue Channel for buffering messages, backed by a jdbc message store
    Code:
    	<jdbc:message-store id="TESTMsgStore" data-source="GlobalMsgStoreDS" region="TEST1" />
    	<si:channel id="TESTQ">
    		<si:queue message-store="TESTMsgStore" />
    	</si:channel>
    2. A pub-sub channel
    Code:
    	<si:publish-subscribe-channel id="TESTPubSubChnl" >
    		<si:interceptors>
    			<ref bean="GlobalMsgInterceptor" />
    		</si:interceptors>
    	</si:publish-subscribe-channel>
    	<si:service-activator input-channel="TESTPubSubChnl" ref="TestSubscriber" method="processMsg" />
    3. A chain to connect the queue and the pubsub channel:
    Code:
    	<si:chain input-channel="TESTQ" output-channel="TESTPubSubChnl">
    		<si:poller fixed-rate="60000" max-messages-per-poll="1" task-executor="">
    			<si:transactional transaction-manager="txManager" />
    		</si:poller>
    		<si:filter ref="GlobalMsgSelector" />
    	</si:chain>

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •