BPM, Workflow, and Case

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

Unfortunately, this setting didn't improve anything. Still, a minute after the start of the import, the 504 gateway timeout occurs. I have the impression that this version of BAW's contains some bug.

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

This seems some underline BAW issue as we are also seeing similar "504 gateway timeout occurs" error. But our scenario is different. We have upgraded and moved on-premise IBM Case Manager to CP4BA 23.0.1 on ARO. When we try to apply audit manifest of case solutions, we do see this error. Something BAW pod is not communicating efficiently and either pod or node where pod is running is losing connection. 

Unfortunately, this setting didn't improve anything. Still, a minute after the start of the import, the 504 gateway timeout occurs. I have the impression that this version of BAW's contains some bug.

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

Unfortunately, this setting didn't improve anything. Still, a minute after the start of the import, the 504 gateway timeout occurs. I have the impression that this version of BAW's contains some bug.

There might be a network component between your browser and the BAW server that interferes. 

You could enable com.ibm.bpmsdk.rest.stp.ServiceWSDLResource=all trace. You should see entry and exiting traces for discoverBusinessObjectList. This way you know how much time the request actually takes. For example, you would see that the exiting trace statements is written after 40 minutes. Then you would need to configure your network component timeouts accordingly.

In the console, when importing methods, I see the call /rest/bpm/wle/pd/v1/createstp/businessObjectList?avoidBasicAuthChallenge=true which ends with error 504 exactly after one minute

<html>
    <title>504 Gateway Timeout</title>
    <body>
        <p>504 Gateway Timeout
    </body>
</html>

When you open the browser console network tab, do you see any kind of response after 60 seconds for the request? Or is it still showing as pending?

In the view where I select the methods I want to import, I click NEXT. The loader appears on the screen and spins steadily for 60 seconds, then stops and nothing happens at all.

Hi @Lukas Davis, the timeout between your browser and the workflow server should be 60 minutes. You can ignore the warning in the log. It just tells you that the thread is running for more than 60 seconds. Which can be fine for long running operations. Do you see any other errors in the log?

What kind of timeout do you observe? Do you get any error in the browser? Maybe you just need to wait for the server to return a response to the browser. We have seen cases where this can take up to 45 minutes. It depends on the size of the WSDL and the number of Business Objects in the process app.

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help. 

HI

IBM BAW, version 23.0.1. New environment. When I try to import a new WSDL, exactly after 60 seconds, I get the timeout and a message in the log:

The elapsed time for the following REST request was 185.48 seconds, which exceeds the warning threshold of 60 seconds: https://xx.xxx.xx.xxx:1025/rest/bpm/wle/pd/v1/createstp/businessObjectList

Does anyone of you know where I can increase this timeout? Please help.