Skip to main content
CollegeSource Support

Troubleshooting the Web Apps

 


When I start up my 4.4 installations of the web apps using Java 6, I get errors generated on startup. Why?

Numerous third-party library changes in the uAchieve 4.4 release means that Java 7 in now required. Please review the system requirements to ensure you are at least meeting the minimum requirements for running 4.4.

I see a bunch of properties files have been moved to the database in 4.4. This is great, but...how can I cross reference the old property names that I know to their new database name?

Over 270 properties were moved in the 4.4 release! See the list of property changes here.

I had all of my configs set up, but now they seem to be lost. What happened?

Be careful–this can happen accidentally in the copy back process. For example, copying from production back to your test environment can wipe out all of your configs. Best practices recommend you do not copy the PROPERTY and PROPERTY_CONFIG tables.

What options exist for debugging the web apps?

Two options exist for troubleshooting CollegeSource web applications: P6Spy SQL Trace and log4jdbc:

P6Spy SQL Trace

The P6Spy SQL trace generates a trace log of every SQL statement run by the uAchieve server, with parameters included.

  1. Download spy.properties file and p6spy.jar
  2. Place the p6spy.jar file on the classpath in <webAppHome>/WEB-INF/lib and place the spy.properties file on your classpath in <webAppHome>/WEB-INF/classes directory.
  3. Edit the web application's .properties file that has the jdbc.driver property setting you want to see SQL statement parameters for and change your driver to:

    <differentPerWebApp>.jdbc.driver=com.p6spy.engine.spy.P6SpyDriver

     

    Web apps.properties files
    uAchieve Planner

    •  udirect.properties
    • ** If daversion=darwin, darwin.properties : If daversion=uachieve, uachieve.properties

    **Note: If having trouble, by default the darwin/uachieve datasource is configured as an alias to the udirect datasource. You might try to configure it NOT to be an alias to see the actual SQL statements going on for requesting and returning an audit. This would be configured in: If daversion=darwin, dars-jdbc-ctx.xml : If daversion=uachieve, uachieve-jdbc-ctx.xml

    uAchieve Self-Service

    • selfservice-database.properties

     

  4. Edit spy.properties and change the property realDriver (will have to scroll down some) to your actual driver from what you had before in the property above. In this example, Oracle is being tested:

    realdriver=oracle.jdbc.driver.OracleDriver

     

  5. A spy.log file should be generated–probably at the root directory.

Troubleshooting: If Nothing Shows Up
If hardly anything shows up in the spy.log, in spy.properties set the property useprefix=true. Then, restart server and try again.

If still nothing, set deregisterdrivers=true, restart the server and try again.

Log6jdbc

Log4jdbc has proven useful when debugging CollegeSource web applications as an easier to get started with and use as compared to p6spy. Follow the steps below to debug web applications with log4jdbc:

  1. Download the log4jbc jar file here.
  2. Drop the log4jdbc4-[version].jar file into [webapp]/WEB-INF/lib
  3. In u.direct properties, tweak the following datasource properties:
    1. udirect.jdbc.driver=net.sf.log4jdbc.jdbcapi.DriverSpy
    2. udirect.jdbc.url=jdbc:log4jdbc:oracle:thin:hostname:port:sid
  4. For the URL, prepend jdbc:log4
  5. Add this in the log4j.xml:
    1. <logger name="log4jdbc.log4j2" level=“info" />

 

  • Was this article helpful?