I was just about to suggest something similar. Use JDB or some other utility to get a thread dump from the JVM when it is hung. That should let you know exactly in what class and method the thread hangs.
You could also change your code to catch (and rethrow) Throwable instead of Exception to double-check that the call to ZipOutputStream is not throwing an Error that is secretly caught somewhere without being logged. Regards, Mattias ----- Original Message ----- From: "Esteban Aliverti" <[email protected]> To: "Rules Users List" <[email protected]> Sent: Wednesday, 31 October, 2012 4:46:53 PM Subject: Re: [rules-users] Noob desperately needing help Did you try to debug your code to see exactly where the hung is? zip4j seems to be open source, you could even debug its internals to see where the problem is and maybe you can get a clue of what is going wrong. Best Regards, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Blog @ http://ilesteban.wordpress.com On Wed, Oct 31, 2012 at 4:26 PM, zaphod < [email protected] > wrote: Wolfgang, Here's my dilemma...there is no exception thrown! I wouldn't even be here asking the question if I was getting an OOME...my problem is that the rule hangs, and from that point on, the entire rules engine is hung, even though other processing continues on that jboss node. Note that I'm using zip4j, as the default zip library provided in Java does not support password-protecting the zip file. That is a requirement of this process. And this is new code...it works perfectly outside the rules container, but not at all inside it. What baffles me is the process hanging...I've been writing Java code for 13 years, and I've never seen a process just hang... Paul _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
