Menu
▾
▴
[Wrapper-user] Wrapper Startup problem
|
From: Saravanan S. <sha...@ya...> - 2006-08-21 18:00:53
|
Hello All, I am getting the below error message in couple of Windows 2000 server and in remaining servers it is working fine STATUS | wrapper | 2006/08/21 13:56:47 | --> Wrapper Started as Service STATUS | wrapper | 2006/08/21 13:56:47 | Launching a JVM... ERROR | wrapper | 2006/08/21 13:56:47 | Unable to write to the EventLog due to: The event log file is full. (0x5de) ERROR | wrapper | 2006/08/21 13:56:47 | Internally setting wrapper.syslog.loglevel=NONE to prevent further messages. INFO | jvm 1 | 2006/08/21 13:56:50 | From [21.08.2006 13:56:50][INFO ] File Client connected successfully to the Sonic Broker INFO | jvm 1 | 2006/08/21 13:56:50 | From [21.08.2006 13:56:50][INFO ] File Client ready to receive the files ERROR | wrapper | 2006/08/21 13:57:16 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2006/08/21 13:57:16 | ADVICE | wrapper | 2006/08/21 13:57:16 | ------------------------------------------------------------------------ ADVICE | wrapper | 2006/08/21 13:57:16 | Advice: ADVICE | wrapper | 2006/08/21 13:57:16 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2006/08/21 13:57:16 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2006/08/21 13:57:16 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2006/08/21 13:57:16 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2006/08/21 13:57:16 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2006/08/21 13:57:16 | the Wrapper classes: ADVICE | wrapper | 2006/08/21 13:57:16 | com.trw.fileclient.TRWFileReceiver ADVICE | wrapper | 2006/08/21 13:57:16 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2006/08/21 13:57:16 | classes to make this initialization processes automatic. ADVICE | wrapper | 2006/08/21 13:57:16 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2006/08/21 13:57:16 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2006/08/21 13:57:16 | within the Wrapper: ADVICE | wrapper | 2006/08/21 13:57:16 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2006/08/21 13:57:16 | ------------------------------------------------------------------------ ADVICE | wrapper | 2006/08/21 13:57:16 | ERROR | wrapper | 2006/08/21 13:57:16 | JVM did not exit on request, terminated STATUS | wrapper | 2006/08/21 13:57:21 | Launching a JVM... INFO | jvm 2 | 2006/08/21 13:57:22 | From [21.08.2006 13:57:22][INFO ] File Client connected successfully to the Sonic Broker INFO | jvm 2 | 2006/08/21 13:57:22 | From [21.08.2006 13:57:22][INFO ] File Client ready to receive the files ERROR | wrapper | 2006/08/21 13:57:50 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2006/08/21 13:57:50 | ADVICE | wrapper | 2006/08/21 13:57:50 | ------------------------------------------------------------------------ If I run the Wrapper command in console it is running without any issues. I am trying to resolve this more than 2 days and am not able to find any clue. Your help is highly appreciated. The configuration file details are *************************************************************************************************** # Java Application wrapper.java.command=C:\j2sdk1.4.2\jre\bin\java # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=com.trw.fileclient.TRWFileReceiver # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=D:\JWrapper\lib\wrapper.jar wrapper.java.classpath.2=D:\test\Receive\FileClient.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1= D:\JWrapper\lib # Java Additional Parameters #wrapper.java.additional.1= # Initial Java Heap Size (in MB) wrapper.java.initmemory=3 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=128 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1=com.trw.fileclient.TRWFileReceiver wrapper.working.dir=D:\test\Receive #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=DEBUG # Log file to use for wrapper output logging. wrapper.logfile=D:/test/receive/log/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=INFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=1000k # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=5 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=DEBUG #wrapper.request_thread_dump_on_failed_jvm_exit=TRUE wrapper.use_system_time=false #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wrapper.console.title=Test Wrapper Sample Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.ntservice.name= Test SAP File Client # Display name of the service wrapper.ntservice.displayname=Test SAP File Client # Description of the service wrapper.ntservice.description=JMS Client to transfer the files to QAD Servers # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false wrapper.ping.timeout=3600 #wrapper.restart.delay=300 #wrapper.max_failed_invocations=5 #wrapper.debug=true **************************************************************************************************** Thanks in advance,. |
