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

Bugs item #868327, was opened at 2003-12-31 10:18
Message generated for change (Comment added) made by biorn_steedom
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: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Simone Bordet (biorn_steedom)
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)


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

>Comment By: Simone Bordet (biorn_steedom)
Date: 2004-01-01 12:16

Message:
Logged In: YES 
user_id=128193

JSR 160 specifies a way to tell the implementation to rebind
instead of doing a bind.
See the JSR 160 documentation about
javax.management.remote.rmi.RMIConnectorServer.JNDI_REBIND_ATTRIBUTE.
I am closing this bug as invalid, since it is sufficient to
add that attibute to the environment map provided to the
connector server to rebind names in JNDI.

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

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