[ mx4j-Bugs-868327 ] JMXConnectorServer binding names rather than rebinding JNDI

Bugs item #868327, was opened at 2003-12-31 01:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=868327&group_id=47745

Category: JSR 160 Implementation
Group: Release 2.0.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: JMXConnectorServer binding names rather than rebinding JNDI

Initial Comment:
second time running the server causes:
java.io.IOException: 
javax.naming.NameAlreadyBoundException: 
jmx/connector/test [Root exception is 
java.rmi.AlreadyBoundException: jmx/connector/test]
	at 
mx4j.remote.resolver.rmi.RMIResolver.bindServer
(RMIResolver.java:199)
	at 
javax.management.remote.rmi.RMIConnectorServer.start
(RMIConnectorServer.java:147)
	at gigaspaces.mx4j.StockFeedProcessing.<init>
(StockFeedProcessing.java:80)
	at gigaspaces.mx4j.StockFeedProcessing.main
(StockFeedProcessing.java:97)


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=868327&group_id=47745


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click