topic [SOLVED]RMI Excpetion not solved in Alfresco Archive

[SOLVED]RMI Excpetion not solved

sisao — Mon, 09 Feb 2009 11:50:48 GMT

Hi,i've gone through a lot of posts about this issue…and i also tought i had solved it by replacing "localhost" with "127.0.0.1" in the alfresco-shared property file, but it worked for a while then it persists…i can start alfresco but if i turn it off i have to reboot in order to start it up again.1

Re: [SOLVED]RMI Excpetion not solved

mrogers — Mon, 09 Feb 2009 12:57:39 GMT

You have a some sort of issue with shutdown. Which is why Alfresco restarts after a reboot.

Which version of Alfresco are you using?
What errors are in your log file?

Re: [SOLVED]RMI Excpetion not solved

sisao — Mon, 09 Feb 2009 14:41:40 GMT

i am using the latest labs release and the snapshot i provided above is from the alfresco.log (startup session)…it's actually boring as everytime i have to restart the server for a change to be applied i have to reboot my machine.

catalina.log interesting rows:

9-feb-2009 15.29.37 org.apache.catalina.core.StandardContext addApplicationListener
INFO: The listener "org.apache.myfaces.webapp.StartupServletContextListener" is already configured for this context. The duplicate definition has been ignored.
9-feb-2009 15.30.00 org.apache.catalina.core.StandardContext start
GRAVE: Error listenerStart
‍‍‍‍‍

other log files are actually empty…i've specified both loopback and dhcp assigned ip into /etc/hosts, i've removed duplicated jars from /WEB-INF/lib and i've forced repository.properties to randomly assign a port number to the RMI services (using "0").

Dont really have a clue but i can see this is common with the RMI jar.

Re: [SOLVED]RMI Excpetion not solved

mrogers — Mon, 09 Feb 2009 15:22:18 GMT

The exception you posted is a symptom of an earlier problem not the problem itself, fiddling with the network settings will have no effect.

What platform are you on?
How are you shutting down alfresco?
Is there nothing in your alfresco log file related to shutdown? Perhaps shutdown errors?

Re: [SOLVED]RMI Excpetion not solved

sisao — Mon, 09 Feb 2009 16:00:14 GMT

I'm using a OsX machine (latest Leopard and JVM 1.5.0).
I shut down alfresco by providing "alfresco.sh stop" …. i have not altered the alfresco.sh script.

This is the catalina output while shutting alfresco down:

9-feb-2009 16.56.34 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8089
9-feb-2009 16.56.35 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
9-feb-2009 16.56.35 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
9-feb-2009 16.56.36 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
9-feb-2009 16.56.37 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
9-feb-2009 16.56.41 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8089
9-feb-2009 16.56.47 org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load org.apache.log4j.spi.NOPLoggerRepository.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1273)
   at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
   at org.apache.log4j.LogManager.getLoggerRepository(LogManager.java:175)
   at org.apache.log4j.LogManager.getLogger(LogManager.java:199)
   at org.apache.log4j.Logger.getLogger(Logger.java:105)
   at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283)
   at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:239)
   at org.alfresco.repo.shutdown.ShutdownBackstop$ShutdownBackstopThread.run(ShutdownBackstop.java:131)
 ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Dunno if that exception is somehow related to that problem…may this somehow related on the fact i have a proper tomcat installation on port 8080 (not active though).