ava.lang.Exception

The scenario did not end properly.

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 web7

  • via Oracle Community by 934564, 1 year ago
    The scenario did not end properly.
  • via Oracle Community by 718594, 1 year ago
    The scenario did not end properly. * at com.sunopsis.dwg.dbobj.SnpScen.a(SnpScen.java)
  • via Oracle Community by G Vijay, 11 months ago
    not exist . See root exception for the specific exception. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "942" to your deployment
  • Stack trace

    • ava.lang.Exception: The scenario did not end properly. at com.sunopsis.dwg.dbobj.SnpScen.a(SnpScen.java) at com.sunopsis.dwg.dbobj.SnpScen.localExecuteSync(SnpScen.java) at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java) at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java) at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(SnpSessTaskSqlS.java) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java) at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java) at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java) at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java) at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java) at com.sunopsis.dwg.cmd.e.k(e.java) at com.sunopsis.dwg.cmd.h.A(h.java) at com.sunopsis.dwg.cmd.e.run(e.java) at java.lang.Thread.run(Thread.java:662)

    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.