Posts tagged "jboss"

LiveCycle: JBoss stopped logging in server.log

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>\server\<profile>\log\server.log

If the JBoss log is no longer logging activity you should check the following:

1. Log4J

The jboss-log4j.xml file is located in <JBOSS_HOME>\server\lc_turnkey\conf and controls logging in JBoss.  If there is any problem with this file then logging may stop working.  You can download this file (jboss-log4j-working) from a fresh LiveCycle installation on JBoss and replace the original (make a backup first).  Restart JBoss after swapping the log4j file and logging should switch to the server1.log file.

2. User account

If you are starting JBoss using a Windows service ensure that the user account used for the service has administrative privileges.  See the installation documentation for further requirements such as disabling UAC on Windows.

reference: (183305796)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 1.5/10 (2 votes cast)

LiveCycle ES: ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener

Issue

 If you have manually configured the JBoss4.2.x  application server and installed LiveCycle ES, you may receive the following exception when starting JBoss:

13:36:29,277 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:36:29,793 ERROR [[/]] Error configuring application listener of class 
org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3797)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4359)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Reason

During the manual configuration of JBoss 4.2.x the documentation from prepareinstallsingle.pdf advises you to disable the JSF libraries contained in [appserver root]/server/all/deploy/jboss-web.deployer.  You must disable the JSF libraries, and also remove the related entries from the web.xml, otherwise the above excpetion will occur when starting JBoss.

Solution

Comment out or remove the following entries from [appserver root]/server/<config-name>/deploy/jboss-web.deployer/conf/web.xml:

<!-- Comment/Remove this -->
<!-- Configures JSF for a web application if thejavax.faces.webapp.FacesServlet is declared -->
<!-- in web.xml.-->
<!--
    <listener>
        <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
    </listener>
-->

<!-- Comment/Remove this -->
<!-- Listens to all web app lifecycle events so that @PreDestroy can becalled on -->
<!-- JSF managed beans that go out of scope. You can comment this out if you-->
<!-- don't use JSF or you don't use annotations on your managed beans.-->
<!--
    <listener>
        <listener-class>com.sun.faces.application.WebappLifecycleListener</listenerclass>
    </listener>
-->

<!--
    <init-param>
        <description>JSF standard tlds</description>
        <param-name>tagLibJar0</param-name>
        <param-value>jsf-libs/jsf-impl.jar</param-value>
    </init-param>
-->
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 3.0/10 (1 vote cast)