Is your environment 64-bit? The wrapper has issues with 64-bit Windows. If that is your case you need a compile of the wrapper that is for 64-bit or buy it from Tanuki since the community edition is flaky on 64-bit.
http://apachejames.wordpress.com/ Simon maintains 64-bit compile - which can be used if you like: http://www.krenger.ch/blog/tag/java-service-wrapper/ On Friday, February 28, 2014 2:08 PM, Phillip Odam <phillip.o...@nitorgroup.com> wrote: Hi Jerry I don't think you're going to find much if anything in the JAMES source code relating to the Java Service Wrapper (JSW). What you will find is the configuration file conf/wrapper.conf which points to the standard entry point for JAMES (org.apache.james.app.spring.JamesAppSpringMain). If you're just worried about starting and stopping JAMES that's about all there is to it. Thanks Phillip On 2/28/14, 6:43 PM, Jerry M wrote: > I understand. Thanks, Juan. > > If I have to dig in and debug this myself, so be it. I can do that. > But I finally got the code downloaded, and the only two java files > with "wrapper" in the filename are MimeWrapper classes. So I will > need a couple of pointers about where to start on this. Is there some > documentation on how the wrapper is supposed to talk to JAMES and what > JAMES code is supposed to be responding with, and what JAMES class the > wrapper is communicating with, etc? > > Thx. > > > On 2/28/2014 5:52 AM, Juan Larriba wrote: >> I'm sorry I can't help anymore here, as I use James on Linux only, >> where the Tanuki service (daemon) works wonderfully! >> >> El 2014-02-28 03:04, Jerry M escribió: >>> I've mentioned this problem briefly in an earlier thread. But it is >>> really a different problem from the one in that thread. So I'm >>> starting a new thread for it. >>> >>> The problem.... I tried intalling the JAMES 3.0 service in Windows >>> Server 2008. (Right out of the box... no config changes). The >>> wrapper install says it worked fine. But it fails to start. I tried >>> running the wrapper in console mode and got the same error. I set the >>> log levels to debug in the conf file. The wrapper tries the same >>> thing five times and fails each time. So the log file snippit below >>> is one of those 5 times. >>> >>> JAMES does start up at least a little bit. All of the log files for >>> JAMES get created with zero length in the log directory. So I know >>> JAMES is getting at least a little bit started. >>> >>> The log says it sends several packets to "the JVM" which I'm assuming >>> mean "JAMES". But then it gets a socket send failure when it tries to >>> send a "START" command. >>> >>> I googled this and saw a post where somebody was using the same Tanuki >>> wrapper code (but not for JAMES) and got this same situation. >>> According to the post, the answer was to reduce the length of the >>> command line. Well... 6419 characters in the JAMES command line could >>> certain qualify as 'long'. But I'm not about to go in and try to >>> figure out if there's any way to take stuff out and shorten it. >>> >>> This is a solid failure. I have never gotten JAMES 3 to run as a >>> service (which is kinda important for a production environment). But >>> I have been running JAMES 2.x.x as a service for years. I also run >>> Apache, Tomcat, MySQL, and several other services without problem. >>> I'm running Java 7. And (thanks to much help from you folks) the >>> JAMES 3.0 server is running on this box, unfortunately only in command >>> line mode at this point. So this is not a JAMES config problem. >>> >>> I'm lost on this. I have no clue why there is a bunch of socket >>> communication, etc. But it isn't working. >>> >>> Can somebody give me some help on this? Is anyone else running James >>> 3 as a service in Windows? >>> >>> Thx. >>> >>> Jerry >>> >>> =============== Wrapper.log =======>> >>> >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | server listening on port >>> 32001. >>> STATUS | wrapper | 2014/02/27 15:16:47 | Launching a JVM... >>> >>> DEBUG | wrapper | 2014/02/27 15:16:47 | command: "C:\Program Files >>> (x86)\Java\jdk1.7.0_05\jre\bin\java.exe" >>> -XX:+HeapDumpOnOutOfMemoryError -Dcom.sun.management.jmxremote=true >>> -Dcom.sun.management.jmxremote.authenticate=false....... >>> ================>> to 6419 characters...... >>> >>> DEBUG | wrapper | 2014/02/27 15:16:47 | JVM started (PID=4624) >>> INFO | jvm 1 | 2014/02/27 15:16:47 | WrapperManager class >>> initialized by thread: main Using classloader: >>> sun.misc.Launcher$AppClassLoader@1ed2ae8 >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Wrapper (Version 3.2.3) >>> http://wrapper.tanukisoftware.org/ >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Copyright 1999-2006 Tanuki >>> Software, Inc. All Rights Reserved. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Wrapper Manager: JVM #1 >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Running a 32-bit JVM. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Wrapper Manager: Registering >>> shutdown hook >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Wrapper Manager: Using >>> wrapper >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Load native library. One or >>> more attempts may fail if platform specific libraries do not exist. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Loaded native library: >>> wrapper-windows-x86-32.dll >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Calling native >>> initialization method. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Initializing WrapperManager >>> native library. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Java Executable: C:\Program >>> Files (x86)\Java\jdk1.7.0_05\jre\bin\java.exe >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Windows version: 6.0.6002 >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Java Version : >>> 1.7.0_05-b05 Java HotSpot(TM) Client VM >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Java VM Vendor : Oracle >>> Corporation >>> INFO | jvm 1 | 2014/02/27 15:16:47 | >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Control event monitor >>> thread started. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Startup runner thread >>> started. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | >>> WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@bde56d, >>> args["start"]) called by thread: main >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Communications runner >>> thread started. >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Open socket to >>> wrapper...Wrapper-Connection >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Opened Socket from 31000 >>> to 32001 >>> INFO | jvm 1 | 2014/02/27 15:16:47 | Send a packet KEY : >>> leVi4EA9QFVx2hn_ >>> INFO | jvm 1 | 2014/02/27 15:16:47 | >>> handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | accepted a socket from >>> 127.0.0.1 on port 31000 >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | read a packet KEY : >>> leVi4EA9QFVx2hn_ >>> DEBUG | wrapper | 2014/02/27 15:16:47 | Got key from JVM: >>> leVi4EA9QFVx2hn_ >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | send a packet >>> LOW_LOG_LEVEL : 0 >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | send a packet PING_TIMEOUT >>> : 30 >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | send a packet PROPERTIES : >>> (Property Values) >>> DEBUG | wrapper | 2014/02/27 15:16:47 | Start Application. >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | send a packet START : start >>> DEBUG | wrapperp | 2014/02/27 15:16:47 | socket send failed. (10035) >>> ERROR | wrapper | 2014/02/27 15:16:47 | Unable to send the start >>> command to the JVM. >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Received a packet >>> LOW_LOG_LEVEL : 0 >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Wrapper Manager: LowLogLevel >>> from Wrapper is 0 >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Received a packet >>> PING_TIMEOUT : 30 >>> INFO | jvm 1 | 2014/02/27 15:16:48 | PingTimeout from Wrapper >>> is 30000 >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Received a packet PROPERTIES >>> : (Property Values) >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Closing socket. >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Open socket to >>> wrapper...Wrapper-Connection >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Opened Socket from 31000 >>> to 32001 >>> INFO | jvm 1 | 2014/02/27 15:16:48 | Send a packet KEY : >>> leVi4EA9QFVx2hn_ >>> INFO | jvm 1 | 2014/02/27 15:16:48 | >>> handleSocket(Socket[addr=/127.0.0.1,port=32001,localport=31000]) >>> DEBUG | wrapperp | 2014/02/27 15:16:48 | server listening on port >>> 32002. >>> ERROR | wrapper | 2014/02/27 15:16:48 | JVM did not exit on request, >>> terminated >>> DEBUG | wrapper | 2014/02/27 15:16:48 | JVM was only running for 1 >>> seconds leading to a failed restart count of 1. >>> DEBUG | wrapper | 2014/02/27 15:16:48 | Waiting 5 seconds before >>> launching another JVM. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>> For additional commands, e-mail: server-user-h...@james.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2014.0.4335 / Virus Database: 3705/7130 - Release Date: >> 02/27/14 >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
