You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/05/04 18:45:16 UTC
[jira] Created: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
TranQL Connector doesn't check Driver Class during deployment
-------------------------------------------------------------
Key: GERONIMO-1986
URL: http://issues.apache.org/jira/browse/GERONIMO-1986
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: deployment, connector
Versions: 1.1
Reporter: Aaron Mulder
Fix For: 1.2
If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Vamsavardhana Reddy closed GERONIMO-1986.
-----------------------------------------
Resolution: Fixed
Thanks Krishnakumar for providing the patch.
Fixed in rev 472993 (branches\1.1) and rev 472998 (trunk).
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.1.2, 1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Vamsavardhana Reddy closed GERONIMO-1986.
-----------------------------------------
Resolution: Fixed
Modified the fix to log a warning instead of throwing a deployment exception if class loading fails.
Rev 473023 (branches\1.1) and rev 473032 (trunk).
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.1.2, 1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Aaron Mulder updated GERONIMO-1986:
-----------------------------------
Attachment: db-plan-no-deps.xml
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, connector
> Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.2
> Attachments: db-plan-no-deps.xml
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Donald Woods updated GERONIMO-1986:
-----------------------------------
Fix Version/s: 1.1.2
(was: 1.1.x)
Affects Version/s: 1.1
1.1.2
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Matt Hogstrom
> Fix For: 1.2, 1.1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Vamsavardhana Reddy reassigned GERONIMO-1986:
---------------------------------------------
Assignee: Vamsavardhana Reddy (was: Matt Hogstrom)
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 1.1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Vamsavardhana Reddy reopened GERONIMO-1986:
-------------------------------------------
Comment from David Jencks on rev 472993 and 472998:
You are assuming that any connector that
has a config-property called "Driver" uses that property for a java
class name that is expected to be on the classpath. I can easily
imagine a jdbc wrapper for a specific database that has a "Driver"
config-property to choose between a type 2 and type 4 driver and e.g.
the property is an Integer rather than a class name.
I think we could either
-- emit a warning if the class can't be loaded rather than throwing
an exception
or
-- only do this check if we are loading the tranql generic jdbc
wrapper in some version.
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1, 1.1.1, 1.1.2
> Reporter: Aaron Mulder
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 1.1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Matt Hogstrom updated GERONIMO-1986:
------------------------------------
Affects Version/s: 1.1.1
(was: 1.1)
Assignee: Matt Hogstrom
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector, deployment
> Affects Versions: 1.1.1
> Reporter: Aaron Mulder
> Assigned To: Matt Hogstrom
> Fix For: 1.2, 1.1.x
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Donald Woods updated GERONIMO-1986:
-----------------------------------
Patch Info: [Patch Available]
Fix Version/s: 1.1.x
Verified patch can be applied to Geronimo 1.1.1 to file modules\connector-builder\src\java\org\apache\geronimo\connector\deployment\ConnectorModuleBuilder.java
This is a usability improvement which should be considered for 1.1.x.
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, connector
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.2, 1.1.x
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=comments#action_12377848 ]
Aaron Mulder commented on GERONIMO-1986:
----------------------------------------
Here's the stack trace:
ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="console.dbpool/LaptopStorePool/1.0/rar?J2EEApplication=null,JCAConnectionFactory=LaptopStorePool,JCAResource=console.dbpool/LaptopStorePool/1.0/rar,ResourceAdapter=console.dbpool/LaptopStorePool/1.0/rar,ResourceAdapterModule=console.dbpool/LaptopStorePool/1.0/rar,j2eeType=JCAManagedConnectionFactory,name=LaptopStorePool"
Unable to load driver class: org.apache.derby.jdbc.EmbeddedDriver
at org.tranql.connector.jdbc.JDBCDriverMCF.setDriver(JDBCDriverMCF.java:147)
at org.tranql.connector.jdbc.JDBCDriverMCF$$FastClassByCGLIB$$81f38179.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.DynamicGBeanDelegate$Operation.invoke(DynamicGBeanDelegate.java:181)
at org.apache.geronimo.gbean.DynamicGBeanDelegate.setAttribute(DynamicGBeanDelegate.java:134)
at org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper.setAttribute(ManagedConnectionFactoryWrapper.java:244)
at org.apache.geronimo.gbean.runtime.GBeanAttribute$DynamicSetterMethodInvoker.invoke(GBeanAttribute.java:438)
at org.apache.geronimo.gbean.runtime.GBeanAttribute.setValue(GBeanAttribute.java:411)
at org.apache.geronimo.gbean.runtime.GBeanAttribute.inject(GBeanAttribute.java:342)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:960)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:174)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:505)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:486)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:852)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:338)
at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:852)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219)
at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34)
at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99)
at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31)
at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163)
at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86)
at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80)
at $Proxy0.invoke(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:552)
Caused by: java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDriver
at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:249)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at org.tranql.connector.jdbc.JDBCDriverMCF.loadClass(JDBCDriverMCF.java:310)
at org.tranql.connector.jdbc.JDBCDriverMCF.setDriver(JDBCDriverMCF.java:144)
... 74 more
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, connector
> Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.2
> Attachments: db-plan-no-deps.xml
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Krishnakumar B (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Krishnakumar B updated GERONIMO-1986:
-------------------------------------
Attachment: tranql-1986-updated.patch
Check if "Driver" attribute has a value. Not all tranql plans have "Driver" attribute
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, connector
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check
Driver Class during deployment
Posted by "Krishnakumar B (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ]
Krishnakumar B updated GERONIMO-1986:
-------------------------------------
Attachment: tranql-1986.patch
Check in ConnectorModuleBuilder if Driver class id there in ClassLoader ( cl ). If not throw a Deployment Exception. This way the exception can be thrown at deployment and not when GBean starts.
> TranQL Connector doesn't check Driver Class during deployment
> -------------------------------------------------------------
>
> Key: GERONIMO-1986
> URL: http://issues.apache.org/jira/browse/GERONIMO-1986
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, connector
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.2
>
> Attachments: db-plan-no-deps.xml, tranql-1986.patch
>
>
> If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available.
> It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira