IT Process Automation

 View Only
  • 1.  pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 06:03 AM

    Hi,

     

    I am using pam 4.2 version, I wanted to restart my pam service and after I restarted and try to open pam url the service is going down. If I start the service again within fraction of seconds its going down.

    Has anyone faced this issue.



  • 2.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 06:13 AM

    Try to check boot and c2o logs. There should be some information what is going on. Probably PAM cannot log on to SQL or SQL transaction log is full or something similar.



  • 3.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 06:23 AM

    Yes we had db account which was removed for some activity and it was recreated.Now we have that DB account in place,then too I am not able to start it. I tried to reconfigure my db using the document available online. Tried to run pam_domain_windows from Program Files (x86)\CA\PAM\server\c2o\.c2orepository\thirdParty but it say need to run from third party



  • 4.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 06:52 AM

    Try to start pam_domain_windows.bat from installation DVD1



  • 5.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 07:00 AM

    I tired that but it doesn't give me an option for reconfigure. I have option for reinstall , I am sacred if reinstall may affect the old workflow process .can you please suggest is it ok to reinstall pam so workflow process created will not be affected???



  • 6.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 07:50 AM

     

    I don't get configure existing installation as shown in above image. I just have option reinstall



  • 7.  Re: pam 4.2 orchestrator service is not starting up

    Broadcom Employee
    Posted Apr 06, 2016 09:11 AM

    A reinstall does not affect the process definitions or the process instances as they are stored at the database level.  And yes, you must always launch the PAM install from DVD1 and the third party install. 

     

    But I'm concerned that a reinstall may or may not address the issue.  Did you review the c2o.log to see if there were any ERROR messages?  It sounds like you are aware of something changing at the database level that may be the problem, but the logs should tell you that.  This could be as simple as a port that PAM needs is in use.  And if it is something like that, a reinstall will not fix the problem.



  • 8.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 09:31 AM

    Hi,

    Now my c2o log file is also not getting updated. only boot file. But from c20 log I can see below db error

    2016-04-05 14:47:32,728 ERROR [org.hibernate.util.JDBCExceptionReporter] [eportingManager] Unable to get managed connection for RuntimeLibDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS)

    2016-04-05 14:47:32,728 ERROR [com.optinuity.c2o.reporting.ReportingManager] [eportingManager] Failed to propagate data to Reporting database

    org.hibernate.exception.GenericJDBCException: Cannot open connection

    at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)

    at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)

    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)

    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)

    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:424)

    at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)

    at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)

    at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1538)

    at org.hibernate.loader.Loader.doQuery(Loader.java:661)

    at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)

    at org.hibernate.loader.Loader.doList(Loader.java:2211)

    at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2095)

    at org.hibernate.loader.Loader.list(Loader.java:2090)

    at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375)

    at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338)

    at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)

    at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)

    at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)

    at com.optinuity.c2o.reporting.ReportingManager.processQueryStoreData(ReportingManager.java:1250)

    at com.optinuity.c2o.reporting.ReportingManager.startReporterProcess(ReportingManager.java:1006)

    at com.optinuity.c2o.reporting.ReportingManager.access$500(ReportingManager.java:86)

    at com.optinuity.c2o.reporting.ReportingManager$2.run(ReportingManager.java:301)

    Caused by: org.jboss.util.NestedSQLException: Unable to get managed connection for RuntimeLibDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS)

    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)

    at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)

    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:421)

    ... 17 more

    Caused by: javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441)

    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)

    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)

    ... 19 more

    Caused by: org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Login failed for user 'sa_temp'.)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)

    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:622)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)

    ... 23 more

    Caused by: java.sql.SQLException: Login failed for user 'sa_temp'.

    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)

    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)

    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)

    at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:632)

    at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:371)

    at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)

    ... 28 more

    2016-04-05 14:47:32,837 INFO  [com.optinuity.c2o.reporting.ReportingManager] [eportingManager] Statement retrieved and executed in 203 ms; Cleaning reported data from C2OQueryStore....

    2016-04-05 14:47:32,868 WARN  [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] [eportingManager] Throwable while attempting to get a new connection: null

    org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Login failed for user 'sa_temp'.)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)

    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:679)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)

    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)

    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)

    at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)

    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:421)

    at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)

    at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:94)

    at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)

    at org.hibernate.engine.query.NativeSQLQueryPlan.performExecuteUpdate(NativeSQLQueryPlan.java:157)

    at org.hibernate.impl.SessionImpl.executeNativeUpdate(SessionImpl.java:1163)

    at org.hibernate.impl.SQLQueryImpl.executeUpdate(SQLQueryImpl.java:334)

    at com.optinuity.c2o.persistence.RuntimeDatabaseManager.cleanQueryStore(RuntimeDatabaseManager.java:3196)

    at com.optinuity.c2o.reporting.ReportingManager.cleanQueryTable(ReportingManager.java:1215)

    at com.optinuity.c2o.reporting.ReportingManager.startReporterProcess(ReportingManager.java:1009)

    at com.optinuity.c2o.reporting.ReportingManager.access$500(ReportingManager.java:86)

    at com.optinuity.c2o.reporting.ReportingManager$2.run(ReportingManager.java:301)

    Caused by: java.sql.SQLException: Login failed for user 'sa_temp'.

    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)

    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)

    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)

    at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:632)

    at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:371)

    at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)

    ... 22 more

    2016-04-05 14:47:32,868 WARN  [org.hibernate.util.JDBCExceptionReporter] [eportingManager] SQL Error: 0, SQLState: null

    2016-04-05 14:47:32,868 ERROR [org.hibernate.util.JDBCExceptionReporter] [eportingManager] Unable to get managed connection for RuntimeLibDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS)

    2016-04-05 14:47:32,868 ERROR [com.optinuity.c2o.reporting.ReportingManager] [eportingManager] Failed to clear processed data from main database; will do it again later

    org.hibernate.exception.GenericJDBCException: Cannot open connection

    at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)

    at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)

    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)

    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)

    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:424)

    at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)

    at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:94)

    at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)

    at org.hibernate.engine.query.NativeSQLQueryPlan.performExecuteUpdate(NativeSQLQueryPlan.java:157)

    at org.hibernate.impl.SessionImpl.executeNativeUpdate(SessionImpl.java:1163)

    at org.hibernate.impl.SQLQueryImpl.executeUpdate(SQLQueryImpl.java:334)

    at com.optinuity.c2o.persistence.RuntimeDatabaseManager.cleanQueryStore(RuntimeDatabaseManager.java:3196)

    at com.optinuity.c2o.reporting.ReportingManager.cleanQueryTable(ReportingManager.java:1215)

    at com.optinuity.c2o.reporting.ReportingManager.startReporterProcess(ReportingManager.java:1009)

    at com.optinuity.c2o.reporting.ReportingManager.access$500(ReportingManager.java:86)

    at com.optinuity.c2o.reporting.ReportingManager$2.run(ReportingManager.java:301)

    Caused by: org.jboss.util.NestedSQLException: Unable to get managed connection for RuntimeLibDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS)

    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)

    at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)

    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:421)

    ... 11 more

    Caused by: javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441)

    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)

    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)

    ... 13 more

    Caused by: org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Login failed for user 'sa_temp'.)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)

    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)

    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:679)

    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)

    ... 17 more

    Caused by: java.sql.SQLException: Login failed for user 'sa_temp'.

    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)

    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)

    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)

    at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:632)

    at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:371)

    at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)

    ... 22 more

    2016-04-05 14:47:32,946 INFO  [com.optinuity.c2o.reporting.ReportingManager] [eportingManager] C2OQueryStore cleanedup



  • 9.  Re: pam 4.2 orchestrator service is not starting up
    Best Answer

    Broadcom Employee
    Posted Apr 06, 2016 09:42 AM

    Yes, so the connection to the database is, in fact, the issue.  Make sure to use the "test connect" button on the database info screen in the reinstall to confirm you can connect to the database.



  • 10.  Re: pam 4.2 orchestrator service is not starting up

    Posted Apr 06, 2016 10:20 AM

    Hi,

     

    After I reinstall pam and reconfigured the pam db it started working. As Andrew told reinstall will not impact on process created. Care should be taken that we are not creating new db.