<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/wrapper/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/wrapper/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/wrapper/discussion/</id><updated>2019-12-20T14:14:15.469000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>Disabling TLS Version 1</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/41a8680b63/?limit=25#009e" rel="alternate"/><published>2019-12-20T14:14:15.469000Z</published><updated>2019-12-20T14:14:15.469000Z</updated><author><name>Steven M Nelligan</name><uri>https://sourceforge.net/u/snelliga/</uri></author><id>https://sourceforge.neta092f33dd5810f8143f5b92ad148af29ebc5d924</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am running Mule ESB version 3.2.0 with Java Service Wrapper Standard Edition 64-bit 3.5.53.&lt;br/&gt;
I am running Java 7&lt;br/&gt;
I need to disable protocol TSLv1.&lt;br/&gt;
I've changed the configuration file wrapper-additional.conf to only specify TLSv1.2. (see attached conf file)&lt;br/&gt;
Per the log file, ClientHello is using TLSv1 (see attached log file)&lt;/p&gt;
&lt;p&gt;I need to force TLSv1.2.&lt;/p&gt;
&lt;p&gt;Do I need a new version of the wrapper?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Problem disabling TLSv1</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/03566a2753/?limit=25#3abe" rel="alternate"/><published>2019-12-20T14:00:55.755000Z</published><updated>2019-12-20T14:00:55.755000Z</updated><author><name>Steven M Nelligan</name><uri>https://sourceforge.net/u/snelliga/</uri></author><id>https://sourceforge.net13725bd5b01905dcc97464d981b6ab4fe56639a9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Is this the corrrect forum for this type of question?&lt;br/&gt;
Would there be a better source of information?&lt;/p&gt;
&lt;p&gt;Thanks in advance&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Problem disabling TLSv1</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/03566a2753/?limit=25#edee" rel="alternate"/><published>2019-12-19T14:37:11.197000Z</published><updated>2019-12-19T14:37:11.197000Z</updated><author><name>Steven M Nelligan</name><uri>https://sourceforge.net/u/snelliga/</uri></author><id>https://sourceforge.net896ac1989b87162ec64594f1e25dfe1637661675</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am running Mule ESB version 3.2.0 with Java Service Wrapper Standard Edition 64-bit 3.5.53.&lt;br/&gt;
I am running Java 7&lt;br/&gt;
I need to disable protocol TSLv1.&lt;br/&gt;
I've changed the configuration file wrapper-additional.conf to only specify TLSv1.2. (see attached conf file)&lt;br/&gt;
Per the log file, ClientHello is using TLSv1 (see attached log file)&lt;/p&gt;
&lt;p&gt;I need to force TLSv1.2.&lt;/p&gt;
&lt;p&gt;Do I need a new wrapper?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Wrapper in Zombie state</title><link href="https://sourceforge.net/p/wrapper/discussion/122337/thread/8f91f7cccf/?limit=25#a72b" rel="alternate"/><published>2019-01-22T00:13:24.512000Z</published><updated>2019-01-22T00:13:24.512000Z</updated><author><name>Leif Mortenson</name><uri>https://sourceforge.net/u/mortenson/</uri></author><id>https://sourceforge.net654810f40a7ad3b92612460c8d8607fcaaf7ddac</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Muhammad&lt;br/&gt;
Please be sure to read over the Method 3 documentation.&lt;br/&gt;
This is custom code on your end so it is not possible to help much without seeing the source.&lt;br/&gt;
But there is nothing in the log about the WrapperManager being initialized and the notice that you are seeing happens when the WrapperManager and your WrapperListener.start method complete.  So most likely the Java code is not written correctly..&lt;br/&gt;
Nothing about the Wrapper or Linux upgrade should have affected this.  Maybe your code has different logic based on the environment?&lt;br/&gt;
Please add some debug output to your code and make sure that &lt;/p&gt;
&lt;hr/&gt;
&lt;p&gt;WrapperManager.start( new Main(), args );&lt;/p&gt;
&lt;hr/&gt;
&lt;p&gt;is being called, and that your WrapperListener.start is being called and returns a value.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;br/&gt;
Leif&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Wrapper in Zombie state</title><link href="https://sourceforge.net/p/wrapper/discussion/122337/thread/8f91f7cccf/?limit=25#91fc" rel="alternate"/><published>2019-01-21T11:51:43.832000Z</published><updated>2019-01-21T11:51:43.832000Z</updated><author><name>Muhammad Jamil Chaudhary</name><uri>https://sourceforge.net/u/mjamilc/</uri></author><id>https://sourceforge.netb587abd25f213c1da4e80a1ef64be13f5dd57e4b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Lief,&lt;/p&gt;
&lt;p&gt;Thank you for your kind response.&lt;br/&gt;
Yes we are using 3 and made a class GenericEngineStarter to use in our applications.&lt;/p&gt;
&lt;p&gt;I am looking the class how our developer implemented the GenericEngineStarter and  WrapperManager class.&lt;/p&gt;
&lt;p&gt;Answer to your question is YES we are using few tools to get the detail from the log of the applications to triggering alerts and doing some statistics.&lt;/p&gt;
&lt;p&gt;Is there any easy way to control shut down and start of application in the hanging state&lt;/p&gt;
&lt;p&gt;Should I consider to use lated version of wrapper 3.5.36?&lt;/p&gt;
&lt;p&gt;here are few we are already configured &lt;/p&gt;
&lt;p&gt;wrapper.on_exit.default=RESTART&lt;/p&gt;
&lt;p&gt;wrapper.on_exit.0=RESTART&lt;/p&gt;
&lt;p&gt;wrapper.on_exit.99=SHUTDOWN&lt;/p&gt;
&lt;p&gt;wrapper.ntservice.process_priority=LOW&lt;/p&gt;
&lt;p&gt;wrapper.ping.interval=5&lt;/p&gt;
&lt;p&gt;wrapper.ping.timeout=30&lt;/p&gt;
&lt;p&gt;wrapper.ping.timeout.action=DUMP,RESTART&lt;/p&gt;
&lt;p&gt;wrapper.ping.alert.threshold=1&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Wrapper in Zombie state</title><link href="https://sourceforge.net/p/wrapper/discussion/122337/thread/8f91f7cccf/?limit=25#8109" rel="alternate"/><published>2019-01-21T11:11:20.013000Z</published><updated>2019-01-21T11:11:20.013000Z</updated><author><name>Leif Mortenson</name><uri>https://sourceforge.net/u/mortenson/</uri></author><id>https://sourceforge.net063a54c0792d82fbfb2ee971a176ef2abe7fab75</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Are you attempting to use Integration method 3?  This would mean that your GenericEngineStarter class is directly or indirectly implementing the WrapperListener interface.&lt;br/&gt;
In this case you need to be starting up the WrapperManager and then calling start with the WrapperListener instance.  It is then important that your WrapperListener.start method always return in a timely manner.  Please see the following page for details:&lt;br/&gt;
&lt;a href="https://wrapper.tanukisoftware.com/doc/english/integrate-listener.html" rel="nofollow"&gt;https://wrapper.tanukisoftware.com/doc/english/integrate-listener.html&lt;/a&gt;&lt;br/&gt;
The error you see will happen if the WrapperManager is never set up correctly or if the WrapperListener.start method is never returned.&lt;/p&gt;
&lt;p&gt;In general we recommend using one of the more simple integration methods (1, 2, or 4) unless absolutely necessary.&lt;br/&gt;
&lt;a href="https://wrapper.tanukisoftware.com/doc/english/integrate.html" rel="nofollow"&gt;https://wrapper.tanukisoftware.com/doc/english/integrate.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I have a question for you though.&lt;br/&gt;
It looks like all of your Java side log output is being sent to a different log tool, so nothing is being sent to the console.&lt;br/&gt;
How and why are you doing this?  The wrapper has a number of useful features which rely on this output so I want to understand what you are doing to help with our design of the product.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br/&gt;
Leif&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Wrapper in Zombie state</title><link href="https://sourceforge.net/p/wrapper/discussion/122337/thread/8f91f7cccf/?limit=25#04ca" rel="alternate"/><published>2019-01-21T10:36:56.922000Z</published><updated>2019-01-21T10:36:56.922000Z</updated><author><name>Muhammad Jamil Chaudhary</name><uri>https://sourceforge.net/u/mjamilc/</uri></author><id>https://sourceforge.net68c90de15af3cbe210a08916932f4f9e80f685d0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We did OS upgrade from 6.5 to 6.9 of Linux. After upgrade few of our applications start behaving strange. Wrapper Version is 3.5.26,  JDK version 1.7.0_71.&lt;/p&gt;
&lt;p&gt;It looks JVM stuck on shut down until manualy stop the service.&lt;br/&gt;
In the stack trace of wrapper i can see which is not giving any helpfull detail.&lt;/p&gt;
&lt;p&gt;Log detail of wrapper:&lt;/p&gt;
&lt;p&gt;EBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[Connection]&lt;/span&gt; | Connection retrieved from the pool: oracle.jdbc.driver.T4CConnection@45fda6a8&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[Connection]&lt;/span&gt; | Setting a statement cache size of: 25&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[TX]&lt;/span&gt; | Connection created com.CDRator.billing.support.core.StatefulBroker@77084cb5&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[SQL.UPDATE.PROCESS_MONITOR]&lt;/span&gt; | SQL Update: 1-  Records:1 - UPDATE PROCESS_MONITOR SET NAME = 'CellCWholesale_CDRExport_FNB1', TIMEOUT = 60, COMPUTER = 'lxtpcwb01.cellc.net', ALERT_TIMESTAMP = to_date('2019-01-21 10:24:48', 'yyyy-mm-dd hh24:mi:ss'), ALERT_RECEIPIENT_GROUP_ID = 201411191322367901, ENABLED = 1, EMAIL_MESSAGE_UP = 'CellCWS CellCWholesale_CDRExport_FNB1 is back up.', EMAIL_SUBJECT_UP = 'CellCWS CellCWholesale_CDRExport_FNB1 is back up.', SMS_MESSAGE_UP = 'CellCWs CellCWholesale_CDRExport_FNB1 is back up.', IS_DOWN = 0, CONFIRM_UP = 1, SMS_MESSAGE = 'CellCWS CellCWholesale_CDRExport_FNB1 is down.  Its last succesful run was at LABEL@LASTRUN.', EMAIL_MESSAGE = 'CellCWS CellCWholesale_CDRExport_FNB1 is down.  Its last succesful run was at LABEL@LASTRUN.', EMAIL_SUBJECT = 'CellCWS CellCWholesale_CDRExport_FNB1 is down.', DO_STATISTIC_LOGGING = '', LOG_ZERO_REC_STATISTIC = '' WHERE ID = 201612151424502401&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[Connection]&lt;/span&gt; | Connection being released to the pool: oracle.jdbc.driver.T4CConnection@45fda6a8&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[TX]&lt;/span&gt; | Connection released com.CDRator.billing.support.core.StatefulBroker@77084cb5&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | &lt;span&gt;[TX]&lt;/span&gt; | Skipping commitTransactionToken, token is false com.CDRator.billing.support.core.StatefulBroker@77084cb5&lt;br/&gt;
DEBUG | 2019-01-21 10:22:19 | &lt;span&gt;[appMain]&lt;/span&gt; | Wait for internal delay of 1000&lt;span&gt;[ms]&lt;/span&gt;&lt;br/&gt;
 INFO | 2019-01-21 10:22:20 | &lt;span&gt;[appMain]&lt;/span&gt; | Engine has exceeded time to live (1800000ms)&lt;br/&gt;
 INFO | 2019-01-21 10:22:20 | &lt;span&gt;[appMain]&lt;/span&gt; | Engine shutting down...&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: ShutdownHook started&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Send a packet STOP : 0&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Pausing for 1,000ms to allow a clean shutdown...&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Control-Event-Monitor]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Stopped checking for control events.&lt;br/&gt;
DEBUG | 2019-01-21 10:22:20 | &lt;span&gt;[Wrapper-Connection]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Received a packet STOP : &lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Thread, Wrapper-Shutdown-Hook, handling the shutdown process.&lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: calling listener.stop()&lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: returned from listener.stop() -&amp;gt; 0&lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: shutdownJVM(0) Thread: Wrapper-Shutdown-Hook&lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: wait for 0 shutdown locks to be released.&lt;br/&gt;
DEBUG | 2019-01-21 10:22:21 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Send a packet STOPPED : 0&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Closing backend connection.&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Connection]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Closed backend socket (Normal): java.net.SocketException: Socket closed&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Connection]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Returned from backend handler.&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: ShutdownHook complete&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Connection]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: Server daemon shut down&lt;br/&gt;
DEBUG | 2019-01-21 10:22:22 | &lt;span&gt;[Wrapper-Shutdown-Hook]&lt;/span&gt; | &lt;span&gt;[SysOut]&lt;/span&gt; | WrapperManager Debug: WrapperManger stopped due to Shutdown Hook&lt;/p&gt;
&lt;p&gt;Now time is 10:35 &lt;/p&gt;
&lt;p&gt;In Wrapper log&lt;/p&gt;
&lt;p&gt;ERROR  | wrapper  | 2019/01/21 10:32:45 | JVM did not exit on request, termination requested.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 | Signal trapped.  Details:&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 |   signal number=17 (SIGCHLD), source="unknown"&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 | Received SIGCHLD, checking JVM process status.&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:32:45 | JVM received a signal SIGKILL (9).&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:32:45 | JVM process is gone.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 | JVM process exited with a code of 1, setting the wrapper exit code to 1.&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:32:45 | JVM exited after being requested to terminate.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 | Preparing to restart with mode 2.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:32:45 | Waiting 60 seconds before launching another JVM.&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:33:45 | Reloading Wrapper configuration...&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Working directory set to: /apps/RATOR/engines/wrapper/3.5.26/bin&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Working directory set to: /apps/RATOR/engines/CellCWholesale_CDRExport_FNB&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Working directory set to: /apps/RATOR/engines/CellCWholesale_CDRExport_FNB&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Resolved the real path of wrapper.java.command as an absolute reference: /apps/java/jdk1.7.0_71/bin/java&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Magic number for file /apps/java/jdk1.7.0_71/bin/java: 0x7f454c46&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Startup Timeouts: wrapper.startup.timeout=30, wrapper.startup.delay.console=0, wrapper.startup.delay.service=0, wrapper.restart.delay=60&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30, wrapper.ping.alert.threshold=1&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Shutdown Timeouts: wrapper.shutdown.timeout=30, wrapper.jvm_exit.timeout=15, wrapper.jvm_cleanup.timeout=10, wrapper.jvm_terminate.timeout=10&lt;br/&gt;
DEBUG  | wrapperp | 2019/01/21 10:33:45 | Send a packet LOGFILE : wrapper.log&lt;br/&gt;
DEBUG  | wrapperp | 2019/01/21 10:33:45 | Socket send failed.  Bad file descriptor&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | active log file changed: wrapper.log&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:33:45 | Launching a JVM...&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 | Java Command Line:&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[0]&lt;/span&gt; : /apps/java/jdk1.7.0_71/bin/java&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[1]&lt;/span&gt; : -Xms10m&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[2]&lt;/span&gt; : -Xmx2048m&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[3]&lt;/span&gt; : -Djava.library.path=/apps/RATOR/engines/wrapper/3.5.26/lib&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[4]&lt;/span&gt; : -classpath&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[5]&lt;/span&gt; : /apps/RATOR/engines/lib-bootstrap:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-advanced-queuing.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-management_console-bootstrap_persistence.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-management_console-commands.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-management_console-core.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-management_console-engine_framework.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/rator-management_console-remote_logging.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/aqapi.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/jackson-core-asl.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/jackson-mapper-asl.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/javax.jms.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/jta.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/ojdbc6.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/ojdbc14.jar:/apps/RATOR/engines/lib-bootstrap/Rator/lib/3rdparty/wrapper.jar&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[6]&lt;/span&gt; : -Dwrapper.key=NjQn3cUnOjtNFWQoJgsAlIP_jPKsIlgY&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[7]&lt;/span&gt; : -Dwrapper.port=32037&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[8]&lt;/span&gt; : -Dwrapper.debug=TRUE&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[9]&lt;/span&gt; : -Dwrapper.disable_console_input=TRUE&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[10]&lt;/span&gt; : -Dwrapper.pid=4967&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[11]&lt;/span&gt; : -Dwrapper.version=3.5.26-st&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[12]&lt;/span&gt; : -Dwrapper.native_library=wrapper&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[13]&lt;/span&gt; : -Dwrapper.arch=x86&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[14]&lt;/span&gt; : -Dwrapper.service=TRUE&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[15]&lt;/span&gt; : -Dwrapper.cpu.timeout=10&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[16]&lt;/span&gt; : -Dwrapper.jvmid=794&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[17]&lt;/span&gt; : -Dwrapper.lang.domain=wrapper&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[18]&lt;/span&gt; : -Dwrapper.lang.folder=../lang&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[19]&lt;/span&gt; : com.CDRator.billing.engine.GenericEngineStarter&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[20]&lt;/span&gt; : -R&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[21]&lt;/span&gt; : CellCWholesale_CDRExport_FNB&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:33:45 |   Command&lt;span&gt;[22]&lt;/span&gt; : -P&lt;br/&gt;
INFO   | jvm 794  | 2019/01/21 10:33:45 | GenericEngineStarter.main()&lt;br/&gt;
INFO   | jvm 794  | 2019/01/21 10:33:45 | bootstrap properties file used: file:/apps/RATOR/engines/lib-bootstrap/bootstrap.properties&lt;br/&gt;
ERROR  | wrapper  | 2019/01/21 10:34:14 | Startup failed: Timed out waiting for a signal from the JVM.&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | &lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | ------------------------------------------------------------------------&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | Advice:&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | The Wrapper consists of a native component as well as a set of classes&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | which run within the JVM that it launches.  The Java component of the&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | Wrapper must be initialized promptly after the JVM is launched or the&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | Wrapper will timeout, as just happened.  Most likely the main class&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | specified in the Wrapper configuration file is not correctly initializing&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | the Wrapper classes:&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 |     com.CDRator.billing.engine.GenericEngineStarter&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | While it is possible to do so manually, the Wrapper ships with helper&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | classes to make this initialization processes automatic.&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | Please review the integration section of the Wrapper's documentation&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | for the various methods which can be employed to launch an application&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | within the Wrapper:&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 |     &lt;a href="http://wrapper.tanukisoftware.com/doc/english/integrate.html" rel="nofollow"&gt;http://wrapper.tanukisoftware.com/doc/english/integrate.html&lt;/a&gt;&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | ------------------------------------------------------------------------&lt;br/&gt;
ADVICE | wrapper  | 2019/01/21 10:34:14 | &lt;br/&gt;
ERROR  | wrapper  | 2019/01/21 10:34:14 | JVM did not exit on request, termination requested.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 | Signal trapped.  Details:&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 |   signal number=17 (SIGCHLD), source="unknown"&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 | Received SIGCHLD, checking JVM process status.&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:34:14 | JVM received a signal SIGKILL (9).&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:34:14 | JVM process is gone.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 | JVM process exited with a code of 1, setting the wrapper exit code to 1.&lt;br/&gt;
STATUS | wrapper  | 2019/01/21 10:34:14 | JVM exited after being requested to terminate.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 | Preparing to restart with mode 2.&lt;br/&gt;
DEBUG  | wrapper  | 2019/01/21 10:34:14 | Waiting 60 seconds before launching another JVM.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Could not find method getJMSDestination in class com.ibm.mq.jms.MQQueue</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/49c4257d/?limit=25#5d19" rel="alternate"/><published>2018-08-06T11:43:15.961000Z</published><updated>2018-08-06T11:43:15.961000Z</updated><author><name>Moorthy</name><uri>https://sourceforge.net/u/moorthyrajendra/</uri></author><id>https://sourceforge.net9ffd5aa8f49e3a927172fa0b309dd3bb14f1a13d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;we are using tanuki wrapper with tc server. we are getting below INFO log at wrapper.log. Looks like it's JVM log but not sure why this info log are displaying in wrapper.log&lt;/p&gt;
&lt;p&gt;can we consider this as normal and ignore?&lt;/p&gt;
&lt;p&gt;INFO   | jvm 1    | 2018/06/25 11:16:17 | Wrapper (Version 3.2.3) &lt;a href="http://wrapper.tanukisoftware.org" rel="nofollow"&gt;http://wrapper.tanukisoftware.org&lt;/a&gt;&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:17 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:17 | &lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:18 | Jun 25, 2018 11:16:18 AM org.apache.catalina.startup.Catalina load&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:18 | INFO: Initialization processed in 873 ms&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:19 | 2018-06-25 11:16:19 &lt;span&gt;[000004a0]&lt;/span&gt; info    &lt;span&gt;[native]&lt;/span&gt; License = license ok; &lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:34 | Jun 25, 2018 11:16:34 AM org.apache.catalina.startup.Catalina start&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:16:34 | INFO: Server startup in 16173 ms&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:20:10 | 2018-06-25 11:20:10 &lt;span&gt;[00001cb8]&lt;/span&gt; debug   &lt;span&gt;[java  ]&lt;/span&gt; &lt;span&gt;[messaging ]&lt;/span&gt; Could not find method getJMSDestination in class com.ibm.mq.jms.MQQueue&lt;br/&gt;
INFO   | jvm 1    | 2018/06/25 11:20:24 | 2018-06-25 11:20:24 &lt;span&gt;[00001cb8]&lt;/span&gt; debug   &lt;span&gt;[java  ]&lt;/span&gt; &lt;span&gt;[messaging ]&lt;/span&gt; Could not find method getJMSDestination in class com.ibm.mq.jms.MQQueue&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Profiling JVM that has been wrapped by Tanuki Wrapper as Windows Service</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/d2f35362/?limit=25#67a0" rel="alternate"/><published>2017-09-12T12:12:43.080000Z</published><updated>2017-09-12T12:12:43.080000Z</updated><author><name>Ahmad Fauzi</name><uri>https://sourceforge.net/u/fauzi16/</uri></author><id>https://sourceforge.net7802b4d779a3ef6dbd47ace756a5f68b3e862a76</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I'm new with Tanuki Wrapper, I have Java Application that been wrapped with Tanuki Wrapper into Windows Service, I found "Pinging the JVM took 4 seconds to respond." and need to investigate and profile about the application JVM, but unfortunately profiler software like JProfiler or jvisuamvm can not detect any running JVM. Even I open windows Task Manager and check the running service I find java.exe that I believe it is my running application, but again i suspect that it caused by already been wrapped as windows service make JProfiler and JvisualVM unable to detect / profile the my running application's JVM.&lt;/p&gt;
&lt;p&gt;Is it possible to make JVM visible and is detected for profiler software to be able to profile it ? whether do i have to adding new property or something else ?&lt;/p&gt;
&lt;p&gt;Really appreciate for any comment..&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>tanuki wrapper 3.5.30 and openJPA enhanced request</title><link href="https://sourceforge.net/p/wrapper/discussion/122338/thread/2b5525a5/" rel="alternate"/><published>2016-07-26T03:31:09.845000Z</published><updated>2016-07-26T03:31:09.845000Z</updated><author><name>julian</name><uri>https://sourceforge.net/u/juescude/</uri></author><id>https://sourceforge.net07ad9f1912434031913f7ac612027e2b5eb2a645</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I´m new with the tanuki and I have been experiencing some problem trying to run Apache OpenJAP on the warreper, the main problem is wen I run the project on eclipse works fine, but on tanuki I got the following error:&lt;/p&gt;
&lt;p&gt;org.apache.openjpa.persistence.ArgumentException: This configuration disallows runtime optimization, but the following listed types were not enhanced at build time or at class load time with a javaagent&lt;/p&gt;
&lt;p&gt;I have tried to place the persistence.xml file in the META-INF with not much success, so if some one hade this problem I will apreciate some tips&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>