2590801 - JDBC connection errors with process infected with signal 11 - SAP ASE | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2590801 - JDBC connection errors with process infected with signal 11 - SAP ASE

Symptom

  • You can see in application log the the following stack:

ERROR com.elementfleet.notification.service.impl.NotificationExceptionProcessorImpl.logGeneralException(85) | com.elementfleet.notification.exception.NotificationException:
### Error updating database. Cause: java.sql.SQLException: JZ0C0: Connection is already closed.
### Cause: java.sql.SQLException: JZ0C0: Connection is already closed.
; SQL []; JZ0C0: Connection is already closed.; nested exception is java.sql.SQLException: JZ0C0: Connection is already closed. com.elementfleet.notification.exception.NotificationException:
### Error updating database. Cause: java.sql.SQLException: JZ0C0: Connection is already closed.
### Cause: java.sql.SQLException: JZ0C0: Connection is already closed.
; SQL []; JZ0C0: Connection is already closed.; nested exception is java.sql.SQLException: JZ0C0: Connection is already closed.
at com.elementfleet.notification.service.impl.PrepareNotificationServiceImpl.logAndMapNotificationRequest(PrepareNotificationServiceImpl.java:139)
at com.elementfleet.notification.service.impl.PrepareNotificationServiceImpl.execute(PrepareNotificationServiceImpl.java:82)
at com.elementfleet.notification.service.impl.NotificationProcessingServiceImpl.execute(NotificationProcessingServiceImpl.java:76)
at com.elementfleet.notification.messagedriven.NotificationRetryConsumer.protectedOnMessage(NotificationRetryConsumer.java:76)
at com.elementfleet.notification.messagedriven.AbstractConsumer.onMessage(AbstractConsumer.java:37)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:685)
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:623)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:591)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:308)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:246)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1137)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1129)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1031)
at java.lang.Thread.run(Thread.java:745)

  • The stacktrace in ASE errolog may contains some of the following functions:

kisignal
free__linkedcst
sub__locator
subp
subparams
s_execsetvar
s_execute
tdsrecv__dynexec
tdsrecv_dynamic


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 
  • Jconnect for JDBC 7.07
  • Windows x64
  • LINUX x64

Product

SAP Adaptive Server Enterprise 15.7

Keywords

CR731718, 731718, CR#731718, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers, characted ser, conversion, sort order , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.