9:31 a.m.
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 CP1
Reporter: Pavel Macik
Priority: Blocker
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
9:36 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: SOAPProcessor.java.diff
Attached a patch for
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER1/...
that fixes the issue...
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 CP1
Reporter: Pavel Macik
Priority: Blocker
Attachments: SOAPProcessor.java.diff
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
10:36 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Kumar B reassigned JBESB-3470:
-------------------------------------
Assignee: Magesh Kumar B
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 CP1
Reporter: Pavel Macik
Assignee: Magesh Kumar B
Priority: Blocker
Attachments: SOAPProcessor.java.diff
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
11:10 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Kumar B commented on JBESB-3470:
---------------------------------------
Reproduced using webservice_producer QS by setting the following
<jms-listener name="JMS-Gateway" busidref="quickstartGwChannel"
maxThreads="10" is-gateway="true"/>
...
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel" maxThreads="10"/>
and sending 1000 messages from client
for (int i=0;i < 1000; i++)
sender.send(tm);
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 CP1
Reporter: Pavel Macik
Assignee: Magesh Kumar B
Priority: Blocker
Attachments: SOAPProcessor.java.diff
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
2:17 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Kumar B updated JBESB-3470:
----------------------------------
Fix Version/s: 4.9 CP1
Affects Version/s: 4.9
(was: 4.9 CP1)
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
2:23 a.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Kumar B resolved JBESB-3470.
-----------------------------------
Resolution: Done
JBESB_4_9_CP revision: 34918
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
7:08 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik reopened JBESB-3470:
--------------------------------
Magesh,
the SOAPProcessor is still not thread safe even after your patch.
There is following problem:
When second thread tries to lookup the 'java:comp/env' context while the first
thread (which is suppose to create the nonexisting subcontext) is between the lookup call
(that causes the NNFE) and creating the 'env' subcontext of 'java:comp'
context the second thread will again throw the NNFE that is catched and the second new
'env' subcontext is being created. But since the first thread already created the
subcontext, the "javax.naming.NameAlreadyBoundException; remaining name
'env'" (NABE)exception is thrown...
So my suggestion is to catch the NABE on 'enc.createSubContext("env")'
method call and either ignore it or at least log it on WARN/DEBUG level..
Thanks
Pavel
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
6:41 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: SOAPProcessor.java.diff
I believe I have a thread safe solution... see attached SOAPProcessor.java.diff
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff, SOAPProcessor.java.diff
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
6:43 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: (was: SOAPProcessor.java.diff)
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
6:47 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: SOAPProcessor.java.diff
The patch is for http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_9_CP
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
6:47 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: (was: SOAPProcessor.java.diff)
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: Magesh Kumar B
Priority: Blocker
Fix For: 4.9 CP1
Attachments: SOAPProcessor.java.diff
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
6:14 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Keith Babo reassigned JBESB-3470:
---------------------------------
Assignee: Keith Babo (was: Magesh Bojan)
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
Attachments: SOAPProcessor.java.diff
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
6:32 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Keith Babo commented on JBESB-3470:
-----------------------------------
Fix applied with revision 34995.
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
Attachments: SOAPProcessor.java.diff
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
6:32 a.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Keith Babo resolved JBESB-3470.
-------------------------------
Resolution: Done
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
Attachments: SOAPProcessor.java.diff
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
3:07 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik commented on JBESB-3470:
------------------------------------
The attached patch file is not T-S so I'm removing it .
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
Attachments: SOAPProcessor.java.diff
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
3:09 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Pavel Macik updated JBESB-3470:
-------------------------------
Attachment: (was: SOAPProcessor.java.diff)
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
4:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
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
6:49 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner reopened JBESB-3470:
---------------------------------
Assignee: (was: Keith Babo)
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
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
7:50 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3470:
--------------------------------
Attachment: Quickstart_webservice_producer.esb
Quickstart_webservice_producer.war
Deployable quickstart, test using webservice_producer 'ant runtest'
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
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
7:50 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3470:
--------------------------------
Attachment: diffs
Suggested fix
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
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
7:50 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3470:
-------------------------------------
The issue is that the wrong thread context classloader is being initialised for AS5
deployments so the correct 'env' is not being picked up.
I modified the webservice_producer quickstart to create two separate deployments (a war
file and an associated esb file). The war file was also modified to include environment
properties and to have these printed out when the webservice was invoked.
Testing this on AS4 deployments show that it works as expected, without having to modify
the TCCL. On AS5 deployments it is necessary to obtain the JBossWebMetaData to obtain the
ENCLoader irrespective of whether we are using CXF or native.
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
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
10:12 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Bojan reassigned JBESB-3470:
-----------------------------------
Assignee: Magesh Bojan
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
3:18 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3470:
-------------------------------------
Magesh, please wait before doing anything on this. I'm still chasing up the other CXF
issue.
Will reassign back to you once this is done.
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
3:18 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner reassigned JBESB-3470:
-----------------------------------
Assignee: Kevin Conner (was: Magesh Bojan)
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: Kevin Conner
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
8:34 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Kevin Conner reassigned JBESB-3470:
-----------------------------------
Assignee: Magesh Bojan (was: Kevin Conner)
Assigning back to Magesh, still chasing up the other CXF issue.
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
5:57 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Work on JBESB-3470 started by Magesh Bojan.
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
12:48 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Work on JBESB-3470 stopped by Magesh Bojan.
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
12:48 a.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3470) SOAPProcessor isn't thread-safe
[
https://jira.jboss.org/browse/JBESB-3470?page=com.atlassian.jira.plugin.s...
]
Magesh Bojan resolved JBESB-3470.
---------------------------------
Resolution: Done
Committed fix provided by Kevin.
JBESB_4_9_CP revision: 35160
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: Magesh Bojan
Priority: Blocker
Fix For: 4.9 CP1
Attachments: diffs, Quickstart_webservice_producer.esb,
Quickstart_webservice_producer.war
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
4985
days inactive
5006
days old
27 comments
5 participants
participants (5)
-
Keith Babo (JIRA) -
Kevin Conner (JIRA)
-
Magesh Bojan (JIRA)
-
Magesh Kumar B (JIRA)
-
Pavel Macik (JIRA)