[JBoss Messaging] - Re: MySQL in Cluster question
by jbabad
Hi,
This is a follow-on... similar testing I've now seen the set of exceptions below. Is there some configuration of JBoss/MySQL that I'm missing?
It's quite difficult to reliably replicate the problem at a known point, but I am seeing these errors and the ones in the previous posting happen on a regular basis. Any help/suggestions would be really appreciated.
The other question I suppose I should ask is whether people have experienced these sorts of issues either with JBoss4.2.x/JBossMQ combination or with JBoss4.2.x/JBM1.4.2
Thanks,
Joseph.
| 13:54:48,442 WARN [JDBCSupport] SQLException caught, SQLState HY000 code:1296- assuming deadlock detected, try:1
| java.sql.SQLException: Got error 4010 'Node failure caused abort of transaction' from NDB
| at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
| at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
| at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515)
| at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447)
| at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951)
| at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101)
| at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554)
| at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2046)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1964)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1949)
| at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365)
| at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(JDBCPersistenceManager.java:1637)
| at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1370)
| at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474)
| at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512)
| at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(JDBCPersistenceManager.java:1408)
| at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:226)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2212)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:499)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:755)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:397)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeTarget(SessionAdvised$send_7280680627620114891.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
| at sun.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
| at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
| 13:54:48,444 WARN [JDBCSupport] Trying again after a pause
| 13:54:48,525 WARN [TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@9eb61a[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1323140 handles=1 lastUse=1233928488441 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@3f9de3 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@96a235 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@1c58721 txSync=null]
| java.sql.SQLException: Can't lock file (errno: 157)
| at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
| at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
| at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515)
| at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447)
| at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951)
| at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101)
| at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554)
| at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2046)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1964)
| at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1949)
| at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365)
| at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1343)
| at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474)
| at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512)
| at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(JDBCPersistenceManager.java:1408)
| at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:226)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2212)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:499)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:755)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:397)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeTarget(SessionAdvised$send_7280680627620114891.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
| at sun.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
| at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207718#4207718
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207718
17 years, 4 months
JBoss5 on Debian: call for testers
by Philipp Huebner
Hello,
I'm writing on behalf of the Debian pkg-jboss group.
JBoss 5 is being packaged by us with the overall goal to get it into
Debian. There is still much work to do, especially in the build process,
packaging more components of JBoss separately, and getting those already
packaged separately working with JBoss 5.
But our first priority is to get it working in a usable way, and I
believe we have reached a usable status now.
The profiles "default", "minimal", "web" and "standard" seem to be
working ("all" isn't yet), but we would like to find people who want to
use JBoss on Debian and are able to test it.
So far we've been developing on Debian unstable, would be interesting if
someone tests it on Debian testing and reports back to us.
Packages are available from [1].
The ones I am talking about are jbossas5, libjbossas5-java and
jbossas5-doc, all in version 5.0.0~GA-0.5.
At the moment, you also need the temporary package jbossas5-libs (0.4-1)
for the others to work.
Further information can be found on [2].
Please let any discussion concerning this take place on the
pkg-jboss-maintainer list [3], hosted on alioth [4].
Feedback, testing and help is welcome and much appreciated.
[1] deb http://pkg-jboss.alioth.debian.org unstable/all/
[2] https://wiki.debian.org/JBossPackaging
[3] https://alioth.debian.org/mail/?group_id=30355
[4] https://alioth.debian.org/projects/pkg-jboss
Regards,
Philipp Hübner
17 years, 4 months
[JBoss jBPM] - Re: performance limits of jbpm
by roschmel
Do you refer to the new GWT Console? - I tested it in 3.3.0 and it was not really finished by then....
Logging:
I would like to solve two issues - 1) the log service is just to slow - its the main perfomance bottleneck of the enigne - 2) Is unsafe becuase it does not log when something goes wrong.
To have really good logs after a crash you must log you stuff (nearly) immidieatly to a persistent store. Otherwise when you pull the plug out of your server you have now idea what you already have done.
Additionally when you want to now that your database has a problem - then you might not be able to log this to the database.
Conclusion:
Really good logs must be written nearly immediatily to an extremly high available store ( - the local file system).
So I try to write the logs and the process hisotry using log4j and its MDC to the file system. From their you can transfer it to the database or you can direclty configure a JDBC Appender within log4j to write it to the db. Then you would need to look at the files just in case the db was unavailable.
The main problem is that this does not work without patching jBPM. The LoggingInstance is hardcoeded in the ProcessInstance and the logging service only gets called at the end of execution. This is were I am stuck at the moment. I would need a way to configure the LoggingInstance just like the Services.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207703#4207703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207703
17 years, 4 months