Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Bundle startup order in virgin VWS
Bundle startup order in virgin VWS [message #800093] Thu, 16 February 2012 12:27 Go to next message
Barbara Rosi-Schwartz is currently offline Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009
Senior Member
Hello.

When I start a virgin VWS, with the standard three artefacts in its pickup directory, what determines the order in which they are started?

I have two instances of VWS running, one of them starts up without fail every time, whereas the other one occasionally fails to do so because it is waiting for services and dependencies that are not yet available and eventually gives up after 180 seconds.

Any ideas?

TIA,
B.
Re: Bundle startup order in virgin VWS [message #800097 is a reply to message #800093] Thu, 16 February 2012 12:30 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Barbara, you can define that using a plan; see: http://www.eclipse.org/virgo/documentation/virgo-documentation-2.1.0.RELEASE/docs/virgo-programmer-guide/html/ch04s03.html

hth,

Miles
Re: Bundle startup order in virgin VWS [message #800576 is a reply to message #800097] Fri, 17 February 2012 03:39 Go to previous messageGo to next message
Barbara Rosi-Schwartz is currently offline Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009
Senior Member
Thanks Miles.

This is a virgin installation though. Do I still require a plan? And if so, what is the order supposed to be? In the pickup dir there are a jar, a par and a plan.

Thanks,
B.
Re: Bundle startup order in virgin VWS [message #800613 is a reply to message #800576] Fri, 17 February 2012 04:19 Go to previous messageGo to next message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
The three items in the pickup directory are the splash screen WAR file, the admin console plan, and the hosted repository PAR file. There are no dependencies between these three, so the startup order should not matter. The startup order is undefined - it depends on the vagaries of the file system lookup.

Is the VWS that is failing a virgin install? Is it running in a different environment to the other two (e.g. machine, OS, JRE)?
Re: Bundle startup order in virgin VWS [message #800648 is a reply to message #800613] Fri, 17 February 2012 05:06 Go to previous messageGo to next message
Barbara Rosi-Schwartz is currently offline Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009
Senior Member
Yes, it is a virgin Virgo and yes, it is running on a Red Hat Enterprise Linux 5 box, whereas the others are running on Windows 7.

Here's an excerpt of the log file when things fail:
[2012-02-16 15:38:21.682] startup-tracker              <KE0001I> Kernel starting. 
[2012-02-16 15:38:22.556] service-monitor-thread-1     <KE0100W> Reference '&deployer' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:38:22.557] service-monitor-thread-1     <KE0100W> Reference '&objectNameCreator' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.model.management.RuntimeArtifactModelObjectNameCreator)'. 
[2012-02-16 15:38:23.845] service-monitor-thread-1     <KE0100W> Reference '&runtimeArtifactModel' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.model.RuntimeArtifactModel)'. 
[2012-02-16 15:38:23.846] service-monitor-thread-1     <KE0100W> Reference '&applicationDeployer' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:38:37.575] service-monitor-thread-1     <KE0100W> Reference '&deployer' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:38:37.576] service-monitor-thread-1     <KE0100W> Reference '&objectNameCreator' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.model.management.RuntimeArtifactModelObjectNameCreator)'. 
[2012-02-16 15:38:38.855] service-monitor-thread-1     <KE0100W> Reference '&runtimeArtifactModel' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.model.RuntimeArtifactModel)'. 
[2012-02-16 15:38:38.856] service-monitor-thread-1     <KE0100W> Reference '&applicationDeployer' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:39:22.788] service-monitor-thread-1     <KE0100W> Reference '&deployer' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:39:22.789] service-monitor-thread-1     <KE0100W> Reference '&objectNameCreator' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.model.management.RuntimeArtifactModelObjectNameCreator)'. 
[2012-02-16 15:39:23.864] service-monitor-thread-1     <KE0100W> Reference '&runtimeArtifactModel' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.model.RuntimeArtifactModel)'. 
[2012-02-16 15:39:23.865] service-monitor-thread-1     <KE0100W> Reference '&applicationDeployer' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:40:22.813] service-monitor-thread-1     <KE0100W> Reference '&deployer' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:40:22.814] service-monitor-thread-1     <KE0100W> Reference '&objectNameCreator' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.model.management.RuntimeArtifactModelObjectNameCreator)'. 
[2012-02-16 15:40:23.873] service-monitor-thread-1     <KE0100W> Reference '&runtimeArtifactModel' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.model.RuntimeArtifactModel)'. 
[2012-02-16 15:40:23.874] service-monitor-thread-1     <KE0100W> Reference '&applicationDeployer' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:41:21.803] startup-tracker              <KE0004E> Kernel failed to start within 180 seconds. 
[2012-02-16 15:41:22.833] service-monitor-thread-1     <KE0100W> Reference '&deployer' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:41:22.834] service-monitor-thread-1     <KE0100W> Reference '&objectNameCreator' in bundle 'org.eclipse.virgo.kernel.shell' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.model.management.RuntimeArtifactModelObjectNameCreator)'. 
[2012-02-16 15:41:23.882] service-monitor-thread-1     <KE0100W> Reference '&runtimeArtifactModel' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.model.RuntimeArtifactModel)'. 
[2012-02-16 15:41:23.883] service-monitor-thread-1     <KE0100W> Reference '&applicationDeployer' in bundle 'org.eclipse.virgo.kernel.model' version '3.0.0.M03' is waiting for service with filter '(objectClass=org.eclipse.virgo.kernel.deployer.core.ApplicationDeployer)'. 
[2012-02-16 15:41:28.363] startup-tracker              <ME0003I> Dump 'serviceability/dump/2012-02-16-15-41-803' generated 
[2012-02-16 15:41:28.364] startup-tracker              <KE0011I> Immediate shutdown initiated. 


Thanks.
Re: Bundle startup order in virgin VWS [message #800661 is a reply to message #800648] Fri, 17 February 2012 05:26 Go to previous message
Glyn Normington is currently offline Glyn Normington
Messages: 1222
Registered: July 2009
Senior Member
Presumably it's a slow box or somehow the default JVM heap size is so small that a lot of GC activity is taking place and slowing down Virgo startup. See bug 366423 for more.
Previous Topic:JMX Mbean registration and configuration artifacts
Next Topic:Error w/Spring 3.1.0.RELEASE in repository/usr w/Virgo Tomcat 3.5.0.M02
Goto Forum:
  


Current Time: Wed Aug 27 15:11:50 EDT 2014

Powered by FUDForum. Page generated in 0.02318 seconds