[esb-issues] [JBoss JIRA] Commented: (JBESB-1624) MySQL and large messages
[ http://jira.jboss.com/jira/browse/JBESB-1624?page=comments#action_12405069 ]
Haagen Hasle commented on JBESB-1624:
-------------------------------------
I didn't create the MySQL database, and the guy that did is out of office for 6 weeks,
but I think it is a fairly standard MySQL version 5 installation using the InnoDB engine.
Running on Windows Server 2003 R2 SP2.
I got this out of it:
Server version: 5.0.45-community-nt MySQL Community Edition (GPL)
Protocol version: 10
Server characterset: utf8
Db characterset: utf8
Hope this helps..
MySQL and large messages
------------------------
Key: JBESB-1624
URL: http://jira.jboss.com/jira/browse/JBESB-1624
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2.1 CP1
Reporter: Tom Cunningham
Logging this bug on behalf of Haagen Hassle (cut and pasted from forum reference) :
As far as I can tell, we tried to send a message that was too big, so big that MySQL
(that we use as the database for the ESB) couldn't handle it. We're trying to
solve this by increasing the max_allowed_packet for MySQL.
What I thought you would like to know though, is that the ESB never got out of this
error-situation. It tries the same SQL-statement over and over. It wrongfully assumes that
a deadlock is the cause of the problem, and therefore tries again after a while. But
because a deadlock is not the cause of the problem, the same thing happens over and over
again. Until I stop the server.
It looks like this might really come from code in JBoss Messaging, not in JBoss ESB, so
maybe I'm posting this to the wrong forum.. But maybe you'd like to know anyway?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira