Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9036

Unicode characters in the installation path prevents the EAP server from starting, especially TransactionManager

    Details

    • Steps to Reproduce:
      Hide
      • Install JBoss EAP server on a location where the path contains Unicode character like "/home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/bin" .
      • Try to start JBoss EAP server normally and you will hit the ERROR as shown in JIRA description.
      Show
      Install JBoss EAP server on a location where the path contains Unicode character like "/home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/bin" . Try to start JBoss EAP server normally and you will hit the ERROR as shown in JIRA description.
    • Workaround:
      Workaround Exists
    • Workaround Description:
      • Make sure the JBoss EAP installation path does not contain any Unicode character.
    • Estimated Difficulty:
      Medium
    • Release Notes Text:
      Hide
      In previous versions of JBoss EAP 5, a bug existed that prevented the server from starting if the installation path included Unicode characters. Upon encountering a path that contained a Unicode character, the server would exit with an error similar to the following:

      <screen>2012-05-16 10:59:20,599 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Instantiated: name=TransactionManager state=Described
      java.lang.ExceptionInInitializerError: java.net.MalformedURLException: no protocol: /home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/server/default/conf/jbossts-properties.xml
      </screen>

      The root cause was traced to JBossTS and an upgrade of that component has resolved this issue.
      Show
      In previous versions of JBoss EAP 5, a bug existed that prevented the server from starting if the installation path included Unicode characters. Upon encountering a path that contained a Unicode character, the server would exit with an error similar to the following: <screen>2012-05-16 10:59:20,599 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Instantiated: name=TransactionManager state=Described java.lang.ExceptionInInitializerError: java.net.MalformedURLException: no protocol: /home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/server/default/conf/jbossts-properties.xml </screen> The root cause was traced to JBossTS and an upgrade of that component has resolved this issue.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW
    • Target Release:

      Description

      The installation directory of my JBoss EAP 5.1.2 contains a Unicode character like this "/home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/bin" .
      Due to this JBoss EAP server fails to start and it gives the following ERROR inside server.log .

      2012-05-16 10:59:20,599 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Instantiated: name=TransactionManager state=Described
      java.lang.ExceptionInInitializerError: java.net.MalformedURLException: no protocol: /home/JBossEAP/حج/jboss-eap-5.1.2/jboss-as/server/default/conf/jbossts-properties.xml
      at com.arjuna.ats.arjuna.common.arjPropertyManager.<clinit>(arjPropertyManager.java:70)
      at com.arjuna.ats.jbossatx.jta.TransactionManagerService.<clinit>(TransactionManagerService.java:110)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:149)
      at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106)
      at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80)
      at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:296)
      at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:115)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
      at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
      ..........

      This indicates that it could be the "TransactionManager" which is unable to understand the path with Unicode characters.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  istudens Ivo Studensky
                  Reporter:
                  mhussain Musharraf Hussain
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: