Hello Armin,
here is the stacktrace:
org.apache.ojb.broker.PersistenceBrokerSQLException:
java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver]Fehler
in der Funktionsreihenfolge.
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeUpdate(JdbcAccessImpl.java:
551)
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBrokerImpl.java:
1441)
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:
1341)
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:
700)
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersistenceBroker.java:
165)
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersistenceBroker.java:
165)
kos.generator.DataObject.storeInstance(DataObject.java: 68)
kos.wnetz.modules.fs2.FileSystem.saveFileProperties(FileSystem.java:
231)
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:
no source available)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
java.lang.reflect.Method.invoke(Method.java: 324)
kos.wnetz.system.Action.invoke(Action.java: 234)
kos.wnetz.system.ActionHandler.invoke(ActionHandler.java: 42)
kos.wnetz.servlets.WNetz.doRequest(WNetz.java: 98)
kos.wnetz.servlets.WNetz.doPost(WNetz.java: 74)
javax.servlet.http.HttpServlet.service(HttpServlet.java: 763)
javax.servlet.http.HttpServlet.service(HttpServlet.java: 856)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
284)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
204)
... 22 weitere Elemente...
Tino
Armin Waibel wrote:
Hi Tino,
Tino Schöllhorn wrote:
Hi,
I am using OJBrc5 (rebuild from CVS head) and I have some troubles
with my database: sometimes (not always) when I want to insert or
update an object via ojb the JdbcOdbcBridge throws an function
sequence error.
From my previous experiences this error occurs when a resultset r is
read and the statement which produced the resultset r is already closed.
Could you post the stack trace?
regards,
Armin
I already tried to switch off connection-pooling. But now I am helpless.
Any ideas?
Tino
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
