Valid reason for creating a JMS connection and not starting it?

Question

We are facing performance issues with one of our EMS servers, and therefore started to analyze the connections being made to the server.

Currently one user have created 142 connections to our server with isStarted=false, and approx 50% of these connections were created for more than a month ago.

What could be a valid reason for creating a connection and not starting it?

The EMS Java API Documentation only says this:

public boolean isStarted()

Indicates whether or not the connection as been started by the client.

Returns:
    true if the connection has been started, false otherwise.

Thanks for any further explanations regarding this topic!

Answer 1

Probably the application is only sending messages and not receiving any messages. Messages can be sent even if the connection is stopped. JMS 1.1 Specification section 4.3.3 paragraph 4 says A MessageProducer can send messages while a Connection is stopped.. You might want to check the application for this point.