[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] RUNNING XMLBLASTER AS WINDOWS SERVICE

JAYAGOPALAN BALASUBRAMANI wrote:

Hi all,
i have installed xmlBlaster server in windows 2000 with j2sdk1.4.0.

         Iam having problems in running XMLBLASTER AS WINDOWS SERVICE.

         I have follwed the instructions from Java Service Wrapper.


i am using wrapper_win32_3.0.3 for running a java application as service in windows 2000.

When i run the /bin/App.bat from the console
i get the following error message.

jvm 1 | [Jun 13, 2003 12:41:51 AM WARN Main-/node/http_172_42_172_10_3412] j
ava.io.IOException: System.in can not be used when the JVM is being controlled b
y the Java Service Manager. 

Hi,

i haven't tried it but probably this xmlBlaster option helps

  -useKeyboard false

which does prevent using System.in()

regards
Marcel


wrapper.conf

# Java Application
wrapper.java.command=java

# Java Main class
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/wrappertest.jar
wrapper.java.classpath.3=../lib/xmlBlaster.jar



# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib

# Java Additional Parameters
#wrapper.java.additional.1=
wrapper.java.additional.1=-Dprogram.name=xmlBlaster.bat


# Initial Java Heap Size (in MB)
wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=64

# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.xmlBlaster.Main

# Port which the native wrapper code will attempt to connect to
wrapper.port=1777

#********************************************************************
# 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=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/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=0

# 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=0

# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper NT 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=xmlBlaster

# Display name of the service
wrapper.ntservice.displayname=MOM SERVER

# Description of the service
wrapper.ntservice.description=MOM SERVER

# 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


#end of wrapper.conf

         Has any one wrapped xmlBlaster as service?

        Thanks in advance.


regds.
Jay