I would also try looking up just "topic" and once I had that namespace, I would
print out the names of all objects in the namespace. Looking at the set of
returned names might give you a clue as to what is going on. For example, you
might find the the URL for JNDI is incorrect ad you have been l
The way to deal with this is to first find a destination lookup that works for
you.
E.g. try looking up one of the example destinations e.g. queue/testQueue that
is shipped with JBM.
Once you have done that and are satisified that lookups do, in general work
(you can also run the examples for
Hi Peter,
I should point out all the configuration works with messaging 1.2 in JBoss
4.0.5.
The client code is stand alone. It call lookup all pre-configured
destination coming with the package of 1.3.
The topicName was passed as an arguement to the method, which was set as a
sta
I guess I should also ask, where is your client running? Within the application
server? If not, I need to see the jndi.properties file because the code that
obtains the initial context is not setting any properties.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
I would be interested to see how topicName is set in your Java code. One thing
that is bugging me is the name not found exception usually lists only the
specific name (e.g., topic or xCacheInvalidationTopic), I do not recall every
seeing a full name (e.g., topic/xCacheInvalidationTopic) in the
Sorry mbean should look like:
|
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=PostOffice
| true
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052296#4052296
Reply to the post :
http://www.jboss.co
Here is what I see in JNDIView:
| +- topic (class: org.jnp.interfaces.NamingContext)
| | +- testDurableTopic (class: org.jboss.jms.destination.JBossTopic)
| | +- TopicWithOwnRedeliveryDelay (class:
org.jboss.jms.destination.JBossTopic)
| | +- xCacheInvalidationTopic (class:
If it is in JNDIView, you should be able to look it up. Please post the excerpt
from the destinations xml file that declares your topic, the code you use to
lookup the topic, and the jndi,properties file you are using (if any).
View the original post :
http://www.jboss.com/index.html?module=bb&
You certainly don't need to restart the server every time you deploy/undeploy a
destination.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052274#4052274
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052274
_
I am using JBoss AS 4.2.0.GA. Yes I started server every time I made change on
any of config files.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052273#4052273
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052273
__
Sorry, my mistake. My topic does show up in JNDI view but cannot find by
jndi.lookup.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052271#4052271
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052271
___
Which version of JBoss are you using? Did you restart the server?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052269#4052269
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052269
_
Thanks Peter, I did look at the Global JNDI Namespace in JNDIView, my topic is
not there. My understanding is that by adding a destination in
destination-service.xml, name service should be able pick it up in JNDI space.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
Have you used the list method of the jboss:service=JNDIView MBean within
jmxconsole (or twiddle) to determine if the the topic was registered as you
expected?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052266#4052266
Reply to the post :
http://www.jboss
14 matches
Mail list logo
