Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1248 closed defect (fixed)

Long running job may cause a timeout on session on internal job queue

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: critical Milestone: BASE 2.11
Component: core Version:
Keywords: Cc:

Description

It seems like if a job doesn't do anything for some time that triggers call to SessionControl?. the session is automatically logged out and closed and this results in problems later. Since the session is closed the problems can't be reported back and they are not properly logged either. There are only two indications of the problem:

  • The job is left in "Executing" state. It is not executing and trying to abort it leave it in "Aborting" state.
  • Tomcat's log file contains:
23:13:07,275 ERROR jobqueue:518 - Exception while executing job: Job[id=190; name=M6#80.1]
net.sf.basedb.core.PermissionDeniedException: Permission denied: SessonControl is closed
	at net.sf.basedb.core.SessionControl.updateLastAccess(SessionControl.java:211)
	at net.sf.basedb.core.SessionControl.logout(SessionControl.java:669)
	at net.sf.basedb.core.InternalJobQueue$JobRunner.run(InternalJobQueue.java:507)
	at java.lang.Thread.run(Thread.java:619)

Change History (3)

comment:1 Changed 13 years ago by Nicklas Nordborg

Owner: changed from everyone to Nicklas Nordborg
Status: newassigned

comment:2 Changed 13 years ago by Nicklas Nordborg

Resolution: fixed
Status: assignedclosed

(In [4801]) Fixes #1248: Long running job may cause a timeout on session on internal job queue

comment:3 Changed 13 years ago by Nicklas Nordborg

(In [4819]) References #1248: Long running job may cause a timeout on session on internal job queue

Fixes and old error in the tests that was discovered by the fix to #1248.

Note: See TracTickets for help on using tickets.