Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Workflow CPAN distribution.

Report information
The Basics
Id: 52558
Status: resolved
Priority: 0/
Queue: Workflow
People
Owner: jonasbn [...] cpan.org
Requestors:
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 1.32
Fixed in: (no value)

History Show all quoted text
  Tue Dec 08 04:56:14 2009 danny [...] sadinoff.com - Ticket created
What is the simplest and most direct approach to dealing with the case where the mysql server hangs up on Workflow's persister? "Failed to create workflow: DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/lib/perl5/site_perl/5.10.0/Workflow/Persister/DBI.pm line 226." 1) It's not obvious to me where to configure reconnect. 2) If reconnect wasn't an option, I can't see how to tell workflow to reconnect to the underlying database.
  Wed Dec 16 15:59:44 2009 jonasbn [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #52558]
Date: Wed, 16 Dec 2009 21:59:25 +0100
To: bug-Workflow [...] rt.cpan.org
From: Jonas Brømsø Nielsen <jonasbn [...] gmail.com>
Hi Danny, Perhaps this is something we should discuss on the list. The RT is a good reference point, but I do not regard the stuff you describe as trivial by any means. jonasbn On 08/12/2009, at 10.56, Danny Sadinoff via RT wrote: Show quoted text
> Tue Dec 08 04:56:14 2009: Request 52558 was acted upon. > Transaction: Ticket created by DSADINOFF > Queue: Workflow > Subject: (No subject given) > Broken in: 1.32 > Severity: Important > Owner: Nobody > Requestors: > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=52558 > > > > What is the simplest and most direct approach to dealing with the case > where the mysql server hangs up on Workflow's persister? > > "Failed to create workflow: DBD::mysql::st execute failed: MySQL server > has gone away at > /usr/local/lib/perl5/site_perl/5.10.0/Workflow/Persister/DBI.pm line 226." > > 1) It's not obvious to me where to configure reconnect. > 2) If reconnect wasn't an option, I can't see how to tell workflow to > reconnect to the underlying database. > >
  Wed Dec 16 15:59:45 2009 The RT System itself - Status changed from 'new' to 'open'
  Sat Jan 30 14:34:10 2010 jonasbn [...] cpan.org - Taken
  Sat Jan 30 14:40:27 2010 jonasbn [...] cpan.org - Correspondence added
Subject: Workflow::Persister::DBI reconnect implementation
Possible solution, sent to list for evaluation: http://sourceforge.net/mailarchive/forum.php?thread_name=E9C55B97-0DD1-49E9-9F24- DE3FAE982534%40gmail.com&forum_name=perl-workflow-devel jonasbn
  Sat Jan 30 14:41:09 2010 jonasbn [...] cpan.org - Subject changed from (no value) to 'Workflow::Persister::DBI reconnect implementation'
  Sun Sep 06 14:55:21 2015 jonasbn [...] cpan.org - Correspondence added
Issue migrated to Github: https://github.com/jonasbn/perl-workflow/issues/8 jonasbn
  Mon Dec 07 14:45:45 2020 jonasbn [...] cpan.org - Status changed from 'open' to 'resolved'