DAMLink Add on installation Issue

Hi Experts,

After I install DAMLink on the OTMM server as mentioned in guide and when I start the OTMM services OTMM service won't start. Please assist, I am doing Hybris Integration for the first time. It'll be great help if anyone can assist me.

The Error I am facing in appserver log is:

"TearDown/HornetQActivation 2016-10-17 13:28:16,663 | TRACE | session= | user= | org.hornetq.core.server | Connection removed 5cc098aa-9427-11e6-987b-27211a54fdd1 from server HornetQServerImpl::serverUUID=6228e17f-9023-11e6-b1d9-233dfeb8dc21: java.lang.Exception: trace
   at org.hornetq.core.remoting.server.impl.RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:565)
   at org.hornetq.core.remoting.impl.invm.InVMAcceptor$Listener.connectionDestroyed(InVMAcceptor.java:278)
   at org.hornetq.core.remoting.impl.invm.InVMConnection.close(InVMConnection.java:118)
   at org.hornetq.core.remoting.impl.invm.InVMAcceptor.disconnect(InVMAcceptor.java:231)
   at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener.connectionDestroyed(InVMConnector.java:207)
   at org.hornetq.core.remoting.impl.invm.InVMConnection.close(InVMConnection.java:118)
   at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.internalClose(RemotingConnectionImpl.java:586)
   at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.destroy(RemotingConnectionImpl.java:373)
   at org.hornetq.core.client.impl.ClientSessionFactoryImpl.checkCloseConnection(ClientSessionFactoryImpl.java:1211)
   at org.hornetq.core.client.impl.ClientSessionFactoryImpl.closeCleanSessions(ClientSessionFactoryImpl.java:553)
   at org.hornetq.core.client.impl.ClientSessionFactoryImpl.interruptConnectAndCloseAllSessions(ClientSessionFactoryImpl.java:522)
   at org.hornetq.core.client.impl.ClientSessionFactoryImpl.close(ClientSessionFactoryImpl.java:562)
   at org.hornetq.ra.inflow.HornetQMessageHandler.teardown(HornetQMessageHandler.java:285)
   at org.hornetq.ra.inflow.HornetQActivation$1.run(HornetQActivation.java:440)"

Thanks,

Hillin

Find more posts tagged with

Comments

Xaver_Fischer

Hi Hillin,

can you provide more info?

The log section you provided is only logged as TRACE and it seems to happen when the system tries to tearDown the message handler. There must be also some earlier ERROR logs in mediamanager-appserver.log file that indicate the reason, why the service is not starting anymore.

Best regards,

Xaver

Quoted Hillin Glittus on 10/17/2016 12:25 PM:

Hi Experts,

The Error I am facing in appserver log is:

Thanks,

Hillin

Hillin_Glittus

Thanks Xaver,

I am attaching the mediamanager app server log(It is of 13MB so I have zipped it). Please do let me know what is causing the service not to start.

It'll be a great help me.

Really appreciate,

Thanks,

VIshwas

Xaver_Fischer

Hi,

it looks like there is an issue in otmm.xml to be found e.g. in $JBOSS_HOME/standalone/configuration.

There is a section <system-properties> with the definition of the SESSION_ID_ALPHABET property like:

<property xmlns="urn:jboss:domain:1.7" name="org.apache.catalina.session.ManagerBase.SESSION_ID_ALPHABET" value="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz012345678901"/>

The issue is the version 1.7 of the domain namespace: xmlns="urn:jboss:domain:1.7"

Can you please adjust the version to 3.0 or whatever is defined at the beginning of the xml file and try to start the service again?

Best regards,

Xaver

Hillin_Glittus

Hi Xavier,

Thanks for replying,

I cannot find the entire line what you have quoted above in the wildfly_home/standalone/configurationotmm.xml file. PLease let me kow if this line is available anywhere else?

Oe what else may be the issue. Please assist

Thanks a lot,

Vishwas

Xaver_Fischer

Hi Vishwas,

is there any other occurrance of urn:jboss:domain:1.7 in otmm.xml?

That's the FATAL error from mediamanager-appserver.log:

\OTMM-Pre-Reqs\wildfly-9.0.2.Final\modules,D:\OTMM-Pre-Reqs\wildfly-9.0.2.Final\modules\system\layers\base,D:\OTMM-Pre-Reqs\MediaManager,D:\OTMM-Pre-Reqs\MediaManager))Controller Boot Thread 2016-10-18 10:31:17,120 | ERROR | session=       | user=           | org.jboss.as.server | WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) at org.jboss.as.server.ServerService.boot(ServerService.java:350) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) at java.lang.Thread.run(Thread.java:745)Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[40,1]Message: WFLYCTL0198: Unexpected element '{urn:jboss:domain:1.7}property' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:89) at org.jboss.as.controller.parsing.ParseUtils.requireNamespace(ParseUtils.java:258) at org.jboss.as.server.parsing.CommonXml.parseSystemProperties(CommonXml.java:375) at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:438) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:144) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:106) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 3 moreController Boot Thread 2016-10-18 10:31:17,120 | FATAL | session=       | user=           | org.jboss.as.server | WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Best regards,
Xaver

Hillin_Glittus

Hi Xaver,

No I cannot see any occurance of urn:jboss:domain:1.7 in otmm.xml file.

Shall i send you the otmm.xml file?

Thanks,

Vishwas

Xaver_Fischer

In case other people run into the same issue, here a summary and solution:

Eventually it was the xmlns="urn:jboss:domain:1.7" namespace attribute in the otmm.xml ($JBOSS_HOME/standalone/configuration). See also earlier reply in this thread.

The "ant install" of DAMLink OTMM Addon creates this entry within the <system-properties> section under some circumstances on a Wildfly deployment of OTMM 16 with DAMLink OTMM Addon version 16.

Changing the version number from 1.7 to 3.0 in otmm.xml solves the issue: xmlns="urn:jboss:domain:3.0"

Best regards,

Xaver