You could stop and restart your jbase_agent with logging (to a file) and try to find the request(s). This may be needles in haystacks if you have a lot going on. If when you find the culprit you could run a separate jbase_agent in foreground (using a different port) and even potentially debug if you have a version that supports that (and assuming it’s a REST type client app). jbase_agent -d -JD {remaining options….} With the above you can also do remote debugging with -JR Having said that it might not be
-- Sent from my iPhone On Mar 9, 2023, at 9:01 AM, troyd1 <t...@mninter.net> wrote:
-- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to jBASE@googlegroups.com To unsubscribe, send email to jbase-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to jbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jbase/AD3B9B6C-6FEC-4B3B-89B8-68F80402E567%40gmail.com. |
- Hung processes troyd1
- Re: Hung processes Peter Falson
- Re: Hung processes troyd1
- Re: Hung processes Peter Falson