How do I use Command Line to Work With Pramati Server?

How do I use Command Line to Work With Pramati Server?

Pramati Server provides a command line interface, the Pramati Server Shell, using which you can perform various Server-related tasks, such as deploying and checking status, from local and remote machines. These tasks can be performed in two modes:

• Interactive mode
• Non-interactive mode

How do I Start Server From command Line?

How do I Start Server From command Line on Windows?

How do I Start Server From command Line on Linux/Unix?

The following start up options are available for starting the server.

Starting Server in Verbose mode

This option starts the server in verbose mode. In the verbose mode, a comprehensive list of all the configuration properties is displayed.

> ./runserver.sh -verbose

Starting and Stopping Deployed Applications at Server Startup

Applications can be started at server startup using the -startapps option. This option starts all applications that are deployed on the server. Applications can also be configured to be started at server startup by setting the auto-start tag in pramati-j2ee-server.xml of the deployed applications to true:

<auto-start>TRUE</auto-start>

> ./runserver.sh -startapps

> ./runserver.sh -startapps false

Disabling Shell Prompt at Server Startup

By default, when the Server is started, the shell prompt is made available for general administration. The shell can be disabled by using the -noshell option as:

> ./runserver.sh -noshell

Redirecting Output at Server Startup

Server output can be redirected at server startup using the -redirect option.

> ./runserver.sh -redirect

• stdErr.log: This file contains information about any errors that might have occurred when server starts up.
• stdOut.log: This file contains information about all server messages generated at server startup.

Starting Server With Username and Password

Server can be started by providing a username and password at server startup by using the -user and -password options. This prompts you for the username and password at server startup.

> ./runserver.sh -user root -password

Starting Server in Realms

The server can be started in a realm by using the -realm option. This starts the server for that realm. The default realm is system.

> ./runserver.sh -realm

Performing Cleanup at Server Startup

Certain cleanup operations can be performed at server startup. For example, corrupted directories are cleaned up at the time the server starts. The -cleanupapps option does this:

>./runserver.sh -cleanupapps

Testing JDBC Resources at Server Startup

JDBC resource can be tested at server startup by using the -testJDBCResources option. If a JDBC resource test fails, an error will show up as shown below:

Error while attempting to get a Connection for the ConnectionFactory [Doc_CF]
2:52:58 PM-     Doc_CF                                              [  FAILED  ]

. /runserver.sh -verbose -testJDBCResources

Specifying Nodes at Server Startup

Pramati server can be configured with various nodes. Each node is an instance of the server. A particular node can be started by using the -nodedir option.

> ./runserver.sh -nodedir myNode

Synchronizing Nodes in Clusters at Server Startup

In a clustered scenario, configuration of other nodes can be synched up at server start up. This option uploads the configuration of the node to the database.

> ./runserver.sh -uploadconfig

What is the Default Server Prompt?

The j2eeadmin@default:> prompt indicates that you are attached to the J2EE Shell, and connected to the default Server node.

How do I Connect to Remote Server?

not connected:>

This indicates that the shell is currently not connected to any server. To connect it interactively to a server, use the command: connect <enter>

This prompts you for entering the following parameters:

ipaddress[localhost]:
naming port[9191]:
realm [system]:
user name[root]:
password[*******]:

The default values are provided in square brackets, to accept the default values, press Enter. You can also use connect -file <filename _moz-userdefined=""> where <filename _moz-userdefined=""> is the name of the file that stores the connection data in the following format: <filename></filename>.

connect -ip <ip> -port <port> -realm <realm> -user <user> -password <password> 

For example, connect -ip 127.0.0.1 -port 9191 -realm realm -user root -password pramati

This connects the shell to the server running on the localhost with the naming service started on port 9191. The default user name is root and password is pramati.

How do I Back Up and Restore Server Configuration?

• Configuration files are corrupted inadvertently or deliberately, or through file system corruption at the OS level.
• Hardware failure
• Human error

How do I Restore Backed up Configurations?

Alternatively, for named backups, the name of the Configuration backup can be specified. For example: C:\PServer50_1016\server\bin>runserver -restore backupJune06.

What are the Types of Shells?

• J2EE Shell
• Resource Shell
• JMS Shell
• Kernel Shell
• SQL Shell
• OS Shell
• Security Shell

What are the Generic Shell Commands?

Table 1: List of Generic Commands

Typing any available shell name inside any shell takes you to that Shell.

How do I use Shell Commands in Interactive Mode?

What are the Default J2EE Shell Commands?

Table 2: Description of J2EE Shell commands

What are the Resource Shell Commands?

Table 3: Commands in the Resource Shell

What are the JMS Shell Commands?

Table 4: Commands in the JMS Shell

What are the Kernel Shell Commands?

• administer deployable/restartable services at runtime
• create nodes/cluster configurations at runtime

To access this shell, type chsh and choose the number corresponding to the kernel shell or type kernel directly at the command prompt.

The shell prompt changes to kerneladmin@<server_name _moz-userdefined=""></server_name>

A list of commands is displayed on first entry into the shell. Typing help also displays the same information.

Table 5: Commands in the Kernel Shell

What are the SQL Shell Commands?

You can specify the following commands:

Table 6: Commands in the SQL Shell

Any valid SQL queries can be executed using the SQL Shell.

Note: You should disconnect from a DB or a datasource in the SQL shell before exiting from it, else the Server disconnects you automatically.

What is the OS Shell?

What are the Security Shell Commands?

Table 7: Commands in the Security Shell

Any valid Security queries can be executed using this shell.

How do I use Shell Commands in Batch Mode?

java com.pramati.RemoteShell -file [batch_file_location]

For example, you can create a batch file starter.pmt at /home/both/scripts/ that contains the following command set:

connect -ip 127.0.0.1 -port 9191 -realm realm -user root -password pramati
start myApp.ear
start anotherApp.ear
disconnect

Type: java com.pramati.RemoteShell -file /home/both/scripts/starter.pmt

This connects the shell to the Server that is running on localhost at port 9191. It starts myApp.ear and anotherApp.ear, and disconnects from the server - this does not stop the application. You can use the shell in Batch mode to write a script, which will shut down the Server.

Note: You need to have the required privileges to execute this script.

You can create and run a shutdown script to connect to the Server running on localhost and shut it down. Save the following commands in a file, for example, shutdown.pmt, at /home/both/scripts/:

connect -ip 127.0.0.1 -port 9191 -realm realm -user root -password pramati
shutdown

Type: java com.pramati.RemoteShell -file /home/both/scripts/shutdown.pmt

This command shuts down the Server.

How do I add Customized Commands?

Each Shell provides a command mapping between the commands and their class names. For example, the classname for the command list is com.pramati.services.command.j2ee.LISTCommand.

How does it work?

In the event of a command being invoked by the user, that is not presently registered, the CM tries to locate the command handler on the fly by making use of the following mechanism:

Compose the handler class name- <command _moz-userdefined="" uppercase="" to="" name-="">Command. For example, if command was get_app_status, then the class name would be GET_APP_STATUSCommand.

The CM tries to load this class. Normally, the class should be either in the server’s classpath or in the EXT directory <install_dir>\server\lib\ext.

If a new command is being written, then the command class file should be placed in a jar, and the jar be placed in the \ext directory.

How do I Load Customized Commands?

This adds the command to be used on the command line. The command will be available in only the particular Shell in which it was loaded.

How do I Alias Server Commands?

How do I Validate Archives?

java com.pramati.j2ee.deploy.validator.earvalidator.EARValidator <name and location of the archive>

Note: Before validating an archive from the command prompt, ensure that the classpath has been set. To set the classpath, run setup.sh on Unix or setup.bat on Windows located at <install_dir>\server\bin.

The following options can be specified with this command:

Table 8: Commands for Validating an Archive

For example, at the command prompt, type java com.pramati.tools.validator.earvalidator. EARValidator -a -oreport.txt orderApp.ear.

How do I Start Processes at Server Launch?

How do I Kickstart Processing at Server Launch?

Table 9: Options to be passed for the com.pramati.tools.bss.ServerLauncher class

Note: The next release of Server Launcher will also allow you to directly launch the Server. The current release supports only the launching of processes after the Server has started.

The default value for waitSeconds $TIME is two minutes for starting just the Server. There may be reasons why the wait may be more than two minutes:

• When Server starts for the first time after installation, the AdminConsole.war (the Console application) is auto-deployed
• The Server is started with auto-start applications
• A slow database may mean extra time to create the required datasources

How do I Start Server Launcher?

java com.pramati.tools.bss.ServerLauncher
-waitForServerInit
-host $HOSTNAME
-namingport $PORT
-waitSeconds $TIME
-verbose  -help

This utility should be invoked after the Pramati Server startup call. Host Name and Wait Time assume default values if not specified (for the default values refer to Table 9 above). namingport and waitForServerInit are mandatory - and are the only options supported with the present version.

How do I Shutdown Server?

• Normal Shutdown
• Immediate Shutdown

What is the Command for Normal Server Shutdown?

To initiate Normal Shutdown, enter the following in the default Shell: j2eeadmin@default> shutdown

What is the Command for Immediate Server Shutdown?

The Immediate Shutdown command can be used in scenarios where the Server may have to be started from inside an application-specific startup/init/bootstrap scripts/program. Shutdown command is provided in the J2EEServerMBean, and is executable from the Server and Remote Shells.

To initiate Immediate Shutdown, enter: j2eeadmin@default> shutdown <seconds>

After the specified time for shutdown (<seconds _moz-userdefined="">), the Server VM is forcefully exited. If the delay is zero, the Server VM exits immediately.

Invoking Immediate Shutdown

Immediate Shutdown can be invoked in one of two ways:

From the Server ShellTo initiate an Immediate Shutdown using the Shell, enter: j2eeadmin@default> shutdown <force timeout seconds>

Using MBeans The Server Shutdown can be effected programmatically using the J2EEServerMBean. The MBean is located using the MBean Server.

To look up the MBean using JNDI, create an initial context using the correct environment properties.

Context IC=newInitialContext(props);
J2EEServerMBean.mbean=(J2EEServerMBean)ic.lookup("root-server-mbean")

The method to be executed is: J2EEServerMBean.stop (forceTimeoutSeconds)

How do I Start Standalone Message Server?

1. Open a command window at <install_dir>\server\bin
2. Execute: runserver -node <nodename>
3. Specify the Message Server node name in <nodename> that you have created.

Note: For a Message Server node, ensure that JMSService is enabled in server-config.xml, located at <install_dir>\server\nodes\<node-name>\config.

The command to start Standalone J2EE Server, a J2EE Server Cluster or Message Server node is same. The command runserver -node <nodename> also helps in creation of a new node.

How do I View JMS Statistics?

The output may look like:

Free Memory: 1513 KBytes.
Total Memory: 1984 KBytes.

How do I List Destinations?

jmsadmin@default:>list destinations
Bound Topics: JMSTopic
Bound Queues: JMSQueue

In JMS context, there are two types of destination objects: Topic and Queue. These are used in point-to-point or publish or subscribe messaging domains. The Message Server console provides a command to find all, configured and list destinations.

How do I List Topics?

jmsadmin@default:>list topics
Bound Topics: JMSTopic, StockMarket

It displays all the configured topics on the server.

How do I List Queues?

jmsadmin@default:>list queues
Bound Queues: JMSQueue, SellQueue, BuyQueue

To list queues configured on the server using Message Server command line or the shell, use the command list queue. It displays all the configured queues on the server.

How do I List Factories?

jmsadmin@default:>list factories
Topic Connection Factories: JMSTopicConnectionFactory
Queue Connection Factories: JMSQueueConnectionFactory
XA Topic Connection Factories: JMSXATopicConnectionFactory
XA Queue Connection Factories: JMSXAQueueConnectionFactory

This command displays all the configured connection factories on the server.

How do I View Message Server Status?

How do I View Destination Details?

The following information about Queues are available:

• Max Queue size: The maximum queue size of the Queue.
• Total Messages Pending: The number of pending messages. Messages yet to be processed.
• Messages Pending in MessageList: The number of messages getting processed by existing receivers.
• Messages Pending in Orphaned List: The orphaned list contains the messages that were discarded and delivered to the dead message queue.
• Messages in the Persistent Store: The number of messages available in the Persistant store. This can be a file or a database.
• Messages in the Temp Persistent Store: When temporary store for a message is enabled, the discarded messages are stored in a temporary store. This specifies the number of messages in the temporary store.
• Messages Delivered: The total number of messages delivered to client proxies. Client proxies are proxies created for every client who is either subscribing to a topic or a queue. Client proxies reside on the server.

The following information about a Topic is available:

• Total Messages Pending: The number of pending messages for this topic.
• Messages Pending in MessageList: The number of pending messages in the Message List.
• Messages Pending in Orphaned List: The number of orphaned messages.
• Messages Delivered: The total number of messages delivered to client proxies. Client proxies are proxies created for every client who is either subscribing to a topic or a queue. Client proxies reside on the Server.

What are Timed Messages?

• Number of timed Messages in the runtime: This specifies the number of times messages that are available at run-time.
• Number of timed Messages sent: This number of messages that have been sent.
• Total number of timed Messages: The total number of timed messages that were configured.

What are Client Details?

• No. of Clients Connected: The total number of clients connected.
• Client IP: The hostname/IP address of the Client.
• Client ID: A unique ID of this client.
• Connection started: This is true if the connection to the client has started.
• Messages pending: This specifies the number of messages that are yet to be delivered to the client.
• Messages unacknowledged: Specifies the number of messages for which the JMS acknowledgement is yet to be received.
• Messages delivered: The total number of messages delivered to the client.

What are the Active/Inactive Durable Subscribers?

• Client - ID: The client-id of the inactive durable subscriber.
• Subscriber Name: The name of the subscriber who is inactive.
• Messages pending: In case of a durable subscriber, the number of pending messages is displayed.

What is the Thread Pool Status?

• MessageQueue Pool Status
• Pool limit
• Created count
• Active thread count
• Waiting thread count
• Pending job count

This section displays status of the topic delivery thread. The topic delivery thread is responsible for delivering messages to a subscriber of a topic:

• Pool limit
• Created count
• Active thread count
• Waiting thread count
• Pending job count

What is the Activation Status?

How do I Detect Deadlocks in EJBs?

j2eeadmin@default> detectDeadlock
No Deadlocks Detected.

In the above case, no deadlocks are detected.

How do I View Destinations and Connection Factories?

Table 10: Commands for Viewing list of Destinations and Command Factories

How do I Monitor Datasources?

1. Type the following command at the resource shell: start_tracking <Datasource_Name>. For example, ressh@default> start_tracking Oracle_DS.
2. Exit from the resource shell and check the status of the resource at J2EE server shell. To view details such as pool sizes, PreparedStatements, and memory usage, type the following command at the shell: status resource <DataSourceName> all. For example:

   j2eeadmin@default> status resource jdbc/DB1
   
   ====================================================
   Status generated on
   
   Mon Apr 17 17:47:45 GMT+05:30 2006
   ====================================================
   ----------------------------------------------------
               < Starting resource status >
   ----------------------------------------------------
   Datasource Name           :[jdbc/DB1]
   Connection Factory Name   :[demo_cf]
   Transaction participation :[true]
   Configuration details:
   Initial pool size         = 1
   Minimum pool size         = 5
   Maximum pool size         = 20
   Idle timeout              = 300 seconds
   Conn. request timeout     = 10 seconds
   Refresh interval          = 300 seconds
   Validation mode           = default
   
   Current Pool Status:
   Total requests                = 0
   Total connections             = 1
   Free connections              = 1
   Connections in use            = 0
   Object being validated        = false
   Total timed out requests      = 0
   Currently waiting threads     = 0
   Waiting threads peak          = 0
   Total connections destroyed   = 0
      Total invalid connections  = 0
   Total connection validations  = 0
   Total connection leaks        = 0
   Prepared statement cache
      Configured cache size  = 20
      Cache hit ratio        = 0
   Note:
   1. Unclosed connections are closed in finalize -
      Start the server with the system property
      com.pramati.resource.njdbc.debugconnectionleak=true
      to determine the source of these leaks.
   2. Unclosed prepared statements are closed when the connection wrapper is closed.
   ----------------------------------------------------
                < Ending resource status >
   ----------------------------------------------------
   Use the 'all' flag to view a more detailed status
   
   -------------- Memory Usage--------------
   Total VM memory = 20201k
   Free VM memory = 7211k
   -----------------------------------------
   Server started at Mon Apr 17 17:47:06 GMT+05:30 2006
   Server uptime 0 days 0 hrs 0 minutes 39 seconds
   
   j2eeadmin@default>
   

How do I Perform Advanced Monitoring for Datasources?

java  -server
-Dcom.pramati.util.pool.debugRetainedConnections=true
-Dinstall.root=%install_root%
-Djava.security.policy=%install_root%\lib\pramati\pramati.java.policy
-Djava.security.auth.policy=%install_root%\lib\pramati\pramati.jaas.policy
-Djacorb.home=%install_root%\lib\tp\jacorb com.pramati.Server %*

Note: This feature is available only for Pramati Server 4.1 SP3 and above.

This enables advanced instrumentation for datasource connection usage, including:

• The source of the getConnection (the application code where the getConnection was done).
• The time for which the connection has been in use.
• Filtering the output based on a time period so that only connection information which have been in use for greater than, say, n milliseconds, are shown.

This can help track down points in the application code which might be holding on to connections for too long and potentially starving other requests.

The output can be viewed by typing status resource <datasource name> all on the J2EE shell. For viewing this information, type status resource <datasource name> InUseConnections. This prints all connections that are currently in use for the datasource specified by <datasource name>.

For additional filtering as in points 2 and 3 above, type:status resource <datasource name> InUseConnections ConnectionsInUseFor=250

This prints all connections in use for the datasources that have been in use for more than 250 milliseconds.

In all the above command combinations, omitting the datasource name would print out the information for all datasources defined on the server.

Sample

----------------------------------------------------
            < Starting resource status >
----------------------------------------------------
Datasource Name           :[orads]
Connection Factory Name   :[oraclecf]
Transaction participation :[true]
Transaction isolation     :[unspecified]

Configuration details:
Initial pool size         = 1
Minimum pool size         = 5
Maximum pool size         = 20
Idle timeout              = 300 seconds
Conn. request timeout     = 10 seconds
Refresh interval          = 300 seconds
Validation mode           = default
Current Pool Status:
Total requests                = 1
Total connections             = 1
Free connections              = 0
Connections in use            = 1
Object being validated        = false
Total timed out requests      = 0
Currently waiting threads     = 0
Waiting threads peak          = 0
Total connections destroyed   = 0
   Total invalid connections  = 0
Total connection validations  = 1
Total connection leaks        = 0
Prepared statement cache
   Configured cache size  = 20
   Cache hit ratio        = 0
Note:
1. Unclosed connections are closed in finalize -
   Start the server with the system property
   com.pramati.resource.njdbc.debugconnectionleak=true
   to determine the source of these leaks.
2. Unclosed prepared statements are closed when
   the connection wrapper is closed.
Printing connection info for: 1
connection[0] has been in use for 9875 ms.
java.lang.Exception: InUseConnection
        at
        com.pramati.util.pool.ShrinkingPool$InuseInfo.
            (ShrinkingPool.java:945)
        at
        com.pramati.util.pool.ShrinkingPool.addToInUsePool
            (ShrinkingPool.java:505)
        at
        com.pramati.util.pool.ShrinkingPool._getObject
            (ShrinkingPool.java:267)
        at
        com.pramati.util.pool.ShrinkingPool.getObject
            (ShrinkingPool.java:235)
        at
        com.pramati.util.pool.ShrinkingPool.getObject
            (ShrinkingPool.java:224)
        at
        com.pramati.resource.njdbc.ContainerAuthoredDS.getConnectionFromPool
            (ContainerAuthoredDS.java:223)
        at
        com.pramati.resource.njdbc.PramatiDataSource._getConnection
            (PramatiDataSource.java:319)
        at
        com.pramati.resource.njdbc.ContainerAuthoredDS.getConnection
            (ContainerAuthoredDS.java:105)
        at
        com.pramati.jsp.generated.conn._jspService_delegate
            (conn.java:68)
        at
        com.pramati.jsp.generated.conn._jspService
            (conn.java:87)
        at
        com.pramati.jsp.runtime.HttpJspSuper.service
            (HttpJspSuper.java:91)
        at
        javax.servlet.http.HttpServlet.service
            (HttpServlet.java:802)
        at
        com.pramati.web.servlet.core.ServiceAction.run
            (ServiceAction.java:74)
        at
        com.pramati.security.util.PramatiSecurityHelper._doAs
            (PramatiSecurityHelper.java:54)
        at
        com.pramati.services.security.spi.SecurityHelper.doAs
            (SecurityHelper.java:124)
        at
        com.pramati.web.servlet.core.PramatiFilterChainImpl.invokeTargetWebResource
            (PramatiFilterChainImpl.java:219)
        at
        com.pramati.web.servlet.core.PramatiFilterChainImpl.doFilter
            (PramatiFilterChainImpl.java:140)
        at
        com.pramati.web.util.servlets.filters.TitleFilter.doFilter
            (TitleFilter.java:33)
        at
        com.pramati.web.servlet.core.PramatiFilterChainImpl.invokeTargetFilter
            (PramatiFilterChainImpl.java:163)
        at
        com.pramati.web.servlet.core.PramatiFilterChainImpl.doFilter
            (PramatiFilterChainImpl.java:132)
        at
        com.pramati.web.servlet.core.PramatiFilterChainImpl.startDoFilter
            (PramatiFilterChainImpl.java:88)
        at
        com.pramati.web.interceptors.ServiceInterceptor.preProcess
            (ServiceInterceptor.java:138)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:62)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:63)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:63)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:63)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:63)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultInterceptor.process
            (DefaultInterceptor.java:63)
        at
        com.pramati.web.interceptors.core.InterceptorChainImpl.processNext
            (InterceptorChainImpl.java:48)
        at
        com.pramati.web.interceptors.core.DefaultProcessContainer.process
            (DefaultProcessContainer.java:97)
        at
        com.pramati.web.core.WorkerThread.processConnection
            (WorkerThread.java:332)
        at
        com.pramati.web.core.WorkerThread.processConnection
            (WorkerThread.java:303)
        at
        com.pramati.web.core.WorkerThread.run
            (WorkerThread.java:128)
-----------------------------------------

How do I Configure Request Sniffing?

shell@start_request_sniff [-trace] [-file <output_filename>]

To turn it off, use the following command: shell@stop_request_sniff

What is the Format of Sniffer Log?

• One entry each for a Request, response, and TracePoint
• All entries appear in multiple lines
• Each entry is preceded by a marker - "##"
• Each entry has common info on first line such as: ##<WEB/EJB/JMS><REQUEST/RESPONSE/TRACE> Thread ID Timestamp System generate ID, followed by more information on the subsequent lines.

A request has additional information. Consider the iBank application which will contain information such as:

client ID= "127.0.0.1"
context = "bank"
URI = "bank/transfer.jsp"

Response includes just the response details. In case of WEB, it includes be the response headers.

Sample Output for Request Sniffing

## WEB RESPONSE Thread-15 1:24:27 PM ID:1077350067734
Client Id =127.0.0.1
Context =/
URI =/OrderBookWeb/
Details =HTTP/1.1 404 The requested resource was not found. Please check the URI above.
Server: Pramati Server
Date: Sat, 25 Feb 2006 07:54:28 GMT
Content-Length: 1125
Content-Type: text/html
Connection: Keep-Alive

A JMS Request Sniff would look as below:

## JMS REQUEST RMI TCP Connection(75)-192.168.1.29 4:42:49 PM ID:1077534769960
Client Id =192.168.1.29-502058352
Context =sendMessage msgId:ID:1673361:1077534769340:192.168.1.29:destination:QUEUE: JMSQueue
URI =sendMessage
Details =sendMessage
##
## JMS RESPONSE RMI TCP Connection(75)-192.168.1.29 4:42:49 PM ID:1077534769960
Client Id =192.168.1.29-502058352
Context =sendMessage msgId:ID:1673361:1077534769340:192.168.1.29:destination:QUEUE: JMSQueue
URI =sendMessage
Details =sendMessage done
##

In the above sniff log generated:

• Client Id - Represents the connection id after a connection has been established.
• Context - The context based on the operation being performed in the current thread. For example, in case of sendMessage above we must know the messageId and the destination for the message. Hence they are captured in the context.
• URI - This is not of much relevance in case of JMS. It is logged as the first call in the current thread.
• Details - This represents the resource being requested for along with arguments in case of request and response object in case of response. Also in the response we mention whether the particular operation was a success or a failure.

© Pramati Technologies 2007	Runs on Pramati Server | Feedback | Legal