This content has been marked as final.
Show 2 replies
-
1. Re: Looking up java:/JmsXA through HA-JNDI
adrian.brock May 21, 2007 3:56 AM (in response to sergeypk)"sergeypk" wrote:
What could be the problem?
Let's enumerate them shall we.
1) Asking a user question in a development forum
2) Asking a jndi question in a jms forum
3) Asking an FAQ
All in all it shows you are totally unobservant and have made no attempt to understand
or research the problem.
To really answer your question (since I'm going to be nice for once, but pedantic :-)
1) What you should have noticed is that HAJNDI is a jndi issue
and should therefore be asked in the asked in the JNDI forum
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=62086
Which has a "READ THIS FIRST" in block captials to get your attention,
like the "DONT POST USER QUESTIONS HERE" that you ignored in this forum.
2) That helpful post has a link to the JNDI FAQ
http://www.jboss.org/wiki/Wiki.jsp?page=JBossNSFAQ
3) Which contains a common mistakes section
like trying to lookup java:/ remotely (a clustered lookup via HAJNDI is a remote
lookup - obviously)
http://wiki.jboss.org/wiki/Wiki.jsp?page=WhyDoIGetNameNotFoundException
Hmm maybe the name of that FAQ might be relevant to your problem anyway?
4) Why you want to do a cluster lookup on a pool is beyond me anyway.
It completely negates the point of pooling resources which is why the pool
is only available locally.
5) Any jndi lookup from an ejb should be configured as a resource-ref
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoICreateAResourceRef
6) It is the JMSProvider that defines the JMS connection factory to use for the
resource adapter. The pool is always local, the provider can use whatever
jndi settings you like.
http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJMSProvider
7) I got bored at this point. :-) -
2. Re: Looking up java:/JmsXA through HA-JNDI
sergeypk May 21, 2007 4:23 AM (in response to sergeypk)Dear Mr. Chief Cerberus Scientist,
thank you for your detailed answer. I promise I will only be stupid when you are not looking in the future. :-)