1 Reply Latest reply on Jan 2, 2009 11:34 PM by jaikiran pai

    DS files not being loaded when using wrapper - w2k3

    Chris R Newbie

      Ok, I apologize if this is the wrong forum, if so mods please move. I am running JBoss 4.0.3 (upgrading isn't an option). I have two separate instances running as a windows service (windows server 2003 w/sp1) using the wrapper. When I start up the AS as a service it fails to use the xxxxx-ds.xml file located under \server\default\deploy, it uses some other local-tx-datastore file. What is interesting though is if i start the AS from the command line (run.bat) with no options it works correctly. There doesn't seem to be any errors in the log file, but this is my first time dealing with ds files in jboss. Any reason for this? Below is the wrapper.conf and the ds file. thanks in advanced....

      # Wrapper Properties
      # Java Application
      # 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.
      # Java Classpath (include wrapper.jar) Add class path elements as
      # needed starting from 1
      # Java Library Path (location of Wrapper.DLL or libwrapper.so)
      # Java Additional Parameters
      # Initial Java Heap Size (in MB)
      # Maximum Java Heap Size (in MB)
      # Application parameters. Add parameters as needed starting from 1
      wrapper.app.parameter.3=-c default
      # Wrapper Logging Properties
      # Format of output for the console. (See docs for formats)
      # Log Level for console output. (See docs for log levels)
      # Log file to use for wrapper output logging.
      # Format of output for the log file. (See docs for formats)
      # Log Level for log file output. (See docs for log levels)
      # 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.
      # Maximum number of rolled log files which will be allowed before old
      # files are deleted. The default value of 0 implies no limit.
      # Log Level for sys/event log output. (See docs for log levels)
      # Wrapper Windows Properties
      # Title to use when running as a console
      wrapper.console.title=JBoss Console 2
      # 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=JBoss 2
      # Display name of the service
      wrapper.ntservice.displayname=JBoss Service (v4.0.3 SP1) 2
      # Description of the service
      wrapper.ntservice.description=JBoss Application Server
      # Service dependencies. Add dependencies as needed starting from 1
      # Mode in which the service is installed. AUTO_START or DEMAND_START
      # Allow the service to interact with the desktop.


      FYI the 'X's are info i removed.

        • 1. Re: DS files not being loaded when using wrapper - w2k3
          jaikiran pai Master


          Is this an intentional setting you have done? When you start without this parameter from the command line, i guess this value is DefaultPartition. If you don't need this, then remove it from the wrapper.conf (and make sure, when you remove, you renumber those properties correctly).


          Is this an actual value in that conf file? Or did you modify this while posting? 1) There should be a space separating the -b and the IP address (2) The IP address must be a valid one.

          wrapper.app.parameter.3=-c default

          Though this param suggests that you are starting the "default" server profile, when you start the service, are you sure the "default" profile is being started? You can look at the log file (boot.log and server.log) to see which profile is being started.

          Ok, I apologize if this is the wrong forum

          Looks like a jboss service configuration question than JCA, so Installation & Configuration forum http://www.jboss.com/index.html?module=bb&op=viewforum&f=61 would have been the right place :-)