Recent changes to support-requests

#308 WrapperStartStopApp.maxStartMainWait fails to act

Maxime Andrighetto — Wed, 29 Jan 2025 03:27:45 -0000

Hello Sanjib,

Thank you for reporting this issue.

The startup waiting time, which defaults to 2 seconds, is not criterion of success or failure. It just defines the number of seconds that the WrapperStartStopApp class will wait before assuming that the application has started. In other words, both cases where the main method completes before or after the 2 seconds will be considered successful (as long as the exit code is 0).

Looking at the log output you sent, the Wrapper process is receiving a SIGCHLD from the JVM and detects that the JVM has terminated. This can happen if your main class called system.exit(1) or returned with error code 1.

The log you attached is a bit difficult to read because there is not timestamps and no column to distinguish the source (JVM vs Wrapper). You may want to add the 'P' and 'T' column to show this information:
https://wrapper.tanukisoftware.com/doc/english/prop-console-format.html

Did you remove some lines from the output? In debug mode, the Wrapper should show more output like the command line, etc.. These messages are also helpful in understanding issues.

Do you encounter the same issue when running without -javaagent? It would be interesting to see the command lines generated by the Wrapper when this option is added.

If possible, please send us your full log file on a private email at support@tanukisoftware.com.

Best Regards,

Maxime

WrapperStartStopApp.maxStartMainWait fails to act

Sanjib Chakraborty — Tue, 28 Jan 2025 11:59:50 -0000

wrapper version; 3.5.53

Java process startup (with -javaagent) fails, due to default 2 sec startup criteria. As pr documentation https://wrapper.tanukisoftware.com/doc/english/integrate-start-stop-nix.html#TuneUp tried bypassing the default timeout settings. But unable to do so, as if they dont seem to impact.

wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperStartStopApp.waitForStartMain=TRUE
&
wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperStartStopApp.maxStartMainWait=300

However, with in debug mode the process (with -javaagent) starts properly since debug overrides the WrapperStartStopApp.maxStartMainWait system property as documented.

How shall the wrapper configuration be debugged further? Following is the process log in wrapper verbose mode:

[startup.sh] Starting a plain Tanuki process...
Running Software AG Integration Server 11.1 (default)...
wrapper  | Configured log file set to '/Applications/IS111/IntegrationServer/instances/default/logs/wrapper.log'.
wrapper  | Base configuration file is /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper.conf
wrapper  | Found #include file in /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper.conf: %INSTALL_AREA%/configuration/wrapper-license.conf
wrapper  |   After environment variable replacements: /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper-license.conf
wrapper  |   Reading included configuration file, /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper-license.conf
wrapper  | The "wrapper.anchorfile" property was defined on the Wrapper command line and can not be overwritten.
wrapper  |   Ignoring redefinition on line #108 of configuration file: /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper.conf
wrapper  |   Fixed Value wrapper.anchorfile=/Applications/IS111/IntegrationServer/instances/default/bin/wrapper.anchor
wrapper  |   Ignored Value wrapper.anchorfile=/Applications/IS111/IntegrationServer/instances/default/bin/wrapper.anchor
wrapper  | Found #include file in /Applications/IS111/IntegrationServer/instances/default/configuration/wrapper.conf: %INSTALL_AREA%/configuration/custom_wrapper.conf
wrapper  |   After environment variable replacements: /Applications/IS111/IntegrationServer/instances/default/configuration/custom_wrapper.conf
wrapper  |   Reading included configuration file, /Applications/IS111/IntegrationServer/instances/default/configuration/custom_wrapper.conf
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Standard Edition 64-bit 3.5.53
wrapper  |   Copyright (C) 1999-2023 Tanuki Software, Ltd. All Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.com
wrapper  |   Licensed to Software AG for Software AG Integration Server
wrapper  | 
wrapper  | Release time: 2023/03/09 00:00:00
wrapper  | Build time:   2023/03/08 19:07:00
wrapper  | Timezone:     IST (+0630) Offset: -19800, hasDaylight: 1
wrapper  | Using tick timer.
wrapper  | PID:          79129
wrapper  | Signal trapped.  Details:
wrapper  |   signal number=20 (SIGCHLD), source="unknown"
wrapper  | Received a 'SIGCHLD' signal.  Checking JVM process status.
wrapper  | Java version: 17.0.13
wrapper  | Java vendor: OpenJDK
wrapper  | Java bits: 64-Bit
wrapper  | Reading the JVM output using the encoding of the current locale (UTF-8).
wrapper  | Classpath element, wrapper.java.classpath.2, does not exist: %JAVA_SYSTEM_CLASSPATH%
wrapper  | Classpath element, wrapper.java.classpath.3, does not exist: /Applications/IS111/common/lib/wm-converters.jar
wrapper  | Resolved the real path of wrapper.java.command as an absolute reference: /Applications/IS111/jvm/jvm/bin/java
wrapper  | Magic number for file /Applications/IS111/jvm/jvm/bin/java: 0xcffaedfe
wrapper  | The 'JAVA_BOOT_CLASSPATH' environment variable was referenced but has not been defined.
wrapper  | Startup Timeouts: wrapper.startup.timeout=30, wrapper.startup.delay.console=0, wrapper.startup.delay.service=0, wrapper.restart.delay=5
wrapper  | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=300, wrapper.ping.alert.threshold=75
wrapper  | Shutdown Timeouts: wrapper.shutdown.timeout=0, wrapper.jvm_exit.timeout=0, wrapper.jvm_cleanup.timeout=10, wrapper.jvm_terminate.timeout=10
wrapper  | Launching a JVM...
wrapper  | JVM started (PID=79131)
wrapper  | Signal trapped.  Details:
wrapper  |   signal number=20 (SIGCHLD), source="unknown"
wrapper  | Received a 'SIGCHLD' signal.  Checking JVM process status.
wrapper  | JVM process exited with a code of 1, setting the Wrapper exit code to 1.
wrapper  | JVM exited while loading the application.
wrapper  | The thread reading stdin is not responding. Stop reading console input.
wrapper  | Preparing to restart with mode 2.
wrapper  | Automatic JVM Restarts disabled.  Shutting down.
wrapperp | closing backend server.
wrapper  | Exit code: 1
wrapper  | <-- Wrapper Stopped

#307 Allow running a second process

Leif Mortenson — Tue, 21 Sep 2021 00:56:14 -0000

Can you explain a bit more what you are wanting to do? How is the second process triggered?

The Wrapper lets you launch managed child processes with the WrapperManager.exec method. Similar to the Runtime.exec, but you have more control over forking, and the Wrapper will manage the lifecycles of the child processes. It is also possible to trigger child processes in response to events. These are both Pro features however.

Allow running a second process

Mark de Groot — Mon, 20 Sep 2021 11:05:00 -0000

I'm looking for a way to allow my service to temporarily start a second process. For instance to have the process start with a specific command-line flag, --status for example. The process should start, and dump some status info and quit again.

Obviously the Wrapper does not allow this, since the main process is already running. Any idea how we could accomplish this?

#76 Encountered Error 1067 : The process terminated unexpectedly

Karen Mitchell — Mon, 26 Mar 2018 23:24:17 -0000

Solution provided on this website.
https://www.errorsolutions.tech/error/error-1067-the-process-terminated-unexpectedly/

java.net.UnknownHostException: home

adekunle adeyemi — Fri, 08 Sep 2017 01:39:03 -0000

I am using the wrapper for my service and having this error when i run it on Linux. It works fine on windows without any issue. here is the error that is throwing

INFO   | jvm 1    | 2017/09/08 01:27:57 | Control event monitor thread started.
INFO   | jvm 1    | 2017/09/08 01:27:57 | Startup runner thread started.
INFO   | jvm 1    | 2017/09/08 01:27:57 | Communications runner thread started.
INFO   | jvm 1    | 2017/09/08 01:27:57 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 1    | 2017/09/08 01:27:57 | Opened Socket from 31000 to 32000
INFO   | jvm 1    | 2017/09/08 01:27:57 | Send a packet KEY : sbTAzUhAbwvTJyLj
INFO   | jvm 1    | 2017/09/08 01:27:57 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
DEBUG  | wrapperp | 2017/09/08 01:27:57 | accepted a socket from 127.0.0.1 on port 31000
DEBUG  | wrapperp | 2017/09/08 01:27:57 | read a packet KEY : sbTAzUhAbwvTJyLj
DEBUG  | wrapper  | 2017/09/08 01:27:57 | Got key from JVM: sbTAzUhAbwvTJyLj
DEBUG  | wrapperp | 2017/09/08 01:27:57 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2017/09/08 01:27:57 | send a packet PING_TIMEOUT : 30
DEBUG  | wrapperp | 2017/09/08 01:27:57 | send a packet PROPERTIES : (Property Values)
DEBUG  | wrapper  | 2017/09/08 01:27:57 | Start Application.
DEBUG  | wrapperp | 2017/09/08 01:27:57 | send a packet START : start
INFO   | jvm 1    | 2017/09/08 01:27:57 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 1    | 2017/09/08 01:27:57 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2017/09/08 01:27:57 | Received a packet PING_TIMEOUT : 30
INFO   | jvm 1    | 2017/09/08 01:27:57 | PingTimeout from Wrapper is 30000
INFO   | jvm 1    | 2017/09/08 01:27:57 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 1    | 2017/09/08 01:27:57 | Received a packet START : start
INFO   | jvm 1    | 2017/09/08 01:27:57 | calling WrapperListener.start()
INFO   | jvm 1    | 2017/09/08 01:27:57 | Waiting for WrapperListener.start runner thread to complete.
INFO   | jvm 1    | 2017/09/08 01:27:57 | WrapperListener.start runner thread started.
INFO   | jvm 1    | 2017/09/08 01:27:57 | WrapperListener.start runner thread stopped.
INFO   | jvm 1    | 2017/09/08 01:27:57 | returned from WrapperListener.start()
INFO   | jvm 1    | 2017/09/08 01:27:57 | Send a packet STARTED : 
INFO   | jvm 1    | 2017/09/08 01:27:57 | Startup runner thread stopped.
DEBUG  | wrapperp | 2017/09/08 01:27:57 | read a packet STARTED : 
DEBUG  | wrapper  | 2017/09/08 01:27:57 | JVM signalled that it was started.
INFO   | jvm 1    | 2017/09/08 01:28:00 | Exception in thread "pool-1-thread-1" java.lang.RuntimeException: java.net.UnknownHostException: home
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.nhs.uk.ohis.send.jsw.SendRunnable.run(SendRunnable.java:41)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.lang.Thread.run(Thread.java:748)
INFO   | jvm 1    | 2017/09/08 01:28:00 | Caused by: java.net.UnknownHostException: home
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.net.Socket.connect(Socket.java:589)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at java.net.Socket.connect(Socket.java:538)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.ftp.impl.FtpClient.doConnect(FtpClient.java:964)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.ftp.impl.FtpClient.tryConnect(FtpClient.java:924)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:1019)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.ftp.impl.FtpClient.connect(FtpClient.java:1005)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:294)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:400)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.core.io.UrlResource.getInputStream(UrlResource.java:167)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.core.io.support.EncodedResource.getInputStream(EncodedResource.java:143)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.core.io.support.PropertiesLoaderUtils.fillProperties(PropertiesLoaderUtils.java:98)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.core.io.support.PropertiesLoaderSupport.loadProperties(PropertiesLoaderSupport.java:175)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.core.io.support.PropertiesLoaderSupport.mergeProperties(PropertiesLoaderSupport.java:156)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:78)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:694)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:669)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:461)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:93)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.apache.camel.spring.Main.createDefaultApplicationContext(Main.java:217)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.apache.camel.spring.Main.doStart(Main.java:157)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   at org.nhs.uk.ohis.send.jsw.SendRunnable.run(SendRunnable.java:31)
INFO   | jvm 1    | 2017/09/08 01:28:00 |   ... 3 more
INFO   | jvm 1    | 2017/09/08 01:28:00 | Wrapper Manager: ShutdownHook started
INFO   | jvm 1    | 2017/09/08 01:28:00 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2017/09/08 01:28:00 | Send a packet STOP : 0
DEBUG  | wrapperp | 2017/09/08 01:28:00 | read a packet STOP : 0
DEBUG  | wrapper  | 2017/09/08 01:28:00 | JVM requested a shutdown. (0)
DEBUG  | wrapper  | 2017/09/08 01:28:00 | wrapperStopProcess(0) called.
DEBUG  | wrapper  | 2017/09/08 01:28:00 | Sending stop signal to JVM
DEBUG  | wrapperp | 2017/09/08 01:28:00 | send a packet STOP : NULL
INFO   | jvm 1    | 2017/09/08 01:28:00 | Received a packet STOP : 
INFO   | jvm 1    | 2017/09/08 01:28:01 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
INFO   | jvm 1    | 2017/09/08 01:28:01 | calling listener.stop()
INFO   | jvm 1    | 2017/09/08 01:28:01 | returned from listener.stop() -> 0
INFO   | jvm 1    | 2017/09/08 01:28:01 | shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2017/09/08 01:28:01 | Send a packet STOPPED : 0
DEBUG  | wrapperp | 2017/09/08 01:28:01 | read a packet STOPPED : 0
DEBUG  | wrapper  | 2017/09/08 01:28:01 | JVM signalled that it was stopped.
INFO   | jvm 1    | 2017/09/08 01:28:01 | Closing socket.
DEBUG  | wrapperp | 2017/09/08 01:28:01 | socket read no code (closed?).
DEBUG  | wrapperp | 2017/09/08 01:28:01 | server listening on port 32001.
INFO   | jvm 1    | 2017/09/08 01:28:01 | Wrapper Manager: ShutdownHook complete
INFO   | jvm 1    | 2017/09/08 01:28:01 | Server daemon shut down
DEBUG  | wrapper  | 2017/09/08 01:28:02 | JVM exited normally.
DEBUG  | wrapper  | 2017/09/08 01:28:02 | Signal trapped.  Details:
DEBUG  | wrapper  | 2017/09/08 01:28:02 |   signal number=17 (SIGCHLD), source="unknown"
DEBUG  | wrapper  | 2017/09/08 01:28:02 | Received SIGCHLD, checking JVM process status.
DEBUG  | wrapper  | 2017/09/08 01:28:02 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
STATUS | wrapper  | 2017/09/08 01:28:02 | <-- Wrapper Stopped

Any help will be appreciated

Unable to execute Java command.

Legioner — Mon, 21 Nov 2016 17:21:09 -0000

Hello we have a product that has a service that suddenly stopped running after server restart.
We have java.exe in place in the proper directory (../jre/bin) and all paths are available from the folder where the execution takes place. SYSTEM account also has all rights into the folders.I also checked and all the jar files indicated in below log are present in the system.
The OS is Windows and we have following in the wrapper log:

FATAL | wrapper | 2016/11/19 16:21:37 | Unable to execute Java command.
FATAL | wrapper | 2016/11/19 16:21:37 | "..\jre\bin\java" -Djavax.net.ssl.keyStore=C:/Cisco/CVP/conf/security/.ormKeystore -Djavax.net.ssl.keyStorePassword=<NEED_TO_MODIFY> -Djavax.net.ssl.keyStoreType=JCEKS -Djavax.net.ssl.trustStore=C:/Cisco/CVP/conf/security/.keystore -Djavax.net.ssl.trustStorePassword=<XXXXXXXXXX> -Djavax.net.ssl.trustStoreType=JCEKS -Dcom.sun.management.config.file=../conf/orm_jmx.properties -Dccbu.logging.config.file=log4j_orm.xml -Djava.rmi.server.hostname=192.168.1.15 -Djava.library.path="../lib" -classpath "../lib/wrapper.jar;../lib/jms.jar;../lib/log4j.jar;../lib/commons-lang.jar;../lib/commons-beanutils.jar;../lib/commons-io.jar;../lib/commons-collections.jar;../lib/commons-configuration.jar;../lib/cisco-util.jar;../lib/ccbu-common.jar;../lib/jaxb-api.jar;../lib/jaxb-impl.jar;../lib/jaxb1-impl.jar;../lib/stax-api.jar;../lib/jaxb-xjc.jar;../lib/cvp-common.jar;../lib/activation.jar;../lib/ccbu-auth.jar;../lib/ccbu-wsm.jar;../lib/dom4j.jar;../lib/jaxen.jar;../lib/ocom.jar;../lib/cmdsvc.jar;../lib/cliparser.jar;../lib/ftpserver-dev.jar;../lib/commons-logging.jar;../lib/commons-codec.jar;../lib/commons-httpclient.jar;../lib/orm.jar;../lib/jackson-core-asl.jar;../lib/jackson-mapper-asl.jar;../lib/jersey-bundle.jar;../lib/jersey-core.jar;../lib/jettison.jar;../lib/commons-vfs2.jar" -Dwrapper.key="XXXXXXXXXXXXXX" -Dwrapper.port=32000 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperStartStopApp com.cisco.cvp.oamp.orm.ORMStarter 1 start com.cisco.cvp.oamp.orm.ORMStarter false 1 stop
FATAL | wrapper | 2016/11/19 16:21:37 | Critical error: wait for JVM process failed

#304 Calls to http://wrapper.tanukisoftware.org from JVM hitting firewall

Leif Mortenson — Sat, 24 Sep 2016 12:16:44 -0000

The Wrapper or its Java has never opened any external connections so I am not sure what they would be seeting here.

Much later versions send emails and do remote logging, but both of those are to configured hosts.

Are they able to tell any information about what is the request?
Is it possible that another tool is making a request based on information in the Wrapper Jar's manifest?

Calls to http://wrapper.tanukisoftware.org from JVM hitting firewall

Benedict — Fri, 23 Sep 2016 15:24:34 -0000

Hi There,

We've had a query from one of our customers saying that the JVM our product is using is calling out to http://wrapper.tanukisoftware.org and its hitting their internal firewall.

We are not sure why this is happening and how to prevent it. Does anyone any ideas.

This is what is shows in our service log file.

STATUS | wrapper | 2016/07/20 03:09:59 | Launching a JVM...
INFO | jvm 1 | 2016/07/20 03:10:04 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2016/07/20 03:10:04 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
INFO | jvm 1 | 2016/07/20 03:10:04 |

#303 need support for s390x architecture community edition

Alexandre — Tue, 20 Sep 2016 02:30:19 -0000

Hi Prajakta,

I'm sorry for the delay to answer you.

Unfortunately we do not release the Wrapper s390x for community edition.

Only standard and professional editions are available and they require a license.

Please note that for example the Wrapper Standard edition will work with Mule Community edition. The Wrapper and Mule are 2 different software and the edition doesn't need to match.

Please let me know if you have any other questions.

Regards,
Alexandre Klein