Bug 893362
Summary: | EBWS enabled service cannot be deployed when space is present in server directory name (NPE) | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
Component: | JBossESB, JBossWS | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.3.0 GA | CC: | soa-p-jira |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
If the JBoss Enterprise SOA Platform is installed into a directory which has a space in its name then the ESB archive cannot be deployed as a null-pointer exception is thrown. To work around this issue, add "-Dorg.jboss.net.protocol.file.useURI=false" to your start-up script.
|
Story Points: | --- |
Clone Of: | Environment: |
SOA-P 5.3.1 ER3 with JBossWS Native
|
|
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jiri Pechanec
2013-01-09 08:19:16 UTC
This is JBPAPP-10417 and can be worked around by adding "-Dorg.jboss.net.protocol.file.useURI=false" to the startup scripts. I believe we will have to move forward with this enabled in our startup scripts. I can confirm that with the given sysproperty the issue disappears |