com.tc.objectserver.persistence.sleepycat.DBException

Environment invalid because of previous exception: com.sleepycat.je.RunRecoveryException

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web1

  • via Unknown by troy216,
  • Stack trace

    • com.tc.objectserver.persistence.sleepycat.DBException: Environment invalid because of previous exception: com.sleepycat.je.RunRecoveryException at com.tc.objectserver.persistence.sleepycat.SleepycatPersistenceTransactionProvider.newTransaction(SleepycatPersistenceTransactionProvider.java:25) at com.tc.objectserver.persistence.sleepycat.ClientStatePersistorImpl.deleteClientState(ClientStatePersistorImpl.java:113) at com.tc.objectserver.persistence.sleepycat.ConnectionIDFactoryImpl.channelRemoved(ConnectionIDFactoryImpl.java:114) at com.tc.object.net.DSOChannelManagerImpl.fireChannelRemovedEvent(DSOChannelManagerImpl.java:168) at com.tc.object.net.DSOChannelManagerImpl.access$200(DSOChannelManagerImpl.java:36) at com.tc.object.net.DSOChannelManagerImpl$GenericChannelEventListener.channelRemoved(DSOChannelManagerImpl.java:180) at com.tc.net.protocol.tcm.ChannelManagerImpl.fireChannelRemovedEvent(ChannelManagerImpl.java:59) at com.tc.net.protocol.tcm.ChannelManagerImpl.removeChannel(ChannelManagerImpl.java:119) at com.tc.net.protocol.tcm.ChannelManagerImpl.notifyChannelEvent(ChannelManagerImpl.java:100) at com.tc.net.protocol.tcm.AbstractMessageChannel.fireEvent(AbstractMessageChannel.java:243) at com.tc.net.protocol.tcm.AbstractMessageChannel.fireChannelClosedEvent(AbstractMessageChannel.java:134) at com.tc.net.protocol.tcm.AbstractMessageChannel.close(AbstractMessageChannel.java:146) at com.tc.net.protocol.tcm.HydrateHandler.handleEvent(HydrateHandler.java:26) at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:142)

    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

    We couldn't find other users who have seen this exception.