Unsolved
This post is more than 5 years old
5 Posts
0
2045
February 19th, 2013 08:00
Content Server - JBoss startup error
Hi all,
we have Documentum 6.6 running on a Linux environment (RedHat). JBoss version is 4.3.0.
When I try to startup JBoss on Content Server, I receive an error.
Strangely I have 2 Content Servers in this environment, and the other one is still working without any errors.
Nothing changed recently and I can't explain how this error can be appeared.
Here it is a portion of the startup log:
5:53:47,413 INFO [TomcatDeployer] deploy, ctxPath=/ACS, warUrl=.../deploy/acs.ear/bocs.war/
14948 [FelixStartLevel] WARN com.documentum.fc.common.impl.logging.LoggingConfigurator - Using default log4j configuration
15443 [Thread-28] ERROR STDERR - Exception in thread "Thread-28"
15454 [Thread-28] ERROR STDERR - java.lang.NoClassDefFoundError: org/apache/commons/lang/builder/ToStringStyle
15454 [Thread-28] ERROR STDERR - at com.documentum.fc.common.DfFileWatcher.getConfigCheckInterval(DfFileWatcher.java:31)
15454 [Thread-28] ERROR STDERR - at com.documentum.fc.common.DfFileWatcher.run(DfFileWatcher.java:54)
15454 [Thread-28] ERROR STDERR - Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.apache.commons.lang.builder.ToStringStyle
15454 [Thread-28] ERROR STDERR - at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
15454 [Thread-28] ERROR STDERR - at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514)
15454 [Thread-28] ERROR STDERR - at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408)
15454 [Thread-28] ERROR STDERR - at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
15454 [Thread-28] ERROR STDERR - at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
15454 [Thread-28] ERROR STDERR - ... 2 more
15467 [FelixStartLevel] ERROR STDERR - java.lang.ExceptionInInitializerError
15467 [FelixStartLevel] ERROR STDERR - at com.documentum.acs.sdi.servlet.ACS.init(ACS.java:54)
15467 [FelixStartLevel] ERROR STDERR - at com.documentum.osgi.http.service.impl.HttpService.register(HttpService.java:28)
15467 [FelixStartLevel] ERROR STDERR - at com.documentum.acs.sdi.osgi.ServletActivator$HttpTrackerCustomizer.addingService(ServletActivator.java:48)
15467 [FelixStartLevel] ERROR STDERR - at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)
15467 [FelixStartLevel] ERROR STDERR - at org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:891)
15467 [FelixStartLevel] ERROR STDERR - at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:296)
15467 [FelixStartLevel] ERROR STDERR - at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:235)
15467 [FelixStartLevel] ERROR STDERR - at com.documentum.acs.sdi.osgi.ServletActivator.start(ServletActivator.java:25)
15467 [FelixStartLevel] ERROR STDERR - at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589)
15467 [FelixStartLevel] ERROR STDERR - at org.apache.felix.framework.Felix._startBundle(Felix.java:1671)
15467 [FelixStartLevel] ERROR STDERR - at org.apache.felix.framework.Felix.startBundle(Felix.java:1588)
15468 [FelixStartLevel] ERROR STDERR - at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1180)
15468 [FelixStartLevel] ERROR STDERR - at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:265)
15468 [FelixStartLevel] ERROR STDERR - at java.lang.Thread.run(Thread.java:619)
The entire startup log is attached.
Any idea?
S.P.
d5m
31 Posts
0
March 15th, 2013 07:00
Could you fix this issue? I'm getting the same error.
Ste91
5 Posts
0
April 11th, 2013 07:00
Hi, at this time I couldn't manage to fix the issue.
Stefano
aldago-zF7Lc
463 Posts
1
April 11th, 2013 07:00
Have you tried copying the apache-commons located in Documentum shared folder to the Jboss' lib folder? It's a bit radical but it should work
Ste91
5 Posts
0
April 12th, 2013 02:00
Hi Alvaro,
thanks for your reply.
I did what you suggested.
Actually, copying jar files into Jboss' lib folder has removed the error in log4j.log.
Nevertheless there still was a problem; when I tried to start JBoss, the output was splitted into two logs: nohup.out (the command used to startup Jboss is "nohup.out ./startMethodServer.sh") and log4j.log. The warning was: " [...] Problem locating log4j [...] Using default log4j configuration [...]".
So I checked deeply: the dfc.jar in $DCTM_SHARED/jboss4.3.0/server/DctmServer_MethodServer/deploy/acs.ear/APP-INF/lib was unaligned with the other CS (in this environment we have 2 CS). Don't ask me why they were unaligned: the version was the same, but not the size. Maybe someone has changed it remotely but the operation somehow went wrong.
Anyway, I copied the other CS' dfc.jar into this one: all problems were solved.
After that I also removed the .jar you suggested me to copy: it is working good.
Thanks again for your help.
Regards,
Stefano