Skip to main content
Kofax

MarkView Application Server - Troubleshooting frameworks deployment issues

  1. Last updated
  2. Save as PDF
11938
Article # 304164 - Page views: 459

Summary

11938

Applies To

  • ERP System: All
  • MarkView Version: All

Behavior

In WebLogic

  • Unable to deploy the Frameworks ear file in WebLogic.
  • BEA-149202 error when deploying the Frameworks ear file.
    <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'frameworks'.>
    [[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.markview.integrations.sap.archivelink.controller.ControllerServlet:92 - Invalid command mapping for Command = adminContRep
  • MarkView Server fails to start up after re-deploying the Frameworks with a status of FAILED_NOT_RESTARTABLE.

In OAS

  • MarkView Servver fails to start up on OAS.
  • Docserver.log reports errors similar to the samples below in OAS.

[OC4J Launcher] ERROR com.markview.frameworks.services.ServiceProxy:48: - Service Locator unable to locate service frameworks.PreferenceService com.markview.frameworks.blogic.PreferenceService [1] javax.naming.NameNotFoundException: markview/frameworks/PreferenceService/1 not found

[OC4J Launcher] ERROR org.springframework.web.context.ContextLoader:215: - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'frameworks.LogLevelInitializerService-impl' defined in class path resource [com/markview/docserver/docserver-remote.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.markview.frameworks.blogic.LogLevelInitializerServiceImpl]: Constructor threw exception; nested exception is com.markview.frameworks.services.ServiceLocatorError: Service Locator unable to locate service: frameworks.PreferenceService com.markview.frameworks.blogic.PreferenceService [1]

In Wildfly

  • Certain Application Deployments like docserver, erp and viewer fails to start with error messages similar to below:

Service Locator unable to locate service frameworks.PreferenceService com.markview.frameworks.blogic.PreferenceService [1] javax.naming.NameNotFoundException: markview/frameworks/PreferenceService/1 not found

Error creating bean with name 'frameworks.LogLevelInitializerService-impl' defined in class path resource [com/markview/docserver/docserver- remote.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.markview.frameworks.blogic.LogLevelInitializerServiceImpl]: Constructor threw exception; nested exception is com.markview.frameworks.services.ServiceLocatorError: Service Locator unable to locate service: frameworks.PreferenceService com.markview.frameworks.blogic.PreferenceService [1]

Known Causes

The installation or upgrade of the MarkView components sometimes alters the deployment order in WebLogic, OAS or Wildfly

Resolution

WebLogic:

The Frameworks object in WebLogic needs to be deployed before all other objects. It is necessary to check the deployment order in WebLogic and confirm that Frameworks deploys first (by having a lower deployment order value). If the issue persists then physically re-start the server.

  1. Check the deployment order in the WebLogic console
    • On Weblogic console -> Deployments should have a deployment order value of 100; except for Frameworks which should have a value of 50
  2. If Frameworks does not have a lower deployment order value than the other deployments, change the order value for Frameworks,
    • Click on Frameworks to review the properties
    • Click on Lock&Edit and enter a new value of 50 and save it
    • Go back to WebLogic console -> Deployments and check the new value is now 50
  3. Re-start the MarkView server from WebLogic.
    • On WebLogic console -> Environment -> Servers -> Control (tab page) -> Shutdown
    • On WebLogic console -> Environment -> Servers - > Control (tab page) -> Start.

OAS:

The Frameworks object in OAS needs to be deployed right after MVASTRS and before all other MarkView objects.

  1. Review $ORACLE_HOME/j2ee/markview/config/default-web-site.xml and $ORACLE_HOME/j2ee/markview/config/server.xml. Order the lines in both files to ensure that Frameworks is deployed just after mvastrs and before all other MarkView components.

    If you have other working environments then consider comparing the files against those in the working environments.

    Following is an example default-web-site.xml indicating the deployment order in OAS.

    • Grey: Components deployed before Frameworks. TRS (mvastrs) should be the last component deployed before Frameworks.

    • Dark Grey: Frameworks followed by the remaining MarkView components.

      <?xml version='1.0'<web-site xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance
      xsi:noNamespaceSchemaLocation='http://xmlns.oracle.com/oracleas/sch...-site-10_0.xsd port='12501' protocol='ajp13' display-name='OC4J 10g (10.1.3) Default Web Site' schema-major-version='10' schema-minor-version='0' >

      <?xml version='1.0'<web-site xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance (http://www.w3.org/2001/XMLSchema-instance)' xsi:noNamespaceSchemaLocation='http://xmlns.oracle.com/oracleas/schema/web-site-10_0.xsd (http://xmlns.oracle.com/oracleas/schema/web-site-10_0.xsd)' port='12501' protocol='ajp13' display-name='OC4J 10g (10.1.3) Default Web Site' schema-major-version='10' schema-minor-version='0' >
<default-web-app application='default' name='defaultWebApp' root='/j2ee' />
< web-app application='system' name='dms' root='/dmsoc4j' />
< web-app application='system' name='JMXSoapAdapter-web' root='/JMXSoapAdapter' />
< web-app application='default' name='jmsrouter_web' load-on- startup='true' root='/jmsrouter' />
< web-app application='javasso' name='javasso-web' root='/jsso' />
< web-app application='ascontrol' name='ascontrol' load-on-startup='true' root='/em' ohs-routing='false' />
<web-app application='datatags' name='webapp' load-on-startup='true' root='/webapp' />
< web-app application='mvastrs' name='mvastrs' load-on-startup='true' root='/mvastrs' />
<web-app application='frameworks' name='frameworks' load-on-startup='true' root='/frameworks' />
< web-app application='frameworks' name='usermgmt' load-on-startup='true' root='/usermgmt' />
< web-app application='mvasbcg' name='mvasbcg' load-on-startup='true' root='/mvasbcg' />
< web-app application='graphics' name='graphics' load-on-startup='true' root='/graphics' />
< web-app application='mvasplsql' name='mvasplsql' load-on-startup='true' root='/markview' />
< web-app application='mvasdtm' name='mvasdtm' load-on- startup='true' root='/mvasdtm' />
< web-app application='filecapture' name='filecapture' load-on-startup='true' root='/filecapture' />
< web-app application='sfasmm' name='sfasmm' load-on-startup='true' root='/sfasmm' />
< web-app application='process' name='process-srvcs-6.7.0' load-on-startup='true' root='/process-srvcs' />
< web-app application='mvas' name='mvas' load-on-startup='true' root='/mvee-viewer' />
< web-app application='mvasvue' name='mvasvue' load-on-startup='true' root='/mvasvue' />
< web-app application='connector' name='connector-srvcs-6.7.0' load-on-startup='true' root='/connector-srvcs' />
< web- app application='erp' name='erp-srvcs-6.8.0' load-on-startup='true' root='/erp-srvcs' />
< web-app application='connector-ap' name='connector-ap-srvcs-6.7.0' load-on-startup='true' root='/connector-ap-srvcs' />
< web-app application='self-service-invoice' name='ssi' load-on-startup='true' root='/ssi' />
< access-log path='../log/default-web-access.log' split='day' />
file:///C:/Kapow_temp/CRMKB/snapshots/11938/index.html 2/4
7/11/2018 < /web-site>

Please also check the Server.xml.

Wildfly:

The Frameworks object in OAS needs to be deployed right after MVASTRS and before all other MarkView deployments.
Review $JBOSS_HOME/standalone/configuration/standalone.xml and at the end of the file, verify to ensure that Frameworks is deployed just after mvastrs and before all other MarkView components.

If you have other working enviornments then consider comparing the standalone.xml file against those in the working environments.

Following is an example snippet from the standalone.xml indicating the deployment order in Wildfly:

<deployments>
<deployment name="mvastrs" runtime-name="mvastrs-ear.ear">
<content sha1="ae693e4830e716f426463d03a30bf8e17f12be76"/>
</deployment>
<deployment name="frameworks" runtime-name="frameworks.ear">
<content sha1="ef8037fb52e2f97e35d146dd0ced5a8b291533be"/> </deployment>
<deployment name="core-apps" runtime-name="core-apps.ear">
<content sha1="1b4b2aaf1d14b2c315420f82c1336e86fcfc5aa3"/>
</deployment>
<deployment name="process" runtime-name="process.ear">
<content sha1="cd2cb38fd6374f06fd147d3a1d52a67dee67507b"/>
</deployment>
<deployment name="viewer" runtime-name="viewer.ear">
<content sha1="7b4ba475313a2572e6a2005e962591ddec0c8cd6"/>
</deployment>
<deployment name="erp-integration-oracle" runtime-name="erp-integration-oracle.ear"> <content sha1="4330ea0dbaa8deabca0b57c49ad266489a7ae8c6"/>
</deployment>
<deployment name="analytics-markview" runtime-name="analytics-markview-ear.ear" enabled="false"> <content sha1="5f2472daa76235720b7ea93d99166b8a0b8fc4cd"/>
</deployment>
<deployment name="analytics-core" runtime-name="analytics-core-ear.ear" enabled="false">
<content sha1="8cce5d98087def798638749287469fcb0e38d50e"/>
</deployment>
<deployment name="self-service-invoice" runtime-name="self-service-invoice-ear.ear"> <content sha1="2f6592bab1d91eabd97148178aa68c782760fe39"/>
</deployment>
<deployment name="analytics-actionable" runtime-name="analytics-actionable-ear.ear" enabled="false">
<content sha1="17d45587911a10d9edc0b8c7aa82d5c0b6264c41"/> </deployment>
</deployments>

Keywords: BEA-149202 , frameworks , deploy , ear, Start up, Start, boot up, bounce