[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20608#action_20608
]
gjoseph edited comment on MAGNOLIA-2567 at 1/21/09 3:29 PM:
-------------------------------------------------------------------
Hi,
Your logs mostly show templating errors, making it a little hard to spot the
actual workflow related issue. I only saw one exception which seem to indicate
something is indeed wrong with the workflow, but not necessarily that it is
corrupt.
So far, this doesn't qualify as a bug in Magnolia itself. We're lacking vital
information to qualify this, such as: how the workflows are started, and when
this error occurs (systematically, under high load, when starting wf's
simultaneously, etc.)
In any case, I'd advise to update to the latest 3.6 release of Magnolia for
greater performance and stability.
If you have a support contract with us, please use the [appropriate support
channel|http://documentation.magnolia-cms.com/support.html] (you can "move" the
issue if you're so inclined). Otherwise, you might find help on the [users'
list|http://documentation.magnolia-cms.com/stay-updated.html] too.
was (Author: gjoseph):
Hi,
Your logs mostly show templating errors, making it a little hard to spot the
actual workflow related issue. I only saw one exception which seem to indicate
something is indeed wrong with the workflow, but not necessarily that it is
corrupt.
So far, this doesn't qualify as a bug in Magnolia itself. We're lacking vital
information to qualify this, such as: how the workflows are started, and when
this error occurs (systematically, under high load, when starting wf's
simultaneously, etc.)
In any case, I'd advise to update to the latest 3.6 release of Magnolia for
greater performance and stability.
If you have a support contract with us, please use the
[http://documentation.magnolia-cms.com/support.html|appropriate support
channel] (you can "move" the issue if you're so inclined). Otherwise, you might
find help on the [users'
list|http://documentation.magnolia-cms.com/stay-updated.html] too.
> After an deployment, the repository of the jackrabbit is maybe corrupt
> ----------------------------------------------------------------------
>
> Key: MAGNOLIA-2567
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2567
> Project: Magnolia
> Issue Type: Bug
> Components: workflow
> Affects Versions: 3.5.8
> Environment: OS: FreeBSD7
> Jackrabbit on Mysql 5.0
> jdk-1.6.0.3p4
> tomcat-5.5.25
> Reporter: Thomas Sperger
> Assignee: Gregory Joseph
> Attachments: flows.html.xml, magnolia-error.log
>
>
> Jackrabbit is using a mysql database which runs locally on the same server.
> After an deployment in magnolia, a few days later the workflow isn't working
> any more and it
> seems that the jackrabbit repoistory is maybe corrupt.
> There were no changes to the configuration at all.
> The mysql-database was checked with "mysqlcheck" and is consistent.
> See attached the magnolia-error.log and the flows.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
