1 Reply Latest reply on Mar 16, 2004 1:21 PM by marcos taro

    [Win2k.Service] XML problem when starting

    marcos taro Newbie

      I just got the Java Service Wrapper (http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html) and I'm using the method integration 2. When I try to run I got this exception:
      -----------------------------------------------
      2004-03-16 15:46:19,283 WARN [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config: file:/C:/jboss-3.2.3/server/default/conf/login-config.xml
      org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1.
      Was expecting one of:

      ...

      at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:389)
      at org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:327)
      at org.jboss.security.auth.login.SunConfigParser.config(SunConfigParser.java:98)
      at org.jboss.security.auth.login.SunConfigParser.parse(SunConfigParser.java:57)
      at org.jboss.security.auth.login.SunConfigParser.doParse(SunConfigParser.java:79)
      at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:273)
      at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:257)
      at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:233)
      at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:152)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:534)
      2004-03-16 15:46:19,293 INFO [org.jboss.security.auth.login.XMLLoginConfig] Started jboss.security:service=XMLLoginConfig
      -----------------------------
      Before I already tried to use another javaService tool (http://www.alexandriasc.com/software/JavaService/documentation.html) but I was getting the same error.
      Does anyone knows what's happening???

      thanks in advance.

        • 1. Re: [Win2k.Service] XML problem when starting
          marcos taro Newbie

          Here is my conf file:


          #********************************************************************
          # Wrapper Properties
          #********************************************************************
          # Java Application
          wrapper.java.command=C:/j2sdk1.4.2_03/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=org.tanukisoftware.wrapper.WrapperStartStopApp

          # Java Classpath (include wrapper.jar) Add class path elements as
          # needed starting from 1

          wrapper.java.classpath.1=C:/jboss-3.2.3/lib/wrapper.jar
          wrapper.java.classpath.2=C:/jboss-3.2.3/bin/run.jar
          wrapper.java.classpath.3=C:/jboss-3.2.3/bin/shutdown.jar
          wrapper.java.classpath.4=C:/jboss-3.2.3/lib/jdom.jar
          wrapper.java.classpath.5=C:/jboss-3.2.3/lib/commons-logging.jar
          wrapper.java.classpath.6=C:/jboss-3.2.3/lib/concurrent.jar
          wrapper.java.classpath.7=C:/jboss-3.2.3/lib/getopt.jar
          wrapper.java.classpath.8=C:/jboss-3.2.3/lib/gnu-regexp.jar
          wrapper.java.classpath.9=C:/jboss-3.2.3/lib/jboss-boot.jar
          wrapper.java.classpath.10=C:/jboss-3.2.3/lib/jboss-common.jar
          wrapper.java.classpath.11=C:/jboss-3.2.3/lib/jboss-jmx.jar
          wrapper.java.classpath.12=C:/jboss-3.2.3/lib/jboss-system.jar
          wrapper.java.classpath.13=C:/jboss-3.2.3/lib/commons-httpclient.jar
          wrapper.java.classpath.14=C:/jboss-3.2.3/lib/log4j-boot.jar
          wrapper.java.classpath.15=C:/jboss-3.2.3/lib/webdavlib.jar
          wrapper.java.classpath.16=C:/jboss-3.2.3/lib/xercesImpl.jar
          wrapper.java.classpath.17=C:/jboss-3.2.3/lib/xml-apis.jar


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

          # Java Additional Parameters
          #wrapper.java.additional.1=

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

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

          # The first application parameter is the name of the class whose main
          # method is to be called when the application is launched. The class
          # name is followed by the number of parameters to be passed to its main
          # method. Then comes the actual parameters.
          wrapper.app.parameter.1=org.jboss.Main
          wrapper.app.parameter.2=0


          # The start parameters are followed by the name of the class whose main
          # method is to be called to stop the application. The stop class name
          # is followed by a flag which controls whether or not the Wrapper should
          # wait for all non daemon threads to complete before exiting the JVM.
          # The flag is followed by the number of parameters to be passed to the
          # stop class's main method. Finally comes the actual parameters.
          wrapper.app.parameter.3=org.jboss.Shutdown
          wrapper.app.parameter.4=true
          wrapper.app.parameter.5=0




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

          # Display name of the service
          wrapper.ntservice.displayname=JBoss

          # Description of the service
          wrapper.ntservice.description=JBoss 3.2.3

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

          # Allow the service to interact with the desktop.
          wrapper.ntservice.interactive=false