Skip to main content
3-Newcomer
June 16, 2016
Question

Error launching Integrity client, JVM_Bind error.

  • June 16, 2016
  • 2 replies
  • 4623 views

User is getting a "Address already in use: JVM_Bind" error when the client launches.  The client appears to be installed correctly and the user has access to the installation directory.  Below are the log entries:

 

Integrity Client starting ...

 

Loading properties from C:\Program Files (x86)\Integrity\IntegrityClient10\IntegrityClientSite.rc

 

Loading: mks.ic.common.daemon.CommonConfiguration

 

Loading: mks.ic.aaa.daemon.AaConfiguration

 

Loading: mks.ic.si.daemon.SiConfiguration

 

Loading: mks.ic.sd.daemon.SdConfiguration

 

Loading: mks.ic.ci.daemon.CiConfiguration

 

Loading: mks.ic.ci.daemon.RqConfiguration

 

Loading: mks.ic.ci.daemon.TmConfiguration

 

Loading: mks.ic.api.daemon.ApiConfiguration

 

2016-06-15 06:09:39,340 (main) GENERAL(10): OnlyOneSessionPolicy loaded

 

2016-06-15 06:09:39,470 (main) GENERAL(10): Starting HTTP daemon

 

2016-06-15 06:09:39,589 (main) GENERAL(10): Server loaded configuration file: C:\Users\AD64106.ad\IntegrityClient.rc.

 

2016-06-15 06:09:39,767 (main) GENERAL(10): ICNoAuthenticationPolicy loaded

 

2016-06-15 06:09:39,782 (main) GENERAL(10): ICLocalConnectionPolicy loaded.

 

Cannot create daemon: Address already in use: JVM_Bind

 

2016-06-15 06:09:39,827 (main) ERROR(0) java.net.BindException: java.net.BindException: Address already in use: JVM_Bind

 

            at java.net.DualStackPlainSocketImpl.bind0(Native Method)

 

            at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)

 

            at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:382)

 

            at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)

 

            at java.net.ServerSocket.bind(ServerSocket.java:375)

 

            at java.net.ServerSocket.<init>(ServerSocket.java:237)

 

            at java.net.ServerSocket.<init>(ServerSocket.java:128)

 

            at mks.net.http.HttpServer.<init>(HttpServer.java:164)

 

            at mks.net.http.HttpServer.<init>(HttpServer.java:127)

 

            at mks.ic.common.daemon.Daemon.<init>(Daemon.java:189)

 

            at mks.ic.common.daemon.CommonConfiguration.startServices(CommonConfiguration.java:84)

 

            at mks.frame.app.model.App.startServices(App.java:495)

 

            at mks.ic.common.daemon.IntegrityClient.startupStandaloneClient(IntegrityClient.java:438)

 

            at mks.ic.common.daemon.IntegrityClient.main(IntegrityClient.java:159)

 

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

 

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 

            at java.lang.reflect.Method.invoke(Method.java:483)

 

            at com.zerog.lax.LAX.launch(DashoA10*..)

 

            at com.zerog.lax.LAX.main(DashoA10*..)

 

 

    2 replies

    16-Pearl
    June 16, 2016

    Hello Jennifer O'dell‌,

    Have you searched the Integrity Knowledge Base?  A search for "Address already in use: JVM_Bind" returns CS117504  as the first hit.  I think that article should help you resolve your issue.

    Regards,

    Kael

    1-Visitor
    June 17, 2016

    In our environment the most frequent reason for this error is that another integrity process is already running at this machine. Maybe its another user, whcih had started integrity and doesnt close the application and a new user is logging in and try to use Integrity also. So if you are using Windows just look at the taskmanager (and be sure to look at processes for all users) and search for some integrity process.

    kind regards, Jens

    16-Pearl
    June 17, 2016

    It's also possible that there is another process entirely using the client port (the default port used is 31000).

    Regards,

    Kael