[esb-issues] [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Tue Sep 7 05:44:52 EDT 2010
[ https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12549357#action_12549357 ]
Kevin Conner commented on JBESB-3470:
-------------------------------------
Something is wrong here, we should not be creating the 'env' subcontext.
> SOAPProcessor isn't thread-safe
> -------------------------------
>
> Key: JBESB-3470
> URL: https://jira.jboss.org/browse/JBESB-3470
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.9
> Reporter: Pavel Macik
> Assignee: Keith Babo
> Priority: Blocker
> Fix For: 4.9 CP1
>
>
> The SOAPProcessor during message processing creates and destroys a subcontext named "env" which is fine when the ESB service is configured as single-threaded. But when the ESB service's action pipeline is configured as multi-threaded (maxThreads > 1) one of the following exceptions will occure:
> javax.naming.NameNotFoundException: env not bound
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
> at org.jnp.server.NamingServer.unbind(NamingServer.java:349)
> at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:871)
> at org.jnp.interfaces.NamingContext.destroySubcontext(NamingContext.java:1193)
> at org.jnp.interfaces.NamingContext.destroySubcontext(NamingContext.java:1185)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:231)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> or
> javax.naming.NameAlreadyBoundException; remaining name 'env'
> at org.jnp.server.NamingServer.createSubcontext(NamingServer.java:619)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1116)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1096)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:229)
> ... 7 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list