Hi Junior,
Which version are you using? Seems this is similar to
https://wso2.org/jira/browse/ESBJAVA-4392.
Thanks
On Thu, Apr 5, 2018 at 2:33 AM, Júnior wrote:
> Hi,
>
> I am seeing a lot of PassThroughMessageProcessor threads in Waiting state.
>
> Is this normal? Is
Hi Aditya,
I tested your API configuration with a mock backend which returns a simple
JSON payload and I didn't get the mentioned error. Please find the
configurations [2].
[1]
{
"test": "test"
}
[2]
API:
http://ws.apache.org/ns/synapse; name="cacheAPI2"
context="/cache2">
Hi,
I am seeing a lot of PassThroughMessageProcessor threads in Waiting state.
Is this normal? Is there a way to set then to remove stale threads?
Thanks,
--
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Respected Sir/Madam,
If you are able to store any json response into cache. Using any freely
available rest service on net. Please share me the api example.
Thanks and Regards,
Aditya
On Wed, Apr 4, 2018 at 10:22 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:
> Respected
Respected Sir/Madam,
I am using wso2ei 6.1.1 .
The backend service is returning a big json response of about 2000 lines.
If I remove cache mediator both finder and collector from above service. I
am able to receive the backend response in wso2ei api service.
The backend response contains some
Hi All,
I'm working on an "alarm management" test app. The idea is as follows:
- I've an EventStream with following important fields:
-- event_type = type of the event. i.e. threshold_exceeded_event
-- event_source = the entity that is going to be monitored. i.e.
region1.router1.cpu_utilization
Hi,
I also noticed that both the EI nodes are on the same local machine so they
have the same console url defined. ie. https://:443/carbon . Could
that be an issue?
Thanks,
Dhanya
--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
This is similar to this issue[1]. Which version are you using?
[1] https://wso2.org/jira/browse/ESBJAVA-4318
On Wed, Apr 4, 2018 at 5:07 PM, Thishani Lucas wrote:
> Hi Aditya,
>
> Could you please elaborate more about the response sent by the backend?
> What kind of message
Hi Aditya,
Could you please elaborate more about the response sent by the backend?
What kind of message type does it send?
Thanks,
Thishani
On Wed, Apr 4, 2018 at 4:26 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:
> Respected Madam,
>
> Tried adding " action="remove"/>".
>
> But
Respected Madam,
Tried adding "".
But still got the same error. Plus the rest service i am using is not
returning empty response, tested it.
http://ws.apache.org/ns/synapse
">
Hi Adiya,
According to the logs, you are receiving 202 accepted success code, that
means the response cached for the Endpoint might returning an empty body.
Could you please add the following property before cache mediator in order
to return the body from the cache to the Endpoint.
Try
Respected Sir/Madam,
Below is my api :
http://ws.apache.org/ns/synapse
">
Hi,
Thanks for reply.
I know 60 is recommendation.
But, I want to know why that value setting is not working and which class
is closing the connection that keepalive time elapsed.
And why don't close the conmection that keepalive time elapsed.
Thanks.
2018년 4월 4일 (수) 오후 3:55, Dinusha
Hi,
I believe you are doing a tuning in the gateway.
However the default recommendation of the worker_thread_keepalive_sec is 60
sec. Anyhow, this value should be less than the socket timeout value.
You can find more info by following the documentation[1].
[1]
Hi,
I'm using wso2am-2.1.0
I changed worker_thread_keepalive_sec to 30.
But PassThroughMessageProcessor keep connection over that time.
I think that connection is close only if target endpoint close connection.
How can I set the keep-alive timeout?
Thanks.
15 matches
Mail list logo