Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Shipeng Tian (Shipeng_Tian)
MBAFC
Developer
MBAFC
CN
Shipeng_Tian Member since 2014 26 posts
MBAFC
Posted: Feb 18, 2016
Last activity: Feb 22, 2016
Posted: 18 Feb 2016 3:49 EST
Last activity: 22 Feb 2016 20:23 EST
Closed

SQL Problems

Is there somebody know why this happend?

2015-12-19 22:00:11,631 [ce Thread Pool -- 59] [          ] [                    ] [                    ] (      etier.impl.EngineStartup) WARN    - PegaRULES shutdown initiated.

2015-12-19 22:00:11,684 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - Starting RuleUsage snapshot: recent

2015-12-19 22:00:27,714 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - RuleUsage snapshot completed: recent (committed 727 usage instances and 3119 detail instances)

2015-12-19 22:00:27,715 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - Starting RuleUsage snapshot: shutdown

2015-12-19 22:00:33,234 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - RuleUsage snapshot completed: shutdown (committed 727 usage instances and 0 detail instances)

2015-12-19 22:00:33,278 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (   search.internal.RuleIndexer) WARN    - Received request to interrupt indexing.

2015-12-19 22:00:33,284 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (nal.async.AsyncServicesManager) INFO    - Shutting down AsyncServicesManager.

Show More

Is there somebody know why this happend?

2015-12-19 22:00:11,631 [ce Thread Pool -- 59] [          ] [                    ] [                    ] (      etier.impl.EngineStartup) WARN    - PegaRULES shutdown initiated.

2015-12-19 22:00:11,684 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - Starting RuleUsage snapshot: recent

2015-12-19 22:00:27,714 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - RuleUsage snapshot completed: recent (committed 727 usage instances and 3119 detail instances)

2015-12-19 22:00:27,715 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - Starting RuleUsage snapshot: shutdown

2015-12-19 22:00:33,234 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (internal.context.RuleUsageImpl) INFO    - RuleUsage snapshot completed: shutdown (committed 727 usage instances and 0 detail instances)

2015-12-19 22:00:33,278 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (   search.internal.RuleIndexer) WARN    - Received request to interrupt indexing.

2015-12-19 22:00:33,284 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (nal.async.AsyncServicesManager) INFO    - Shutting down AsyncServicesManager.

2015-12-19 22:00:33,284 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (      pega.TRACE.adp_lifecycle) INFO    - Shutting down AsyncServicesManager.

2015-12-19 22:00:33,284 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (al.async.AsyncServicesExecutor) INFO    - Shutting down, declarative load threadpool

2015-12-19 22:00:33,288 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    - Connection to pegarules left at shutdown

2015-12-19 22:00:33,289 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    - Connection to pegadata left at shutdown

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    - Base database information:

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Database name:  pegadata

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Defined by:     JNDI name

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Data source name:       java:comp/env/jdbc/PegaRULES

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Minimum connection count:       0

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Maximum connection count:       unlimited

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Failover database:      none

2015-12-19 22:00:33,293 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Default Schema: GLPD

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    - Base database information:

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Database name:  pegarules

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Defined by:     JNDI name

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Data source name:       java:comp/env/jdbc/PegaRULES

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Minimum connection count:       0

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Maximum connection count:       unlimited

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Failover database:      none

2015-12-19 22:00:33,294 [ce Thread Pool -- 59] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) INFO    -    Default Schema: GLPR

2015-12-19 22:00:33,300 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [     PegaRULES:07.10] (  internal.access.DatabaseImpl) ERROR   - There was a problem with the database when getting a list:

2015-12-19 22:00:33,300 [  PegaRULES-Batch-1] [  STANDARD] [                    ] [    PegaRULES:07.10] (  internal.access.DatabaseImpl) ERROR  - There was a problem with the database when getting a list: com.pega.pegarules.pub.database.ConnectionException: There was a problem processing the results of a database list: code: 0 SQLState: Message: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac From: (BB1BD5B3D73DF93B934807843112A26FA) SQL: select pzPVStream from GLPD.pr_assign where pyAssignmentStatus = ? and (pxUpdateDateTime Caused by SQL Problems. Problem #1, SQLState null, Error code 0: java.sql.SQLException: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:163) at com.pega.pegarules.data.internal.access.PageResultPackager.packageResults(PageResultPackager.java:363) at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6224) at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6022) at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:5985) at com.pegarules.generated.activity.ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.step3_circum0(ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.java:382) at com.pegarules.generated.activity.ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.perform(ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.java:116) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275) at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10265) at com.pegarules.generated.activity.ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.step4_circum0(ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.java:349) at com.pegarules.generated.activity.ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.perform(ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.java:120) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:884) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1192) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:829) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:617) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) at java.lang.Thread.run(Thread.java:745) Caused by: java.sql.SQLException: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.tryLock(BaseWrapperManagedConnection.java:408) at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:147) at org.jboss.jca.adapters.jdbc.WrappedStatement.lock(WrappedStatement.java:114) at org.jboss.jca.adapters.jdbc.WrappedStatement.getResultSet(WrappedStatement.java:727) at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.getResultSetFromStatement(DatabasePreparedStatementImpl.java:1336) at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.getResultSet(DatabasePreparedStatementImpl.java:1348) at com.pega.pegarules.data.internal.access.PageResultPackager.packageResults(PageResultPackager.java:248) ... 20 more

      

2015-12-19 22:00:33,307 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [     PegaRULES:07.10] (ernal.async.BatchRequestorTask) ERROR - Batch activity "Assign-.AgentBulkProcessing" threw:
com.pega.pegarules.pub.PRRuntimeError: There was a problem processing the results of a database list: code: 0 SQLState: <none> Message: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac
at com.pegarules.generated.activity.ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.step3_circum0(ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.java:384)
at com.pegarules.generated.activity.ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.perform(ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.java:116)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10265)
at com.pegarules.generated.activity.ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.step4_circum0(ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.java:349)
at com.pegarules.generated.activity.ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.perform(ra_action_agentbulkprocessing_7fa98f1baeaec24ce7482333b6a97816.java:120)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:884)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1192)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:829)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:617)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.pega.pegarules.pub.database.ConnectionException: There was a problem processing the results of a database list: code: 0 SQLState: <none> Message: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac
From: (BB1BD5B3D73DF93B934807843112A26FA)
SQL: select pzPVStream from GLPD.pr_assign where pyAssignmentStatus = ? and (pxUpdateDateTime <=  ? or pxUpdateDateTime is null) and pxObjClass = ? order by pzInsKey
SQL Inserts: <IN PROCESS> <20151219T175533.277 GMT> <Assign-Schedule-Future>

Caused by SQL Problems. Problem #1, SQLState null, Error code 0: java.sql.SQLException: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:163)
at com.pega.pegarules.data.internal.access.PageResultPackager.packageResults(PageResultPackager.java:363)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6224)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6022)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:5985)
at com.pegarules.generated.activity.ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.step3_circum0(ra_action_cleanupbulkprocessqueue_969a73e625d86cce5a006589f59f57ba.java:382)
... 16 more
Caused by: java.sql.SQLException: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7a104cac
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.tryLock(BaseWrapperManagedConnection.java:408)
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:147)
at org.jboss.jca.adapters.jdbc.WrappedStatement.lock(WrappedStatement.java:114)
at org.jboss.jca.adapters.jdbc.WrappedStatement.getResultSet(WrappedStatement.java:727)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.getResultSetFromStatement(DatabasePreparedStatementImpl.java:1336)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.getResultSet(DatabasePreparedStatementImpl.java:1348)
at com.pega.pegarules.data.internal.access.PageResultPackager.packageResults(PageResultPackager.java:248)
... 20 more

Show Less
To see attachments, please log in.
Data Integration

Posted: 8 years ago
Posted: 18 Feb 2016 7:48 EST
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

Looks like you are shutting down jboss app server through cli command and the server is not shutting down gracefully. If that is the case, this article provides a local solution: https://community.pega.com/support-articles/pega-not-shutting-down-gracefully-jboss

To see attachments, please log in.
Posted: 8 years ago
Posted: 22 Feb 2016 19:29 EST
Abubaker Syed (AbubakerS)
Amazon Corp

Amazon Corp
US

We had exact problem and were able to resolve this based on the response on the SR I raised. BTW we still have issues with custom datasources. How do we add lookup name for custom application datasources?

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice