Tomcat 3 -- servlets don't reload..

2006-02-28 Thread Frances
when I make changes to a servlet I don't see changes unless I turn 
tomcat off and on...  this is a huge pain, it's at work, where we can't 
be turning Tomcat off and on all day long whenever we make changes to a 
servlet..  Is there a way around this?  (Does Tomcat 3 come with a 
Manager?  I can't find manager-howto.html among docs (which does come 
with Tomcat 5..)  many thanks..


Frances


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 3 -- servlets don't reload..

2006-02-28 Thread Frances

Frances wrote:
when I make changes to a servlet I don't see changes unless I turn 
tomcat off and on...  this is a huge pain, it's at work, where we can't 
be turning Tomcat off and on all day long whenever we make changes to a 
servlet..  Is there a way around this?  (Does Tomcat 3 come with a 
Manager?  I can't find manager-howto.html among docs (which does come 
with Tomcat 5..)  many thanks..


Frances


I do have this for every webapp in server.xml:

 

so why won't servlets reload when I make changes to them?  (again, this 
is on Tomcat 3, 3.2.2, to be precise..)  thanks again..  Frances



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 3 -- servlets don't reload..

2006-03-01 Thread Frances
thank you very much Larry..  oh brother, my boss insists there's a way.. 
 there HAS to be a way..  how can a servlet container be designed that 
only reloads servlets when you restart it?  ok, thanks again...



Larry Isaacs wrote:

I has been quite a while since I have used Tomcat 3.3.x.
My recollection is that accessing the changed servlet would
trigger a reload of the webapp.  This differs from the newer
Tomcats which have a background thread checking for changes.
Also, with a default configuration, I don't recall anything
special that was needed beyond setting the context to be
reloadable.  I can't say why this isn't working for you.

As for the manager, Tomcat came with an admin webapp.  However,
it never got far enough along to be worthy of its own manual.
It's mentioned briefly in the User's Guide, but I think that is
about it.  If you want a "real" manager/admin webapp, you will
need to upgrade to a newer Tomcat.

Cheers,
Larry



-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Frances
Sent: Tuesday, February 28, 2006 12:49 PM
To: users@tomcat.apache.org
Subject: Tomcat 3 -- servlets don't reload..

when I make changes to a servlet I don't see changes unless I 
turn tomcat off and on...  this is a huge pain, it's at work, 
where we can't be turning Tomcat off and on all day long 
whenever we make changes to a servlet..  Is there a way 
around this?  (Does Tomcat 3 come with a Manager?  I can't 
find manager-howto.html among docs (which does come with 
Tomcat 5..)  many thanks..


Frances


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Tomcat 3 -- reading props w/xml..

2006-03-10 Thread Frances
I'm on Tomcat 3, it comes with an xml-apis.jar, but no docs..  do you 
know where I can find docs for it..  I'm trying to read properties with 
xml, can't use loadFromXML() because that method is 1.5-only..  don't 
know if xml-apis.jar is it, but... why no docs...


thank you...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 3 -- reading props w/xml..

2006-03-11 Thread Frances

Bill Barker wrote:
"Frances" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]


I'm on Tomcat 3, it comes with an xml-apis.jar, but no docs..  do you know 
where I can find docs for it..  I'm trying to read properties with xml, 
can't use loadFromXML() because that method is 1.5-only..  don't know if 
xml-apis.jar is it, but... why no docs...





Urm, you must be getting this from a third-party provider, since no official 
release of TC 3.x ships with anything as modern as xml-apis.jar.  All 
official TC 3.3.x releases default to crimson if no other XML parser is 
available.


thank you for yr response..  this is at work, then maybe somebody put 
the xml-api in there..  either way, on my windows machine locally am 
running Tomcat 5, and that one did come with an xml-apis.jar (I know, I 
did not put it there..) but also no docs..  I'm on 1.4, what api (& 
docs) pls do I use for this.. thank you again..



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



need help with isapi and ntdll problem for windows 2008 R2/tomcat 6

2011-02-01 Thread Frances Wang
Hello,

We are running Tomcat 6.0.26 on Windows Server 2008 R2 Enterprise 64 Bit using 
IIS and isapi redirector version 1.2.30 (just upgraded to 1.2.31).  The 6 
months or so we have been using Tomcat  have been plagued with intermittent 
periods crashes and instability.  Specifically, tomcat requests are resulting 
in crashes and the application log shows numerous (over 1200) instances of 
error 1000:
Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 
0x4a5bd0eb
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc005
Fault offset: 0x0004d174
Faulting process id: 0x1254
Faulting application start time: 0x01cbc19aceedc9cd
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 0d413cc2-2d8e-11e0-92d0-005056340288

We installed debug diag on the machine and opened a case with Microsoft since 
it seemed like it was a MS problem.  After opening a case and sending MS 
several dump files for analysis we were told:

We are failing during a call into isapi_redirect64.  It appears to be passing a 
bad value for a critical section to NTDLL (0x`0003) which in turn 
is causing the Access Violation to occur.


Here is the complete email response from MS with some of the data from the 
dumps:

All of the dumps show the same issue:



Child-SP  RetAddr   Call Site

`019bd040 `7734d0a2 ntdll!RtlpWaitOnCriticalSection+0xb4

`019bd0f0 `6a6d1c41 ntdll!RtlEnterCriticalSection+0xab

`019bd120 `6a6bd40c isapi_redirect64!jk_md5+0x1c1 
`019bd150 `6a6ebbb7 isapi_redirect64!ajp_service+0xb4c

`019bd1e0 `6a6c679a isapi_redirect64!uri_worker_map_open+0x2c7

`019bd240 07fe`f31bc540 
isapi_redirect64!read_registry_init_data+0x89a

`019be520 07fe`f31c4007 isapi!ProcessIsapiRequest+0x13c 
`019be580 07fe`f31bb421 isapi!W3_ISAPI_HANDLER::DoWork+0x4fb

`019be690 07fe`f31bb964 isapi!RequestDoWork+0x40d `019be720 
07fe`f3db2fa7 isapi!CIISHttpModule::OnExecuteRequestHandler+0x1c

`019be760 07fe`f3db464e 
iiscore!NOTIFICATION_CONTEXT::RequestDoWork+0x233

`019be7a0 07fe`f3db4465 
iiscore!NOTIFICATION_CONTEXT::CallModulesInternal+0x17f

`019be890 07fe`f3db5e56 
iiscore!NOTIFICATION_CONTEXT::CallModules+0x25

`019be8e0 07fe`f3de51bd iiscore!W3_CONTEXT::DoWork+0x3a6 
`019bec00 07fe`f3de55df 
iiscore!W3_MAIN_CONTEXT::StartNotificationLoop+0x5d

`019bec30 07fe`f319551e iiscore!W3_CONTEXT::ExecuteRequest+0x2bf

`019becb0 07fe`f3191060 filter!RequestDoWork+0x40be 
`019bf360 07fe`f3db6ac1 
filter!CIISHttpModule::OnPostAuthenticateRequest+0x20

`019bf3a0 07fe`f3db464e 
iiscore!NOTIFICATION_CONTEXT::RequestDoWork+0x20a

`019bf3e0 07fe`f3db4465 
iiscore!NOTIFICATION_CONTEXT::CallModulesInternal+0x17f

`019bf4d0 07fe`f3db593d 
iiscore!NOTIFICATION_CONTEXT::CallModules+0x25

`019bf520 07fe`f3db8ede iiscore!W3_CONTEXT::DoWork+0x326 
`019bf840 07fe`f3da10d2 iiscore!W3_MAIN_CONTEXT::OnNewRequest+0x1ea

`019bf870 07fe`f3da109c w3dt!UL_NATIVE_REQUEST::DoWork+0x126

`019bf8d0 07fe`f4581fba w3dt!OverlappedCompletionRoutine+0x1c

`019bf900 07fe`f4582024 w3tp!THREAD_POOL_DATA::ThreadPoolThread+0x7a

`019bf950 07fe`f45820a1 w3tp!THREAD_POOL_DATA::ThreadPoolThread+0x34

`019bf980 `770ff56d 
w3tp!THREAD_MANAGER::ThreadManagerThread+0x61

`019bf9b0 `77333281 kernel32!BaseThreadInitThunk+0xd 
`019bf9e0 ` ntdll!RtlUserThreadStart+0x1d



We are failing during a call into isapi_redirect64.  It appears to be passing a 
bad value for a critical section to NTDLL (0x`0003) which in turn 
is causing the Access Violation to occur.



This is a TomCat redirector from the Apache Foundation:



0:004> lmvm isapi_redirect64

start end module name

`6a6b `6a714000   isapi_redirect64   (export symbols)   
isapi_redirect64.dll

Loaded symbol image file: isapi_redirect64.dll

Image path: D:\isapiRedirect\isapi_redirect64.dll

Image name: isapi_redirect64.dll

Timestamp:Thu Sep 09 18:04:53 2010 (4C895A05)

CheckSum: 00062701

ImageSize:00064000

File version: 1.2.30.0

Product version:  1.2.30.0

File flags:   0 (Mask 3F)

File OS:  40004 NT Win32

File type:1.0 App

File date:.

Translations: 0409.04b0

CompanyName:  Apache Software Foundation

ProductName:  Apache Tomcat Connectors project

InternalName: isapi_redirect-1.2.30

OriginalFilename: isapi_redirect-1.2.30.dll

ProductVersion:   1.2.