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 2012/11/02 09:59:12 UTC

[jira] [Resolved] (AMQ-4153) ActiveMQWASInitialContextFactory issue in transform logic

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

Claus Ibsen resolved AMQ-4153.
------------------------------

    Resolution: Fixed
    
> ActiveMQWASInitialContextFactory issue in transform logic
> ---------------------------------------------------------
>
>                 Key: AMQ-4153
>                 URL: https://issues.apache.org/jira/browse/AMQ-4153
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 5.8.0
>
>
> See nabble
> http://activemq.2283324.n4.nabble.com/Help-configuring-ActiveMQ-as-JMSProvider-in-WebSphere-tp4658603.html
> The code in ActiveMQWASInitialContextFactory is flawed.
> If the WAS has:
> java.naming.queue=jms/systemMessageQueue
> Then the logic assumes there is a .xxx in the key, eg
> java.naming.queue.foo=jms/systemMessageQueue
> But it may not be and then you get a StringIndexOutOfBoundsException

--
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