[esb-issues] [JBoss JIRA] Commented: (JBESB-1433) [Connector] invalid Object Name - InstanceNotFoundException - on server shutdown
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Tue Jun 3 11:19:21 EDT 2008
[ http://jira.jboss.com/jira/browse/JBESB-1433?page=comments#action_12415417 ]
Kevin Conner commented on JBESB-1433:
-------------------------------------
This appears to be a remoting issue and may have been fixed by an update. I have tried to reproduce it on trunk, CP and SOA platform but without success.
> [Connector] invalid Object Name - InstanceNotFoundException - on server shutdown
> --------------------------------------------------------------------------------
>
> Key: JBESB-1433
> URL: http://jira.jboss.com/jira/browse/JBESB-1433
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.2.1
> Environment: SOA Platform 4.2.0 beta 1, RHEL5, Oracle 10g
> Reporter: Martin Vecera
> Assigned To: Tom Cunningham
> Fix For: 4.2.1 CP3
>
> Attachments: server.log
>
>
> The server shows errors like this shutdown:
> 08:10:39,668 ERROR [Connector] invalid Object Name
> javax.management.InstanceNotFoundException: jboss.remoting:service=invoker,transport= socket,host=jawa02.englab.brq.redhat.com,port=4446,dataType=invocation,enableTcpNoDelay=true,marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller,socketTimeout=600000,unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller is not registered.
> Full list is in the attached file.
> Steps to reproduce (100%):
> 1) Start the server.
> 2) After the server is started stop it by Ctrl+C.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list