Re: built-in Catalyst server restarting issue

I’m not an Oracle dev but I suspect the connection is what’s hanging you up. A possible place to start is adding RaiseError so you might have a better chance to see what’s happening. Generally, you should never use DBI without RaiseError or, at the least, PrintError set.

options => { AutoCommit => 1,
             RaiseError => 1, },
[download]

Comment on Re: built-in Catalyst server restarting issue Select or Download Code

Replies are listed 'Best First'.
Re^2: built-in Catalyst server restarting issue by art84 (Initiate) on Nov 07, 2011 at 16:14 UTC
(it's me, the original author of the thread, just logged in) Thank you for your reply, but RaiseError changed nothing (well, it shouldn't change anything as I know, only report errors) and it didn't report anything: `Saw changes to the following files: - /path_to_my_project/MyProject/lib/MyProject/Model/DB.pm (modify) Attempting to restart the server` [download] The good part is that the issue is related to the DB connection for sure. I've just installed MySQL and tested using it and it does work correctly. So, it's something Oracle specific and maybe someone with Oracle knowledge could help .. I hope.	[reply] [d/l]
Re^3: built-in Catalyst server restarting issue by AbrekUS (Acolyte) on Jul 06, 2012 at 17:31 UTC
That is because signal handling has changed in the newer version of the Oracle client. Use the "ora_connect_with_default_signals" option to restore default signal handler: `options => { AutoCommit => 1, ora_connect_with_default_signals => [ 'INT' ], },` [download]	[reply] [d/l]