Hi Craig, I have followed your advise and attached a debugger. Since this is a remote server the process was painfully slow.
So I did not manage to get to the bottom of it, but in the process I realized that a couple of jars required at runtime were missing. Put them in and that fixed the issue. Thanks for your help. Regards, *Fernando Israel* Managing Director tel: +598(2) 900 0159 cel: +598(99) 275 928 web: www.kognoz.com On Fri, Jul 30, 2010 at 11:24 PM, Craig Ringer <[email protected]>wrote: > On 31/07/10 08:21, Fernando Israel wrote: > > > To give you a bit more information, the code is basically an axis web > > service, that gets called by a client. When it reaches the line above, I > > know it hangs because I have println statements before and after, and > never > > passes that line, and the client behaves as having got a reply -i.e. > > continues its thread, but the server never sends a response back because > it > > hangs on that line (I see that using axis's SOAP monitor). > > > > Any ideas what this might be ?. > > Attach a debugger and get a stack trace showing the state of that thread > and (if it's blocked on a lock) any other threads in the same app. > That'll provide some information about where fop is blocked and why. > > It's easy to debug apps running in Java app servers, and it's whole lot > better than relying on print statements. If you don't know how to > manually connect a debugger, use an IDE like NetBeans or Eclipse that'll > do it for you with enough smarts to just debug your particular app. > > -- > Craig Ringer > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
