[jboss-jira] [JBoss JIRA] Commented: (JBAS-5345) New instance of resources injected on every onMessage MDB call
Dok Tora (JIRA)
jira-events at lists.jboss.org
Mon Mar 31 10:11:40 EDT 2008
[ http://jira.jboss.com/jira/browse/JBAS-5345?page=comments#action_12405902 ]
Dok Tora commented on JBAS-5345:
--------------------------------
Running the script below will cause an OutOfMemoryError after about 350-400 calls (on my setup):
-----------
URL="http://<IPADDRESS>:8080/EJB3Trail/serviceobjects/injection/calculator.jsp?action=send&start=25&end=65&growthrate=0.08&saving=300&submit=Calculate"
out=/dev/null
content=/dev/null
i=0
while [ $i -ne 1000 ]; do
i=`echo "1 + $i" | bc -q`
echo $i
wget $URL --output-file $out --output-document $content
sleep 1
done
---------------
The error:
Can't create thread: 5
13:56:32,687 ERROR [JmsServerSession] Unable to schedule work
javax.resource.spi.work.WorkRejectedException: org.jboss.util.threadpool.ThreadPoolFullException: java.lang.OutOfMemoryError: unable to create new native thread
at org.jboss.resource.work.WorkWrapper.rejected(WorkWrapper.java:250)
at org.jboss.util.threadpool.BasicTaskWrapper.taskRejected(BasicTaskWrapper.java:345)
at org.jboss.util.threadpool.BasicTaskWrapper.rejectTask(BasicTaskWrapper.java:164)
at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417)
at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)
at org.jboss.resource.work.JBossWorkManager.executeWork(JBossWorkManager.java:205)
at org.jboss.resource.work.JBossWorkManager.scheduleWork(JBossWorkManager.java:144)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.start(JmsServerSession.java:212)
at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:330)
at java.lang.Thread.run(Thread.java:613)
Caused by: org.jboss.util.threadpool.ThreadPoolFullException: java.lang.OutOfMemoryError: unable to create new native thread
... 7 more
Can't create thread: 5
13:56:32,690 WARN [Connection] Connection failure:
javax.jms.JMSException: Unable to schedule work: javax.resource.spi.work.WorkRejectedException: org.jboss.util.threadpool.ThreadPoolFullException: java.lang.OutOfMemoryError: unable to create new native thread
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.start(JmsServerSession.java:217)
at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:330)
at java.lang.Thread.run(Thread.java:613)
13:56:32,690 WARN [Connection] Unable to start exception listener thread:
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:592)
at org.jboss.mq.Connection.asynchFailure(Connection.java:435)
at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:359)
at java.lang.Thread.run(Thread.java:613)
Can't create thread: 5
13:58:33,714 ERROR [STDERR] org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.lang.OutOfMemoryError: unable to create new native thread)
> New instance of resources injected on every onMessage MDB call
> --------------------------------------------------------------
>
> Key: JBAS-5345
> URL: http://jira.jboss.com/jira/browse/JBAS-5345
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB3
> Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.0.5.GA
> Environment: Java version: 1.5.0_13,Apple Computer, Inc.
> OS-System: Mac OS X 10.4.11,i386
> also
> Java version: 1.5.0_07,Sun Microsystems Inc.
> Java VM: Java HotSpot(TM) Server VM 1.5.0_07-b03,Sun Microsystems Inc.
> OS-System: Windows 2003 5.2,x86
> Reporter: Dok Tora
> Assigned To: Carlo de Wolf
> Attachments: CalculatorMDB.java, EJB3Trail.ear, EJB3Trail.ear, RecordManagerBean.java
>
>
> A new instance of an injected bean is created every time the onMessage() method of an MDB is called.
> Details with sample code modifications to EJBTrailBlazer for reproduction can be found here:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132331
> Problem was replicated in 4.0.5.GA, 4.2.1 and 4.2.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list