Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.3.GA
Reporter: Adrian Brock
An undocmentated feature has been added to the jms rar in 4.2.3
Sadly it doesn't work properly. This needs fixing, documentating and testing.
It should also be made the default since we don't want to wait forever when we stop an
If an MDB doesn't shutdown in the time then we should log a warning.
Discussion from the mailing list:
c) forceClearOnShutdown, et. al.
The idea looks good, but the implementation is rubbish.
It shows a fundamental misunderstooding on how the pool works.
The notification happens once for each session that ends
(and hence so does your loop).
In practice with the default config, it will leave
the loop after the first session ends (almost immediately) when in the
default config there are still 14 other sessions to go.
A 1 second default wait is also unrealistic. Many people have MDBs
that take longer than this to process something.
In fact, this should be the default behaviour (but with different
configuration). Nothing should wait forever! :-)
The defaults should be specified in conf/standardjboss.xml
and the ejb3 equivalent aop interceptors file such that
users can easily change them.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira