Bug 1178849 - Infinite WARN loop HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select
Summary: Infinite WARN loop HHH000444: Encountered request for locking however dialect...
Keywords:
Status: CLOSED DUPLICATE of bug 1115454
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Marco Rietveld
QA Contact: Jiri Svitak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-05 14:42 UTC by Jiri Svitak
Modified: 2016-09-20 05:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-20 15:35:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jiri Svitak 2015-01-05 14:42:19 UTC
Description of problem:
Infinite WARN loop Unknown Command implemenation with name 'com.bpms.flood.command.SimpleIncrementCallback'

09:06:43,544 WARN  [org.hibernate.loader.Loader] (pool-12-thread-1) HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes
09:06:43,553 WARN  [org.jbpm.executor.impl.AvailableJobsExecutor] (pool-12-thread-1) Unexpected error while processin executor's job Unknown Command implemenation with name 'com.bpms.flood.command.SimpleIncrementCallback': java.lang.IllegalArgumentException: Unknown Command implemenation with name 'com.bpms.flood.command.SimpleIncrementCallback'
	at org.jbpm.executor.impl.ClassCacheManager.findCommandCallback(ClassCacheManager.java:99) [jbpm-executor-6.2.0.CR3-redhat-1.jar:6.2.0.CR3-redhat-1]
	at org.jbpm.executor.impl.ClassCacheManager.buildCommandCallback(ClassCacheManager.java:131) [jbpm-executor-6.2.0.CR3-redhat-1.jar:6.2.0.CR3-redhat-1]
	at org.jbpm.executor.impl.AvailableJobsExecutor.executeJob(AvailableJobsExecutor.java:150) [jbpm-executor-6.2.0.CR3-redhat-1.jar:6.2.0.CR3-redhat-1]
	at org.jbpm.executor.impl.ExecutorRunnable.run(ExecutorRunnable.java:42) [jbpm-executor-6.2.0.CR3-redhat-1.jar:6.2.0.CR3-redhat-1]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [rt.jar:1.7.0_67]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_67]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.7.0_67]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]


Version-Release number of selected component (if applicable):
BPM Suite 6.1.0.ER3

Steps to Reproduce:
1. I have installed bpm suite 6.1.0.ER3 using installer (necessary for correct JMS setup) locally and later deployed it on brmsperf02 performance machine. This involved change to Oracle12c database.
2. I have started the server and the problem appeared. The warning kept throwing.
3. I do not understand why, because I have not cloned anything yet to the business-central. com.bpms.flood.command.SimpleIncrementCallback is a class which is not inside QE bpms-assets.git repository. This class is only in my local private jbossqe-process-flood repository and this repository is not cloned or otherwise used by business central, so I really do not know what is going on.

Actual results:
Infinite WARN loop.

Expected results:
No infinite WARN loop. Business central is independent on other maven projects stored on the same machine.

Additional info:
BPM Suite 6.1.0.ER3 on EAP 6.3.1.GA
Oracle12c database
bpmsperf02 performance lab machine

Comment 1 Jiri Svitak 2015-01-05 16:36:02 UTC
I am sorry, after cleaning the Oracle database and restarting the server, only the following warning is thrown each second:

11:35:15,178 WARN  [org.hibernate.loader.Loader] (pool-12-thread-1) HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes
11:35:18,178 WARN  [org.hibernate.loader.Loader] (pool-12-thread-1) HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes
...

Comment 2 Maciej Swiderski 2015-01-16 15:06:46 UTC
this seems like duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1115454

Comment 3 Marco Rietveld 2015-01-20 15:16:07 UTC
Jiri, would it be okay to close this BZ as a duplicate of 1115454?

Comment 4 Jiri Svitak 2015-01-20 15:35:42 UTC
Maciej, Marco,
yes this is a duplicate. Closing.

*** This bug has been marked as a duplicate of bug 1115454 ***


Note You need to log in before you can comment on or make changes to this bug.