[jboss-jira] [JBoss JIRA] Reopened: (JBAS-5852) InvokerLocator Connector no longer available on 3873

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reopened JBAS-5852:
------------------------------------

      Assignee: Brian Stansberry  (was: Andrew Lee Rubinger)


Sorry, this was a flaw in my check-in yesterday. The intent was to implement what we discussed in #ejb3 last week; i.e. to temporarily have an SBM-enabled file come from the AS ejb3 module rather than from the unpacked ejb3-core.jar.  But the SBM-enabled file didn't get included in the check-in.

This reveals a pretty big hole in smoke-tests, since running those showed no issue. :-) JBAS-5854

> InvokerLocator Connector no longer available on 3873
> ----------------------------------------------------
>
>                 Key: JBAS-5852
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5852
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Andrew Lee Rubinger
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: JBossAS-5.0.0.CR2
>
>
> Problem is exhibited in TestSuite:
> org.jboss.test.ejb3.test.SimpleSessionUnitTestCase.testSession
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://127.0.0.1:3873
> Locally, I don't see anything open on 3873 using:
> $> sudo netstat -anp |grep 3873

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira