Thanks Arun. I shall look into that.
On Mon, Jul 14, 2008 at 12:43 PM, <glassfish_at_javadesktop.org> wrote:
> Sandhya,
>
> This doesn't answer your question directly, but if you want to see details
> of the message transaction, you can also consider using a stand-alone
> network monitoring tool that runs independently of the app server or client.
> For example, you can use ethereal (also now known as "wireshark"). This
> will allow you to capture the messages passed between client and server and
> then view them, at whatever level of detail you choose. With one of these
> tools, set up a filter to catch just the traffic going to and from the TCP
> port your web server is listening on, catch the traffic, then view it. This
> may or may not meet your needs. It has the advantage of being "passive" -
> that is, it doesn't affect your server configuraiton or performance at all.
> It has the disadvantage of requiring extra set-up and somewhat fiddly
> configuration - these tools are intended for network and protocol engineers
> more than software developers. These tools are more suitable as a test or
> debugging tool than as any kind of production monitoring tool, but they can
> be valuable sometimes.
>
> Just a suggestion.
>
> Duncan
> [Message sent by forum member 'duncant' (duncant)]
>
> http://forums.java.net/jive/thread.jspa?messageID=286475
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
Regards,
Sandhya