Re: JERI thread names
Geoffrey Arnold <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Thanks Bob and Gregg. Bob, I wasn't aware of the output available from BasicInvocationDispatcher log levels, however even that doesn't get me what I need. My issue is exactly what Gregg mentioned, namely the ability to associate logging for the entire context of a given remote invocation with an IP address, not just the remote method. Geoff. On 10/11/07, Gregg Wonderly <[email protected]> wrote: > Bob Scheifler wrote: > > Geoffrey Arnold wrote: > > > >> It would be useful for logging/debugging purposes if the name of the > >> JERI mux request dispatch thread (@see > >> com.sun.jini.jeri.internal.mux.MuxServer) included some information > >> about the caller (we would specifically be interested in the IP > >> address of the caller). > > > > Could you describe what analysis problems you're trying to aid? > > I take it that the client host logged at FINEST for inbound calls > > by BasicInvocationDispatcher is not sufficient? > > When trying to debug transactions that are hung and other things visible in > stack traces, it nice to be able to see threads named with host addresses or > other direct indicators so that you can assure yourself of which thread is > associated with which activity. > > Gregg Wonderly > > -------------------------------------------------------------------------- > Getting Started: http://www.jini.org/wiki/Category:Getting_Started > Community Web Site: http://jini.org > jini-users Archive: http://archives.java.sun.com/archives/jini-users.html > Unsubscribing: email "signoff JINI-USERS" to [email protected] > -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]