hi there
Thanks for the prompt reply.
I am using MyISAM - but can change to InnoDB if that is recommended/will get
rid of my problems.
Where do I configure the wait_timeout?
thanks
Gavin
----- Original Message -----
From: "Grégory Joseph" <[email protected]>
To: "Magnolia User-List" <[email protected]>
Sent: Thursday, December 09, 2010 10:28 AM
Subject: Re: [magnolia-user] MySQL Persistence
It seems a little unrelated, but I've noticed similar issues when using
MyISAM, but not with InnoDB engines. Which one are you using ?
Did you configure the wait_timeout on the server ?
-g
On 09 Dec 2010, at 10:24, Gavin Purnell wrote:
hi there
Apologies if this has been covered but I have searched the forum and
elsewhere...
I am using SLES 10, magnolia-4.3.6 base install - but just put 4.4 on,
apache-tomcat-5.5.27 with MySQL 5.0.26 on a separate server.
I have tried setting up Magnolia to talk to MySQL as per the install
notes - in particular
http://wiki.magnolia-cms.com/display/WIKI/Changing+Jackrabbit+PersistenceManager
I have Magnolia working in two nearly identical installs - the only
difference is that one is fully within my network - the other had the
MySQL database inside my network and the Magnolia Apache server in my DMZ.
Both installs have Author and Publisher on the same server.
The internal set up works fine, with no connectivity issues. But I do get
the same symptoms in the logs that I will describe in a second.
The DMZ install however has had a number of connectivity issues.
Sometimes Connection time out when I try and connect. Sometimes I can get
to the logon page but just cannot logon. Generally very
unstable/unpredictable.
I did have autoReconnect=true in both setups initially - there seemed to
be conflicting advice as to whether to have this?
Since I took this off the Author instance in the DMZ it has been a bit
more stable.
But in both setups I see a lot of errors in my logs:
2010-12-03 08:11:06,193 ERROR
..persistence.bundle.util.ConnectionRecoveryManager: could not execute
statement, reason: The last packet successfully received from the server
was 79,257,344 milliseconds ago. The last packet sent successfully to the
server was 79,257,344 milliseconds ago. is longer than the server
configured value of 'wait_timeout'. You should consider either expiring
and/or testing connection validity before use in your application,
increasing the server configured values for client timeouts, or using the
Connector/J connection property 'autoReconnect=true' to avoid this
problem., state/code: 08S01/0
2010-12-03 08:11:06,815 ERROR
core.persistence.bundle.BundleDbPersistenceManager: rollback failed
2010-12-03 08:11:06,815 ERROR
core.persistence.bundle.BundleDbPersistenceManager: Reason: No
operations allowed after connection closed.Connection was implicitly
closed by the driver.
2010-12-03 08:11:06,815 ERROR
core.persistence.bundle.BundleDbPersistenceManager: State/Code: 08003/0
I have now moved the MySQL database for my DMZ installation into the DMZ -
but still get the connection dropping and can't reliably get into the
system
I'd appreciate any feedback/advice.
Are these Errors - or really just warnings? Should I have a validity test
to check the connection is alive - if so how?
thanks in advance
Gavin
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1153 / Virus Database: 426/3275 - Release Date: 11/23/10
Internal Virus Database is out of date.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
