com.splwg.shared.common.LoggedException: The following stacked messages were reported as the LoggedException was rethrown: com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception has occurred calling the remote JVM com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception occurred invoking remote command. The root LoggedException was: Exception flushing stream. - 2012-04-11 17:15:48,463 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 started with arguments: 2 9905 9906 2 - 2012-04-11 17:15:48,565 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,480 [main] INFO (shared.environ.ApplicationProperties) loaded properties from resource spl. properties: {spl.runtime.cobol.sql.cursoredCache.maxRows=10, spl.tools.loaded.applications=base,ccb,cm, spl.runtime.cobol.sql.disableQueryCache=false, spl.runtime.utf8Database=true, spl.runtime.cob ol.encoding=UTF8, spl.runtime.cobol.sql.cache.maxTotalEntries=1000, spl.runtime.cobol.cobrcall=false, spl.runtime.cobol.sql.fetchSize=150, spl.runtime.environ.init.dir=/ccbV210/TRUIBMSTG/etc, spl.r untime.sql.highValue=?, spl.runtime.service.extraInstallationServices=CILTINCP, spl.runtime.oracle.statementCacheSize=300} - 2012-04-11 17:15:48,666 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,513 [Remote JVM:2 Main ] INFO (cobol.host.SocketStrategy) Socket strategy set to com.splwg. base.support.cobol.host.sockets.UnixDomainSocketStrategy - 2012-04-11 17:15:48,776 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,518 [Remote JVM:2 Main ] INFO (host.sockets.UnixDomainSocketStrategy) Using this directory for socket files: /ccbV210/TRUIBMSTG/runtime - 2012-04-11 17:15:48,886 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 listening for requests on port: 9906 - 2012-04-11 17:15:58,706 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger) java.lang.RuntimeException: No command runner was registered with this remote JVM after waiting 10000ms - 2012-04-11 17:15:58,707 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:58,706 [Remote JVM:2 Main ] INFO (cobol.host.RemoteJVM) Shutting down loggers and exiting Remo te JVM 2 - 2012-04-11 17:15:58,809 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger)

Oracle Community | 846231 | 5 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    MKSYSB for Linux

    Oracle Community | 5 years ago | 846231
    com.splwg.shared.common.LoggedException: The following stacked messages were reported as the LoggedException was rethrown: com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception has occurred calling the remote JVM com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception occurred invoking remote command. The root LoggedException was: Exception flushing stream. - 2012-04-11 17:15:48,463 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 started with arguments: 2 9905 9906 2 - 2012-04-11 17:15:48,565 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,480 [main] INFO (shared.environ.ApplicationProperties) loaded properties from resource spl. properties: {spl.runtime.cobol.sql.cursoredCache.maxRows=10, spl.tools.loaded.applications=base,ccb,cm, spl.runtime.cobol.sql.disableQueryCache=false, spl.runtime.utf8Database=true, spl.runtime.cob ol.encoding=UTF8, spl.runtime.cobol.sql.cache.maxTotalEntries=1000, spl.runtime.cobol.cobrcall=false, spl.runtime.cobol.sql.fetchSize=150, spl.runtime.environ.init.dir=/ccbV210/TRUIBMSTG/etc, spl.r untime.sql.highValue=?, spl.runtime.service.extraInstallationServices=CILTINCP, spl.runtime.oracle.statementCacheSize=300} - 2012-04-11 17:15:48,666 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,513 [Remote JVM:2 Main ] INFO (cobol.host.SocketStrategy) Socket strategy set to com.splwg. base.support.cobol.host.sockets.UnixDomainSocketStrategy - 2012-04-11 17:15:48,776 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,518 [Remote JVM:2 Main ] INFO (host.sockets.UnixDomainSocketStrategy) Using this directory for socket files: /ccbV210/TRUIBMSTG/runtime - 2012-04-11 17:15:48,886 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 listening for requests on port: 9906 - 2012-04-11 17:15:58,706 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger) java.lang.RuntimeException: No command runner was registered with this remote JVM after waiting 10000ms - 2012-04-11 17:15:58,707 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:58,706 [Remote JVM:2 Main ] INFO (cobol.host.RemoteJVM) Shutting down loggers and exiting Remo te JVM 2 - 2012-04-11 17:15:58,809 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger)

    Root Cause Analysis

    1. com.splwg.shared.common.LoggedException

      The following stacked messages were reported as the LoggedException was rethrown: com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception has occurred calling the remote JVM com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:80): An exception occurred invoking remote command. The root LoggedException was: Exception flushing stream. - 2012-04-11 17:15:48,463 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 started with arguments: 2 9905 9906 2 - 2012-04-11 17:15:48,565 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,480 [main] INFO (shared.environ.ApplicationProperties) loaded properties from resource spl. properties: {spl.runtime.cobol.sql.cursoredCache.maxRows=10, spl.tools.loaded.applications=base,ccb,cm, spl.runtime.cobol.sql.disableQueryCache=false, spl.runtime.utf8Database=true, spl.runtime.cob ol.encoding=UTF8, spl.runtime.cobol.sql.cache.maxTotalEntries=1000, spl.runtime.cobol.cobrcall=false, spl.runtime.cobol.sql.fetchSize=150, spl.runtime.environ.init.dir=/ccbV210/TRUIBMSTG/etc, spl.r untime.sql.highValue=?, spl.runtime.service.extraInstallationServices=CILTINCP, spl.runtime.oracle.statementCacheSize=300} - 2012-04-11 17:15:48,666 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,513 [Remote JVM:2 Main ] INFO (cobol.host.SocketStrategy) Socket strategy set to com.splwg. base.support.cobol.host.sockets.UnixDomainSocketStrategy - 2012-04-11 17:15:48,776 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:48,518 [Remote JVM:2 Main ] INFO (host.sockets.UnixDomainSocketStrategy) Using this directory for socket files: /ccbV210/TRUIBMSTG/runtime - 2012-04-11 17:15:48,886 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) Remote JVM 2 listening for requests on port: 9906 - 2012-04-11 17:15:58,706 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger) java.lang.RuntimeException: No command runner was registered with this remote JVM after waiting 10000ms - 2012-04-11 17:15:58,707 [JVM 2 INFO logger] INFO (cobol.host.ProcessLogger) - 2012-04-11 17:15:58,706 [Remote JVM:2 Main ] INFO (cobol.host.RemoteJVM) Shutting down loggers and exiting Remo te JVM 2 - 2012-04-11 17:15:58,809 [JVM 2 ERROR logger] ERROR (cobol.host.ProcessLogger)

      at com.splwg.base.support.cobol.host.RemoteJVM.waitForServerToRegisterRunner()
    2. com.splwg.base
      RemoteJVM.waitForServerToRegisterRunner
      1. com.splwg.base.support.cobol.host.RemoteJVM.waitForServerToRegisterRunner(RemoteJVM.java:163)
      1 frame