You can use the IIOP log property of EAServer to trace IIOP session activity by setting com.sybase.jaguar.server.iiop.log to true and restarting the server. All IIOP traffic between all clients and the server is written to the server log.
The log may be helpful in diagnosing these problems:
Client application issues, such as login failures
Component issues, including:
Method invocation errors
Result sets not returned as expected
Trouble connecting to the target database
Intercomponent call errors
The log may be difficult to decipher when multiple clients are talking to the server in parallel. If possible, run only one client when using the IIOP log information.
IIOP logging is verbose
IIOP logging can quickly
fill up the disk and diminish server performance. Use IIOP logging only for short durations;
turn it off as soon as you gather the information you need.
For C/C++ and PowerBuilder clients, Table 1-13 describes how to direct the ORB to log IIOP protocol trace information.
