[openjms-developer] [ openjms-Bugs-1955171 ] Issue with Hierarchical topics

[SourceForge.net]

Bugs item #1955171, was opened at 2008-04-30 18:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&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.7-beta-1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: kashabm (kashabm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Issue with Hierarchical topics

Initial Comment:
I am trying to create hierarchical topics and I have the following in the configuration file:

<AdministeredTopic name="Topic1.Topic2" />
<AdministeredTopic name="Topic1.Topic2.Topic3" />

The creation of these topics seems to be fine. However, when "Topic1.Topic2.Topic3" is looked up in the JNDI context as follows, there is an exception thrown:

Topic topic = (Topic) context.lookup( "Topic1.Topic2.Topic3" );

The exception stackTrace is as follows:

javax.naming.NotContextException: Topic1/Topic2
at org.codehaus.spice.jndikit.AbstractLocalContext.lookupSubContext(AbstractLocalContext.java:380)
at org.codehaus.spice.jndikit.AbstractLocalContext.lookup(AbstractLocalContext.java:311)
at org.codehaus.spice.jndikit.rmi.server.RMINamingProviderImpl.lookup(RMINamingProviderImpl.java:158)
at org.exolab.jms.server.net.RemoteNamingProvider.lookup(RemoteNamingProvider.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530)
at org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPool.java:211)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

If "Topic1/Topic2" is not created by having only
<AdministeredTopic name="Topic1.Topic2.Topic3" /> in the config file, everything works fine.

I am not sure if this is an expected behavior but I was expecting to create hierarchical chain of topics and subscribe to specific topics in the chain.

Thanks,

K

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&group_id=54559

[SourceForge.net]

Bugs item #1955171, was opened at 2008-04-30 18:03
Message generated for change (Settings changed) made by kashabm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&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.7-beta-1
Status: Open
Resolution: None

Priority: 7

Private: No
Submitted By: kashabm (kashabm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Issue with Hierarchical topics

Initial Comment:
I am trying to create hierarchical topics and I have the following in the configuration file:

<AdministeredTopic name="Topic1.Topic2" />
<AdministeredTopic name="Topic1.Topic2.Topic3" />

The creation of these topics seems to be fine. However, when "Topic1.Topic2.Topic3" is looked up in the JNDI context as follows, there is an exception thrown:

Topic topic = (Topic) context.lookup( "Topic1.Topic2.Topic3" );

The exception stackTrace is as follows:

javax.naming.NotContextException: Topic1/Topic2
at org.codehaus.spice.jndikit.AbstractLocalContext.lookupSubContext(AbstractLocalContext.java:380)
at org.codehaus.spice.jndikit.AbstractLocalContext.lookup(AbstractLocalContext.java:311)
at org.codehaus.spice.jndikit.rmi.server.RMINamingProviderImpl.lookup(RMINamingProviderImpl.java:158)
at org.exolab.jms.server.net.RemoteNamingProvider.lookup(RemoteNamingProvider.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530)
at org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPool.java:211)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

If "Topic1/Topic2" is not created by having only
<AdministeredTopic name="Topic1.Topic2.Topic3" /> in the config file, everything works fine.

I am not sure if this is an expected behavior but I was expecting to create hierarchical chain of topics and subscribe to specific topics in the chain.

Thanks,

K

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&group_id=54559

[SourceForge.net]

Bugs item #1955171, was opened at 2008-04-30 18:03
Message generated for change (Comment added) made by kashabm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&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.7-beta-1
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: kashabm (kashabm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Issue with Hierarchical topics

Initial Comment:
I am trying to create hierarchical topics and I have the following in the configuration file:

<AdministeredTopic name="Topic1.Topic2" />
<AdministeredTopic name="Topic1.Topic2.Topic3" />

The creation of these topics seems to be fine. However, when "Topic1.Topic2.Topic3" is looked up in the JNDI context as follows, there is an exception thrown:

Topic topic = (Topic) context.lookup( "Topic1.Topic2.Topic3" );

The exception stackTrace is as follows:

javax.naming.NotContextException: Topic1/Topic2
at org.codehaus.spice.jndikit.AbstractLocalContext.lookupSubContext(AbstractLocalContext.java:380)
at org.codehaus.spice.jndikit.AbstractLocalContext.lookup(AbstractLocalContext.java:311)
at org.codehaus.spice.jndikit.rmi.server.RMINamingProviderImpl.lookup(RMINamingProviderImpl.java:158)
at org.exolab.jms.server.net.RemoteNamingProvider.lookup(RemoteNamingProvider.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530)
at org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPool.java:211)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

If "Topic1/Topic2" is not created by having only
<AdministeredTopic name="Topic1.Topic2.Topic3" /> in the config file, everything works fine.

I am not sure if this is an expected behavior but I was expecting to create hierarchical chain of topics and subscribe to specific topics in the chain.

Thanks,

K

----------------------------------------------------------------------

Comment By: kashabm (kashabm)

Date: 2008-04-30 18:10

Message:
Logged In: YES
user_id=1927704
Originator: YES

Correction:

The hierarchical topic is actually looked up as follows

Topic topic = (Topic) context.lookup( "Topic1/Topic2/Topic3" );

However, the hierarchical topic is specified as <AdministeredTopic
name="Topic1.Topic2.Topic3" /> in the config file.

Thanks,

K

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1955171&group_id=54559