unknown OutOfMemoryError

[sic <si...@naver.com>]

I'm using servicemix 3.2.1 and have a question about an unknown cause to the
OutOfMemoryError.

In default setting, servicemix defines three kinds of standard flows in
servicemix.xml which is seda, jms and jca.

In this state, I'm deploying jms and bean serviceunit and client requests a
few(maybe 200 number of data per day).

Then the following error occured occasionally in all of the servicemix
components once per month :

pool-component.servicemix-jsr181-thread-1
org.apache.servicemix.common.AsyncBaseLifeCycle:338 - Error polling delivery
channel
java.lang.OutOfMemoryError
	at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1642)
	at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1820)
	at
java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:301)
	at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.accept(DeliveryChannelImpl.java:271)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.pollDeliveryChannel(AsyncBaseLifeCycle.java:314)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle$1.run(AsyncBaseLifeCycle.java:300)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
	at java.lang.Thread.run(Thread.java:810)

And servicemix gets abnormal status, cannot do anything until I restart the
servicemix engine.

Does anybody have some idea about this issue?

I guess it could be releated to the flow which is seda jms and jca.

With these 3 flows, I don't know how the flow could be set in my service
unit.

But actually, there is no way for me to analyze this situation.

I appreciate any kinds of comments that will be helpful for me.

regards,
sic
-- 
View this message in context: http://servicemix.396122.n5.nabble.com/unknown-OutOfMemoryError-tp2801716p2801716.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: unknown OutOfMemoryError

[sic <si...@naver.com>]

flow which I guess for the main reason is irrelevant to this issue.

In the first tracing of exception line, AbstractQueuedSynchronizer seems to
synchronize its container on the inside of jdk.

and we use IBM jdk - version is JDK 1.5.0 SR7.

memory leak state on AbstractQueuedSynchronizer.addConditionWaiter () has
already been reported on jdk of both Sun and IBM.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6460501
https://www.ibm.com/developerworks/java/jdk/aix/j532/fixes.html#SR9

although not knowing anything for sure, we are expecting the jdk's bug at
least for now and will observe what happens after upgrading jdk version.

regards,
sic
-- 
View this message in context: http://servicemix.396122.n5.nabble.com/unknown-OutOfMemoryError-tp2801716p2846208.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.