cancel
Showing results for 
Search instead for 
Did you mean: 

non starting of virtual server:following msg appeared

kshitizgupta
Champ in-the-making
Champ in-the-making
INFO: XML validation disabled
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: java.lang.NullPointerException
        at org.alfresco.catalina.host.AVMHostConfig$AVMWebappDescriptor.setParen
tRepo(AVMHostConfig.java:2038)
        at org.alfresco.catalina.host.AVMHostConfig.deployAVMWebappsInDependency
Order(AVMHostConfig.java:1014)
        at org.alfresco.catalina.host.AVMHostConfig.deployAllAVMwebappsInReposit
ory(AVMHostConfig.java:403)
        at org.alfresco.catalina.host.AVMHostConfig.deployApps(AVMHostConfig.jav
a:244)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
        at org.alfresco.catalina.host.AVMHostConfig.start(AVMHostConfig.java:196
)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:310)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:119)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)

Mar 15, 2007 7:34:38 PM org.alfresco.mbeans.VirtServerRegistrationThread registe
rVirtServer
INFO: Connected to remote Alfresco JMX Server
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.alfresco.catalina.host.AVMHost.start(AVMHost.java:586)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442
)
        at org.apache.catalina.core.StandardService.start(StandardService.java:4
50)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:709
)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        … 6 more
12 REPLIES 12

caedmon
Champ in-the-making
Champ in-the-making
Sorry for being incredibly dense here…  How am I supposed to install as a windows service?



Ok, so a more thorough search of the forum turned this up…

http://forums.alfresco.com/viewtopic.php?t=4071

Going back to lurking….

jcox
Champ in-the-making
Champ in-the-making
Hey, I was finally able to get this to happen on a local machine,
and was able to track the problem down & fix it.

See:  http://issues.alfresco.com/browse/WCM-434

If you want to try out *just* this fix & don't want to wait for 2.1, you can grab a nightly, and toss
$VIRTUAL_TOMCAT_HOME/server/lib/alfresco-catalina-virtual.jar into a 2.0.x distribution.
Restart the virt server, and you're all set (no need to restart the alfresco webapp).

Thanks again to those who gave me their debug log files.

  - Jon

jcox
Champ in-the-making
Champ in-the-making
If for some reason you cannot upgrade to r5648 or better,
you could do the following:

        [0]  Turn off the virt server.

        [1]  Mount the AVM via cifs

        [2]  Look at  <storename>:/www/avm_webapps/*
             for each store corresponding to an author
             (e.g.:  mysite–alice:/www/avm_webapps/*

        [3]  Via cifs, delete any webapp dir/file that isn't also in staging.
              When you do this, be sure to list every file,
              including hidden files.  If you're on windows, I prefer to
              use a cygwin shell and do an  "ls -laF"

        [4]  When doing a bulk import prior to r5648, do it
              in staging not an author area.

        [5]  Now that everything within your author stores at the
              /www/avm_webapps/* level is seen via transparency,
             your virt server should be able to start again.

Again, the best approach is to upgrade to >= r5648,
so this workaround only applies to those who cannot.

I hope this helps,
  -Jon