1 Reply Latest reply on Oct 14, 2014 7:16 AM by wdfink

    moving TCP configurations from jboss EAP-4.2 to Jboss EAP-6.1

    swapnil007

      Hi,

       

       

      In my case i am working on one migration project. We are migrating Jboss EAP 4.2 to Jboss EAP 6.1.

       

       

      In one place I got damn confused , the clustering properties of TCP are defined in %JBOSS_HOME%\ server\<server-name> \deploy\jboss-web.deployer\META-INF\jboss-service.xml  of jboss 4.2.

       

       

      I have not found any proper way to migrate it to jboss EAP-6.1.

       

       

      We tried to put this configuration inside our server specific standalone.xml . This change cause below error.

       

       

      Error at log level=======>>>

       

       

      14:47:57,246 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPer

      sistenceException: JBAS014676: Failed to parse configuration

      at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Final-redhat-8.jar:

      7.2.0.Final-redhat-8]

      at org.jboss.as.server.ServerService.boot(ServerService.java:308) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

      at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final

      -redhat-8]

      at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[297,3]

      Message: Unexpected element '{urn:jboss:domain:jgroups:1.1}subsystem'

      at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]

      at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redh

      at-2]

      at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1028) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

       

      at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:449) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-

      8]

      at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:136) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

      at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

      at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]

      at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]

      at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Final-redhat-8.jar:

      7.2.0.Final-redhat-8]

      ... 3 more

       

       

      14:47:57,249 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages

      for details.

       

       

      PFA server specific Standalone.xml file - (refer section = 297-394).

       

      Kindly suggest me where i can configure this change in EAP-6.1 AS. If possible recommend some documents for it.

       

       

      Thanks,

      Swapnil

        • 1. Re: moving TCP configurations from jboss EAP-4.2 to Jboss EAP-6.1
          wdfink

          You should use the jboss-cli script to start the management CLI interface.

          It will give you help via tab-completition and attribute descriptions to set the correct values which might be different from former EAP version.

           

          As you migrate from EAP to EAP I suppose you have a subscription, so you are able to search the knowledgebase for articles how to change JGroups to TCP.

          Also you might open a support ticket.