There is a potential bug in run.conf sourced by both run.sh and shutdown.sh.
http://jira.jboss.com/jira/browse/JBAS-4155
Unless anyone objects, it will be removed from shutdown.sh.
Also, commented out debugging options exist in both run.con:
| # Sample JPDA settings for remote socket debuging
| #JAVA_OPTS="$JAVA_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
|
| # Sample JPDA settings for shared memory debugging
| #JAVA_OPTS="$JAVA_OPTS -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"
|
and run.sh
| #JPDA options. Uncomment and modify as appropriate to enable remote debugging .
| #JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
|
One of 2 will be removed, so if you have any preferences, speak up.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042328#4042328
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042328
When calling session.recover, the message was being ACKed only when session.close was called.
Even when you don't have anything to recover, SessionAspect::handleRecover was setting recoverCalled to true, and handlePostDeliver wouldn't be able to ACK anything.
This would be okay if the client aways called session.close afterward... but for instance when using JCA the session is never closed (well.. at least for the life cycle of a testcase).
So.. I'm now only setting recoverCalled if there is anything to be recovered, so this would be okay.
I have added XATestBase::testRecoverOnXA with an expected behavior. We could change this anyway we want as long this test works.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042283#4042283
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042283