[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod closed JBREM-82:
---------------------------
Resolution: Done
Fix Version: 1.2.0 beta
Have updated the ObjectName generated for the server invoker to be unique to
the locator uri so that if a new server invoker is created by the
InvokerRegistry, then that invoker will be registered with the MBeanServer. If
InvokerRegistry does not create a new server invoker, but returns an existing
one because the locator uri was the same, then it will not re-register that
invoker with the MBeanServer.
> Bad warning in Connector.
> -------------------------
>
> Key: JBREM-82
> URL: http://jira.jboss.com/jira/browse/JBREM-82
> Project: JBoss Remoting
> Type: Bug
> Components: transport
> Versions: 1.2.0 beta
> Environment: In Jboss Head (CVS)
> Reporter: rimmeraj
> Assignee: Tom Elrod
> Priority: Minor
> Fix For: 1.2.0 beta
>
>
> JBoss head:
> remoting/src/main/org/jboss/remoting/transport/Connector.java , start method
> after you create the server invoker you try to register it with the mbean
> server. If it fails you register a warning. When you are using the ejb3
> deployers it registers its own socket Connector. It is quite legal to have
> the standard Connector in conf/jboss-service.xml registers a socket
> protocol. The EJB3 deployer registers a socket listener on a different port.
> This triggers an annoying warning that in my option is more of a programming
> error that a valid warning.
>
> Warning.
> Error registering invoker [EMAIL PROTECTED] with MBeanServer.
> javax.management.InstanceAlreadyExistsException:
> jboss.remoting:service=invoker,transport=socket already registered.
> Suggested Fix.
> 1. org/jboss/remoting/transport/InvokerRegistry.java, createServerInvoker
> should log a warning if the InvokerLocator is already found.
> 2. Connector.java, start should check to see if the object name is not
> registered before trying. Something like
> ObjectName name=new ObjectName(invoker.getMBeanObjectName());
> try
> {
> server.getInstance(name);
> }
> catch(InstanceNotFoundException e)
> {
> server.registerMBean(invoker, name);
> invoker.setMBeanServer(server);
> }
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
