Deploying App in AppWorks Gateway remains in status "is yet to deploy" or pending

I receive the following error message within the logs:

2017-04-24 19:58:41.275 INFO com.opentext.otag.service.agent.ServiceBootstrapListener - Started bootstrapping otsync-connector
2017-04-24 19:58:41.300 INFO com.opentext.otag.service.agent.AppFilter - Initializing OTAG app filter for otsync-connector
2017-04-24 19:58:45.450 INFO org.reflections.Reflections - Reflections took 3512 ms to scan 79 urls, producing 3803 keys and 21161 values
2017-04-24 19:58:45.505 INFO com.opentext.otag.service.agent.AppManagementAgent - Resolved service startup class - com.opentext.otsync.connector.OTSyncConnector
2017-04-24 19:58:45.519 WARN com.opentext.otag.service.agent.AppManagementAgent - !!!!!WARNING!!!!! - potential AppWorks service issue - !!!!!WARNING!!!!!
2017-04-24 19:58:45.519 WARN com.opentext.otag.service.agent.AppManagementAgent - Classes that must be started early can interfere with the host containers startup sequence (usually Servlet technology, ContextListeners, WebListeners, etc...), please implement the AWServiceContextHandler interface if you wish to use the Gateways services safely when your service starts. This interface can be found in the otag-service-development-kit
2017-04-24 19:58:45.520 INFO com.opentext.otag.service.agent.AppManagementAgent - ServletContextListeners:-
2017-04-24 19:58:45.527 WARN com.opentext.otag.service.agent.AppManagementAgent - Found potential problem class com.opentext.otag.service.agent.ServiceBootstrapListener: implements ServletContextListener
2017-04-24 19:58:45.528 WARN com.opentext.otag.service.agent.AppManagementAgent - Found potential problem class org.apache.tomcat.websocket.server.WsContextListener: implements ServletContextListener
2017-04-24 19:58:45.528 WARN com.opentext.otag.service.agent.AppManagementAgent - Found potential problem class org.apache.commons.logging.impl.ServletContextCleaner: implements ServletContextListener
2017-04-24 19:58:45.529 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registering supplied OTAG message handlers
2017-04-24 19:58:45.542 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.OtagMessageHandler com.opentext.otsync.connector.auth.registration.AuthRegistrationHandler
2017-04-24 19:58:45.634 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.OtagMessageHandler com.opentext.otsync.connector.OTSyncConnector
2017-04-24 19:58:45.644 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.OtagMessageHandler com.opentext.otag.sdk.provided.OtagUrlUpdateHandler
2017-04-24 19:58:45.645 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.OtagMessageHandler com.opentext.otsync.connector.auth.trustedprovider.TrustedServerKeyRegistrationHandler
2017-04-24 19:58:45.667 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.OtagMessageHandler com.opentext.otsync.connector.auth.OTSyncAuthHandler
2017-04-24 19:58:45.675 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.AWServiceContextHandler com.opentext.otsync.otag.components.HttpClientService
2017-04-24 19:58:45.676 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.AWServiceContextHandler com.opentext.otsync.connector.auth.registration.AuthRegistrationHandler
2017-04-24 19:58:45.676 WARN com.opentext.otag.service.context.components.AWComponentContext - Context already contains this an instance of this type, class [Lcom.opentext.otag.service.context.components.AWComponent;
2017-04-24 19:58:45.676 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.AWServiceContextHandler com.opentext.otsync.connector.auth.trustedprovider.TrustedServerKeyRegistrationHandler
2017-04-24 19:58:45.677 WARN com.opentext.otag.service.context.components.AWComponentContext - Context already contains this an instance of this type, class [Lcom.opentext.otag.service.context.components.AWComponent;
2017-04-24 19:58:45.677 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.handlers.AWServiceContextHandler com.opentext.otsync.connector.OTSyncConnector
2017-04-24 19:58:45.678 WARN com.opentext.otag.service.context.components.AWComponentContext - Context already contains this an instance of this type, class [Lcom.opentext.otag.service.context.components.AWComponent;
2017-04-24 19:58:45.678 INFO com.opentext.otag.service.agent.AWComponentManager - *** APP-COMPONENT-MANAGER *** Registered interface com.opentext.otag.sdk.connector.EIMConnectorService com.opentext.otsync.connector.OTSyncConnector
2017-04-24 19:58:45.678 WARN com.opentext.otag.service.context.components.AWComponentContext - Context already contains this an instance of this type, class [Lcom.opentext.otag.service.context.components.AWComponent;
2017-04-24 19:58:46.287 INFO com.opentext.otag.service.agent.ServiceBootstrapListener - Container is not ready for service to start, sleeping ...
2017-04-24 19:58:49.165 ERROR com.opentext.otag.sdk.client.v3.AbstractOtagServiceClient - ServiceClient instances cannot be used safely before the host container has been setup and the Gateway has started, please delay client construction until after AWServiceContextHandler#onStart has fired within yourservices @AWServiceStartupComplete method has fired
2017-04-24 19:58:49.167 ERROR com.opentext.otag.service.agent.AppManagementAgent - *** APP-MANAGEMENT-AGENT *** Uncaught exception in app registration thread
java.lang.IllegalStateException: ServiceClient instances cannot be used safely before the host container has been setup and the Gateway has started, please delay client construction until after AWServiceContextHandler#onStart has fired within yourservices @AWServiceStartupComplete method has fired
at com.opentext.otag.sdk.client.v3.AbstractOtagServiceClient.ensureGatewayIsReady(AbstractOtagServiceClient.java:249)
at com.opentext.otag.sdk.client.v3.AbstractOtagServiceClient.(AbstractOtagServiceClient.java:100)
at com.opentext.otag.sdk.client.v3.SettingsClient.(SettingsClient.java:41)
at com.opentext.otag.service.agent.AWComponentManager.registerSettingsHandlers(AWComponentManager.java:94)
at com.opentext.otag.service.agent.AppManagementAgent.lambda$start$1(AppManagementAgent.java:308)
at java.lang.Thread.run(Unknown Source)
2017-04-24 19:58:49.175 ERROR com.opentext.otag.sdk.client.v3.AbstractOtagServiceClient - ServiceClient instances cannot be used safely before the host container has been setup and the Gateway has started, please delay client construction until after AWServiceContextHandler#onStart has fired within yourservices @AWServiceStartupComplete method has fired
2017-04-24 19:58:56.296 INFO com.opentext.otag.service.agent.ServiceBootstrapListener - Container is not ready for service to start, sleeping ...

Comments

  • SDay
    SDay E
    #2 Answer ✓

    Hi

    What App are you deploying into AppWorks 16 ?

    Can you also confirm the otag-listener load stmt is in your server.xml ?

    <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/>
    <!-- Prevent memory leaks due to use of particular java/javax APIs-->
    <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
    <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener"/>
    <Listener className="com.opentext.otag.tomcat.TomcatLifecycleListener"/>
    <!-- Global JNDI resources
    
  • Okay it seemed to have worked out. I have used an old Server file. Thank you!

  • Hi

    You are more than welcome

    Glad you solved the issue

    Simon

  • Hi

    You are more than welcome

    Glad you solved the issue

    Simon