[jbossts-issues] [JBoss JIRA] (JBTM-2123) XATMI implementation tests fail to create the orb management function

Amos Feng (JIRA) issues at jboss.org
Wed Mar 12 12:33:10 EDT 2014 

    [ https://issues.jboss.org/browse/JBTM-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952381#comment-12952381 ] 

Amos Feng commented on JBTM-2123:
---------------------------------

It looks like the jboss-as does not start successfully due to some configure errors. see the server.log
{noformat}
JAVA_OPTS already set in environment; overriding default settings with values:  -Xmx256m -XX:MaxPermSize=256m
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el5/blacktie/wildfly-8.0.1.Final-SNAPSHOT

  JAVA: /usr/local/jdk1.7.0_45/bin/java

  JAVA_OPTS:  -server  -Xmx256m -XX:MaxPermSize=256m -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE

=========================================================================

Listening for transport dt_socket at address: 8787
09:04:19,477 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
09:04:20,486 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.1.Final
09:04:21,628 WARN  [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended
09:04:21,703 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: WildFly 8.0.1.Final-SNAPSHOT "WildFly" starting
/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el5/tools/maven/bin/mvn -s tools/maven/conf/settings.xml -Dorson.jar.location=/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el5/ext/ -Dbpa=centos55x32 clean install   -f blacktie/pom.xml -Djbossas.ip.addr=localhost
09:04:23,868 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[401,13]
Message: JBAS014664: An element of this type named 'jms-destinations' has already been declared
	at org.jboss.as.controller.parsing.ParseUtils.duplicateNamedElement(ParseUtils.java:254) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.messaging.MessagingSubsystemParser.processHornetQServer(MessagingSubsystemParser.java:204)
	at org.jboss.as.messaging.Messaging13SubsystemParser.processHornetQServers(Messaging13SubsystemParser.java:212)
	at org.jboss.as.messaging.MessagingSubsystemParser.readElement(MessagingSubsystemParser.java:134)
	at org.jboss.as.messaging.MessagingSubsystemParser.readElement(MessagingSubsystemParser.java:93)
	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1131) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:458) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
	... 3 more

09:04:23,913 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
09:04:24,056 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.0.1.Final-SNAPSHOT "WildFly" stopped in 0ms
{noformat}
                
> XATMI implementation tests fail to create the orb management function
> ---------------------------------------------------------------------
>
>                 Key: JBTM-2123
>                 URL: https://issues.jboss.org/browse/JBTM-2123
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: BlackTie
>            Reporter: Gytis Trikleris
>            Assignee: Amos Feng
>            Priority: Blocker
>             Fix For: 5.0.2
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/462/
> {code}
> org.jboss.narayana.blacktie.jatmibroker.core.conf.ConfigurationException: Could not create the orb management function
> 	at org.jacorb.orb.iiop.ClientIIOPConnection.connect(Unknown Source)
> 	at org.jacorb.orb.giop.GIOPConnection.sendMessage(Unknown Source)
> 	at org.jacorb.orb.giop.GIOPConnection.sendRequest(Unknown Source)
> 	at org.jacorb.orb.giop.ClientConnection.sendRequest(Unknown Source)
> 	at org.jacorb.orb.giop.ClientConnection.sendRequest(Unknown Source)
> 	at org.jacorb.orb.Delegate.invoke_internal(Unknown Source)
> 	at org.jacorb.orb.Delegate.invoke(Unknown Source)
> 	at org.jacorb.orb.Delegate.is_a(Unknown Source)
> 	at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:130)
> 	at org.omg.CosNaming.NamingContextExtHelper.narrow(NamingContextExtHelper.java:73)
> 	at org.jboss.narayana.blacktie.jatmibroker.core.transport.OrbManagement.<init>(OrbManagement.java:76)
> 	at org.jboss.narayana.blacktie.jatmibroker.core.transport.OrbManagement.getInstance(OrbManagement.java:42)
> 	at org.jboss.narayana.blacktie.jatmibroker.core.transport.TransportFactory.<init>(TransportFactory.java:47)
> 	at org.jboss.narayana.blacktie.jatmibroker.xatmi.server.BlackTieServer.<init>(BlackTieServer.java:89)
> 	at org.jboss.narayana.blacktie.jatmibroker.xatmi.server.BlackTieServerTestCase.setUp(BlackTieServerTestCase.java:31)
> {code}
> {code}
> Tests in error: 
>   TestConnection.setUp:29 » Configuration Could not create the orb management fu...
>   TestRollbackOnly.setUp:43 » Configuration Could not create the orb management ...
>   TestRollbackOnly.setUp:43 » Configuration Could not create the orb management ...
>   TestRollbackOnly.setUp:43 » Configuration Could not create the orb management ...
>   TestRollbackOnly.setUp:43 » Configuration Could not create the orb management ...
>   TestRollbackOnly.setUp:43 » Configuration Could not create the orb management ...
>   TestSpecQuickstartOne.setUp:38 » Configuration Could not create the orb manage...
>   TestSpecQuickstartTwo.setUp:33 » Configuration Could not create the orb manage...
>   TestTPACall.setUp:33 » Configuration Could not create the orb management funct...
>   TestTPACall.setUp:33 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPAlloc.setUp:37 » Configuration Could not create the orb management funct...
>   TestTPCall.setUp:36 » Configuration Could not create the orb management functi...
>   TestTPCall.setUp:36 » Configuration Could not create the orb management functi...
>   TestTPCall.setUp:36 » Configuration Could not create the orb management functi...
>   TestTPCall.setUp:36 » Configuration Could not create the orb management functi...
>   TestTPCall.setUp:36 » Configuration Could not create the orb management functi...
>   TestTPCancel.setUp:33 » Configuration Could not create the orb management func...
>   TestTPCancel.setUp:33 » Configuration Could not create the orb management func...
>   TestTPCancel.setUp:33 » Configuration Could not create the orb management func...
>   TestTPConnect.setUp:38 » Configuration Could not create the orb management fun...
>   TestTPConnect.setUp:38 » Configuration Could not create the orb management fun...
>   TestTPConnect.setUp:38 » Configuration Could not create the orb management fun...
>   TestTPConversation.setUp:39 » Configuration Could not create the orb managemen...
>   TestTPConversation.setUp:39 » Configuration Could not create the orb managemen...
>   TestTPDiscon.setUp:34 » Configuration Could not create the orb management func...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPGetRply.setUp:35 » Configuration Could not create the orb management fun...
>   TestTPRecv.setUp:35 » Configuration Could not create the orb management functi...
>   TestTPReturn.setUp:33 » Configuration Could not create the orb management func...
>   TestTPReturn.setUp:33 » Configuration Could not create the orb management func...
>   TestTPReturn.setUp:33 » Configuration Could not create the orb management func...
>   TestTPSend.setUp:35 » Configuration Could not create the orb management functi...
>   TestTPSend.setUp:35 » Configuration Could not create the orb management functi...
>   TestTPSend.setUp:35 » Configuration Could not create the orb management functi...
>   TestTPService.setUp:35 » Configuration Could not create the orb management fun...
>   TestTimeToLive.setUp:33 » Configuration Could not create the orb management fu...
>   TestTopic.setUp:33 » Configuration Could not create the orb management functio...
>   TestTopic.setUp:33 » Configuration Could not create the orb management functio...
>   BlackTieServerTestCase.setUp:31 » Configuration Could not create the orb manag...
>   BlackTieServerTestCase.setUp:31 » Configuration Could not create the orb manag...
>   BlackTieServerTestCase.setUp:31 » Configuration Could not create the orb manag...
>   BlackTieServerTestCase.setUp:31 » Configuration Could not create the orb manag...
>   BlackTieServerTestCase.setUp:31 » Configuration Could not create the orb manag...
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list