Interesting post. someone on tomcat user mail list had asked a question similar to this thread/post. The common denominator = new version of Java 7.0.21.
For whatever reason, something has changed with (placement/location of) Java 7.0.21 'server JVM', and IMO, I'm not liking that, but I guess Java/Oracle decided to do this, since they are trying to make JRE/JVM more secure. listening in on this thread; i may also need to read the corresponding/earlier thread on tomcat user mail list as well. I'm still at Java 7 versions 13, I think, on both my dev and prod servers. On Wed, May 15, 2013 at 4:54 PM, m1000 <[email protected]> wrote: > In fact I rebooted and I see a little more in the logs : > > [2013-05-15 16:51:08] [info] Commons Daemon procrun (1.0.10.0 64-bit) > started > [2013-05-15 16:51:08] [info] Running 'TomEE' Service... > [2013-05-15 16:51:08] [info] Starting service... > *[2013-05-15 16:51:08] [error] Failed creating java * > [2013-05-15 16:51:08] [error] ServiceStart returned 1 > [2013-05-15 16:51:10] [info] Run service finished. > [2013-05-15 16:51:10] [info] Commons Daemon procrun finished > > So... unzipping the new server jre (its a tar.gz on windows too!) and > setting up JAVA_HOME and JRE_HOME isn't enough for the service ? > > I will try with a real java install (exe). > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-as-a-Service-Windows-7-x64-tp4662996p4662999.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
