-
1. Help with error from my log file
xavierpayne2 Nov 23, 2004 12:46 PM (in response to sheckler)I'm getting this exception:
sactionException: could not register synchronization with JTA TransactionManager
at org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:545)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:486)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
How do I debug this??? -
2. Re: Warnings from DefaultPartition within > 2 node cluster
sheckler Nov 24, 2004 4:32 AM (in response to sheckler)Additional information:
I am using a dedicated list of nodes as java.naming.provider.url such as node1:1100,node2:1100,node3:1100 for HAJNDI lookup of HAJMS connectionFactories, queues and topics -
3. Re: Warnings from DefaultPartition within > 2 node cluster
rolfz Nov 24, 2004 4:40 AM (in response to sheckler)Welcome in the club
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=54596 -
4. Re: Warnings from DefaultPartition within > 2 node cluster
sheckler Nov 24, 2004 4:58 AM (in response to sheckler)Thanks!
so this warning (which should be a debug message) is really just a warning and just tells me that the second node is not the HAJMS master as the third node tried to lookup via HAJNDI the total list of nodes. It is important to mention, that the 3rd node has no problem to get the queues from the first node (HAJMS master) at last and the application seems to work properly.
Stefan Heckler -
5. Re: Warnings from DefaultPartition within > 2 node cluster
starksm64 Nov 24, 2004 9:05 PM (in response to sheckler)Correct. It will just be a debug message in the next jboss releases.
-
6. Re: Warnings from DefaultPartition within > 2 node cluster
xavierpayne2 Dec 14, 2004 3:48 PM (in response to sheckler)Hey all, for now in your all/conf/log4j.xml
If you set the log threshold for the console (and file) appenders to ERROR for the package:
org.jboss.ha
These Warnings will no longer appear and you will reclaim a great deal of performance.
the xml snippet in your log4j.xml would look like this