You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/07/09 07:57:49 UTC
[jira] [Commented] (AMQ-4588) org.apache.activemq.util.IdGenerator
calls non-configurable new ServerSocket(0);
[ https://issues.apache.org/jira/browse/AMQ-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702958#comment-13702958 ]
Claus Ibsen commented on AMQ-4588:
----------------------------------
Fixed this in Camel as well: CAMEL-6521
> 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