-
Bug
-
Resolution: Done
-
Major
-
4.6.1.CP13
-
None
If the path to arjuna configuration file contains unicode characters the XMLFilePlugin class fails to read it. XMLFilePlugin then calls DocumentBuilder#parse(String uri) which expects the argument being a valid URI. As long as URI spec does not support unicode chars the filename in XMLFilePlugin needs to be converted to a valid URI without any unicode/special characters.
Note that FileLocator.locateFile performs some conversions over the filename, but these do not seem to be enough.
This bug prevents Arjuna from starting which subsequently prevents EAP from starting.
- blocks
-
JBPAPP-9036 Unicode characters in the installation path prevents the EAP server from starting, especially TransactionManager
- Resolved