You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Debbie Shapiro <DS...@cardiacscience.com> on 2012/01/10 02:16:47 UTC
Tomcat 7 service not starting
Hello -
I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
Re: Tomcat 7 service not starting
Posted by Pid <pi...@pidster.com>.
On 10/01/2012 01:16, Debbie Shapiro wrote:
> Hello -
> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
What does "update a couple of jar files" refer to? Tomcat or InetSoft?
Does this procedure also involve updating Tomcat and if so, how did you
do that?
You didn't actually say, but I assume from the error that you are using
Windows. Did you check the Tomcat log files and find any errors there?
p
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
--
[key:62590808]
Re: Tomcat 7 service not starting
Posted by Konstantin Kolinko <kn...@gmail.com>.
2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Subject: Tomcat 7 service not starting
>
>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>
> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>
Are you using JRE or JDK?
If JRE then OK, as its path is always the same.
If JDK then you must update service configuration to use the new version of JDK.
What jar files did you replace?
I'd also replace tomcat7.exe and tomcat7w.exe, review configuration
changes [1] and clear all files from work directory.
Do you use tc-native DLL?
What OS it is?
[1] http://tomcat.apache.org/migration.html
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
> Subject: Tomcat 7 service not starting
> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
I checked and indeed we can modify the default location for the sree.log. I'm not sure why they don't default these to a log directory, but definitely something I can ask them about. There is a second log it produces that also defaults to this location for the scheduler, but I don't see that in the properties file. I don't think there's any concern for these logs piling up, however. I have an automated process that creates a new file each night and compacts the old one and I do monitor it regularly. The new Windows operating systems may be a bigger deal, but we're starting to configure our servers with secondary disks rather than install the applications to the C: drive. We have run into the Administrator restriction on other applications on different servers already.
Please create a HelpStar ticket for any requests for assistance. This will help us better track your request.
http://helpstar
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Wednesday, January 11, 2012 11:15 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
Debbie Shapiro wrote:
> I'm not sure what the logs are supposed to look like in other implementations as I've only ever used Tomcat with Inetsoft.
About the multiple restart issue : I was merely curious on that one. It has nothing to do
with the InetSoft application, nor (I think) with Tomcat.
What seemed strange to me is this :
- the Tomcat Windows Service was started, and it crashed (because of the problem with the
JVM, now corrected)
- but then, without apparently further intervention on your part, it tried to start again
after 10-15 seconds, and crashed again.
- and then it tried to start again, and crashed again.
So, unless you repeatedly clicked yourself on the "Start" button of the service, what
caused it to try to start again repeatedly by itself ?
Normally, as far as I know, when a Windows Service crashes, it stays crashed until you do
something about it; but here it didn't..
But as I mentioned, this was just curiosity on my part, nothing essential.
Could you specify what looked off? Maybe I can ask them what it is doing. I don't think
we have any special settings in our Windows OS that would cause unusual behavior.
>
> Yes, the sree.log is indeed in the classes folder. That is where InetSoft records its activity. This is the vendor code, not anything I have developed. I've been using the tool for a number of years now without any major issues. What kind of issues would you expect to see due to this? Maybe I can ask them about that as well.
>
About the location of the "sree.log" file :
It is unusual for server applications to put a logfile in the same directory as the
"programs" (in this case, the InetSoft web application's java classes).
For one thing, it makes the logfile harder to find, because no programmer or sysadmin
would at first think of looking for a logfile there.
Then, since it's location is not obvious, this file may grow and grow over time without
being noticed, until the disk is full, and cause some other unexpected issues.
It looks like the location of the logfile may be specified in the "properties" file that
is mentioned somewhere in the logs. The default may be "here" (where the classes are),
but it may be better to change this, to be for example in the same directory as the Tomcat
logs. You can probably ask InetSoft about this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
I think it might have just been me testing it and restarting it a few times in a row. We do not have it set to automatically restart after failing, but I do have it set to Automatic startup when the server reboots.
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Wednesday, January 11, 2012 11:51 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
Caldarale, Charles R wrote:
>> From: André Warnier [mailto:aw@ice-sa.com]
>> Subject: Re: Tomcat 7 service not starting
>
>> what caused it to try to start again repeatedly by itself ?
>
> Pretty much any Windows service can be configured to automatically restart when it terminates.
Right, I see that now : Services..Tomcat..Properties.. then the 3rd tab (on my German XP
Workstation, that's called "Wiederherstellen"). You can set it to restart automatically
after the 1st, 2d, and further failures.
It's still not the default setting for Tomcat however, so someone must have set it
specifically to do that on Debbie's system.
You have to use the real service console, not tomcat7w.exe, to change that setting.
>
>> It is unusual for server applications to put a logfile in the
>> same directory as the "programs" (in this case, the InetSoft
>> web application's java classes).
>
> Newer versions of Windows also require running as administrator (not just administrator privileges) in order to write to C:\Program Files (or its variants). This can be problematic for apps that try to keep everything in their installation directory.
>
Good to know also.
So Debbie might want to change that logfile's location, to avoid another mysterious
failure the day that system gets upgraded or the application moved to a more recent server.
And maybe pass this on to the InetSoft people, in case they didn't know yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7 service not starting
Posted by André Warnier <aw...@ice-sa.com>.
Caldarale, Charles R wrote:
>> From: André Warnier [mailto:aw@ice-sa.com]
>> Subject: Re: Tomcat 7 service not starting
>
>> what caused it to try to start again repeatedly by itself ?
>
> Pretty much any Windows service can be configured to automatically restart when it terminates.
Right, I see that now : Services..Tomcat..Properties.. then the 3rd tab (on my German XP
Workstation, that's called "Wiederherstellen"). You can set it to restart automatically
after the 1st, 2d, and further failures.
It's still not the default setting for Tomcat however, so someone must have set it
specifically to do that on Debbie's system.
You have to use the real service console, not tomcat7w.exe, to change that setting.
>
>> It is unusual for server applications to put a logfile in the
>> same directory as the "programs" (in this case, the InetSoft
>> web application's java classes).
>
> Newer versions of Windows also require running as administrator (not just administrator privileges) in order to write to C:\Program Files (or its variants). This can be problematic for apps that try to keep everything in their installation directory.
>
Good to know also.
So Debbie might want to change that logfile's location, to avoid another mysterious
failure the day that system gets upgraded or the application moved to a more recent server.
And maybe pass this on to the InetSoft people, in case they didn't know yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: André Warnier [mailto:aw@ice-sa.com]
> Subject: Re: Tomcat 7 service not starting
> what caused it to try to start again repeatedly by itself ?
Pretty much any Windows service can be configured to automatically restart when it terminates. You have to use the real service console, not tomcat7w.exe, to change that setting.
> It is unusual for server applications to put a logfile in the
> same directory as the "programs" (in this case, the InetSoft
> web application's java classes).
Newer versions of Windows also require running as administrator (not just administrator privileges) in order to write to C:\Program Files (or its variants). This can be problematic for apps that try to keep everything in their installation directory.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7 service not starting
Posted by André Warnier <aw...@ice-sa.com>.
Debbie Shapiro wrote:
> I'm not sure what the logs are supposed to look like in other implementations as I've only ever used Tomcat with Inetsoft.
About the multiple restart issue : I was merely curious on that one. It has nothing to do
with the InetSoft application, nor (I think) with Tomcat.
What seemed strange to me is this :
- the Tomcat Windows Service was started, and it crashed (because of the problem with the
JVM, now corrected)
- but then, without apparently further intervention on your part, it tried to start again
after 10-15 seconds, and crashed again.
- and then it tried to start again, and crashed again.
So, unless you repeatedly clicked yourself on the "Start" button of the service, what
caused it to try to start again repeatedly by itself ?
Normally, as far as I know, when a Windows Service crashes, it stays crashed until you do
something about it; but here it didn't..
But as I mentioned, this was just curiosity on my part, nothing essential.
Could you specify what looked off? Maybe I can ask them what it is doing. I don't think
we have any special settings in our Windows OS that would cause unusual behavior.
>
> Yes, the sree.log is indeed in the classes folder. That is where InetSoft records its activity. This is the vendor code, not anything I have developed. I've been using the tool for a number of years now without any major issues. What kind of issues would you expect to see due to this? Maybe I can ask them about that as well.
>
About the location of the "sree.log" file :
It is unusual for server applications to put a logfile in the same directory as the
"programs" (in this case, the InetSoft web application's java classes).
For one thing, it makes the logfile harder to find, because no programmer or sysadmin
would at first think of looking for a logfile there.
Then, since it's location is not obvious, this file may grow and grow over time without
being noticed, until the disk is full, and cause some other unexpected issues.
It looks like the location of the logfile may be specified in the "properties" file that
is mentioned somewhere in the logs. The default may be "here" (where the classes are),
but it may be better to change this, to be for example in the same directory as the Tomcat
logs. You can probably ask InetSoft about this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
I'm not sure what the logs are supposed to look like in other implementations as I've only ever used Tomcat with Inetsoft. Could you specify what looked off? Maybe I can ask them what it is doing. I don't think we have any special settings in our Windows OS that would cause unusual behavior.
Yes, the sree.log is indeed in the classes folder. That is where InetSoft records its activity. This is the vendor code, not anything I have developed. I've been using the tool for a number of years now without any major issues. What kind of issues would you expect to see due to this? Maybe I can ask them about that as well.
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Tuesday, January 10, 2012 11:43 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
Debbie Shapiro wrote:
> I was able to get this woring again just by reinstalling the 64-bit Java 1.6.0_30 JRE. Not sure what went awry, but it's working now. Yay!
>
> Thanks for all your help!
>
>
Good.
There is still something quite bizarre in those logs below : it looks like, after each
startup error, a series of other attempts are made to start that service, at 1ß-15 seconds
interval. Is this some setting in the Windows OS ?
In any case, it quite confuses the logs..
Another thing that I noticed in your earlier logs :
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat
7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
That is quite a bizarre place for a logfile (in the same location as the application's
classes ?). If it really writes a logfile there, this is bound to create some problems
later on, probably when you least expect them.
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> -----Original Message-----
> From: Debbie Shapiro
> Sent: Tuesday, January 10, 2012 1:42 PM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat 7 service not starting
>
> Sorry for the confusion. The log files are the ones in the Tomcat\logs directory. I don't know why that one file has 1-8-2012 dates. The file was created on 1-9-2012, thus the confusion. I attempted to restart the service again today and it generated three files: tomcat7-stderr, tomcat7-stdout and commons-daemon.
>
>
> The contents are as follows:
> Commons-daemon:
> [2012-01-10 12:46:15] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:46:15] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:46:15] [info] Starting service...
> [2012-01-10 12:46:22] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:46:22] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:46:22] [info] Starting service...
> [2012-01-10 12:49:38] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:49:38] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:49:38] [info] Starting service...
> [2012-01-10 12:50:01] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:50:01] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:50:01] [info] Starting service...
>
>
> Tomcat7-stderr:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:46:22 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:49:38 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:50:01 Commons Daemon procrun stderr initialized
>
>
> Tomcat7-stdout:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:46:22 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:49:38 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:50:01 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
>
>
> My order of operations for the upgrade was as follows:
>
> 1) stopped Tomcat service
> 2) upgraded the 64-bit Java to 1.6.0_30 JRE
> 3) upgraded the 32-bit Java to 1.6.0_30 JRE
> 4) replaced the jar files for the InetSoft application in the following directories per InetSoft's directions:
> \Style Report Enterprise\lib (design.jar and sree.jar)
> \Tomcat\webapps\sree\WEB-INF\lib (sree.jar only)
> 5) change the web.xml to use sree.jar (instead of InetSoft's previously named sree_pro.jar - they did a name change with the new version).
> 6) restarted Tomcat service - at this point things were no longer working
>
> I will try the steps you've outlined below and see if this makes a difference.
>
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> -----Original Message-----
> From: André Warnier [mailto:aw@ice-sa.com]
> Sent: Tuesday, January 10, 2012 12:27 PM
> To: Tomcat Users List
> Subject: Re: Tomcat 7 service not starting
>
>
> Debbie,
>
> It looks all a bit confusing, particularly since
> - you tell us about logfiles, but without providing the exact path/filename of each file
> - the timestamps in some of these files indicate events which happened almost 24 h apart
> - some of these messages are not errors; they look like "normal" application messages
> (although sometimes in a strange place).
>
> It looks like your main problem is some kind of broken Java JVM, as per these messages :
>
> > 2012-01-09 16:15:55 Commons Daemon procrun stdout initialized
> Error occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> which apparently started happening at 2012-01-09 16:15:55.
>
> Other messages which you show, such as
>
> > 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space:
> [FileSystemDataSpace]
> > Can not find sree properties in ./sree.properties
> > Writing log to .\sree.log
> ...
>
> are from the previous day (but they don't look like errors per se).
>
> Presumably, you first replaced these application jars and tried to restart Tomcat then,
> and it seems to have worked at least in part, then.
> Then, the next day, you must have updated Java, and that's when things started to look ugly.
>
> But this is quite a bit of guesswork, because we don't know that application, and we don't
> know exactly which logfiles you are talking about, nor the order in which you did things.
>
>
> My personal recommendation at this stage, to try making some sense of the situation, would
> be :
>
> 1)
> a) find and delete /all/ the Tomcat and application logfiles that you find under the
> Tomcat directories. Also clear the Windows Event logs if you are allowed to do so (maybe
> first save them to file).
>
> b) When you have done the above carefully, try to restart Tomcat, once; I assume it will
> not work.
> c) then, after this /one/ unsuccesful attempt, find the logfiles again in the Tomcat log
> directories (and look at the Windows System Event log for any interesting messages).
> And then let us know which exact (path/filename) logfiles you find, and their content.
>
> 2) later, you may have to de-install both of your Java JVMs, and re-install one of them.
> And maybe re-install Tomcat.
> But let's see the logfiles first.
>
>
> Debbie Shapiro wrote:
>> Thank you all for your responses. Combining all the questions and answers into one email...
>>
>>
>>
>> Hi, are you able to see the log files in the log folder?
>>
>> Conway
>>
>>
>>
>> A: Yes, I can see the log files.
>> The localhost file says catalina serviceManager initalized successfully.
>>
>> Commons-daemon has the following:
>> [2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
>> [2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
>> [2012-01-08 23:30:12] [info] Starting service...
>> [2012-01-08 23:30:13] [info] Service started in 1203 ms.
>> [2012-01-09 16:15:03] [info] Stopping service...
>>
>> I show 2 tomcat7-stdout files
>> One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
>>
>> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
>> Can not find sree properties in ./sree.properties
>> Writing log to .\sree.log
>> The logging properties is: sree.properties
>> InetSoft 10.2 build 0908111301 started
>> Fail to get sree home from "web.xml as servlet parameter".
>> Get sree home from "web.xml as global parameter" successfully.
>> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
>> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
>>
>> The other has different errors:
>>
>> 2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>>
>>
>>
>>
>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>> Subject: Tomcat 7 service not starting
>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>
>> - Chuck
>>
>>
>>
>> A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
>>
>>
>>
>>
>> 2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>>> Subject: Tomcat 7 service not starting
>>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>>
>> Are you using JRE or JDK?
>> If JRE then OK, as its path is always the same.
>>
>> If JDK then you must update service configuration to use the new version of JDK.
>>
>>
>>
>> A: It is the JRE only.
>>
>>
>> What jar files did you replace?
>>
>> A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
>>
>> I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
>>
>> A: Why would these need to be replaced?
>> Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
>>
>>
>> Do you use tc-native DLL?
>>
>> A: I don't even understand the question! LOL
>>
>>
>> What OS it is?
>> Win 2003 Server R2 SP2 Standard 64-bit
>>
>>
>> [1] http://tomcat.apache.org/migration.html
>>
>> Best regards,
>> Konstantin Kolinko
>>
>>
>>
>>
>>
>>
>>
>>
>> On 10/01/2012 01:16, Debbie Shapiro wrote:
>>> Hello -
>>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>> What does "update a couple of jar files" refer to? Tomcat or InetSoft?
>>
>>
>> A: InetSoft only.
>>
>>
>>
>> Does this procedure also involve updating Tomcat and if so, how did you do that?
>>
>>
>> A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
>>
>>
>>
>>
>> You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
>>
>>
>> A: Yes, Win 2003 Server (described above more detail).
>> A: Yes, there are some errors in the Tomcat log files, displayed above.
>>
>> p
>>
>>
>>
>> Debbie Shapiro
>> Data Warehouse Manager
>> Cardiac Science
>> Office: 425.402.2233
>>
>> Visit us at www.cardiacscience.com
>> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>>
>>
>>
>> -----Original Message-----
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Sent: Tuesday, 10 January 2012 2:17 p.m.
>> To: users@tomcat.apache.org
>> Subject: Tomcat 7 service not starting
>>
>> Hello -
>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>>
>>
>>
>>
>> Debbie Shapiro
>> Data Warehouse Manager
>> Cardiac Science
>> Office: 425.402.2233
>>
>> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
>> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>>
>>
>> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7 service not starting
Posted by Pid <pi...@pidster.com>.
On 11/01/2012 07:43, André Warnier wrote:
>>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat
> 7.0.6\webapps\sree\WEB-INF\classes/sree.log
>>> The logging properties is: sree.properties
>
> That is quite a bizarre place for a logfile (in the same location as the
> application's classes ?). If it really writes a logfile there, this is
> bound to create some problems later on, probably when you least expect
> them.
+1 That location is a really bad one for a log file.
p
--
[key:62590808]
Re: Tomcat 7 service not starting
Posted by André Warnier <aw...@ice-sa.com>.
Debbie Shapiro wrote:
> I was able to get this woring again just by reinstalling the 64-bit Java 1.6.0_30 JRE. Not sure what went awry, but it's working now. Yay!
>
> Thanks for all your help!
>
>
Good.
There is still something quite bizarre in those logs below : it looks like, after each
startup error, a series of other attempts are made to start that service, at 1ß-15 seconds
interval. Is this some setting in the Windows OS ?
In any case, it quite confuses the logs..
Another thing that I noticed in your earlier logs :
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat
7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
That is quite a bizarre place for a logfile (in the same location as the application's
classes ?). If it really writes a logfile there, this is bound to create some problems
later on, probably when you least expect them.
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> -----Original Message-----
> From: Debbie Shapiro
> Sent: Tuesday, January 10, 2012 1:42 PM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat 7 service not starting
>
> Sorry for the confusion. The log files are the ones in the Tomcat\logs directory. I don't know why that one file has 1-8-2012 dates. The file was created on 1-9-2012, thus the confusion. I attempted to restart the service again today and it generated three files: tomcat7-stderr, tomcat7-stdout and commons-daemon.
>
>
> The contents are as follows:
> Commons-daemon:
> [2012-01-10 12:46:15] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:46:15] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:46:15] [info] Starting service...
> [2012-01-10 12:46:22] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:46:22] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:46:22] [info] Starting service...
> [2012-01-10 12:49:38] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:49:38] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:49:38] [info] Starting service...
> [2012-01-10 12:50:01] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-10 12:50:01] [info] Running 'Tomcat7' Service...
> [2012-01-10 12:50:01] [info] Starting service...
>
>
> Tomcat7-stderr:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:46:22 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:49:38 Commons Daemon procrun stderr initialized
>
> 2012-01-10 12:50:01 Commons Daemon procrun stderr initialized
>
>
> Tomcat7-stdout:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:46:22 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:49:38 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-10 12:50:01 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
>
>
> My order of operations for the upgrade was as follows:
>
> 1) stopped Tomcat service
> 2) upgraded the 64-bit Java to 1.6.0_30 JRE
> 3) upgraded the 32-bit Java to 1.6.0_30 JRE
> 4) replaced the jar files for the InetSoft application in the following directories per InetSoft's directions:
> \Style Report Enterprise\lib (design.jar and sree.jar)
> \Tomcat\webapps\sree\WEB-INF\lib (sree.jar only)
> 5) change the web.xml to use sree.jar (instead of InetSoft's previously named sree_pro.jar - they did a name change with the new version).
> 6) restarted Tomcat service - at this point things were no longer working
>
> I will try the steps you've outlined below and see if this makes a difference.
>
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> -----Original Message-----
> From: André Warnier [mailto:aw@ice-sa.com]
> Sent: Tuesday, January 10, 2012 12:27 PM
> To: Tomcat Users List
> Subject: Re: Tomcat 7 service not starting
>
>
> Debbie,
>
> It looks all a bit confusing, particularly since
> - you tell us about logfiles, but without providing the exact path/filename of each file
> - the timestamps in some of these files indicate events which happened almost 24 h apart
> - some of these messages are not errors; they look like "normal" application messages
> (although sometimes in a strange place).
>
> It looks like your main problem is some kind of broken Java JVM, as per these messages :
>
> > 2012-01-09 16:15:55 Commons Daemon procrun stdout initialized
> Error occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> which apparently started happening at 2012-01-09 16:15:55.
>
> Other messages which you show, such as
>
> > 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space:
> [FileSystemDataSpace]
> > Can not find sree properties in ./sree.properties
> > Writing log to .\sree.log
> ...
>
> are from the previous day (but they don't look like errors per se).
>
> Presumably, you first replaced these application jars and tried to restart Tomcat then,
> and it seems to have worked at least in part, then.
> Then, the next day, you must have updated Java, and that's when things started to look ugly.
>
> But this is quite a bit of guesswork, because we don't know that application, and we don't
> know exactly which logfiles you are talking about, nor the order in which you did things.
>
>
> My personal recommendation at this stage, to try making some sense of the situation, would
> be :
>
> 1)
> a) find and delete /all/ the Tomcat and application logfiles that you find under the
> Tomcat directories. Also clear the Windows Event logs if you are allowed to do so (maybe
> first save them to file).
>
> b) When you have done the above carefully, try to restart Tomcat, once; I assume it will
> not work.
> c) then, after this /one/ unsuccesful attempt, find the logfiles again in the Tomcat log
> directories (and look at the Windows System Event log for any interesting messages).
> And then let us know which exact (path/filename) logfiles you find, and their content.
>
> 2) later, you may have to de-install both of your Java JVMs, and re-install one of them.
> And maybe re-install Tomcat.
> But let's see the logfiles first.
>
>
> Debbie Shapiro wrote:
>> Thank you all for your responses. Combining all the questions and answers into one email...
>>
>>
>>
>> Hi, are you able to see the log files in the log folder?
>>
>> Conway
>>
>>
>>
>> A: Yes, I can see the log files.
>> The localhost file says catalina serviceManager initalized successfully.
>>
>> Commons-daemon has the following:
>> [2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
>> [2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
>> [2012-01-08 23:30:12] [info] Starting service...
>> [2012-01-08 23:30:13] [info] Service started in 1203 ms.
>> [2012-01-09 16:15:03] [info] Stopping service...
>>
>> I show 2 tomcat7-stdout files
>> One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
>>
>> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
>> Can not find sree properties in ./sree.properties
>> Writing log to .\sree.log
>> The logging properties is: sree.properties
>> InetSoft 10.2 build 0908111301 started
>> Fail to get sree home from "web.xml as servlet parameter".
>> Get sree home from "web.xml as global parameter" successfully.
>> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
>> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
>> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
>> The logging properties is: sree.properties
>>
>> The other has different errors:
>>
>> 2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>> 2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
>> java/lang/NoClassDefFoundError: java/lang/Object
>>
>>
>>
>>
>>
>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>> Subject: Tomcat 7 service not starting
>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>
>> - Chuck
>>
>>
>>
>> A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
>>
>>
>>
>>
>> 2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>>> Subject: Tomcat 7 service not starting
>>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>>
>> Are you using JRE or JDK?
>> If JRE then OK, as its path is always the same.
>>
>> If JDK then you must update service configuration to use the new version of JDK.
>>
>>
>>
>> A: It is the JRE only.
>>
>>
>> What jar files did you replace?
>>
>> A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
>>
>> I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
>>
>> A: Why would these need to be replaced?
>> Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
>>
>>
>> Do you use tc-native DLL?
>>
>> A: I don't even understand the question! LOL
>>
>>
>> What OS it is?
>> Win 2003 Server R2 SP2 Standard 64-bit
>>
>>
>> [1] http://tomcat.apache.org/migration.html
>>
>> Best regards,
>> Konstantin Kolinko
>>
>>
>>
>>
>>
>>
>>
>>
>> On 10/01/2012 01:16, Debbie Shapiro wrote:
>>> Hello -
>>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>> What does "update a couple of jar files" refer to? Tomcat or InetSoft?
>>
>>
>> A: InetSoft only.
>>
>>
>>
>> Does this procedure also involve updating Tomcat and if so, how did you do that?
>>
>>
>> A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
>>
>>
>>
>>
>> You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
>>
>>
>> A: Yes, Win 2003 Server (described above more detail).
>> A: Yes, there are some errors in the Tomcat log files, displayed above.
>>
>> p
>>
>>
>>
>> Debbie Shapiro
>> Data Warehouse Manager
>> Cardiac Science
>> Office: 425.402.2233
>>
>> Visit us at www.cardiacscience.com
>> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>>
>>
>>
>> -----Original Message-----
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Sent: Tuesday, 10 January 2012 2:17 p.m.
>> To: users@tomcat.apache.org
>> Subject: Tomcat 7 service not starting
>>
>> Hello -
>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>>
>>
>>
>>
>> Debbie Shapiro
>> Data Warehouse Manager
>> Cardiac Science
>> Office: 425.402.2233
>>
>> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
>> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>>
>>
>> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
I was able to get this woring again just by reinstalling the 64-bit Java 1.6.0_30 JRE. Not sure what went awry, but it's working now. Yay!
Thanks for all your help!
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: Debbie Shapiro
Sent: Tuesday, January 10, 2012 1:42 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat 7 service not starting
Sorry for the confusion. The log files are the ones in the Tomcat\logs directory. I don't know why that one file has 1-8-2012 dates. The file was created on 1-9-2012, thus the confusion. I attempted to restart the service again today and it generated three files: tomcat7-stderr, tomcat7-stdout and commons-daemon.
The contents are as follows:
Commons-daemon:
[2012-01-10 12:46:15] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:46:15] [info] Running 'Tomcat7' Service...
[2012-01-10 12:46:15] [info] Starting service...
[2012-01-10 12:46:22] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:46:22] [info] Running 'Tomcat7' Service...
[2012-01-10 12:46:22] [info] Starting service...
[2012-01-10 12:49:38] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:49:38] [info] Running 'Tomcat7' Service...
[2012-01-10 12:49:38] [info] Starting service...
[2012-01-10 12:50:01] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:50:01] [info] Running 'Tomcat7' Service...
[2012-01-10 12:50:01] [info] Starting service...
Tomcat7-stderr:
2012-01-10 12:46:15 Commons Daemon procrun stderr initialized
2012-01-10 12:46:22 Commons Daemon procrun stderr initialized
2012-01-10 12:49:38 Commons Daemon procrun stderr initialized
2012-01-10 12:50:01 Commons Daemon procrun stderr initialized
Tomcat7-stdout:
2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:46:22 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:49:38 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:50:01 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
My order of operations for the upgrade was as follows:
1) stopped Tomcat service
2) upgraded the 64-bit Java to 1.6.0_30 JRE
3) upgraded the 32-bit Java to 1.6.0_30 JRE
4) replaced the jar files for the InetSoft application in the following directories per InetSoft's directions:
\Style Report Enterprise\lib (design.jar and sree.jar)
\Tomcat\webapps\sree\WEB-INF\lib (sree.jar only)
5) change the web.xml to use sree.jar (instead of InetSoft's previously named sree_pro.jar - they did a name change with the new version).
6) restarted Tomcat service - at this point things were no longer working
I will try the steps you've outlined below and see if this makes a difference.
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Tuesday, January 10, 2012 12:27 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
Debbie,
It looks all a bit confusing, particularly since
- you tell us about logfiles, but without providing the exact path/filename of each file
- the timestamps in some of these files indicate events which happened almost 24 h apart
- some of these messages are not errors; they look like "normal" application messages
(although sometimes in a strange place).
It looks like your main problem is some kind of broken Java JVM, as per these messages :
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initialized
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
which apparently started happening at 2012-01-09 16:15:55.
Other messages which you show, such as
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space:
[FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
...
are from the previous day (but they don't look like errors per se).
Presumably, you first replaced these application jars and tried to restart Tomcat then,
and it seems to have worked at least in part, then.
Then, the next day, you must have updated Java, and that's when things started to look ugly.
But this is quite a bit of guesswork, because we don't know that application, and we don't
know exactly which logfiles you are talking about, nor the order in which you did things.
My personal recommendation at this stage, to try making some sense of the situation, would
be :
1)
a) find and delete /all/ the Tomcat and application logfiles that you find under the
Tomcat directories. Also clear the Windows Event logs if you are allowed to do so (maybe
first save them to file).
b) When you have done the above carefully, try to restart Tomcat, once; I assume it will
not work.
c) then, after this /one/ unsuccesful attempt, find the logfiles again in the Tomcat log
directories (and look at the Windows System Event log for any interesting messages).
And then let us know which exact (path/filename) logfiles you find, and their content.
2) later, you may have to de-install both of your Java JVMs, and re-install one of them.
And maybe re-install Tomcat.
But let's see the logfiles first.
Debbie Shapiro wrote:
> Thank you all for your responses. Combining all the questions and answers into one email...
>
>
>
> Hi, are you able to see the log files in the log folder?
>
> Conway
>
>
>
> A: Yes, I can see the log files.
> The localhost file says catalina serviceManager initalized successfully.
>
> Commons-daemon has the following:
> [2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
> [2012-01-08 23:30:12] [info] Starting service...
> [2012-01-08 23:30:13] [info] Service started in 1203 ms.
> [2012-01-09 16:15:03] [info] Stopping service...
>
> I show 2 tomcat7-stdout files
> One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
>
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
> The logging properties is: sree.properties
> InetSoft 10.2 build 0908111301 started
> Fail to get sree home from "web.xml as servlet parameter".
> Get sree home from "web.xml as global parameter" successfully.
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
>
> The other has different errors:
>
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
>
>
>
>
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Subject: Tomcat 7 service not starting
>
>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>
> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>
> - Chuck
>
>
>
> A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
>
>
>
>
> 2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>> Subject: Tomcat 7 service not starting
>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>
>
> Are you using JRE or JDK?
> If JRE then OK, as its path is always the same.
>
> If JDK then you must update service configuration to use the new version of JDK.
>
>
>
> A: It is the JRE only.
>
>
> What jar files did you replace?
>
> A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
>
> I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
>
> A: Why would these need to be replaced?
> Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
>
>
> Do you use tc-native DLL?
>
> A: I don't even understand the question! LOL
>
>
> What OS it is?
> Win 2003 Server R2 SP2 Standard 64-bit
>
>
> [1] http://tomcat.apache.org/migration.html
>
> Best regards,
> Konstantin Kolinko
>
>
>
>
>
>
>
>
> On 10/01/2012 01:16, Debbie Shapiro wrote:
>> Hello -
>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
> What does "update a couple of jar files" refer to? Tomcat or InetSoft?
>
>
> A: InetSoft only.
>
>
>
> Does this procedure also involve updating Tomcat and if so, how did you do that?
>
>
> A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
>
>
>
>
> You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
>
>
> A: Yes, Win 2003 Server (described above more detail).
> A: Yes, there are some errors in the Tomcat log files, displayed above.
>
> p
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
>
> -----Original Message-----
> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
> Sent: Tuesday, 10 January 2012 2:17 p.m.
> To: users@tomcat.apache.org
> Subject: Tomcat 7 service not starting
>
> Hello -
> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
I suspect installing the 32-bit Java after the 64-bit Java installation may have had something to do with it, but my Tomcat configuration was pointing to the Program Files and not Program Files (x86), so I don't know if there's some registry setting that was off or something.
InetSoft calls the sree.jar from the web.xml. I don't know anything about why they placed files where they do as this is all vendor coded and I'm just installing as they have directed. However, these are the snippets of the web.xml file where InetSoft is making calls:
<servlet>
<servlet-name>replets</servlet-name>
<servlet-class>inetsoft.sree.web.ServletRepository</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>manager</servlet-name>
<servlet-class>inetsoft.sree.adm.AdmServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>ResourceServlet</servlet-name>
<display-name>Resource Servlet</display-name>
<servlet-class>inetsoft.sree.web.jsp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>team</servlet-name>
<servlet-class>inetsoft.sree.web.team.TeamServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>WSServlet</servlet-name>
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>team</servlet-name>
<url-pattern>/team</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>replets</servlet-name>
<url-pattern>/Reports</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>replets</servlet-name>
<url-pattern>/Reports/dashboard/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>manager</servlet-name>
<url-pattern>/EnterpriseManager</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ResourceServlet</servlet-name>
<url-pattern>/resources</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>WSServlet</servlet-name>
<url-pattern>/SoapRepository</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>WSServlet</servlet-name>
<url-pattern>/SoapDataService</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>WSServlet</servlet-name>
<url-pattern>/PeopleService</url-pattern>
</servlet-mapping>
<taglib>
<taglib-uri>sree.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/sree.jar</taglib-location>
</taglib>
I have upgraded to Tomcat 7.0.23 now as well. :-)
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Tuesday, January 10, 2012 5:26 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Debbie,
On 1/10/12 4:41 PM, Debbie Shapiro wrote:
> Tomcat7-stdout:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError
> occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
It's clear that something is broken, here.
> My order of operations for the upgrade was as follows:
>
> 1) stopped Tomcat service 2) upgraded the 64-bit Java to 1.6.0_30
> JRE 3) upgraded the 32-bit Java to 1.6.0_30 JRE
Is it possible that upgrading the 32-bit version /second/ may have set
the default JRE to the 32-bit version, and you are trying to use
64-bit components for everything else?
> 4) replaced the jar files for the InetSoft application in the
> following directories per InetSoft's directions: \Style Report
> Enterprise\lib (design.jar and sree.jar)
> \Tomcat\webapps\sree\WEB-INF\lib (sree.jar only) 5) change the
> web.xml to use sree.jar (instead of InetSoft's previously named
> sree_pro.jar - they did a name change with the new version).
web.xml does not specify .jar files... so, what did you do, exactly?
Can you check your tomcat6w.exe configuration (run the program; look
at the configuration) to see what JRE you have selected when the
[procrun] service starts?
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html#Tomcat7w_monitor_application
I would also highly recommend at some point (after you have resolved
this particular issue) that you upgrade Tomcat to at least 7.0.21 --
7.0.6 was a looong time ago.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8M5R0ACgkQ9CaO5/Lv0PBtaQCgviXR96n3Je33k08BwKn/UmJy
Hu0AnRnGB2vX8j3y3B9abbqZuIFpmhzQ
=kPhA
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7 service not starting
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Debbie,
On 1/10/12 4:41 PM, Debbie Shapiro wrote:
> Tomcat7-stdout:
>
> 2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError
> occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
It's clear that something is broken, here.
> My order of operations for the upgrade was as follows:
>
> 1) stopped Tomcat service 2) upgraded the 64-bit Java to 1.6.0_30
> JRE 3) upgraded the 32-bit Java to 1.6.0_30 JRE
Is it possible that upgrading the 32-bit version /second/ may have set
the default JRE to the 32-bit version, and you are trying to use
64-bit components for everything else?
> 4) replaced the jar files for the InetSoft application in the
> following directories per InetSoft's directions: \Style Report
> Enterprise\lib (design.jar and sree.jar)
> \Tomcat\webapps\sree\WEB-INF\lib (sree.jar only) 5) change the
> web.xml to use sree.jar (instead of InetSoft's previously named
> sree_pro.jar - they did a name change with the new version).
web.xml does not specify .jar files... so, what did you do, exactly?
Can you check your tomcat6w.exe configuration (run the program; look
at the configuration) to see what JRE you have selected when the
[procrun] service starts?
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html#Tomcat7w_monitor_application
I would also highly recommend at some point (after you have resolved
this particular issue) that you upgrade Tomcat to at least 7.0.21 --
7.0.6 was a looong time ago.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8M5R0ACgkQ9CaO5/Lv0PBtaQCgviXR96n3Je33k08BwKn/UmJy
Hu0AnRnGB2vX8j3y3B9abbqZuIFpmhzQ
=kPhA
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
Sorry for the confusion. The log files are the ones in the Tomcat\logs directory. I don't know why that one file has 1-8-2012 dates. The file was created on 1-9-2012, thus the confusion. I attempted to restart the service again today and it generated three files: tomcat7-stderr, tomcat7-stdout and commons-daemon.
The contents are as follows:
Commons-daemon:
[2012-01-10 12:46:15] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:46:15] [info] Running 'Tomcat7' Service...
[2012-01-10 12:46:15] [info] Starting service...
[2012-01-10 12:46:22] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:46:22] [info] Running 'Tomcat7' Service...
[2012-01-10 12:46:22] [info] Starting service...
[2012-01-10 12:49:38] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:49:38] [info] Running 'Tomcat7' Service...
[2012-01-10 12:49:38] [info] Starting service...
[2012-01-10 12:50:01] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-10 12:50:01] [info] Running 'Tomcat7' Service...
[2012-01-10 12:50:01] [info] Starting service...
Tomcat7-stderr:
2012-01-10 12:46:15 Commons Daemon procrun stderr initialized
2012-01-10 12:46:22 Commons Daemon procrun stderr initialized
2012-01-10 12:49:38 Commons Daemon procrun stderr initialized
2012-01-10 12:50:01 Commons Daemon procrun stderr initialized
Tomcat7-stdout:
2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:46:22 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:49:38 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-10 12:50:01 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
My order of operations for the upgrade was as follows:
1) stopped Tomcat service
2) upgraded the 64-bit Java to 1.6.0_30 JRE
3) upgraded the 32-bit Java to 1.6.0_30 JRE
4) replaced the jar files for the InetSoft application in the following directories per InetSoft's directions:
\Style Report Enterprise\lib (design.jar and sree.jar)
\Tomcat\webapps\sree\WEB-INF\lib (sree.jar only)
5) change the web.xml to use sree.jar (instead of InetSoft's previously named sree_pro.jar - they did a name change with the new version).
6) restarted Tomcat service - at this point things were no longer working
I will try the steps you've outlined below and see if this makes a difference.
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Tuesday, January 10, 2012 12:27 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 service not starting
Debbie,
It looks all a bit confusing, particularly since
- you tell us about logfiles, but without providing the exact path/filename of each file
- the timestamps in some of these files indicate events which happened almost 24 h apart
- some of these messages are not errors; they look like "normal" application messages
(although sometimes in a strange place).
It looks like your main problem is some kind of broken Java JVM, as per these messages :
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initialized
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
which apparently started happening at 2012-01-09 16:15:55.
Other messages which you show, such as
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space:
[FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
...
are from the previous day (but they don't look like errors per se).
Presumably, you first replaced these application jars and tried to restart Tomcat then,
and it seems to have worked at least in part, then.
Then, the next day, you must have updated Java, and that's when things started to look ugly.
But this is quite a bit of guesswork, because we don't know that application, and we don't
know exactly which logfiles you are talking about, nor the order in which you did things.
My personal recommendation at this stage, to try making some sense of the situation, would
be :
1)
a) find and delete /all/ the Tomcat and application logfiles that you find under the
Tomcat directories. Also clear the Windows Event logs if you are allowed to do so (maybe
first save them to file).
b) When you have done the above carefully, try to restart Tomcat, once; I assume it will
not work.
c) then, after this /one/ unsuccesful attempt, find the logfiles again in the Tomcat log
directories (and look at the Windows System Event log for any interesting messages).
And then let us know which exact (path/filename) logfiles you find, and their content.
2) later, you may have to de-install both of your Java JVMs, and re-install one of them.
And maybe re-install Tomcat.
But let's see the logfiles first.
Debbie Shapiro wrote:
> Thank you all for your responses. Combining all the questions and answers into one email...
>
>
>
> Hi, are you able to see the log files in the log folder?
>
> Conway
>
>
>
> A: Yes, I can see the log files.
> The localhost file says catalina serviceManager initalized successfully.
>
> Commons-daemon has the following:
> [2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
> [2012-01-08 23:30:12] [info] Starting service...
> [2012-01-08 23:30:13] [info] Service started in 1203 ms.
> [2012-01-09 16:15:03] [info] Stopping service...
>
> I show 2 tomcat7-stdout files
> One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
>
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
> The logging properties is: sree.properties
> InetSoft 10.2 build 0908111301 started
> Fail to get sree home from "web.xml as servlet parameter".
> Get sree home from "web.xml as global parameter" successfully.
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
>
> The other has different errors:
>
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
>
>
>
>
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Subject: Tomcat 7 service not starting
>
>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>
> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>
> - Chuck
>
>
>
> A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
>
>
>
>
> 2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>> Subject: Tomcat 7 service not starting
>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>
>
> Are you using JRE or JDK?
> If JRE then OK, as its path is always the same.
>
> If JDK then you must update service configuration to use the new version of JDK.
>
>
>
> A: It is the JRE only.
>
>
> What jar files did you replace?
>
> A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
>
> I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
>
> A: Why would these need to be replaced?
> Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
>
>
> Do you use tc-native DLL?
>
> A: I don't even understand the question! LOL
>
>
> What OS it is?
> Win 2003 Server R2 SP2 Standard 64-bit
>
>
> [1] http://tomcat.apache.org/migration.html
>
> Best regards,
> Konstantin Kolinko
>
>
>
>
>
>
>
>
> On 10/01/2012 01:16, Debbie Shapiro wrote:
>> Hello -
>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
> What does "update a couple of jar files" refer to? Tomcat or InetSoft?
>
>
> A: InetSoft only.
>
>
>
> Does this procedure also involve updating Tomcat and if so, how did you do that?
>
>
> A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
>
>
>
>
> You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
>
>
> A: Yes, Win 2003 Server (described above more detail).
> A: Yes, there are some errors in the Tomcat log files, displayed above.
>
> p
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
>
> -----Original Message-----
> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
> Sent: Tuesday, 10 January 2012 2:17 p.m.
> To: users@tomcat.apache.org
> Subject: Tomcat 7 service not starting
>
> Hello -
> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7 service not starting
Posted by André Warnier <aw...@ice-sa.com>.
Debbie,
It looks all a bit confusing, particularly since
- you tell us about logfiles, but without providing the exact path/filename of each file
- the timestamps in some of these files indicate events which happened almost 24 h apart
- some of these messages are not errors; they look like "normal" application messages
(although sometimes in a strange place).
It looks like your main problem is some kind of broken Java JVM, as per these messages :
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initialized
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
which apparently started happening at 2012-01-09 16:15:55.
Other messages which you show, such as
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space:
[FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
...
are from the previous day (but they don't look like errors per se).
Presumably, you first replaced these application jars and tried to restart Tomcat then,
and it seems to have worked at least in part, then.
Then, the next day, you must have updated Java, and that's when things started to look ugly.
But this is quite a bit of guesswork, because we don't know that application, and we don't
know exactly which logfiles you are talking about, nor the order in which you did things.
My personal recommendation at this stage, to try making some sense of the situation, would
be :
1)
a) find and delete /all/ the Tomcat and application logfiles that you find under the
Tomcat directories. Also clear the Windows Event logs if you are allowed to do so (maybe
first save them to file).
b) When you have done the above carefully, try to restart Tomcat, once; I assume it will
not work.
c) then, after this /one/ unsuccesful attempt, find the logfiles again in the Tomcat log
directories (and look at the Windows System Event log for any interesting messages).
And then let us know which exact (path/filename) logfiles you find, and their content.
2) later, you may have to de-install both of your Java JVMs, and re-install one of them.
And maybe re-install Tomcat.
But let's see the logfiles first.
Debbie Shapiro wrote:
> Thank you all for your responses. Combining all the questions and answers into one email...
>
>
>
> Hi, are you able to see the log files in the log folder?
>
> Conway
>
>
>
> A: Yes, I can see the log files.
> The localhost file says catalina serviceManager initalized successfully.
>
> Commons-daemon has the following:
> [2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
> [2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
> [2012-01-08 23:30:12] [info] Starting service...
> [2012-01-08 23:30:13] [info] Service started in 1203 ms.
> [2012-01-09 16:15:03] [info] Stopping service...
>
> I show 2 tomcat7-stdout files
> One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
>
> 2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
> Can not find sree properties in ./sree.properties
> Writing log to .\sree.log
> The logging properties is: sree.properties
> InetSoft 10.2 build 0908111301 started
> Fail to get sree home from "web.xml as servlet parameter".
> Get sree home from "web.xml as global parameter" successfully.
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
> The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
> Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
> The logging properties is: sree.properties
>
> The other has different errors:
>
> 2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
> 2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
> java/lang/NoClassDefFoundError: java/lang/Object
>
>
>
>
>
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Subject: Tomcat 7 service not starting
>
>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>
> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>
> - Chuck
>
>
>
> A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
>
>
>
>
> 2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>>> Subject: Tomcat 7 service not starting
>>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>>
>
> Are you using JRE or JDK?
> If JRE then OK, as its path is always the same.
>
> If JDK then you must update service configuration to use the new version of JDK.
>
>
>
> A: It is the JRE only.
>
>
> What jar files did you replace?
>
> A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
>
> I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
>
> A: Why would these need to be replaced?
> Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
>
>
> Do you use tc-native DLL?
>
> A: I don't even understand the question! LOL
>
>
> What OS it is?
> Win 2003 Server R2 SP2 Standard 64-bit
>
>
> [1] http://tomcat.apache.org/migration.html
>
> Best regards,
> Konstantin Kolinko
>
>
>
>
>
>
>
>
> On 10/01/2012 01:16, Debbie Shapiro wrote:
>> Hello -
>> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
> What does "update a couple of jar files" refer to? Tomcat or InetSoft?
>
>
> A: InetSoft only.
>
>
>
> Does this procedure also involve updating Tomcat and if so, how did you do that?
>
>
> A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
>
>
>
>
> You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
>
>
> A: Yes, Win 2003 Server (described above more detail).
> A: Yes, there are some errors in the Tomcat log files, displayed above.
>
> p
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
>
> -----Original Message-----
> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
> Sent: Tuesday, 10 January 2012 2:17 p.m.
> To: users@tomcat.apache.org
> Subject: Tomcat 7 service not starting
>
> Hello -
> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
>
>
>
>
> Debbie Shapiro
> Data Warehouse Manager
> Cardiac Science
> Office: 425.402.2233
>
> Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
> Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
>
>
> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by Debbie Shapiro <DS...@cardiacscience.com>.
Thank you all for your responses. Combining all the questions and answers into one email...
Hi, are you able to see the log files in the log folder?
Conway
A: Yes, I can see the log files.
The localhost file says catalina serviceManager initalized successfully.
Commons-daemon has the following:
[2012-01-08 23:30:12] [info] Commons Daemon procrun (1.0.5.0 64-bit) started
[2012-01-08 23:30:12] [info] Running 'Tomcat7' Service...
[2012-01-08 23:30:12] [info] Starting service...
[2012-01-08 23:30:13] [info] Service started in 1203 ms.
[2012-01-09 16:15:03] [info] Stopping service...
I show 2 tomcat7-stdout files
One Tomcat7-stdout mentions an error fail to get sree home from web.xml:
2012-01-08 23:30:12 Commons Daemon procrun stdout initializedInitializing data space: [FileSystemDataSpace]
Can not find sree properties in ./sree.properties
Writing log to .\sree.log
The logging properties is: sree.properties
InetSoft 10.2 build 0908111301 started
Fail to get sree home from "web.xml as servlet parameter".
Get sree home from "web.xml as global parameter" successfully.
The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
The logging properties is: sree.properties
The sree properties is: C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.properties
Writing log to C:\Program Files\Apache Software Foundation\Tomcat 7.0.6\webapps\sree\WEB-INF\classes/sree.log
The logging properties is: sree.properties
The other has different errors:
2012-01-09 16:15:55 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 16:28:15 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 16:44:43 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 16:52:27 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 16:53:07 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 17:16:20 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
2012-01-09 17:17:37 Commons Daemon procrun stdout initializedError occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
> Subject: Tomcat 7 service not starting
> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
- Chuck
A: It is Windows 64-bit. I installed both 32-bit and 64-bit JVMs.
2012/1/10 Caldarale, Charles R <Ch...@unisys.com>:
>> From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
>> Subject: Tomcat 7 service not starting
>
>> I also upgraded Java from 1.6.0_20 to 1.6.0_30.
>
> Did you also perhaps change from a 32-bit to a 64-bit JVM (or vice-versa)? The mode of the JVM must match the mode of the Tomcat service wrapper (tomcat7.exe).
>
Are you using JRE or JDK?
If JRE then OK, as its path is always the same.
If JDK then you must update service configuration to use the new version of JDK.
A: It is the JRE only.
What jar files did you replace?
A: These are InetSoft jar files, nothing was replaced or changed on the Tomcat installation.
I'd also replace tomcat7.exe and tomcat7w.exe, review configuration changes [1] and clear all files from work directory.
A: Why would these need to be replaced?
Also, there is nothing in the work directory other than a bunch of directories. The only file I see is in the work\Catalina\localhost\_\org\apache\jsp and there is an index_jsp.class and an index_jsp.java both dated 1/26/2011. So they haven't changed in quite a while.
Do you use tc-native DLL?
A: I don't even understand the question! LOL
What OS it is?
Win 2003 Server R2 SP2 Standard 64-bit
[1] http://tomcat.apache.org/migration.html
Best regards,
Konstantin Kolinko
On 10/01/2012 01:16, Debbie Shapiro wrote:
> Hello -
> I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
What does "update a couple of jar files" refer to? Tomcat or InetSoft?
A: InetSoft only.
Does this procedure also involve updating Tomcat and if so, how did you do that?
A: No, there was no change required to Tomcat. I am still trying to use the same version as before, which is 7.0.6.
You didn't actually say, but I assume from the error that you are using Windows. Did you check the Tomcat log files and find any errors there?
A: Yes, Win 2003 Server (described above more detail).
A: Yes, there are some errors in the Tomcat log files, displayed above.
p
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
-----Original Message-----
From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
Sent: Tuesday, 10 January 2012 2:17 p.m.
To: users@tomcat.apache.org
Subject: Tomcat 7 service not starting
Hello -
I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7 service not starting
Posted by "Liu, Conway (AP - NZ)" <Co...@ap.sony.com>.
Hi, are you able to see the log files in the log folder?
Conway
-----Original Message-----
From: Debbie Shapiro [mailto:DShapiro@cardiacscience.com]
Sent: Tuesday, 10 January 2012 2:17 p.m.
To: users@tomcat.apache.org
Subject: Tomcat 7 service not starting
Hello -
I use Tomcat with the Business Intelligence Web Application InetSoft. I am in the process of upgrading our development server to their latest version (11.2). I also upgraded Java from 1.6.0_20 to 1.6.0_30. The upgrade procedure for InetSoft is to replace a couple of jar files, which I have done. But now Tomcat is no longer starting up. I get an Error 1067. The process terminated unexpectedly. Can anyone provide any guidance on where to look for why this is no longer starting up?
Debbie Shapiro
Data Warehouse Manager
Cardiac Science
Office: 425.402.2233
Visit us at www.cardiacscience.com<http://www.cardiacscience.com/>
Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family
This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org