Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » BIRT » Duplicate JDBC driver issue for 3.7 viewer on JBoss AS 7
Duplicate JDBC driver issue for 3.7 viewer on JBoss AS 7 [message #717062] Fri, 19 August 2011 03:38 Go to next message
Nicklas Karlsson is currently offline Nicklas Karlsson
Messages: 29
Registered: July 2009
Junior Member
When I add an oracle driver jar in the WEB-INF\lib I end up with a

10:23:19,090 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) Deploying JDBC-compliant driver class org.apache.derby.jdbc.AutoloadedDriver (version 10.5)
10:23:19,120 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
10:23:19,121 WARN  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) Unable to instantiate driver class "oracle.jdbc.OracleDriver": org.jboss.msc.service.DuplicateServiceException: Service jboss.jdbc-driver.birt_war is already registered


since the drivers are auto-deployed (JDBC-compliant) and both assume the same name. Is there any known workaround for this? I could remove the Derby driver since I don't need it but other uses might require multiple drivers.

Or should I just install the oracle driver as an AS7 module and make a dependency in META-INF MANIFEST.MF?

Thanks in advance,
Nik
Re: Duplicate JDBC driver issue for 3.7 viewer on JBoss AS 7 [message #717096 is a reply to message #717062] Fri, 19 August 2011 05:39 Go to previous messageGo to next message
Nicklas Karlsson is currently offline Nicklas Karlsson
Messages: 29
Registered: July 2009
Junior Member
The driver module + manifest dependency appear to work
Re: Duplicate JDBC driver issue for 3.7 viewer on JBoss AS 7 [message #717770 is a reply to message #717096] Mon, 22 August 2011 05:37 Go to previous message
Nicklas Karlsson is currently offline Nicklas Karlsson
Messages: 29
Registered: July 2009
Junior Member
And as a mental note, you can't have birt.war as an autodeploying exploded archive unless you move the logs/reports/other changing files out of the directory since (especially) log-writing will cause modified files/directories and a re-deploy (possibly looping)
Previous Topic:BIRT reports driven from SVN as a datasource
Next Topic:Define printers for server side printing
Goto Forum:
  


Current Time: Fri Aug 01 18:33:34 EDT 2014

Powered by FUDForum. Page generated in 0.02014 seconds