You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/08/13 15:45:48 UTC
[jira] Created: (AMQ-2869) Starting the broker in a path with a
space fails
Starting the broker in a path with a space fails
------------------------------------------------
Key: AMQ-2869
URL: https://issues.apache.org/activemq/browse/AMQ-2869
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.4.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.4.0
The root of the problem is Jetty issue described here
http://jira.codehaus.org/browse/JETTY-1063
We can workaround the issue, by making sure to escape urls in our classpath
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2869) Starting the broker in a path with a
space fails
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61206#action_61206 ]
Jim Gomes commented on AMQ-2869:
--------------------------------
I'm not an ActiveMQ Java developer, but I can see how the fix put in place will resolve the problem. However, I did a quick code search, and I came across the call to toURL() in the file ClassLoaderSPIConnectionFactory.java (lines 60 and 67). Do these calls also need the toURI() pre-treatment added?
> Starting the broker in a path with a space fails
> ------------------------------------------------
>
> Key: AMQ-2869
> URL: https://issues.apache.org/activemq/browse/AMQ-2869
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
>
> The root of the problem is Jetty issue described here
> http://jira.codehaus.org/browse/JETTY-1063
> We can workaround the issue, by making sure to escape urls in our classpath
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2869) Starting the broker in a path with a
space fails
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61208#action_61208 ]
Dejan Bosanac commented on AMQ-2869:
------------------------------------
Hi Jim,
this class is part ofnthe performance test plugin (which is on its own ready for an update), so it's not part of the distribution and shouldn't affect this issue.
Cheers
> Starting the broker in a path with a space fails
> ------------------------------------------------
>
> Key: AMQ-2869
> URL: https://issues.apache.org/activemq/browse/AMQ-2869
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
>
> The root of the problem is Jetty issue described here
> http://jira.codehaus.org/browse/JETTY-1063
> We can workaround the issue, by making sure to escape urls in our classpath
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2869) Starting the broker in a path with a
space fails
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2869.
--------------------------------
Resolution: Fixed
Fixed with svn revision 985198
> Starting the broker in a path with a space fails
> ------------------------------------------------
>
> Key: AMQ-2869
> URL: https://issues.apache.org/activemq/browse/AMQ-2869
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
>
> The root of the problem is Jetty issue described here
> http://jira.codehaus.org/browse/JETTY-1063
> We can workaround the issue, by making sure to escape urls in our classpath
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.