Re: Application not start in womonitor
equestInfo) @bci=6, line=221 (Interpreted frame) - org.exolab.jms.net.connector.AbstractConnectionManager.allocateConnection(org.exolab.jms.net.connector.ManagedConnectionFactory, java.security.Principal, org.exolab.jms.net.connector.ConnectionRequestInfo) @bci=27, line=140 (Interpreted frame) - org.exolab.jms.net.connector.AbstractConnectionFactory.getConnection(java.security.Principal, org.exolab.jms.net.uri.URI, java.util.Map) @bci=28, line=167 (Interpreted frame) - org.exolab.jms.net.connector.AbstractConnectionManager.getConnection(java.security.Principal, org.exolab.jms.net.uri.URI, java.util.Map) @bci=44, line=208 (Interpreted frame) - org.exolab.jms.net.orb.Locator.getProxy(java.rmi.server.ObjID, java.security.Principal, java.lang.String, org.exolab.jms.net.connector.ConnectionFactory, java.lang.String, java.lang.ClassLoader, java.util.Map) @bci=8, line=131 (Interpreted frame) - org.exolab.jms.net.orb.Locator.getRegistry(java.security.Principal, java.lang.String, org.exolab.jms.net.connector.ConnectionFactory, java.lang.ClassLoader, java.util.Map) @bci=25, line=103 (Interpreted frame) - org.exolab.jms.net.orb.DefaultORB.getRegistry(java.util.Map) @bci=96, line=267 (Interpreted frame) - org.exolab.jms.client.net.SharedORB.getRegistry(java.util.Map) @bci=5, line=121 (Interpreted frame) - org.exolab.jms.jndi.InitialContextFactory.getInitialContext(java.util.Hashtable) @bci=94, line=144 (Interpreted frame) - javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable) @bci=114, line=684 (Interpreted frame) - javax.naming.InitialContext.getDefaultInitCtx() @bci=12, line=307 (Interpreted frame) - javax.naming.InitialContext.init(java.util.Hashtable) @bci=21, line=242 (Interpreted frame) - javax.naming.InitialContext.(java.util.Hashtable) @bci=33, line=216 (Interpreted frame) - er.changenotification.ERCNConnectionKeeper.openConnection(boolean) @bci=40, line=48 (Interpreted frame) - er.changenotification.ERCNNotificationCoordinator.initialize(com.webobjects.foundation.NSNotification) @bci=106, line=136 (Interpreted frame) - sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) @bci=0 (Interpreted frame) - sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) @bci=87, line=57 (Interpreted frame) - sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) @bci=6, line=43 (Compiled frame) - java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) @bci=57, line=606 (Compiled frame) - com.webobjects.foundation.NSSelector._safeInvokeMethod(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) @bci=3, line=120 (Interpreted frame) - com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(com.webobjects.foundation.NSNotification) @bci=22, line=601 (Interpreted frame) - com.webobjects.foundation.NSNotificationCenter.postNotification(com.webobjects.foundation.NSNotification) @bci=211, line=545 (Interpreted frame) - com.webobjects.foundation.NSNotificationCenter.postNotification(java.lang.String, java.lang.Object) @bci=11, line=559 (Interpreted frame) - com.webobjects.appserver.WOApplication.run() @bci=87, line=895 (Interpreted frame) - er.extensions.appserver.ERXApplication.run() @bci=294, line=1241 (Interpreted frame) - com.webobjects.appserver.WOApplication.main(java.lang.String[], java.lang.Class) @bci=24, line=324 (Interpreted frame) - er.extensions.appserver.ERXApplication.main(java.lang.String[], java.lang.Class) @bci=6, line=726 (Interpreted frame) - com.tec.util.base.TecApplication.main(java.lang.String[], java.lang.Class) @bci=2, line=25 (Interpreted frame) - com.tec.log.Application.main(java.lang.String[]) @bci=3, line=24 (Interpreted frame) - sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) @bci=0 (Interpreted frame) - sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) @bci=87, line=57 (Interpreted frame) - sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) @bci=6, line=43 (Interpreted frame) - java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) @bci=57, line=606 (Interpreted frame) - com.webobjects._bootstrap.WOBootstrap.main(java.lang.String[]) @bci=118, line=87 (Interpreted frame) Thanks. Oscar Gonzalez Perez TECH n From: ch...@global-village.net<mailto:ch...@global-village.net> To: racso...@hotmail.com<mailto:racso...@hotmail.com>; webobjects-dev@lists.apple.com<mailto:webobjects-dev@lists.apple.com> Subject: Re: Application not start in womonitor Date: Fri, 21 Mar 2014 02:48:51 + Hi Oscar, It sounds like your app is deadlocking hanging waiting for a timeout. This can make wotaskd think that it is dead. When this happens, try doing this sudo jstack –F And
[Solved] RE: Application not start in womonitor
Hi all,Thanks to all of you guys, you are great.It was the hosts file.The localhost entry was always there, but an entry for host name was bad.192.168.2.1 INPROTSA-VPS02LFirst I remove it, but didn't work.Then I put the correct entry192.168.8.4 INPROTSA-VPS02LAnd it works. Oscar Gonzalez PerezTECH in AGRO S.A. Subject: Re: Application not start in womonitor From: pa...@logicsquad.net Date: Fri, 21 Mar 2014 17:26:21 +1030 CC: racso...@hotmail.com; webobjects-dev@lists.apple.com To: webobje...@avendasora.com Hi Dave, On 21/03/2014, at 12:51 PM, David Avendasora wrote:I am not an expert in deployment issues, but I see “… Application 'logistica-1' on localhost:2002 …”. The “localhost” makes me wonder if you setup the application in JavaMonitor using “localhost” as the host name. >From what I’ve seen in the past, the hostname needs to be either a routable IP >address (not 127.0.0.1) or a real domain name (not DavesTiBook.local). If you >use a domain name, it also needs to be the name that a reverse-dns lookup will >resolve to. I know that's the conventional wisdom, and I know you started with a disclaimer, but I think that can be a red herring in the general case (though by all means perhaps not in this specific case). We've got an existence proof, if you like, that it's certainly not universally true. We run Wonder wotaskd and JavaMonitor, and have had both of: * localhost as the hostname* 127.0.0.1 as the IP address on hosts for many years now, and have never had a single deployment issue that I can recall. (Of course, I've just cursed myself...) -- Paul Hoadley http://logicsquad.net/ ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
> Le 2014-03-21 à 02:58, Paul Hoadley a écrit : > > Hi Dave, > >> On 21/03/2014, at 12:51 PM, David Avendasora >> wrote: >> >> I am not an expert in deployment issues, but I see “… Application >> 'logistica-1' on localhost:2002 …”. The “localhost” makes me wonder if you >> setup the application in JavaMonitor using “localhost” as the host name. >> >> From what I’ve seen in the past, the hostname needs to be either a routable >> IP address (not 127.0.0.1) or a real domain name (not DavesTiBook.local). If >> you use a domain name, it also needs to be the name that a reverse-dns >> lookup will resolve to. > > I know that's the conventional wisdom, and I know you started with a > disclaimer, but I think that can be a red herring in the general case (though > by all means perhaps not in this specific case). We've got an existence > proof, if you like, that it's certainly not universally true. We run Wonder > wotaskd and JavaMonitor, and have had both of: > > * localhost as the hostname > * 127.0.0.1 as the IP address > > on hosts for many years now, and have never had a single deployment issue > that I can recall. (Of course, I've just cursed myself...) Same thing for me, I did many set ups with localhost and never had a problem. > > -- > Paul Hoadley > http://logicsquad.net/ > > > > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca > > This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
On Mar 21, 2014, at 2:56 AM, Paul Hoadley wrote: > I know that's the conventional wisdom, and I know you started with a > disclaimer, but I think that can be a red herring in the general case (though > by all means perhaps not in this specific case). We've got an existence > proof, if you like, that it's certainly not universally true. We run Wonder > wotaskd and JavaMonitor, and have had both of: > > * localhost as the hostname > * 127.0.0.1 as the IP address > > on hosts for many years now, and have never had a single deployment issue > that I can recall. (Of course, I've just cursed myself...) Ah. Yeah. See, you’re in Australia. Since everything is upside-down / backwards down there I’m guessing that is the *only* configuration that works. Now if I could just work in a convict/wallaby joke … You know, it’s a good thing us 'mericans never do anything worth ridicule. I’d be in trouble. Whew. Dave — WebObjects - so easy that even Dave Avendasora can do it!™ — David Avendasora Senior Software Abuser Nekesto, Inc. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
Hi Dave, On 21/03/2014, at 12:51 PM, David Avendasora wrote: > I am not an expert in deployment issues, but I see “… Application > 'logistica-1' on localhost:2002 …”. The “localhost” makes me wonder if you > setup the application in JavaMonitor using “localhost” as the host name. > > From what I’ve seen in the past, the hostname needs to be either a routable > IP address (not 127.0.0.1) or a real domain name (not DavesTiBook.local). If > you use a domain name, it also needs to be the name that a reverse-dns lookup > will resolve to. I know that's the conventional wisdom, and I know you started with a disclaimer, but I think that can be a red herring in the general case (though by all means perhaps not in this specific case). We've got an existence proof, if you like, that it's certainly not universally true. We run Wonder wotaskd and JavaMonitor, and have had both of: * localhost as the hostname * 127.0.0.1 as the IP address on hosts for many years now, and have never had a single deployment issue that I can recall. (Of course, I've just cursed myself...) -- Paul Hoadley http://logicsquad.net/ ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
On Mar 20, 2014, at 7:21 PM, David Avendasora wrote: > Hola Oscar, > > I am not an expert in deployment issues, but I see “… Application > 'logistica-1' on localhost:2002 …”. The “localhost” makes me wonder if you > setup the application in JavaMonitor using “localhost” as the host name. > > From what I’ve seen in the past, the hostname needs to be either a routable > IP address (not 127.0.0.1) or a real domain name (not DavesTiBook.local). If > you use a domain name, it also needs to be the name that a reverse-dns lookup > will resolve to. You can use localhost as long as it's the only host in your site. Javamonitor will display "localhost / 127.0.0.1". (This probably only works as long as your /etc/hosts file has an entry for localhost.) kib "The trouble with normal is it always gets worse." Bruce Cockburn Klaus Berkling www.berkling.us | @kiberkli | Buy My iPhone app smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
Hi Oscar, It sounds like your app is deadlocking hanging waiting for a timeout. This can make wotaskd think that it is dead. When this happens, try doing this sudo jstack –F And post the results to the list. Chuck On 2014-03-20, 4:58 PM, "Oscar González" wrote: Hi list, I have a problem staring my application from monitor it appear dead. The process is alive in the system I have to kill it to be able try again. I don't know what is this issue. webobjects 5.3.3 ubuntu linux 12.04 apache 2.2 java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) sudo lsof -P -i tcp:1085 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java1720 appserver 116u IPv4 42087 0t0 TCP *:1085 (LISTEN) The wotaskd log throw this. 2014-03-20 17:47:03,154 WARN 79.76 MB/72.24 MB [main] logging.ERXNSLogLog4jBridge (ERXNSLogLog4jBridge.java:44) - Application 'logistica-1' on localhost:2002 stopped running at 2014-03-20 23:47:03 Etc/GMT. The app's current state was: STARTING. The app did not respond for 63521279103seconds which is greater than the allowed threshold of 12 seconds (Lifebeat Interval * WOAssumeApplicationIsDeadMultiplier) so it is assumed to be dead. The last successful communication occurred at: 1-04-25 00:00:00 Etc/GMT. This may be the result of a crash or an intentional shutdown from outside of wotaskd Thanks in advance. Oscar Gonzalez Perez TECH in AGRO S.A ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Application not start in womonitor
Hola Oscar, I am not an expert in deployment issues, but I see “… Application 'logistica-1' on localhost:2002 …”. The “localhost” makes me wonder if you setup the application in JavaMonitor using “localhost” as the host name. From what I’ve seen in the past, the hostname needs to be either a routable IP address (not 127.0.0.1) or a real domain name (not DavesTiBook.local). If you use a domain name, it also needs to be the name that a reverse-dns lookup will resolve to. However, I could be completely wrong about what the localhost value in the error message indicates. I hope this helps! Dave On Mar 20, 2014, at 7:58 PM, Oscar González wrote: > Hi list, > I have a problem staring my application from monitor it appear dead. > The process is alive in the system I have to kill it to be able try again. > I don't know what is this issue. > > webobjects 5.3.3 > ubuntu linux 12.04 > apache 2.2 > java version "1.7.0_51" > Java(TM) SE Runtime Environment (build 1.7.0_51-b13) > Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) > > sudo lsof -P -i tcp:1085 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > java1720 appserver 116u IPv4 42087 0t0 TCP *:1085 (LISTEN) > > > The wotaskd log throw this. > 2014-03-20 17:47:03,154 WARN 79.76 MB/72.24 MB [main] > logging.ERXNSLogLog4jBridge (ERXNSLogLog4jBridge.java:44) - Application > 'logistica-1' on localhost:2002 stopped running at 2014-03-20 23:47:03 > Etc/GMT. > The app's current state was: STARTING. > The app did not respond for 63521279103seconds which is greater than the > allowed threshold of 12 seconds (Lifebeat Interval * > WOAssumeApplicationIsDeadMultiplier) so it is assumed to be dead. > The last successful communication occurred at: 1-04-25 00:00:00 Etc/GMT. This > may be the result of a crash or an intentional shutdown from outside of > wotaskd > > Thanks in advance. > > Oscar Gonzalez Perez > TECH in AGRO S.A > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com > > This email sent to webobje...@avendasora.com — WebObjects - so easy that even Dave Avendasora can do it!™ — David Avendasora Senior Software Abuser Nekesto, Inc. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
