Bug 1192483 - Could not restore timer from ... DeploymentSynchronizerCDInvoker: EOFException: Read past end of file
Summary: Could not restore timer from ... DeploymentSynchronizerCDInvoker: EOFExceptio...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ER6
: 6.1.0
Assignee: Marco Rietveld
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-13 13:49 UTC by Jiri Svitak
Modified: 2020-03-27 20:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:01:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server.log (304.66 KB, text/plain)
2015-02-13 13:49 UTC, Jiri Svitak
no flags Details

Description Jiri Svitak 2015-02-13 13:49:35 UTC
Created attachment 991385 [details]
server.log

Description of problem:
"Could not restore timer from ... DeploymentSynchronizerCDInvoker: EOFException: Read past end of file" errors in server.log on EAP boot and shutdown:

08:31:47,829 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014129: Could not restore timer from /mnt/hudson_workspace/bpms-perf/6.1.x/bpms-6.1.0.ER4/jboss-eap-bpms/node0/data/timer-service-data/business-central.business-central.DeploymentSynchronizerCDInvoker/55eee360-cab3-4360-805e-6ce696e62a9f: java.io.EOFException: Read past end of file
	at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151) [jboss-marshalling-1.4.8.Final-redhat-1.jar:1.4.8.Final-redhat-1]

...

08:31:47,831 ERROR [org.jboss.as.ejb3] (EJB default - 5) JBAS014122: Error during retrying timeout for timer: [id=b4f0566b-311a-4bfa-9f19-8b9e5173f663 timedObjectId=business-central.business-central.DeploymentSynchronizerCDInvoker auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@1270d042 initialExpiration=Fri Jan 23 00:00:00 EST 2015 intervalDuration(in milli sec)=0 nextExpiration=Tue Jan 27 02:54:42 EST 2015 timerState=RETRY_TIMEOUT info=null]: java.lang.NullPointerException
	at org.jboss.as.ejb3.timerservice.TimerServiceImpl.setRollbackOnly(TimerServiceImpl.java:1031) [jboss-as-ejb3-7.4.2.Final-redhat-2.jar:7.4.2.Final-redhat-2]

See the attached full server.log.



Version-Release number of selected component (if applicable):
BPM Suite 6.1.0.ER4
EAP 6.3.2.GA
Oracle12c
brmsperf02 machine
PPI strategy

Steps to Reproduce:
1. Setup BPM Suite 6.1.0.ER4 on EAP 6.3.2.
2. Clone there git://git.app.eng.bos.redhat.com/bpms-assets.git repo.
3. Build&deploy bpms-perf project.
4. Start some instances of Timer process definition (Start->Timer(1s)->End). You can use http://git.app.eng.bos.redhat.com/git/jbossqe-process-flood.git/
and run
mvn clean package exec:exec -Dscenario=Timer_kieREST ...
5. Restart the server.

Actual results:
Could not restore timer from ... DeploymentSynchronizerCDInvoker: EOFException: Read past end of file

Expected results:
Server logs are free of such errors.

Comment 1 Maciej Swiderski 2015-02-13 18:33:30 UTC
fixed by disabling persistence of ejb timers as that is not needed as each server node initializes timer routine for deployment synchronization individually and always on application startup

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/6a9a2ae694bc1e7804ece1ca896b4f3f53d37767

6.2.x:
https://github.com/droolsjbpm/jbpm/commit/0528cfe29c0f9cfe5ab03416becd4a52023ea579

Comment 2 Jiri Svitak 2015-03-06 14:07:37 UTC
Verified in BPM Suite 6.1.0.ER6 on EAP 6.4.0.ER3.

Covered by regular checking of server logs after performance testing.


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