Quantcast

Getting transport error 202: bind failed: Address already in use error starting service

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Getting transport error 202: bind failed: Address already in use error starting service

dahoffer
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting transport error 202: bind failed: Address already in use error starting service

Leif Mortenson-3
David,
Looking at the command line, the Wrapper has bound and is listening on port 32002, and the JVM will then use a port in the 31000-31999 range will be used.  There are no other ports being used by the Wrapper.

As 32002 was used rather than 32000, that means that 32000 and 32001 are in use or were recently in use.   Could you check to make sure that another instance of your application is not currently running?  That would explain the application level port failing to bind.

Cheers,
Leif


On Fri, Nov 14, 2014 at 10:34 AM, David Hoffer <[hidden email]> wrote:
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting transport error 202: bind failed: Address already in use error starting service

dahoffer
I'm not sure I understand.  We do have the production app running...no idea what ports the wrapper is using there.  I need this to run at the same time...for debugging.

-Dave

On Thu, Nov 13, 2014 at 7:02 PM, Leif Mortenson <[hidden email]> wrote:
David,
Looking at the command line, the Wrapper has bound and is listening on port 32002, and the JVM will then use a port in the 31000-31999 range will be used.  There are no other ports being used by the Wrapper.

As 32002 was used rather than 32000, that means that 32000 and 32001 are in use or were recently in use.   Could you check to make sure that another instance of your application is not currently running?  That would explain the application level port failing to bind.

Cheers,
Leif



On Fri, Nov 14, 2014 at 10:34 AM, David Hoffer <[hidden email]> wrote:
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user



------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting transport error 202: bind failed: Address already in use error starting service

dahoffer
Also I should mention I do have this new dev app in a different folder and it has a different name, e.g. dev_ prefixed to name.  Everything else I think is the same.

-Dave

On Thu, Nov 13, 2014 at 7:50 PM, David Hoffer <[hidden email]> wrote:
I'm not sure I understand.  We do have the production app running...no idea what ports the wrapper is using there.  I need this to run at the same time...for debugging.

-Dave

On Thu, Nov 13, 2014 at 7:02 PM, Leif Mortenson <[hidden email]> wrote:
David,
Looking at the command line, the Wrapper has bound and is listening on port 32002, and the JVM will then use a port in the 31000-31999 range will be used.  There are no other ports being used by the Wrapper.

As 32002 was used rather than 32000, that means that 32000 and 32001 are in use or were recently in use.   Could you check to make sure that another instance of your application is not currently running?  That would explain the application level port failing to bind.

Cheers,
Leif



On Fri, Nov 14, 2014 at 10:34 AM, David Hoffer <[hidden email]> wrote:
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user




------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting transport error 202: bind failed: Address already in use error starting service

dahoffer
The need to debug my app has occurred again and I always have trouble getting this to work.  Last time I just used a separate trial license to get me by.  My situation is that we have two production apps running and occasionally I need to setup a separate instance of one of them to debug an issue.  I typically only need the debug instance for about 30 minutes but I can never get JSW to run the separate instance and I don't know why.  We have the pro license I thought I could run any number of instances on the same server, right?  I guess I'm going to have to transition this app off JSW so I can do these quick debug installs...the way it is now I spend way more time getting JSW to run than on the issue at hand.  Do you have a fix for this with JSW?  Is there some flag I can set to temp use non-pro (non-licensed) version...I don't need any of those features especially for debugging session.

-Dave

On Thu, Nov 13, 2014 at 8:13 PM, David Hoffer <[hidden email]> wrote:
Also I should mention I do have this new dev app in a different folder and it has a different name, e.g. dev_ prefixed to name.  Everything else I think is the same.

-Dave

On Thu, Nov 13, 2014 at 7:50 PM, David Hoffer <[hidden email]> wrote:
I'm not sure I understand.  We do have the production app running...no idea what ports the wrapper is using there.  I need this to run at the same time...for debugging.

-Dave

On Thu, Nov 13, 2014 at 7:02 PM, Leif Mortenson <[hidden email]> wrote:
David,
Looking at the command line, the Wrapper has bound and is listening on port 32002, and the JVM will then use a port in the 31000-31999 range will be used.  There are no other ports being used by the Wrapper.

As 32002 was used rather than 32000, that means that 32000 and 32001 are in use or were recently in use.   Could you check to make sure that another instance of your application is not currently running?  That would explain the application level port failing to bind.

Cheers,
Leif



On Fri, Nov 14, 2014 at 10:34 AM, David Hoffer <[hidden email]> wrote:
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user




------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting transport error 202: bind failed: Address already in use error starting service

Leif Mortenson-3
David,
I am sorry you are having trouble.  The Wrapper ships with a 15 minute timed license call src/conf/wrapper-license-timed.conf in the Wrapper distribution.
You should be able to use this for quick tests without needing to obtain an actual trial license.
This should be very painless and simple so I would of course like to help you resolve the problem.

I will also send you a followup message through support.

Cheers,
Leif


On Mon, Dec 15, 2014 at 12:18 AM, David Hoffer <[hidden email]> wrote:
The need to debug my app has occurred again and I always have trouble getting this to work.  Last time I just used a separate trial license to get me by.  My situation is that we have two production apps running and occasionally I need to setup a separate instance of one of them to debug an issue.  I typically only need the debug instance for about 30 minutes but I can never get JSW to run the separate instance and I don't know why.  We have the pro license I thought I could run any number of instances on the same server, right?  I guess I'm going to have to transition this app off JSW so I can do these quick debug installs...the way it is now I spend way more time getting JSW to run than on the issue at hand.  Do you have a fix for this with JSW?  Is there some flag I can set to temp use non-pro (non-licensed) version...I don't need any of those features especially for debugging session.

-Dave

On Thu, Nov 13, 2014 at 8:13 PM, David Hoffer <[hidden email]> wrote:
Also I should mention I do have this new dev app in a different folder and it has a different name, e.g. dev_ prefixed to name.  Everything else I think is the same.

-Dave

On Thu, Nov 13, 2014 at 7:50 PM, David Hoffer <[hidden email]> wrote:
I'm not sure I understand.  We do have the production app running...no idea what ports the wrapper is using there.  I need this to run at the same time...for debugging.

-Dave

On Thu, Nov 13, 2014 at 7:02 PM, Leif Mortenson <[hidden email]> wrote:
David,
Looking at the command line, the Wrapper has bound and is listening on port 32002, and the JVM will then use a port in the 31000-31999 range will be used.  There are no other ports being used by the Wrapper.

As 32002 was used rather than 32000, that means that 32000 and 32001 are in use or were recently in use.   Could you check to make sure that another instance of your application is not currently running?  That would explain the application level port failing to bind.

Cheers,
Leif



On Fri, Nov 14, 2014 at 10:34 AM, David Hoffer <[hidden email]> wrote:
I'm using 3.5.15-pro version.  I have the production service on this VM working but I need to standup a second instance so I can debug a problem.  I'm getting the following error with the second instance.  What is causing 'ERROR: transport error 202: bind failed: Address already in use'?  I have my app configured to use different ports so as to not conflict with the production app...is JSW using the same port?

How can I fix this?

wrapper  | ---------------------------------------------------------------------
wrapper  | The JVM is being launched with a debugger enabled and could possibly
wrapper  | be suspended.  To avoid unwanted shutdowns, timeouts will be
wrapper  | disabled, removing the ability to detect and restart frozen JVMs.
wrapper  | ---------------------------------------------------------------------
wrapper  | Command[0] : /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
wrapper  | Command[1] : -Djava.util.Arrays.useLegacyMergeSort=true
wrapper  | Command[2] : -Xdebug
wrapper  | Command[3] : -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
wrapper  | Command[4] : -Xms64m
wrapper  | Command[5] : -Xmx1024m
wrapper  | Command[6] : -Djava.library.path=./
wrapper  | Command[7] : -classpath
wrapper  | Command[8] : ../lib/activation-1.1.jar:../lib/aopalliance-1.0.jar:../lib/asm-3.3.1.jar:../lib/bcmail-jdk15-1.44.jar:../lib/bcprov-jdk15-1.44.jar:../lib/commons-codec-1.5.jar:../lib/commons-email-1.2.jar:../lib/commons-lang-2.6.jar:../lib/commons-logging-1.1.1.jar:../lib/commons-math-1.2.jar:../lib/commons-net-3.1.jar:../lib/cxf-api-2.7.10.jar:../lib/cxf-rt-bindings-soap-2.7.10.jar:../lib/cxf-rt-bindings-xml-2.7.10.jar:../lib/cxf-rt-core-2.7.10.jar:../lib/cxf-rt-databinding-aegis-2.7.10.jar:../lib/cxf-rt-databinding-jaxb-2.7.10.jar:../lib/cxf-rt-frontend-jaxws-2.7.10.jar:../lib/cxf-rt-frontend-simple-2.7.10.jar:../lib/cxf-rt-management-2.7.10.jar:../lib/cxf-rt-transports-http-2.7.10.jar:../lib/cxf-rt-transports-http-jetty-2.7.10.jar:../lib/cxf-rt-transports-local-2.7.10.jar:../lib/cxf-rt-ws-addr-2.7.10.jar:../lib/cxf-rt-ws-policy-2.7.10.jar:../lib/dhs-commons-1.6-SNAPSHOT.jar:../lib/dom4j-1.6.1.jar:../lib/fluent-hc-4.3.1.jar:../lib/fontbox-1.8.2.jar:../lib/geronimo-servlet_3.0_spec-1.0.jar:../lib/guice-3.0.jar:../lib/guice-assistedinject-3.0.jar:../lib/httpclient-4.3.1.jar:../lib/httpcore-4.3.jar:../lib/ifreelance-pn27284-webservice-1.5-SNAPSHOT.jar:../lib/itext-2.1.7.jar:../lib/javax.inject-1.jar:../lib/jaxb2-basics-runtime-0.6.1.jar:../lib/jaxb-api-2.2.jar:../lib/jaxb-impl-2.2.4.jar:../lib/jdom-1.0.jar:../lib/jempbox-1.8.2.jar:../lib/jetty-continuation-8.1.14.v20131031.jar:../lib/jetty-http-8.1.14.v20131031.jar:../lib/jetty-io-8.1.14.v20131031.jar:../lib/jetty-security-8.1.14.v20131031.jar:../lib/jetty-server-8.1.14.v20131031.jar:../lib/jetty-util-8.1.14.v20131031.jar:../lib/jetty-xml-8.1.14.v20131031.jar:../lib/joda-time-1.6.2.jar:../lib/jsr173_api-1.0.jar:../lib/jsr250-api-1.0.jar:../lib/jsr305-1.3.9.jar:../lib/log4j-1.2.16.jar:../lib/mail-1.4.1.jar:../lib/mortgage-tools-1.4-SNAPSHOT.jar:../lib/neethi-3.0.3.jar:../lib/pdfbox-1.8.2.jar:../lib/poi-3.9.jar:../lib/poi-ooxml-3.9.jar:../lib/poi-ooxml-schemas-3.9.jar:../lib/runtime-0.4.1.jar:../lib/slf4j-api-1.7.5.jar:../lib/stax2-api-3.1.1.jar:../lib/stax-api-1.0-2.jar:../lib/stax-api-1.0.1.jar:../lib/woodstox-core-asl-4.2.0.jar:../lib/wrapper-3.5.15.jar:../lib/wsdl4j-1.6.3.jar:../lib/xml-apis-1.0.b2.jar:../lib/xml-resolver-1.2.jar:../lib/xmlbeans-2.3.0.jar:../lib/xmlschema-core-2.1.0.jar
wrapper  | Command[9] : -Dwrapper.key=RI8htg3WrkuGSLCkOHiJ-0Dkk4OtOvbe
wrapper  | Command[10] : -Dwrapper.port=32002
wrapper  | Command[11] : -Dwrapper.jvm.port.min=31000
wrapper  | Command[12] : -Dwrapper.jvm.port.max=31999
wrapper  | Command[13] : -Dwrapper.pid=20122
wrapper  | Command[14] : -Dwrapper.version=3.5.15-pro
wrapper  | Command[15] : -Dwrapper.native_library=wrapper
wrapper  | Command[16] : -Dwrapper.cpu.timeout=10
wrapper  | Command[17] : -Dwrapper.jvmid=5
wrapper  | Command[18] : -Dwrapper.lang.domain=wrapper
wrapper  | Command[19] : com.qsd.service.jsw.JavaServiceWrapperWebServiceLauncher
wrapper  | Launching a JVM...
jvm 5    | ERROR: transport error 202: bind failed: Address already in use
jvm 5    | ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
jvm 5    | JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
jvm 5    | FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
wrapper  | JVM received a signal UNKNOWN (6).
wrapper  | JVM process is gone.
wrapper  | JVM exited while loading the application.
wrapper  | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
wrapper  |   There may be a configuration problem: please check the logs.
wrapper  | <-- Wrapper Stopped

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Wrapper-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Loading...