Comment #6 on issue 2465 by jean.deruelle: TransactionUnavailableException
http://code.google.com/p/mobicents/issues/detail?id=2465
Hello,
I'm sorry but this is the community version, we don't guarantee any SLAs
(on community) nor *best effort* support on released versions older than
the current ones. Moreover you don't use exactly MSS 1.4 since its revision
is r14760
(http://code.google.com/p/mobicents/source/detail?spec=svn17725&r=14760)
and you're using r12654 (which is much older) so we can guarantee any
quality on this revision as it may be in an unstable state.
This is why we propose the JBCP product based on Mobicents to which you can
subscribe and that has support with guaranteed SLAs on specific versions
for 5 to 7 years + consulting and training services.
JBCP product goes through more extensive QA than the community version and
has regular Cumulative Patches releases and a different lifecycle than the
community version.
I'm willing to help but I don't have a crystal ball and can't guess what's
happening only with a stacktrace which is why I require more information to
efficiently debug this issue (which may not affect a newer release by
example) See http://www.mobicents.org/bug-reporting.html for efficient bug
reporting.
In that link :
"Special Categories: Some categories of problems require special
diagnostics. For example:
Memory leaks - memory dumps and potentially thread dumps will usually help
(e.g. java.lang.OutOfMemoryError,java.lang.StackOverflowError).
Deadlocks - thread dumps before and while running your test case."
If you can provide this, this could give some clues. you may also want to
run your JVM with diagnostics options enabled, from the same link
"Debugging options: Please add following JVM settings for your test case,
if possible
-XX:+HeapDumpOnOutOfMemoryError
-XX:+PrintConcurrentLocks
-XX:+PerfSaveDataToFile"
Even if we find the root cause and it is present on trunk as well you will
have to move to the trunk to get the fix as hot fix patches are only
available for JBCP (except if you maintain your own branch and know how to
backport from trunk to your specific revision)
Why don't you have JBCP instead of Community for production if the system
is so critical ?
