View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006051SymmetricDSBugpublic2023-10-25 16:222023-10-25 16:22
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.14.0 
Target Version3.14.10Fixed in Version3.14.10 
Summary0006051: Sybase ASE result set has already been closed during trigger exists check
DescriptionWhen checking if a trigger exists on Sybase, it can get an error of result set has already been closed.

[AseSymmetricDialect] [background-nohup-3] Tried: select count(*) from dbo.sysobjects where type = 'TR' AND name ='SYM_ON_I_FOR_TRG_DWRK001DBB' which failed, will try again with catalog.
[AseSymmetricDialect] [background-nohup-3] TRY AGAIN Exceute: select count(*) from DWRK001.dbo.sysobjects where type = 'TR' AND name ='SYM_ON_I_FOR_TRG_DWRK001DBB'
[AseSymmetricDialect] [background-nohup-1] Could not figure out if the trigger exists. Assuming that is does not StackTraceKey.init [SqlException:2803195535]
2023-10-20 14:41:56,466 org.jumpmind.db.sql.SqlException: JZ0R0: ResultSet has already been closed.
     at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:308)
     at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:297)
     at org.jumpmind.db.sql.JdbcSqlTemplate.execute(JdbcSqlTemplate.java:501)
     at org.jumpmind.symmetric.db.ase.AseSymmetricDialect.doesTriggerExistOnPlatform(AseSymmetricDialect.java:227)
     at org.jumpmind.symmetric.db.AbstractSymmetricDialect.doesTriggerExist(AbstractSymmetricDialect.java:219)
     at org.jumpmind.symmetric.service.impl.TriggerRouterService.rebuildTriggerIfNecessary(TriggerRouterService.java:2355)
     at org.jumpmind.symmetric.service.impl.TriggerRouterService.updateOrCreateDatabaseTriggers(TriggerRouterService.java:2248)
     at org.jumpmind.symmetric.service.impl.TriggerRouterService.syncTriggers(TriggerRouterService.java:1871)
     at org.jumpmind.symmetric.service.impl.TriggerRouterService.syncTriggers(TriggerRouterService.java:1825)
     at com.jumpmind.symmetric.console.ui.common.ac.doWork(SyncTriggersWorker.java:66)
     at com.jumpmind.symmetric.console.ui.common.L$1.onBackgroundDataRefresh(InProgressNoHangupDialog.java:28)
     at com.jumpmind.symmetric.console.service.impl.BackgroundNoHangupService.refresh(BackgroundNoHangupService.java:48)
     at com.jumpmind.symmetric.console.service.impl.BackgroundNoHangupService$1.run(BackgroundNoHangupService.java:35)
     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
     at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
     at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
     at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.sql.SQLException: JZ0R0: ResultSet has already been closed.
     at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(ErrorMessage.java:832)
     at com.sybase.jdbc4.jdbc.SybResultSet.checkResultSet(SybResultSet.java:2995)
     at com.sybase.jdbc4.jdbc.SybResultSet.next(SybResultSet.java:185)
     at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:1160)
     at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:1160)
     at org.jumpmind.symmetric.db.ase.AseSymmetricDialect$2.execute(AseSymmetricDialect.java:265)
     at org.jumpmind.symmetric.db.ase.AseSymmetricDialect$2.execute(AseSymmetricDialect.java:227)
     at org.jumpmind.db.sql.JdbcSqlTemplate.execute(JdbcSqlTemplate.java:499)
     ... 16 more
Tagsdialect: sybase

Relationships

related to 0006050 closedelong Sybase ASE result set has already been closed during trigger exists check 
related to 0006052 closedelong Sybase ASE result set has already been closed during trigger exists check 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2023-10-25 16:22 elong New Issue
2023-10-25 16:22 elong Status new => assigned
2023-10-25 16:22 elong Assigned To => elong
2023-10-25 16:22 elong Tag Attached: dialect: sybase
2023-10-25 16:22 elong Issue generated from: 0006050
2023-10-25 16:22 elong Relationship added related to 0006050
2023-10-25 16:22 elong Status assigned => resolved
2023-10-25 16:22 elong Resolution open => fixed
2023-10-25 16:22 elong Fixed in Version => 3.14.10
2023-10-25 16:22 elong Issue cloned: 0006052
2023-10-25 16:22 elong Relationship added related to 0006052
2023-10-27 20:06 admin Status resolved => closed