-
Patch
-
Resolution: Obsolete
-
Optional
-
JBossAS-4.0.2 Final
-
None
-
twiddle, jmx
-
Documentation (Ref Guide, User Guide, etc.)
Initial implementation of the JMSStats. The statistics service for JBoss JMS provider is
implemented using a JMSServerInterceptorSupport, this form we can turn on, turn off the
statistics provier. A little changes was necessary to make this work with the JBoss JMS:
1) It was necessary create a sessionNumber to attach the producer and consumer. The session number
is created by connection when the session is created.
2) when a producer is created a Id unique to this connection is used. The subscriptionId is used like
a consumer Id too.
3) the subscription store the session Id to become easy to atach the consumer in a right session.
4) To the producer two JBoss-vendor specific property were created PROPERTY_SESSION_ID and PROPERTY_PRODUCER_ID.
this form we can atach the producer in the correct session.
5) setConnectionToken is used in the JMSServerInterceptorSupport so we can know the real number of connections.
Because the old way fail if there is a connection with only producers.
Tested with JBossMQ unit tests, but is necessary create more tests to this features.
Necessary implements the getDurableSubscriptionCount in the sessin and isTransactional in
the connection.
To make this run is necessary change the files jbossmq-service.xml and hsqldb-jdbc2-service.xml
changes in the patch.
a