Hi Harm, This sort of an issue cannot be occurring because you are using the backend on the same machine. Any way there was an nhttp transport issue of the same type and we have fixed that for the ESB-2.0 and synapse trunk also has these fixes.
You could try ESB 2.0 and see whether this still exists. Also can you consistently reproduce this on the same machine while it is running perfectly on different machines. Thanks, Ruwan Harm Verhagen wrote: > The problem was most definately in the ESB code. > The ESB got into a state where it didn't handle any messages anymore > (deadlock). > It also didn't handle any other messages for _other_ backends anymore. > Only restarting the ESB worked. > > Meanwhile the backend (running on a separate tomcat) the was still > working. (without any restart). > > *workaround* > whenever I fooled the ESB that the backend was running on a different > machine the ESB ran fine.(it really was still running on the same > machine (but rather then accessing it via 'localhost' rerouting the > traffic really through an other machine, where apache routing the > traffic back) > (so: ESB configuration has an endpoint on http://someotherhost/... > on someother host apache proxies the traffic back to the ESB host.) > > Note: maybe this ticket has nothing to do with the original question > on WSAS/ESB on the same machine. I'm not sure. > > Regards, > Harm > > On Wed, Feb 25, 2009 at 1:31 PM, Ruwan Linton <[email protected] > <mailto:[email protected]>> wrote: > > Hi Harm, > > This shouldn't be due to running on the same machine, but rather > due to > some issue on the back end. Have you tried to running on different > machines to narrow down the problem? > > Thanks, > Ruwan > > Harm Verhagen wrote: > > .. > > I had troubles running ESB and the backend on the same machine > due to > > some lowlevel http bugs. > > https://issues.apache.org/jira/browse/SYNAPSE-452 > > > > maybe its unrelated... > > Maybe this is no issue anymore with ESB >= v2 > > > > Regards, > > Harm > > > > On Wed, Feb 25, 2009 at 1:04 PM, Ruwan Linton <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > Paul Fremantle wrote: > > > Takahiro > > > > > > Have you considered the "co-hosting" option where they > both run > > in the > > > same OSGi JVM? We are going to launch the feature pack > downloads > > in 2 > > > days time. > > > > > Yes, you could actually compose a server with both WSAS and ESB > > capabilities so that you can run a single application > (process) on the > > same directory with both capabilities. > > > > We will be releasing an article on how to do this soon (in > 3-4 hours) > > and you will be able to understand how you can do this. > > > > Thanks, > > Ruwan > > > Paul > > > > > > Takahiro OGAWA wrote: > > > > > >> Hi Asanka and Rajika. > > >> > > >> Asanka Abeysinghe wrote: > > >> > > >>> Hi Takahiro, > > >>> You can refer the wiki page [1] to find detailed > information on > > >>> configuration. > > >>> - Asanka > > >>> > > >>> [1] > > > http://wso2.org/wiki/display/carbon/same+host+as+standalone+servers > > >>> > > >>> > > >> This page is that almost I have needed! > > >> > > >> According to your replies, it seems that > > >> 2) would be the practical solution, I think. > > >> > > >> >> 2)Operate WSAS on same machine but another directory and > > process. > > >> >> > > >> >> In this case, WSAS and ESB are installed into different > > directories. > > >> >> It is possible by changing the ports of management > console, > > axis2 > > >> >> and so on, but carbon-core and axis2 will be doubly > started. > > >> > yes you can change the ports and run WSAS and ESB on the > > same machine. > > >> > Have a look at the transport.xml in WSAS distribution. > > >> > > >> Thank you for your kind and quick replies. > > >> > > >> ---- > > >> Takahiro OGAWA > > >> http://www.brainsellers.com/ > > >> > > >> > > >> > > >> _______________________________________________ > > >> Esb-java-user mailing list > > >> [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > >> > > >> > > > > > > > > > > > > _______________________________________________ > > Esb-java-user mailing list > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Esb-java-user mailing list > > [email protected] <mailto:[email protected]> > > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > _______________________________________________ > Esb-java-user mailing list > [email protected] <mailto:[email protected]> > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-user mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > _______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
