John,
I have NO understanding of cocoon at all (have just joined the list), but this rather smells of an interprocess thread deadlock, which I do have experience with (battle scars, once was enough) when using RMI. To proceed I would do a thread dump on both processes (Ctrl-Break on windows, Ctrl-\ or kill -QUIT pid on unix), to find out where where the lock up is (if that is what it really is). I usually do it a couple of dumps a few seconds apart in order to concentrate on the invariant parts of the two dumps. Once you have the dumps, start analysing. Some JVMs give more useful info than others. Sun's JDK/JRE1.4 is pretty useful, 1.3 is not, 1.2 is somewhere between 1.3 and 1.4 in usefulness. The tricky part can be matching the thread on one side making a remote call to the thread on the other side processing the remote call, particularly if there is more than one. If you need more pointers ask, otherwise I hope I have pointed you in the right direction, or helped eliminate one possibility. Bruce > > Hi All, > > Im making some modifications to the DELI library that can be used with > cocoon, but have run into a rather strange problem. When i call one of the > test pages that uses DELI, the request times out UNLESS after a few seconds > i hit ctrl+c to stop tomcat, at which point the DELI stuff gets called, the > profile resolved & a response sent back to a webbrowser... > > I can test the library locally without using either tomcat or cocoon (using > the command line) and it all works find when i do it that way. Not quite > sure where the problem is, or even could be -- is it something to do with > tomcat, or cocoon or...? > > Any suggestions would be appreciated, > (Im using tomcat 4.04, a version of cocoon that came off cvs about a week > before the last release, and win nt4.) > > Thanks, > > JohnG. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
