java.io.IOException: Port in use: COM1

jsystemtest | roni_el | 7 years ago
  1. 0

    Serial connection problem

    jsystemtest | 7 years ago | roni_el
    java.io.IOException: Port in use: COM1
  2. 0

    Integrator Bulk Add to domain problem - All settings seem correct but Getting error: "SEVERE: Couldn't connect to <ourservername>:port"

    Oracle Community | 2 years ago | Nickelaus
    java.io.IOException: Bulk load port already in use. Only one bulk load connection is allowed at a time.
  3. 0

    When a transformation is executed on a Carte Cluster, but fails for any reason, the Sockets created by the clustering do not get released. This prevents a transformation from being re-executed until the affected Carte servers are restarted. {noformat} An error occurred while preparing the execution of the master transformation: Initialisation of transformation failed: 2016/01/29 12:13:43 - General - Logging plugin type found with ID: CheckpointLogTable 2016/01/29 12:13:47 - Carte - Installing timer to purge stale objects after 1440 minutes. 2016/01/29 12:13:47 - Carte - Created listener for webserver @ address : localhost:9081 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - Dispatching started for transformation [kettleClusteringTimestampBug (master)] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error creating server socket: java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0] 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.www.SocketRepository.openServerSocket(SocketRepository.java:113) 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.trans.steps.socketwriter.SocketWriter.init(SocketWriter.java:150) 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2016/01/29 12:14:19 - Writer : 40001.0 - at java.lang.Thread.run(Thread.java:745) 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error creating server socket: java.io.IOException: Server socket on port 40002 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40002.0] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error initializing step [Writer : 40001] 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : java.io.IOException: Server socket on port 40002 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40002.0] 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.www.SocketRepository.openServerSocket(SocketRepository.java:113) 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.trans.steps.socketwriter.SocketWriter.init(SocketWriter.java:150) 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2016/01/29 12:14:19 - Writer : 40002.0 - at java.lang.Thread.run(Thread.java:745) 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error initializing step [Writer : 40002] 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Step [Writer : 40001.0] failed to initialize! 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Step [Writer : 40002.0] failed to initialize! {noformat}

    Pentaho BI Platform Tracking | 10 months ago | Matt Tucker
    java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Integrator Bulk Add to domain problem - All settings seem correct but Getting error: "SEVERE: Couldn't connect to <ourservername>:port"

    Oracle Community | 2 years ago | Nickelaus
    java.io.IOException: Bulk load port already in use. Only one bulk load connection is allowed at a time.
  6. 0

    When a transformation is executed on a Carte Cluster, but fails for any reason, the Sockets created by the clustering do not get released. This prevents a transformation from being re-executed until the affected Carte servers are restarted. {noformat} An error occurred while preparing the execution of the master transformation: Initialisation of transformation failed: 2016/01/29 12:13:43 - General - Logging plugin type found with ID: CheckpointLogTable 2016/01/29 12:13:47 - Carte - Installing timer to purge stale objects after 1440 minutes. 2016/01/29 12:13:47 - Carte - Created listener for webserver @ address : localhost:9081 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - Dispatching started for transformation [kettleClusteringTimestampBug (master)] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error creating server socket: java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0] 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.www.SocketRepository.openServerSocket(SocketRepository.java:113) 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.trans.steps.socketwriter.SocketWriter.init(SocketWriter.java:150) 2016/01/29 12:14:19 - Writer : 40001.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2016/01/29 12:14:19 - Writer : 40001.0 - at java.lang.Thread.run(Thread.java:745) 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error creating server socket: java.io.IOException: Server socket on port 40002 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40002.0] 2016/01/29 12:14:19 - Writer : 40001.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error initializing step [Writer : 40001] 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : java.io.IOException: Server socket on port 40002 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40002.0] 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.www.SocketRepository.openServerSocket(SocketRepository.java:113) 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.trans.steps.socketwriter.SocketWriter.init(SocketWriter.java:150) 2016/01/29 12:14:19 - Writer : 40002.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2016/01/29 12:14:19 - Writer : 40002.0 - at java.lang.Thread.run(Thread.java:745) 2016/01/29 12:14:19 - Writer : 40002.0 - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Error initializing step [Writer : 40002] 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Step [Writer : 40001.0] failed to initialize! 2016/01/29 12:14:19 - kettleClusteringTimestampBug (master) - ERROR (version 5.4.0.4-149, build 1 from 2015-09-17 09.58.29 by buildguy) : Step [Writer : 40002.0] failed to initialize! {noformat}

    Pentaho BI Platform Tracking | 10 months ago | Matt Tucker
    java.io.IOException: Server socket on port 40001 is already in use by [kettleClusteringTimestampBug (master) - Writer : 40001.0]

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      Port in use: COM1

      at systemobject.terminal.RS232.connect()
    2. systemobject.terminal
      Cli.<init>
      1. systemobject.terminal.RS232.connect(RS232.java:48)
      2. systemobject.terminal.Cli.<init>(Cli.java:45)
      2 frames
    3. com.wavion.sysobj
      TigraSerialCLIConnection.connect
      1. com.wavion.sysobj.tigra.TigraSerialCLIConnection.connect(TigraSerialCLIConnection.java:122)
      1 frame