Human Tasks Expired during SOA Server Downtime Throw Error during Server Start-Up and Never Expire after Server is Up (Doc ID 962827.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 30-Nov-2011***


Symptoms

If tasks expire during the SOA server's downtime, those tasks error out  during server startup and never expire after the server comes back up.

In case of the tasks that have already expired  ( "negative expiration") you may see below errors the the SOA container log files available in $SOA_HOME/opmn/logs : 

java.io.FileNotFoundException:
http://hostname:port/orabpel/default/RenewalApplication/1.0/ChooseSurrenderOrCustomerVariation/ChooseSurrenderOrCustomerVariation.task at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1147)
at java.net.URL.openStream(URL.java:1007)
at oracle.xml.parser.v2.XMLReader.openURL(XMLReader.java:2551)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:285)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:259)
at oracle.bpel.services.common.util.AbstractJaxbUtil.unmarshal(AbstractJaxbUtil.java:104)
at oracle.bpel.services.common.util.AbstractJaxbUtil.unmarshal(AbstractJaxbUtil.java:87)
at oracle.bpel.services.workflow.metadata.impl.TaskMetadataCache.getTaskDefinition(TaskMetadataCache.java:236)
at oracle.bpel.services.workflow.metadata.impl.TaskMetadataService.getTaskDefinition(TaskMetadataService.java:196)
at oracle.bpel.services.workflow.repos.driver.oracle.OracleWFTask.updateWFTask(OracleWFTask.java:365)
at oracle.bpel.services.workflow.repos.driver.PersistencyService.updateWFTask(PersistencyService.java:463)
at oracle.bpel.services.workflow.task.impl.TaskService.performPostActionOperation
(TaskService.java:3000)
at oracle.bpel.services.workflow.task.impl.TaskService.performPostActionOperation
(TaskService.java:2865)
at oracle.bpel.services.workflow.task.impl.TaskService.expireTask(TaskService.java:2647)
at oracle.bpel.services.workflow.task.impl.TaskService.expireTask(TaskService.java:2616)
at oracle.bpel.services.workflow.task.ejb.tasktimer.TaskTimerBean.expireTask(TaskTimerBean.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

To debug the issue and to get relevant information in the log files, you should Enable Quartz Logging from BPEL Admin Console->Logging->set org.quartz to Debug Mode and also all the BPEL Loggers to Debug mode, re-run the testcase and then check the container log file from SOA_HOME/opmn/logs directory.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms