com.ibm.db2.jcc.b.DisconnectException: Execution failed due to a distribution protocol error that caused deallocation of the conversation. The identified cursor is not open.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
Execution failed due to a distribution protocol error that caused deallocation of the conversation. The identified cursor is not open.
com.ibm.db2.jcc.b.DisconnectException: Execution failed due to a distribution protocol error that caused deallocation of the conversation. The identified cursor is not open.
at com.ibm.db2.jcc.a.be.j(be.java:303)
at com.ibm.db2.jcc.a.be.i(be.java:186)
at com.ibm.db2.jcc.a.be.a(be.java:138)
at com.ibm.db2.jcc.a.be.c(be.java:40)
at com.ibm.db2.jcc.a.s.c(s.java:58)
at com.ibm.db2.jcc.a.h.bb(h.java:603)
at com.ibm.db2.jcc.a.h.bd(h.java:227)
at com.ibm.db2.jcc.b.ca.getRow(ca.java:1410)
at com.solarmetric.datasource.ResultSetWrapper.getRow(ResultSetWrapper.java:478)
at com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.instantiateRow(LazyResultList.java:186)
at com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.get(LazyResultList.java:142)
at com.solarmetric.kodo.runtime.objectprovider.ResultListIterator.next(ResultListIterator.java:49)
at tolina.kontosperre.logic.MainController.listeAnalysieren(MainController.java:280)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.