Re: [Resin-interest] Stopping Resin due to detected alarm freeze. What?

2009-09-22 Thread Rob Lockstone
On Sep 22, 2009, at 12:44, Scott Ferguson wrote:

> On Sep 22, 2009, at 11:51 AM, Rob Lockstone wrote:
>
>> I've never seen this before and can't find this string in the Resin
>> (non-Pro) source. This happened on several of our server this  
>> morning.
>> But I've never seen it happen before in months of running this
>> particular configuration.
>>
>> Environment:
>>
>> Windows Server 2003
>> Resin Pro 3.1.9 - 100 Server License
>> JDK 1.6_13
>>
>> What would cause this?
>
> Certain types of deadlock or a true JVM or thread freeze.  It's
> detected by the  service.

Thanks, Scott. The fact that it was a result of the ping service got  
me on the right path.

Rob

>
> Resin has an timer thread in Alarm that returns the internal current
> time for Resin.  If that thread freezes, Resin's internal time won't
> be updated and will become out of sync with the
> System.currentTimeMillis().  If that discrepancy gets very large
> (15m), Resin will force an exit.  Basically, it's an indication that
> something is very, very wrong with the JVM.
>
> Since I just updated the shutdown logic for 4.0.2, it might be
> possible for Resin to give a thread dump before exiting in that case.
> Previously, Resin just does a halt() because the JVM might be in such
> a bad state that any additional work might create new problems.
>
> -- Scott



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Stopping Resin due to detected alarm freeze. What?

2009-09-22 Thread Scott Ferguson

On Sep 22, 2009, at 11:51 AM, Rob Lockstone wrote:

> I've never seen this before and can't find this string in the Resin
> (non-Pro) source. This happened on several of our server this morning.
> But I've never seen it happen before in months of running this
> particular configuration.
>
> Environment:
>
> Windows Server 2003
> Resin Pro 3.1.9 - 100 Server License
> JDK 1.6_13
>
> What would cause this?

Certain types of deadlock or a true JVM or thread freeze.  It's  
detected by the  service.

Resin has an timer thread in Alarm that returns the internal current  
time for Resin.  If that thread freezes, Resin's internal time won't  
be updated and will become out of sync with the  
System.currentTimeMillis().  If that discrepancy gets very large  
(15m), Resin will force an exit.  Basically, it's an indication that  
something is very, very wrong with the JVM.

Since I just updated the shutdown logic for 4.0.2, it might be  
possible for Resin to give a thread dump before exiting in that case.   
Previously, Resin just does a halt() because the JVM might be in such  
a bad state that any additional work might create new problems.

-- Scott

>
>
> Rob
>
>
>
> ___
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Stopping Resin due to detected alarm freeze. What?

2009-09-22 Thread Rob Lockstone
I've never seen this before and can't find this string in the Resin  
(non-Pro) source. This happened on several of our server this morning.  
But I've never seen it happen before in months of running this  
particular configuration.

Environment:

Windows Server 2003
Resin Pro 3.1.9 - 100 Server License
JDK 1.6_13

What would cause this?

Rob



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Noob question: Do I have to restart?

2009-09-22 Thread Scott Ferguson

On Sep 22, 2009, at 11:08 AM, d.lo...@uib.es wrote:

>
> On a related note, I think that I've seen Resin close the application
> and restart it before the next page is requested, even though I don't
> remember if that was with previous versions of Resin or depended on
> some time out. Could some one from Resin clarify this point?

There's a timeout thread in addition to the request check.  A request  
will force a check (assuming dependency-check-interval has expired).   
The timeout thread is something slower, like 60s.

-- Scott



>
>
> S!
> D.
>
> PS: S! = Salute!, so it's not my name :)
>
> S'està citant Rom Sok :
>
>> Thanks
>>
>>
>> On Tue, Sep 22, 2009 at 12:10 PM, Jeff Schnitzer  
>> wrote:
>>
>>> Hot deployment works fine for me out of the box, but note that Resin
>>> doesn't immediately reload the webapp when web.xml or the war  
>>> changes.
>>> You have to actually request a page, then the app will reload.
>>>
>>> If you change JSP files they are picked up immediately, no reload
>>> necessary.
>>>
>>> Jeff
>>>
>>> On Tue, Sep 22, 2009 at 7:23 AM, Rom Sok   
>>> wrote:
 Hi,

 Sorry about the newbie question, do I have to restart Resin every  
 time I
 drop a new version of some file into the deployment directory?  
 like say
 web.xml?
 Is there a way to just reload the app without doing the whole  
 "Stop" - >
 "Quit" -> httpd.exe all over again?

 Also, is that what is called hot deployment? Or is there another  
 term for
 redeploying an app without starting the server?

 Thanks,


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest


>>>
>>>
>>> ___
>>> resin-interest mailing list
>>> resin-interest@caucho.com
>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>
>>
>
>
>
> 
>
>
>
>
>
> ___
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Noob question: Do I have to restart?

2009-09-22 Thread d . lopez
Hi,

Be aware though, that hot redeployment requires all the  
libraries/classes that reside in WEB-INF to behave correctly,  
otherwise they are not recicled and end up consuming all the non-Heap  
memory and causing an OOM. And there are tons of libraries out there  
that do not behave properly, even some of the most popular ones. So,  
even though convenient, it is not something I would rely on much,  
unfortunately.

Oh, and there is an attribute in resin.conf (or resin.xml) to control  
the interval to check for changes in the context-senstive files, so  
you can configure it so Resin is not checking all the time in  
production if some files have changed.

On a related note, I think that I've seen Resin close the application  
and restart it before the next page is requested, even though I don't  
remember if that was with previous versions of Resin or depended on  
some time out. Could some one from Resin clarify this point?

S!
D.

PS: S! = Salute!, so it's not my name :)

S'està citant Rom Sok :

> Thanks
>
>
> On Tue, Sep 22, 2009 at 12:10 PM, Jeff Schnitzer wrote:
>
>> Hot deployment works fine for me out of the box, but note that Resin
>> doesn't immediately reload the webapp when web.xml or the war changes.
>>  You have to actually request a page, then the app will reload.
>>
>> If you change JSP files they are picked up immediately, no reload
>> necessary.
>>
>> Jeff
>>
>> On Tue, Sep 22, 2009 at 7:23 AM, Rom Sok  wrote:
>> > Hi,
>> >
>> > Sorry about the newbie question, do I have to restart Resin every time I
>> > drop a new version of some file into the deployment directory? like say
>> > web.xml?
>> > Is there a way to just reload the app without doing the whole "Stop" - >
>> > "Quit" -> httpd.exe all over again?
>> >
>> > Also, is that what is called hot deployment? Or is there another term for
>> > redeploying an app without starting the server?
>> >
>> > Thanks,
>> >
>> >
>> > ___
>> > resin-interest mailing list
>> > resin-interest@caucho.com
>> > http://maillist.caucho.com/mailman/listinfo/resin-interest
>> >
>> >
>>
>>
>> ___
>> resin-interest mailing list
>> resin-interest@caucho.com
>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>
>









___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin Eclipse Feature on Ecliple Galileo (3.5)

2009-09-22 Thread Emil Ong
Is this a fresh install of Galileo or do you have other plugins
installed?  I tested on the Java EE package of Galileo from eclipse.org 
and never saw this error.

Actually, could you send the version of the "org.eclipse.wst.*"
plugins that you've got installed?  It's possible one of our plugin
dependencies is too specific about versions.

Thanks,
Emil

On Tue, Sep 22, 2009 at 01:11:56PM +0200, Michael Ludwig wrote:
> The Resin Eclipse Feature (REF) produces exceptions on my Eclipse
> Galileo (3.5) on Java 1.6 on Windows XP.
> 
> After installation of the REF and the recommended subsequent restart,
> when clicking on the Servers view for the first time, there is an error
> that wasn't there before:
> 
>Could not initialize class
>org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager
> 
> Creating a Resin server ("temporary directory" flavour) works for me.
> When finishing the creation process, the error reoccurs:
> 
>Could not initialize class
>org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager
> 
> When clicking on the new Resin server in the Servers view, same error.
> When trying to start the server, a non-terminating sequence of errors
> occurs (stacktrace following). The funny thing is that the error
> sequence is respawned after clicking on OK or closing the little
> Eclipse error message dialogue.
> 
>  stack trace 
> 
> eclipse.buildId=I20090611-1540
> java.version=1.6.0_11
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> Framework arguments:  -product org.eclipse.epp.package.java.product
> Command-line arguments:  -os win32 -ws win32 -arch x86 -product 
> org.eclipse.epp.package.java.product
> 
> This is a continuation of log file 
> C:\MILU\eclipse35workspace\.metadata\.bak_0.log
> Created Time: 2009-09-22 12:54:41.500
> 
> Error
> Tue Sep 22 12:56:19 CEST 2009
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager
>   at 
> org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getStateImage(ServerDecorator.java:142)
>   at 
> org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStateImage(ServerDecorator.java:137)
>   at 
> org.eclipse.wst.server.ui.internal.cnf.ServerLabelProvider.getImage(ServerLabelProvider.java:76)
>   at 
> org.eclipse.ui.internal.navigator.extensions.SafeDelegateCommonLabelProvider.getImage(SafeDelegateCommonLabelProvider.java:106)
>   at 
> org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:213)
>   at 
> org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:110)
>   at 
> org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:103)
>   at 
> org.eclipse.ui.internal.navigator.NavigatorDecoratingLabelProvider$StyledLabelProviderAdapter.getImage(NavigatorDecoratingLabelProvider.java:60)
>   at 
> org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.getImage(DelegatingStyledCellLabelProvider.java:184)
>   at 
> org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.getImage(DecoratingStyledCellLabelProvider.java:167)
>   at 
> org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.update(DelegatingStyledCellLabelProvider.java:118)
>   at 
> org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.update(DecoratingStyledCellLabelProvider.java:134)
>   at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145)
>   at 
> org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932)
>   at 
> org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at org.eclipse.core.runtime.Platform.run(Platform.java:888)
>   at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
>   at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
>   at 
> org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012)
>   at 
> org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:481)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at org.eclipse.core.runtime.Platform.run(Platform.java:888)
>   at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
>   at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2111)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.internalUpdate(StructuredViewer.java:2094)
>   at 
> org.eclipse.jface.viewers.Stru

Re: [Resin-interest] Noob question: Do I have to restart?

2009-09-22 Thread Rom Sok
Thanks


On Tue, Sep 22, 2009 at 12:10 PM, Jeff Schnitzer wrote:

> Hot deployment works fine for me out of the box, but note that Resin
> doesn't immediately reload the webapp when web.xml or the war changes.
>  You have to actually request a page, then the app will reload.
>
> If you change JSP files they are picked up immediately, no reload
> necessary.
>
> Jeff
>
> On Tue, Sep 22, 2009 at 7:23 AM, Rom Sok  wrote:
> > Hi,
> >
> > Sorry about the newbie question, do I have to restart Resin every time I
> > drop a new version of some file into the deployment directory? like say
> > web.xml?
> > Is there a way to just reload the app without doing the whole "Stop" - >
> > "Quit" -> httpd.exe all over again?
> >
> > Also, is that what is called hot deployment? Or is there another term for
> > redeploying an app without starting the server?
> >
> > Thanks,
> >
> >
> > ___
> > resin-interest mailing list
> > resin-interest@caucho.com
> > http://maillist.caucho.com/mailman/listinfo/resin-interest
> >
> >
>
>
> ___
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
>
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Noob question: Do I have to restart?

2009-09-22 Thread Jeff Schnitzer
Hot deployment works fine for me out of the box, but note that Resin
doesn't immediately reload the webapp when web.xml or the war changes.
 You have to actually request a page, then the app will reload.

If you change JSP files they are picked up immediately, no reload necessary.

Jeff

On Tue, Sep 22, 2009 at 7:23 AM, Rom Sok  wrote:
> Hi,
>
> Sorry about the newbie question, do I have to restart Resin every time I
> drop a new version of some file into the deployment directory? like say
> web.xml?
> Is there a way to just reload the app without doing the whole "Stop" - >
> "Quit" -> httpd.exe all over again?
>
> Also, is that what is called hot deployment? Or is there another term for
> redeploying an app without starting the server?
>
> Thanks,
>
>
> ___
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
>
>


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Noob question: Do I have to restart?

2009-09-22 Thread Rom Sok
Hi,

Sorry about the newbie question, do I have to restart Resin every time I
drop a new version of some file into the deployment directory? like say
web.xml?
Is there a way to just reload the app without doing the whole "Stop" - >
"Quit" -> httpd.exe all over again?

Also, is that what is called hot deployment? Or is there another term for
redeploying an app without starting the server?

Thanks,
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Resin Eclipse Feature on Ecliple Galileo (3.5)

2009-09-22 Thread Michael Ludwig
The Resin Eclipse Feature (REF) produces exceptions on my Eclipse
Galileo (3.5) on Java 1.6 on Windows XP.

After installation of the REF and the recommended subsequent restart,
when clicking on the Servers view for the first time, there is an error
that wasn't there before:

   Could not initialize class
   org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager

Creating a Resin server ("temporary directory" flavour) works for me.
When finishing the creation process, the error reoccurs:

   Could not initialize class
   org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager

When clicking on the new Resin server in the Servers view, same error.
When trying to start the server, a non-terminating sequence of errors
occurs (stacktrace following). The funny thing is that the error
sequence is respawned after clicking on OK or closing the little
Eclipse error message dialogue.

 stack trace 

eclipse.buildId=I20090611-1540
java.version=1.6.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product 
org.eclipse.epp.package.java.product

This is a continuation of log file 
C:\MILU\eclipse35workspace\.metadata\.bak_0.log
Created Time: 2009-09-22 12:54:41.500

Error
Tue Sep 22 12:56:19 CEST 2009
Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.NoClassDefFoundError: Could not initialize class 
org.eclipse.wst.server.ui.internal.provisional.UIDecoratorManager
at 
org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getStateImage(ServerDecorator.java:142)
at 
org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStateImage(ServerDecorator.java:137)
at 
org.eclipse.wst.server.ui.internal.cnf.ServerLabelProvider.getImage(ServerLabelProvider.java:76)
at 
org.eclipse.ui.internal.navigator.extensions.SafeDelegateCommonLabelProvider.getImage(SafeDelegateCommonLabelProvider.java:106)
at 
org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:213)
at 
org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:110)
at 
org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:103)
at 
org.eclipse.ui.internal.navigator.NavigatorDecoratingLabelProvider$StyledLabelProviderAdapter.getImage(NavigatorDecoratingLabelProvider.java:60)
at 
org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.getImage(DelegatingStyledCellLabelProvider.java:184)
at 
org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.getImage(DecoratingStyledCellLabelProvider.java:167)
at 
org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.update(DelegatingStyledCellLabelProvider.java:118)
at 
org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.update(DecoratingStyledCellLabelProvider.java:134)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145)
at 
org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932)
at 
org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at 
org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012)
at 
org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:481)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at 
org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2111)
at 
org.eclipse.jface.viewers.StructuredViewer.internalUpdate(StructuredViewer.java:2094)
at 
org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:2033)
at org.eclipse.jface.viewers.ColumnViewer.update(ColumnViewer.java:554)
at org.eclipse.ui.navigator.CommonViewer.update(CommonViewer.java:540)
at 
org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:1977)
at 
org.eclipse.jface.viewers.StructuredViewer.handleLabelProviderChanged(StructuredViewer.java:1140)
at 
org.eclipse.ui.navigator.CommonViewer.handleLabelProviderChanged(CommonViewer.java:235)
at 
org.eclipse.jface.viewe

Re: [Resin-interest] Caucho site missing eclipse plug-in link?

2009-09-22 Thread Michael Ludwig
Randy Johnson schrieb:
> http://caucho.com/eclipse/
>
> To add this update site to your eclipse
> configuration:
>
>1. Within Eclipse, access the menu: Help -> Software Updates...
>2. Click the "Available Software" tab
>3. Click the "Add Site"
>4. Enter http://caucho.com/eclipse
>5. Click "OK"
>6. Click "Refresh" and install the Resin Eclipse plugin!

Can't see a "Refresh" button in Galileo, but if that's what you're
using you may have to uncheck "Group items by category" in order for
the "Resin Eclipse Feature" to show up.

But there may be errors with Galileo and the Resin Feature. See
following post.

-- 
Michael Ludwig


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest