[jbossts-issues] [JBoss JIRA] Commented: (JBTM-797) orb setup drops exceptions

Misty Stanley-Jones (JIRA) jira-events at lists.jboss.org
Wed Dec 8 20:18:31 EST 2010

    [ https://jira.jboss.org/browse/JBTM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568827#comment-12568827 ] 

Misty Stanley-Jones commented on JBTM-797:

Release Note:

Cause: The ORB did not throw an exception if the specified port was in use.

Consequence: The ORB was left in an unusable state, and the problem was not detectable programmatically, even though a warning was printed to standard output.

Fix: The ORB now throws an exception and tries again to bind to the port.

Result: Developers can detect and deal with failures in ORB setup.

> orb setup drops exceptions
> --------------------------
>                 Key: JBTM-797
>                 URL: https://jira.jboss.org/browse/JBTM-797
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Recovery
>    Affects Versions: 4.13.0
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.14.0
> When the specified orb (actually OA) port is in use the orb setup will fail, leave the orb/oa in an unusable state, print a warning but not be detectable or recoverable programatically. This sucks for the test suite, since it's not uncommon for rec mgr startup to fail due to the O/S not having recycled ports from a previous test process. This situation should be detectable and retryable.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list