SourceForge.net
2005-12-02 12:44:48 UTC
Bugs item #1007712, was opened at 2004-08-12 13:22
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1007712&group_id=54559
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: jndi
Group: v0.7.6.1
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: JNDI createSubcontext call fails for tcp connector
Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.user/
2023)
When hibernate tries to bind to OpenJMS's internal JNDI,
it throws this exception. It only happened since I tried
to switch to the TCP
connector.
javax.naming.NamingException: Unknown request
received: createSubContext
at
org.exolab.jms.server.mipc.NameServiceProvider.notify
(NameServiceProvider.java:128)
at org.exolab.core.ipc.Notifier.start
(Notifier.java:150)
at org.exolab.core.ipc.Notifier.access$000
(Notifier.java:79)
at org.exolab.core.ipc.Notifier$1.run
(Notifier.java:120)
at java.lang.Thread.run(Thread.java:536)
----------------------------------------------------------------------
Message:
Logged In: YES
user_id=557161
Fixed in CVS. Fix will be available in 0.7.7-alpha-2
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2004-08-12 13:28
Message:
Logged In: YES
user_id=557161
The problem is in the
org.exolab.jms.jndi.mipc.NameServiceProxy class, which
is passing invalid requests. Its using "createSubContext"
instead of "createSubcontext" and "destroySubContext"
instead of "destroySubcontext".
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1007712&group_id=54559
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1007712&group_id=54559
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: jndi
Group: v0.7.6.1
Status: Closed
Resolution: Fixed
Priority: 5Resolution: Fixed
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: JNDI createSubcontext call fails for tcp connector
Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.user/
2023)
When hibernate tries to bind to OpenJMS's internal JNDI,
it throws this exception. It only happened since I tried
to switch to the TCP
connector.
javax.naming.NamingException: Unknown request
received: createSubContext
at
org.exolab.jms.server.mipc.NameServiceProvider.notify
(NameServiceProvider.java:128)
at org.exolab.core.ipc.Notifier.start
(Notifier.java:150)
at org.exolab.core.ipc.Notifier.access$000
(Notifier.java:79)
at org.exolab.core.ipc.Notifier$1.run
(Notifier.java:120)
at java.lang.Thread.run(Thread.java:536)
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2005-12-02 23:44Message:
Logged In: YES
user_id=557161
Fixed in CVS. Fix will be available in 0.7.7-alpha-2
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2004-08-12 13:28
Message:
Logged In: YES
user_id=557161
The problem is in the
org.exolab.jms.jndi.mipc.NameServiceProxy class, which
is passing invalid requests. Its using "createSubContext"
instead of "createSubcontext" and "destroySubContext"
instead of "destroySubcontext".
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1007712&group_id=54559