[jboss-jira] [JBoss JIRA] Commented: (AS7-1151) Error while registering Oracle JDBC Diagnosability MBean

[Stefano Maestri (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612009#comment-12612009 ] 

Stefano Maestri commented on AS7-1151:
--------------------------------------

I've tried with latest Orcle 11 driver (11.2.0.2.0) and it works without error both using cli or web-console, and with both in standalone and domain mode.
Maybe it's a proble of this driver you are using, not in in our code. If we have to support this version too, please send it to me by internal email and I'll give it a try.

regards
S.

> Error while registering Oracle JDBC Diagnosability MBean
> --------------------------------------------------------
>
>                 Key: AS7-1151
>                 URL: https://issues.jboss.org/browse/AS7-1151
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 7.0.0.CR1
>            Reporter: Nicklas Karlsson
>
> Deploying the Oracle 11.1 driver jdbc-driver-11.1.0.6.0.jar through the admin console gives a 
> 10:42:15,938 SEVERE [oracle.jdbc] (MSC service thread 1-7) Error while registering Oracle JDBC Diagnosability MBean.: java.lang.NullPointerException
> 	at oracle.jdbc.driver.OracleDriver.registerMBeans(OracleDriver.java:301)
> 	at oracle.jdbc.driver.OracleDriver$1.run(OracleDriver.java:213)
> 	at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_23]
> 	at oracle.jdbc.driver.OracleDriver.<clinit>(OracleDriver.java:209)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_23]
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_23]
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_23]
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_23]
> 	at org.jboss.as.connector.deployers.processors.DriverProcessor.deploy(DriverProcessor.java:66)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> 	at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
> 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
> the driver looks registered/enabled, though, this is just an error from the diagnose bean

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira