[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1829) Sybase transaction log full - dump needed
[
https://jira.jboss.org/jira/browse/JBPM-1829?page=com.atlassian.jira.plug...
]
Heiko Braun resolved JBPM-1829.
-------------------------------
Resolution: Done
[sybase@jbws ~]$ isql -Usa -P -SJBPM -Djbpmtest
1> use master
2> go
3> sp_dboption jbpmtest, "trunc. log on chkpt.", true
4> go
Database option 'trunc. log on chkpt.' turned ON for database 'jbpmtest'.
Running CHECKPOINT on database 'jbpmtest' for option 'trunc. log on
chkpt.' to
take effect.
(return status = 0)
Sybase transaction log full - dump needed
-----------------------------------------
Key: JBPM-1829
URL: https://jira.jboss.org/jira/browse/JBPM-1829
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Assignee: Heiko Braun
Priority: Critical
Fix For: jBPM 3.3.1 GA
After multiple QA runs, the sybase transaction log becomes full and the testsuite stops
Running org.jbpm.examples.raise.RaiseRequestTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.558 sec
As a system admin you can dump the log like this.
[sybase@jbws ~]$ isql -Usa -P -SJBPM -Djbpmtest
1> dump transaction jbpmtest with truncate_only
2> go
Please monitor db transactions and explain why there are so many open transactions the
stay open for a long time.
Run a continous test against sybase and monitor the db state.
I fear that we have a jdbc connection leak or uncommited transactions.
Anyway, the db should not just log because the Tx log becomes full
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira