Bug 1012915 - REST POST request to start a process, sent by jbpm remote client, timed out
Summary: REST POST request to start a process, sent by jbpm remote client, timed out
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Marco Rietveld
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 11:25 UTC by Ivo Bek
Modified: 2016-09-20 05:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:11:27 UTC
Type: Bug


Attachments (Terms of Use)
Simple process with human task (7.90 KB, application/xml)
2013-09-27 11:25 UTC, Ivo Bek
no flags Details
Part of server log with NPE and SQL violations (213.25 KB, text/x-log)
2013-09-27 13:10 UTC, Ivo Bek
no flags Details

Description Ivo Bek 2013-09-27 11:25:58 UTC
Created attachment 803917 [details]
Simple process with human task

Description of problem:

Often happens that the start of process times out thought it's a very simple process definition.
I use the following jbpm remote client to perform the operations:

RemoteRuntimeEngineFactory factory = new RemoteRestSessionFactory(deploymentId, url, userId, password);
        
runtimeEngine = factory.newRuntimeEngine();
kieSession = runtimeEngine.getKieSession();
taskService = runtimeEngine.getTaskService();

then to start a process I just run "kieSession.startProcess(processId, parameters);"

More often it happens on the configurations:
windows 2012 server, oracle jdk 6
RHEL6 x86, oracle jdk 6
RHEL6 x86, openjdk 6

the list might not be complete but with these I'm sure that there not any other serious issues which would influence the performance.

Stacktrace:

java.lang.RuntimeException: Unable to post request: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:146)
	at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:166)
	at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:90)
	at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:281)
	at org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:92)
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:61)
	at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)
	at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)
	at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)
	at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:191)
	at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)
	at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:712)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:517)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
	at org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(ApacheHttpClient4Executor.java:182)
	at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:39)
	at org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor.execute(AcceptEncodingGZIPInterceptor.java:40)
	at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:45)
	at org.jboss.resteasy.client.ClientRequest.execute(ClientRequest.java:443)
	at org.jboss.resteasy.client.ClientRequest.httpMethod(ClientRequest.java:677)
	at org.jboss.resteasy.client.ClientRequest.post(ClientRequest.java:566)
	at org.jboss.resteasy.client.ClientRequest.post(ClientRequest.java:571)
	at org.kie.services.client.api.command.AbstractRemoteCommandObject.executeRestCommand(AbstractRemoteCommandObject.java:210)
	at org.kie.services.client.api.command.AbstractRemoteCommandObject.execute(AbstractRemoteCommandObject.java:69)
	at org.drools.core.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:230)
	at org.jboss.qa.bpms.jbpm.integration.client.Client.startProcess(Client.java:179)
	at org.jboss.qa.bpms.jbpm.integration.client.RemoteRuntimeTest.testGetTaskInstanceInfo(RemoteRuntimeTest.java:163)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Marek Baluch 2013-09-27 12:54:31 UTC
More information about the issue will follow. Looks like there's a NPE on the server side.

Comment 2 Ivo Bek 2013-09-27 13:07:44 UTC
I'm not sure but as I checked the server log It might be caused by https://bugzilla.redhat.com/show_bug.cgi?id=1011008

I will attach the server.log.

Comment 3 Ivo Bek 2013-09-27 13:10:34 UTC
Created attachment 803962 [details]
Part of server log with NPE and SQL violations

I only add that I used Oracle 11gR2.

Comment 4 Kris Verlaenen 2013-09-27 14:36:48 UTC
Marco, could you check why the REST service is not returning an error log if an exception is thrown internally?

Comment 5 Marco Rietveld 2013-10-17 22:33:17 UTC
Talked with Ivo and he mentioned that this hasn't been happening any more with the more recent code base. I've also tested on my own and not been able to reproduce this problem.

Comment 6 Kris Verlaenen 2013-10-21 21:14:27 UTC
Setting to MODIFIED instead of CLOSED so it can be verified by QE as well.

Comment 7 Ivo Bek 2013-12-04 08:35:33 UTC
Verified in BPMS 6.0.0.ER5


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