|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
uPortal 2.6.0GA ships, such that when you start uPortal and log in, you see a LOT of output in the catalina.out file. Further investigation shows this is because the new 'statsContext' configures a System.out.println logger for most portal events. The system.out.println logger should be removed from uPortal and removed from the pre-configured statsContext. Additionally the logging level (which events are logged) for the existing log4j logger should be examined.
|
|
Description
|
uPortal 2.6.0GA ships, such that when you start uPortal and log in, you see a LOT of output in the catalina.out file. Further investigation shows this is because the new 'statsContext' configures a System.out.println logger for most portal events. The system.out.println logger should be removed from uPortal and removed from the pre-configured statsContext. Additionally the logging level (which events are logged) for the existing log4j logger should be examined. |
Show » |
|
Bug
Closed
Minor
uPortal 2.6.0 ships with System.out.println logging turn on for portal events
Modified the statsContext.xml to list the major event types (everything that directly subclasses PortalEvent), commented out all events except the user login/logout and session created/destroyed events. Modifying the list of events that are desired is now, simply a matter of customizing the lines that are commented/uncommented in statsContext.xml.