Trouble Shooting

1.

Problem: log4j:WARN Document root element "log4j:configuration", must match DOCTYPE root "null".

Solution: Add '<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">' to log4j.xml

    e.g.:

    <?xml version="1.0" encoding="UTF-8" ?>

    <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

    <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

    ...

    </log4j:configuration>

 

2.

Problem: [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent!

Solution: Specify encoding in pom.xml

    <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-resources-plugin</artifactId>

        <configuration>

            <encoding>UTF-8</encoding>

        </configuration>

    </plugin>

 

3.

Problem: [ERROR] Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log

Solution: 1.login into Websphere administrative console;

          2.Servers -> Server Types -> Websphere application servers -> server1 -> Generic Properties -> Server-specific;

          3.Change the 'Classloader policy' to 'Single';

          4.Change the 'Class loading model' to 'Classes loaded with parent class loader first';

          5.Restart Websphere.

 

4.

PCIS SSO:

    1.make sure the WAS administrator named - 'java';

    2.navigate to - Security -> Global security;

    3.make the 'Application security - Enable application security' is checked.

 

5.

Problem: JBoss can't found JNDI naming:

Solution: In JBoss, we should prefix 'java:/' in the normal jndi name when referencing.

 

6.

Problem: SQL Server + WAS: 

    If the Microsoft SQL Server JDBC Driver v1.2 or 2.0 is used instead of the jTDS driver, then the SQLServerDictionary will throw an exception while trying to parse the driverName "Microsoft SQL Server JDBC Driver" to determine the server version.

    Example stack :

    java.lang.NumberFormatException: For input string: "JDBC" 

    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

    at java.lang.Integer.parseInt(Integer.java:447)

    at java.lang.Integer.parseInt(Integer.java:497)

    at org.apache.openjpa.jdbc.sql.SQLServerDictionary.connectedConfiguration(SQLServerDictionary.java:92)

Solution: 

    The SQLServerDictionary was updated to properly handle the driverName that the Microsoft SQL Server JDBC Driver v1.2 and v2.0 reports when queried.

    The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.7.  Please refer to the Recommended Updates page for delivery information:

    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

 

7.

Problem: log4j:ERROR Attempted to append to closed appender named [console].

Solution: specify each logger with different appander, let's say, do NOT make same appender type used in two loggers.

          We can define multiple [console] appenders with just different name.

 

8.

Problem: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.

                  sourceId=null[severity=(INFO 0), summary=(Welcome, trs), detail=(Welcome, trs)]

Solution:

    change FacesMessage.SEVERITY_* to StatusMessage.Severity.*

 

9.

Problem:

[HTTPThreadGroup-7] ERROR CS2SSOLogger  13 Sep 2010 01:24:08,682 - com.cargosmart.webapp.filter.CargosmartCentralHelper.isTokenValid(): ____ exception occurred when validate token via web service. exception: No Deserializer found to deserialize a &apos;http://com.oocl.cargosmart2.afw.ws/ICS2AuthenticationWebService.xsd:com_oocl_frm_afw_token_TokenImpl&apos; using encoding style &apos;http://schemas.xmlsoap.org/soap/encoding/&apos;. [java.lang.IllegalArgumentException]

Solution:

open url: http://dengas.corp.oocl.com:8888/admin/AFWWebService?WSDL

check whether the complexType(e.g.:'com_oocl_frm_afw_token_TokenImpl') had been truncated arbitrarily!!!!!!!!!

<complexType name="com_oocl_frm_afw_to_TokenImpl">  <------- 'token' had been truncated to 'to' here, so issue accured.

try to shorten oc4j home path to solve this problem. e.g.: install oc4j in 'c:\oc4j' folder.