Task #537 (closed)
Opened 17 years ago
Closed 15 years ago
Lower log4j settings for JDBCExceptionReporter
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | trivial | Milestone: | OMERO-Beta4 |
Component: | Deployment | Version: | 3.0-M3 |
Keywords: | jboss, postgres, logging | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
JDBCExceptionReporter throws an exception due to #444. A fix is in the works, but we'll need to silence this exception. etc/log4j.properties will work for the tests, but JBOSS_HOME/server/default/conf/log4j.xml will need to be modified for the application server.
Change History (1)
comment:1 Changed 15 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r2799 introduced a JBoss-like log4j.xml configuration which users could opt to use. However, with the OmeroBlitz migration (#1106), this is no longer a problem.