Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Errors Starting Two Instances of Tomcat 6 on Windows Server

DZone's Guide to

Errors Starting Two Instances of Tomcat 6 on Windows Server

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

Today I was setting up a second tomcat instance on a single Windows machine and was not able to run two instances at the same time. The first instance started fine, but when I went to start a second instance the second server would not start.

I found the following errors in the logs from the jakarta_service_20121010.log:

[2012-10-10 14:37:15] [206 javajni.c] [error] The specified module could not be found.
[2012-10-10 14:37:15] [985 prunsrv.c] [error] Failed creating java C:\Java\jre6\bin\client\jvm.dll
[2012-10-10 14:37:15] [1280 prunsrv.c] [error] ServiceStart returned 1

At first, both services where set to use jvm mode for both Startup and Shutdown.

But the solution to allow both to work, was to set both services to Java mode for both Startup and Shutdown as seen here:

Tomcat6w.exe Service settings

Now running multiple instances runs like a charm.

 

 

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Published at DZone with permission of Mick Knutson, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}