IBM Support

JR61515: READ TIMEOUT ERROR OCCURS WHEN YOU DEPLOY ARTIFACTS TO A CPE CONTAINER

Direct link to fix

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In IBM Business Automation Workflow on Cloud, deploying PE
    artifacts to a CPE container fails, resulting with read timeout
    error.
    
    You might see errors in Business Automation Workflow server logs
    similar to this one:
    
    [9/20/19 19:17:00:363 UTC] 000002d4 api E
    com.ibm.casemgmt.intgimpl.messages.CaseMgmtLogger error
    FNRPA0036E The solution cannot be deployed because the following
    Process Engine error occurred during the deployment of the XPDL
    document: java.net.SocketTimeoutException: Read timed out
    com.ibm.casemgmt.intgimpl.deploy.handlers.ContinuableStepExcepti
    on: FNRPA0036E The solution cannot be deployed because the
    following Process Engine error occurred during the deployment of
    the XPDL document: java.net.SocketTimeoutException: Read timed
    out
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.ContinuableStepExcepti
    on.createContinuableStepException(ContinuableStepException.java:
    35)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.pe.GlobalXPDLHandler.c
    heckRetryDeployment(GlobalXPDLHandler.java:255)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.pe.GlobalXPDLHandler.t
    ransferWorkflowCollection(GlobalXPDLHandler.java:205)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.pe.GlobalXPDLHandler.d
    eployWorkflows(GlobalXPDLHandler.java:94)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.RootSolutionHandler.co
    llectAndDeployWorkflowCollections(RootSolutionHandler.java:1145)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.RootSolutionHandler.ac
    cess$900(RootSolutionHandler.java:71)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.RootSolutionHandler$30
    .doStepWork(RootSolutionHandler.java:1000)
    at
    com.ibm.casemgmt.intgimpl.deploy.DeploymentStep.carryOutStep(Dep
    loymentStep.java:79)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.RootSolutionHandler.de
    ploy(RootSolutionHandler.java:1003)
    at
    com.ibm.casemgmt.intgimpl.deploy.SolutionDeployer.deploy(Solutio
    nDeployer.java:224)
    at
    com.ibm.casemgmt.api.admin.DevelopmentSolution$ProcessPendingAct
    ivitiesWorker.process(DevelopmentSolution.java:836)
    at
    com.ibm.casemgmt.api.admin.DevelopmentSolution$BackgroundActivit
    iesProcessor.execute(DevelopmentSolution.java:667)
    at
    com.ibm.casemgmt.intgimpl.BackgroundWorker$2.run(BackgroundWorke
    r.java:116)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:739)
    at javax.security.auth.Subject.doAs(Subject.java:570)
    at
    com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:19
    6)
    at
    com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:15
    3)
    at sun.reflect.GeneratedMethodAccessor314.invoke(Unknown Source)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
    at java.lang.reflect.Method.invoke(Method.java:508)
    at com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:235)
    at com.filenet.api.util.UserContext.doAs(UserContext.java:151)
    at
    com.ibm.casemgmt.intgimpl.BackgroundWorker.run(BackgroundWorker.
    java:113)
    at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    at java.lang.Thread.run(Thread.java:812)
    Caused by: java.net.SocketTimeoutException: Read timed out
    at
    filenet.pe.ejb.client.PEEJBSession.executeRPC(PEEJBSession.java:
    1073)
    at
    filenet.pe.ejb.client.PEEJBSession.transferWorkflowCollection(PE
    EJBSession.java:2218)
    at
    filenet.vw.api.VWSession.transferWFCollection(VWSession.java:315
    6)
    at
    com.ibm.casemgmt.intgimpl.deploy.handlers.pe.GlobalXPDLHandler.t
    ransferWorkflowCollection(GlobalXPDLHandler.java:180)
    ... 23 more
    Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at
    java.net.SocketInputStream.socketRead(SocketInputStream.java:127
    )
    at java.net.SocketInputStream.read(SocketInputStream.java:182)
    at java.net.SocketInputStream.read(SocketInputStream.java:152)
    at
    java.io.BufferedInputStream.fill(BufferedInputStream.java:257)
    at
    java.io.BufferedInputStream.read1(BufferedInputStream.java:297)
    at
    java.io.BufferedInputStream.read(BufferedInputStream.java:356)
    at
    sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:709)
    at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Http
    URLConnection.java:1599)
    at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpU
    RLConnection.java:1504)
    at
    filenet.vw.server.rpc.PostURLDefault.postHttpObjects(PostURLDefa
    ult.java:485)
    at
    filenet.vw.server.rpc.PostURLDefault.postObjects(PostURLDefault.
    java:234)
    at
    filenet.pe.ejb.client.PERPCProxyBase.privateInvokeRPC(PERPCProxy
    Base.java:505)
    at
    filenet.pe.ejb.client.PERPCProxyBase.invokeRPC(PERPCProxyBase.ja
    va:521)
    at
    filenet.pe.ejb.client.PEEJBSession.executeRPC(PEEJBSession.java:
    930)
    ... 26 more
    
    
    PRODUCTS AFFECTED
    IBM Business Automation Workflow
    

Local fix

Problem summary

  • No additional information is available.
    

Problem conclusion

  • A fix that ensures PE artifacts are successfully deployed to the
     CPE container will be included in a future release of Business
    Automation Workflow.
    
    
    PRODUCTS AFFECTED
    IBM Business Automation Workflow
    

Temporary fix

  • Not applicable.
    

Comments

APAR Information

  • APAR number

    JR61515

  • Reported component name

    BPM

  • Reported component ID

    5737A5700

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-26

  • Closed date

    2019-10-15

  • Last modified date

    2025-07-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BPM

  • Fixed component ID

    5737A5700

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SS3PUM","label":"IBM Business Process Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0"}]

Document Information

Modified date:
14 July 2025