Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <10949357.post@talk.nabble.com>
Date: Mon, 4 Jun 2007 06:02:07 -0700 (PDT)
From: QJack <jandrews@pathfire.com>
To: users@activemq.apache.org
Subject: Receiver using jndi.properties, Sender not.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I have a Receiver that is using jndi.properties in the classpath and the
InitialContext is being created with the default contructor. 
InitialContext().  I am also running the broker service.  When I run the
Receiver it appears that it is trying to create its own service instead of
binding to the existing broker.  I think this because I get a JMX connector
"NameAlreadyBoundException".  

I then have a Sender that is creating an InitialContext with the EXACT same
properties as the jndi.properties file using InitialContext(props) and the
jndi.properties is NOT nor should be in it's classpath.  Yet, my receiver
never receives the messages and what's more is that when using JConsole to
monitor my Topics, the receiver's topic never shows.

The JNDI tutorial doesn't mention this.  Also, I've noticed that if I use
the jndi.properties in the classpath for both Receiver and Sender, the same
thing happens, I don't successfully send messages.  

Any clues?

Thanks,

Jeff
-- 
View this message in context: http://www.nabble.com/Receiver-using-jndi.properties%2C-Sender-not.-tf3865081s2354.html#a10949357
Sent from the ActiveMQ - User mailing list archive at Nabble.com.