[
https://issues.apache.org/jira/browse/SM-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009142#comment-13009142
]
Torsten Mielke commented on SM-1206:
------------------------------------
I have seen pretty much the same error when deploying that war into WebSphere
6.1.
Trying to add any SMX shared libraries afterwards (via JMX) results in
{code}
Caused by: javax.naming.NameNotFoundException: Name comp/env/jms not found in
context "java:".
{code}
In addition Websphere spits out the following explanation:
{code}
A JNDI operation on a "java:" name cannot be completed because the server
runtime is not able to
associate the operation's thread with any J2EE application component. This
condition can occur
when the JNDI client using the "java:" name is not executed on the thread of a
server application
request. Make sure that a J2EE application does not execute JNDI operations on
"java:" names within
static code blocks or in threads created by that J2EE application. Such code
does not necessarily run
on the thread of a server application request and therefore is not supported by
JNDI operations on
"java:" names"
{code}
Also, there is some discussion of this error in
http://jlorenzen.blogspot.com/2010/04/possible-solution-for-websphere-issue.html.
>From what I understand the local JNDI namespace java:comp/env is not available
>to any J2EE non-container managed threads.
> ClientFactory JNDI bind fails in non-standalone ServiceMix installs
> -------------------------------------------------------------------
>
> Key: SM-1206
> URL: https://issues.apache.org/jira/browse/SM-1206
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.1, 3.3
> Reporter: Chris Custine
> Assignee: Chris Custine
>
> ClientFactory tries to bind to java:comp/env/jbi/ClientFactory by default and
> this only appears to work when run as a standalone server. The java:comp/env
> naming context is read only according to the JEE spec so the ClientFactory
> can never bind to JNDI when deployed with JBoss deployer, WAR file, etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
