activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4588) org.apache.activemq.util.IdGenerator calls non-configurable new ServerSocket(0);
Date Mon, 08 Jul 2013 19:05:48 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-4588.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.9.0

Patch applied with thanks. 
                
> org.apache.activemq.util.IdGenerator calls non-configurable new ServerSocket(0);
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-4588
>                 URL: https://issues.apache.org/jira/browse/AMQ-4588
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.8.0
>            Reporter: Bill DeCoste
>            Priority: Minor
>             Fix For: 5.9.0
>
>         Attachments: AMQ-4588.patch
>
>
> In order to have the AMQ client run on OpenShift the IdGenerator call 'new ServerSocket(0);'
needs to be configurable to be avoided. OpenShift only allows binding to a specific, provided,
unique loopback address and a limited set of ports. Ideally there would be a configuration
option that allows the stub prefix to be set via a JVM param. The current logic doesn't break
OpenShift as the PermissionDenied exception is caught and swallowed but the stack trace is
ugly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message