[JBoss Cache: Core Edition] - JTA transactions with Atomikos and cache loaders
by feutche
Hello, I've got a problem with JTA transactions using atomikos transaction manager implementation.
I'm using atomikos 3.4.4 and jboss-cache 3.0.2, I know that these are not the latest, but I've checked at least jboss-cache 3.1.0 sources and it looks like it's the same there, let me know if it's not true.
Issue is that cache loader commit is never being called, and that is caused by the fact that atomikos removes transaction from current thread between handlePrepareCommand(...) and handleCommitCommand(...) is being called on CacheStoreInterceptor.
After calling beforeCompletion() transaction is being removed from the thread, so when afterCompletion() and then CacheStoreInterceptor.handleCommitCommand is being invoked (with a command containing global transaction handle), CacheStoreInterceptor.inTransaction() returns false and the command is just ignored.
Please let me know if it's a known issue with atomikos (or it's their issue?).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242024#4242024
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242024
16 years, 9 months
[Management, JMX/JBoss] - Re: Binding Twiddle only with localhost
by sramhu
Contents of http://kbase.redhat.com/faq/docs/DOC-5477
| It is recommended that the jmx-invoker be bound specifically to localhost only. Do it as follows:
|
| In server/<configuration>/conf/jboss-service.xml, look for RMI/JRMP invoker section and update ServerAddress to be localhost. The section should then look something like:
|
| <!-- RMI/JRMP invoker -->
| <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
| name="jboss:service=invoker,type=jrmp">
| <attribute name="RMIObjectPort">4444</attribute>
| <attribute name="ServerAddress">localhost</attribute>
| ....
|
|
|
| In server/<configuration>/deploy/jmx-invoker-service.xml Add the following lines inside the <server> section:
|
| <!-- A pooled invoker bound to localhost -->
| <mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
| name="jboss:service=invoker,type=pooled,host=localhost">
| <attribute name="NumAcceptThreads">1</attribute>
| <attribute name="MaxPoolSize">300</attribute>
| <attribute name="ClientMaxPoolSize">300</attribute>
| <attribute name="SocketTimeout">60000</attribute>
| <attribute name="ServerBindAddress">localhost</attribute>
| <attribute name="ServerBindPort">4443</attribute>
| <attribute
| name="ClientConnectAddress">localhost</attribute>
| <attribute name="ClientConnectPort">0</attribute>
| <attribute name="ClientRetryCount">1</attribute>
| <attribute name="EnableTcpNoDelay">false</attribute>
| <depends
| optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
|
|
| And in the '<mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"' section, change the <depends> element with optional-attribute-name="InvokerName" to "jboss:service=invoker,type=pooled,host=localhost" so that it looks like:
|
| <depends optional-attribute-name="InvokerName">jboss:service=invoker,type=pooled,host=localhost</depends>
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242018#4242018
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242018
16 years, 9 months
[Clustering/JBoss] - Re: Farm deployment errors with large WAR files
by pclark95
Yep, you have the correct way that I am deploying it. I am starting both nodes, one at a time and I wait until they are both up. The 10.200.90.103 is started first and considered the master. Once both are up and clustered I place the war file on the 10.200.90.103 farm directory. I have enabled logging as you had asked and produced the files. Server time drift is minimal, but just so you can adjust between the two log files: 10.200.90.103 is 4 seconds faster than 10.200.90.105.
pclark@10.200.90.103:~/development/servers/jboss-5.1.0.GA/bin$ date
Mon Jul 6 10:08:48 CDT 2009
pclark@10.200.90.105:~/development/servers/jboss-5.1.0.GA/bin$ date
Mon Jul 6 10:08:44 CDT 2009
Here are the startup command for each:
10.200.90.103:
./run.sh -c all -b 10.200.90.103 -Djboss.messaging.ServerPeerID=10 -Djboss.messaging.groupname=TestPostOffice -Djboss.server.log.threshold=WARN -g TestPartition1
10.200.90.105:
./run.sh -c all -b 10.200.90.105 -Djboss.messaging.ServerPeerID=11 -Djboss.messaging.groupname=TestPostOffice -Djboss.server.log.threshold=WARN -g TestPartition1
I have emailed you the log files and the jboss-log4j.xml file (to make sure I enabled logging correctly). It doesn't look like I am able to attach a file to this post.
Thanks for your assistance,
Patrick
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242017#4242017
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242017
16 years, 9 months