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

    XMLWordPrintable

Details

    • 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 Exists
      • Make sure the JBoss EAP installation path does not contain any Unicode character.
    • Medium
    • 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.
    • Documented as Resolved Issue
    • NEW

    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.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-1520 XMLFilePlugin fails to read the configuration if its path contains unicode characters

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-11016 Upgrade jbossts to 4.6.1.GA_CP15

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              istudens@redhat.com Ivo Studensky
              rhn-support-mhussain Musharraf Hussain
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: