Hi Fanny,
If you can give YES as the answer for the following questions then it
will work;
1. Are you using the nhttp transport in ESB?
2. Does that nhttp.properties file is in your classpath of the JBOSS
container? (this will differ from the conf directory, just put
them in the classes directory and see)
Thanks,
Ruwan
unmou wrote:
> Hi all,
>
> Thanks Ruwan for solving my problem last time.
> But unluckily I encountered the same problem again :(
> I've tried to change the setting of nhttp.properties.
> But no matter what value I set, It will be timeout after one minute
>
> I 've deployed ESB into jBoss, and I'm thinking will ESB read the same
> nhttp.properties file?
>
> Thanks!!
>
> Fanny
>
>
>
> Ruwan Linton-3 wrote:
>
>> Hi ummou,
>>
>> This is probably due to the connection timeout, you could increase the
>> socket timeout by putting a file named nhttp.properties file into the
>> webapp/WEB-INF/classes/conf folder with the following entry
>>
>> http.socket.timeout=120000
>>
>> you may change the value of the entry (120000) as per the requirement,
>> this sets the timeout to 2 minutes and the default value is 1 minute.
>>
>> Thanks,
>> Ruwan
>>
>> unmou wrote:
>>
>>> Hi all,
>>> me again... sorry for bothering :(
>>>
>>> I'm sending a small request (<1KB) to ESB with a 226KB response
>>> with a single response, it's doing fine.
>>>
>>> But when I send 50 requests at the same time
>>> only that first 4 or 5 responses are correct
>>> All the others went to the fault mediator
>>>
>>> with error message like this:
>>> http://www.nabble.com/file/p18628598/largeResponse_error.txt
>>> largeResponse_error.txt
>>>
>>> from the following extract:
>>> 11:35:09,807 [140.96.178.114-pc178114.ccl.itri.org.tw]
>>> [HttpClientWorker-8]
>>> WARN Fault handler - setting ERROR_MESSAGE : Connection timeout
>>> 11:35:09,813 [140.96.178.114-pc178114.ccl.itri.org.tw]
>>> [HttpClientWorker-8]
>>> WARN Fault handler - setting ERROR_DETAIL : java.lang.Exception:
>>> Connection
>>> timeout at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:172)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:131)
>>> at
>>> org.apache.synapse.transport.nhttp.ClientHandler$1.run(ClientHandler.java:298)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>>> at java.lang.Thread.run(Thread.java:619)
>>> 11:35:09,813 [140.96.178.114-pc178114.ccl.itri.org.tw]
>>> [HttpClientWorker-8]
>>> WARN Fault handler - setting ERROR_EXCEPTION : java.lang.Exception:
>>> Connection timeout
>>>
>>> I think it was probably caused by timeout.
>>>
>>> But I've set it to turned the Never Timeout action on in the Endpoint.
>>>
>>> Should I make any change to the synapse.threads.*** in the
>>> synapse.properties?
>>>
>>> I've tried to do the same thing:
>>> send those 50 requests concurrently to the servlet directly
>>> It works well (although it was slow)
>>>
>>> So, Can I do anything to tune the connection time?
>>>
>>> Thanks again!
>>>
>>> Fanny
>>>
>>>
>>>
>>>
>> _______________________________________________
>> Esb-java-user mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>>
>
>
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
