java.lang.NullPointerException

This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web123724

  • via Terracotta by unnutz, 11 months ago
    This exception has no message.
  • This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.lang.NullPointerException at net.sourceforge.jtds.jdbc.JtdsStatement.close(JtdsStatement.java:868) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.close(JtdsPreparedStatement.java:485) at org.logicalcobwebs.proxool.AbstractProxyStatement.close(AbstractProxyStatement.java:115) at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:93) at org.logicalcobwebs.proxool.ProxyStatement.intercept(ProxyStatement.java:57) at quickfix.JdbcUtil.close(JdbcUtil.java:143) at quickfix.JdbcStore.set(JdbcStore.java:259) at quickfix.SessionState.set(SessionState.java:299) at quickfix.Session.sendRaw(Session.java:1736) at quickfix.Session.generateLogon(Session.java:1430) at quickfix.Session.next(Session.java:1357) at quickfix.mina.SessionConnector$SessionTimerTask.run(SessionConnector.java:248) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.