Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 66965 - JBoss 3.2.3 can't start web service
Summary: JBoss 3.2.3 can't start web service
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords: PMASKED
Depends on: 64795
Blocks:
  Show dependency tree
 
Reported: 2004-10-10 04:41 UTC by Stephan Fuhrmann
Modified: 2008-01-26 19:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Fuhrmann 2004-10-10 04:41:56 UTC
When trying to start JBoss, the following stuff gets written to the server.log:

...
2004-10-10 13:22:55,551 INFO  [org.jboss.deployment.SARDeployer] nested deployment: file:/var/lib/jboss/default/deploy/jbossweb-tomcat41.sar/naming-common.jar
2004-10-10 13:22:55,552 INFO  [org.jboss.deployment.SARDeployer] nested deployment: file:/var/lib/jboss/default/deploy/jbossweb-tomcat41.sar/tomcat41-service.jar
2004-10-10 13:22:55,552 INFO  [org.jboss.deployment.SARDeployer] nested deployment: file:/var/lib/jboss/default/deploy/jbossweb-tomcat41.sar/commons-beanutils.jar
2004-10-10 13:22:55,552 INFO  [org.jboss.deployment.SARDeployer] nested deployment: file:/var/lib/jboss/default/deploy/jbossweb-tomcat41.sar/servlets-webdav.jar
2004-10-10 13:22:56,361 ERROR [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] Starting failed
org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@10980e7 for org.apache.commons.logging.impl.Log4JLogger
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:414)
        at org.apache.commons.digester.Digester.<init>(Digester.java:346)
        at org.jboss.web.tomcat.tc4.LoggedXmlMapper.<init>(LoggedXmlMapper.java:35)
        at org.jboss.web.tomcat.tc4.ConfigHandler.applyHostConfig(ConfigHandler.java:55)
        at org.jboss.web.tomcat.tc4.EmbeddedTomcatService.initCatalina(EmbeddedTomcatService.java:430)
...
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@10980e7 for org.apache.commons.logging.impl.Log4JLogger
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:432)
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
        ... 74 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
        at java.lang.Class.getConstructor0(Class.java:1930)
        at java.lang.Class.getConstructor(Class.java:1027)
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
        ... 75 more
2004-10-10 13:22:56,370 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.web:service=WebServer
org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@10980e7 for org.apache.commons.logging.impl.Log4JLogger
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:414)
        at org.apache.commons.digester.Digester.<init>(Digester.java:346)
        at org.jboss.web.tomcat.tc4.LoggedXmlMapper.<init>(LoggedXmlMapper.java:35)
        at org.jboss.web.tomcat.tc4.ConfigHandler.applyHostConfig(ConfigHandler.java:55)
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@10980e7 for org.apache.commons.logging.impl.Log4JLogger
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:432)
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
        ... 74 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
        at java.lang.Class.getConstructor0(Class.java:1930)
        at java.lang.Class.getConstructor(Class.java:1027)
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
        ... 75 more
2004-10-10 13:22:56,382 INFO  [org.jboss.deployment.MainDeployer] Deployed package: file:/var/lib/jboss/default/deploy/jbossweb-tomcat41.sar/
2004-10-10 13:22:56,383 INFO  [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/var/lib/jboss/default/deploy/uuid-key-generator.sar
2004-10-10 13:22:56,425 INFO  [org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactoryService] Started jboss:service=UUIDKeyGeneratorFactory



This looks like Tomcat can't start because log4j.jar wasn't found. I expect this problem is something similar to the problem described in bug report 59079, but it isn't a duplicate because it is a real problem and not just an assumption.

There's no web server after starting JBoss. 

Note: the "minimal" version of jboss doesn't report any errors. I expect it to not use web services at all. The problem occurs with "default" and "all" config. 

Adding SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.base.dir=${SERVER_HOME}" to /etc/conf.d/jboss doesn't help.


Reproducible: Always
Steps to Reproduce:
1. Emerge jboss 3.2.3
2. /etc/init.d/jboss start
3. less /var/log/jboss/server.log

Actual Results:  
Half-initialized JBoss without web service! Ports 8080 and 8082 not accessible.



Expected Results:  
Everything should be all right, ports 8080 and/or 8082 (?) should be accessible.

Portage 2.0.50-r11 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.6.8.1
)
=================================================================
System uname: 2.6.8.1 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O3 -pipe -funroll-loops"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2
/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /
usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/sha
re/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/gen
eric/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/lib
/jboss /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe -funroll-loops"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo ftp://gento
o.inode.at/source/ http://gentoo.inode.at/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dga encode esd
 f77 foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww ma
d maildir mikmod mmx motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss p
am pdflib perl png python qt quicktime readline sdl slang spell sse ssl svga tcp
d tetex truetype unicode wxwindows x86 xml2 xmms xprint xv zlib"
Comment 1 Jan Brinkmann (RETIRED) gentoo-dev 2005-02-06 16:12:39 UTC
marking as LATER, reference added to the tracker. also see #81038
Comment 2 Jan Brinkmann (RETIRED) gentoo-dev 2005-02-06 16:29:12 UTC
reopen
Comment 3 Alistair Bush (RETIRED) gentoo-dev 2006-10-28 00:50:27 UTC
I believe that this bug can be closed as WONTFIX by the java team.   3.2.3 is old by any standards and I am hoping to have the jboss-4.* ebuilds that fordfrog and myself have been working on added to the tree shortly.  At that point I believe all previous jboss builds should be removed.

Until then jboss is being worked on available in the migrated-java-experimental-overlay.
Comment 4 Vlastimil Babka (Caster) (RETIRED) gentoo-dev 2008-01-09 06:46:05 UTC
Last rited: http://archives.gentoo.org/gentoo-dev-announce/msg_00069.xml
Comment 5 William L. Thomson Jr. (RETIRED) gentoo-dev 2008-01-26 19:11:54 UTC
Closing bug. Removed from tree, till we get a maintainer and current version
from source.