Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

Post Installation fails when deploying ActiveVOS BPR and URN mapping with "BUILD FAILED D:\infamdm\hub\server\bin\build.xml:93: /.../For additional information see jboss logs Total time: 13 minutes 41 seconds" in MDM
Problem Description
When upgrading from Master Data Management (MDM) 10.1 to MDM 10.2 HotFix 3, post installation fails with the following errors:

BUILD FAILED D:\infamdm\hub\server\bin\build.xml:93: The following error occurred while executing this line: D:\infamdm\hub\server\bin\build.xml:143: ActiveVOS server is not deployed. For additional information see jboss logs Total time: 13 minutes 41 seconds

ActiveVOS database has huge data in the aeprocess and aeb4ptask tables.

The application server logs do not report any hints towards the reason for the issue.


​​
Cause
Solution
Due to huge data in ActiveVOS database, all tables were not getting loaded during ActiveVOS startup.

Also there were table locks during startup.

Customer was using same database for MDM, ActiveVOS and IDQ as well which created resource issue at database end.

Once DQ services were stopped, ActiveVOS got deployed properly.

Recommendation is always to have different database for MDM/ActiveVOS and not to share it with other application if datasize is huge.
More Information
The following thread dump shows messages related to ActiveVOS tables:

DefaultWorkManager-WorkerThread-1" #650 prio=5 os_prio=0 tid=0x000000005bc19800 nid=0xd80 runnable [0x0000000076d1e000]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4838)
- locked <0x00000005d5464118> (a com.microsoft.sqlserver.jdbc.TDSReader)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6150)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:402)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
- locked <0x00000005d548a740> (a java.lang.Object)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:314)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:493)
at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:396)
at org.activebpel.rt.bpel.server.engine.storage.sql.AeAbstractSQLStorage.update(AeAbstractSQLStorage.java:132)
at com.activee.rt.bpel.versioning.storage.sql.AeSQLContributionStorageProvider.deleteStagedContributions(AeSQLContributionStorageProvider.java:354)
at com.activee.rt.bpel.versioning.storage.AeContributionStorage.deleteStagedContributions(AeContributionStorage.java:337)
at com.activee.rt.bpel.versioning.contribution.manager.AePersistentContributionManager.deleteStagedContributions(AePersistentContributionManager.java:298)
- locked <0x00000005d607a3a0> (a com.activee.rt.cluster.multisite.AeMultisiteContributionManager)
at com.activee.rt.cluster.versioning.AeClusteredContributionManager.deleteStagedContributions(AeClusteredContributionManager.java:170)
- locked <0x00000005d607a3a0> (a com.activee.rt.cluster.multisite.AeMultisiteContributionManager)
at com.activee.rt.bpel.versioning.contribution.manager.AePersistentContributionManager.prepareToStart(AePersistentContributionManager.java:128)
at com.activee.rt.cluster.versioning.AeClusteredContributionManager.prepareToStart(AeClusteredContributionManager.java:68)
at org.activebpel.rt.bpel.impl.IAeManagerVisitor$2.visit(IAeManagerVisitor.java:36)
at org.activebpel.rt.bpel.impl.AeManagerAdapter.accept(AeManagerAdapter.java:85)
at org.activebpel.rt.bpel.server.engine.AeBpelEngine.visitManagers(AeBpelEngine.java:1046)
at org.activebpel.rt.bpel.server.engine.AeBpelEngine.prepareManagersToStart(AeBpelEngine.java:228)
at org.activebpel.rt.bpel.server.engine.AeBpelEngine.start(AeBpelEngine.java:303)
at org.activebpel.rt.bpel.server.engine.AeEngineLifecycleWrapper.startBpelEngine(AeEngineLifecycleWrapper.java:241)
at org.activebpel.rt.bpel.server.engine.AeEngineLifecycleWrapper.doStart(AeEngineLifecycleWrapper.java:208)
at org.activebpel.rt.bpel.server.engine.AeEngineLifecycleWrapper$1.run(AeEngineLifecycleWrapper.java:174)
at org.activebpel.work.AeDelegatingWork.run(AeDelegatingWork.java:62)
at org.activebpel.work.AeExceptionReportingWork.run(AeExceptionReportingWork.java:58)
at org.activebpel.work.AeWorkerThread.run(AeWorkerThread.java:156)

   Locked ownable synchronizers:
- <0x00000005d548a848> (a java.util.concurrent.locks.ReentrantLock$FairSync)
Applies To
Product: MDM Multidomain; Active VOS
Problem Type:
User Type:
Project Phase:
Product Version: MDM; ActiveVOS
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:2/11/2019 12:58 AMID:564417
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)