Hi Eric,
See my comments in-line,
Hubert, Eric wrote:
Hello Ruwan,
this sounds like a good idea for moving forward. I've seen your comments
on this in https://issues.apache.org/jira/browse/SYNAPSE-259 and will
closely follow your activities.
Cool. I am planing to finish up the issue with large messages today and
commit the code to synapse today itself, so that I can give you an
another build which will fix the large message handling.
Ruwan, do you have any ideas about the third issue I encountered (the
internal server error 500 and blocking behaviour after an Hessian error
occurs on the server side)? Unfortunately I could not isolate this
problem and send you a small test case to reproduce this. Do I need to
spend more time on this? Was the thread dump of help?
Well, to be frank, I haven't looked at this in detail yet. Once the
other issues are resolved, I will work on resolving this issue as well.
This type of error worries me most. For me it is a worst case scenario
if a single error is able to stop a whole esb instance from processing
requests.
Don't worry Eric, I don't think its serious, I will have a look at it
and let you know soon.
If you find the root cause of this problem, could you please point me to
the relevant source fix!
Will do for sure.
Thanks,
Ruwan
Regards,
Eric
Hi Eric,
Thanks for all the information and this will help me a lot to proceed.
We haven't committed the code yet, (was planing to commit it just
after
your tests) Any way it seems like we are a little late to get this in
to
axis2 1.4 on which synapse 1.2 (next release) is going to depend on,
so
I would like this to be go in to the synapse repo and we can
contribute
this code to axis2 later once it is stabilized.
I will ask Tharindu (The person who did the initial work) to submit a
patch to the synapse dev, so that we can keep on improving the hessian
formatter and builder pair.
Thanks,
Ruwan
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
