tjhannon,
I've changed the title in hopes of catching the attention of some other
people also.
The app client container itself is not directly involved in message
exchanges with remote EJBs. Except for some clean-up work when the VM
exits, the app client container's work is done by the time your client
logic gains control.
One thing you might try is to turn on FINE-level logging in the app
client. In GlassFish v2 the logging control in app clients is rather
coarse so this might generate a lot of output, but it might also offer
some clues about where the time is going.
Make a copy of the sun-acc.xml file that is generated for you in
$domain-directory/config/. Edit the copy to change the log-service
element's 'level' attribute value to FINE. When you launch your app
client add the option
-xml <path-to-edited-sun-acc.xml>
to the appclient command.
Also, have you tried using a network sniffing tool (some people seem to
find wireshark useful) so you know exactly when the return message arrives?
- Tim
glassfish_at_javadesktop.org wrote:
> I am marking the time and logging it before I make the call and after the call returns on the client. I am doing the same when the method is entered and right before the 'return' statement is invoked. The time spent inside the EJB is negligible compared to the time spent for the call on the client. The timestamps in the log indicate the delay is occurring on return.
> [Message sent by forum member 'tjhannon' (tjhannon)]
>
> http://forums.java.net/jive/thread.jspa?messageID=330447
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>