Hi. I had the same problem a few days ago. The problem is with the
console.ini file. Take a look at this:
https://forge.continuent.org/jira/browse/SEQUOIA-917
Regards,
Diego
F L escribió:
Hi,
We think we just had a lock in our postgresql database and sequoia
stopped answering jdbc requests.
Here's what we have in the full_cluster.log when we issued the
'shutdown virtual database'
2007-02-23 09:46:41,923 INFO sequoia.controller.shutdown Waiting for
59 virtual database worker threads to terminate.
2007-02-23 09:46:41,942 INFO
virtualdatabase.VirtualDatabaseWorkerThread.darwin
VirtualDatabaseWorkerThread killed by shutdown,
no clean-up done. Number of pending transaction in scheduler: 1
2007-02-23 09:46:42,005 INFO
virtualdatabase.VirtualDatabaseWorkerThread.darwin
VirtualDatabaseWorkerThread killed by shutdown,
no clean-up done. Number of pending transaction in scheduler: 1
... (it goes on 59 lines like that)
Now, we used to be able to console into the sequoia controller, issue
a 'debug on' and a ,'dump scheduler queues' so we could see what was
going on. Are these commands removed from the console commands cause
I don't see them anymore.
Also, is there a way we could monitor the status of the
'VirtualDatabaseWorkerThread' through jmx cause if so we could write a
small java program that would monitor these status and warn us when
this lock condition arrives
We are using sequoia 2.10.5 with postgresql jdbc-8.1-407 under Tomcat
5.5.20, hotspot 1.5.0_09
Txs,
Francois
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
Sequoia@lists.forge.continuent.org
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
Sequoia@lists.forge.continuent.org
https://forge.continuent.org/mailman/listinfo/sequoia
