Where did H2 DB get this IP (tcp://203.198.80.60:9092)?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

alf1

Hi,

I just downloaded v5.6.  When I tried to start the demo I got the following error message:

Buildfile: /opt/activiti-5.6/setup/build.xml

demo.install:

cfg.create:
     [copy] Copying 1 file to /opt/activiti-5.6/setup/build/activiti-cfg
      [zip] Building zip: /opt/activiti-5.6/setup/build/activiti-cfg.jar
     [echo] copying configuration to ../workspace/activiti-engine-examples/src/main/config
    [unzip] Expanding: /opt/activiti-5.6/setup/build/activiti-cfg.jar into /opt/activiti-5.6/work
ce/activiti-engine-examples/src/main/config

internal.classpath.libs:

internal.taskdef.launch:

h2.start:
   [launch] launching cmd '/opt/activiti-5.6/apps/h2/h2.start.sh ' in dir '/opt/activiti-5.6/apps
'
   [launch] waiting for launch completion msg 'TCP server running on'…
   [launch]   Exception in thread "main" org.h2.jdbc.JdbcSQLException: Exception opening port "H2
P Server (tcp://203.198.80.60:9092)" (port may be in use), cause: "timeout" [90061-132]
   [launch]     at org.h2.message.DbException.getJdbcSQLException(DbException.java:316)
   [launch]     at org.h2.message.DbException.get(DbException.java:167)
   [launch]     at org.h2.tools.Server.start(Server.java:344)
   [launch]     at org.h2.tools.Server.runTool(Server.java:216)
   [launch]     at org.h2.tools.Server.main(Server.java:106)

What I find it strange is the IP address (tcp://203.198.80.60:9092) in the error message. It's not even close to the IP address of the machine.  I expect it to be 'localhost'. I don't know where it gets this IP address.  The script to start the H2 DB does not have this IP in the command line.

#!/bin/sh

java -cp h2*.jar org.h2.tools.Server -baseDir . -tcp -tcpAllowOthers

So where does it get it?

Thanks.

jbarrez

It should just use localhost, so I'm thinking that your machine /etc/hosts must be configured in a strange way for some reason.