Setting up connection pool for DB2

"whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driver

Amit wrote:
>
"whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driverHi. If you can successfully use that driver with one of it's simple
JDBC example programs, then show me that example, at least the
part that makes the connection, and I'll show you how to define a pool.
Joe
PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
Send resumes to [email protected]

Similar Messages

  • Setting up connection pool for cloudscape 10 embedded database

    I got problem with setting connection pool via admin console for cloudscape 10 embedded in j2ee 1.4 (Application server 8.1), what im doing is:
    -in resources/jdbc/ConnectionPools i add a new pool
    - datasource classname i set up as: "org.apache.derby.jdbc.EmbeddedXADataSource"
    -resource type: "javax.sql.XADataSource"
    -DatabaseName: "jdbc:derby:D:\\Programowanie\J2EE\domains\domain1\config\notesData"
    -set no password and user, becouse i havet set this in database
    and when i ping to that datebase i got error:"Operation 'pingConnectionPool' failed in 'resources' Config Mbean."
    when i change Datasource Classname to: "org.apache.derby.jdbc.EmbeddedDataSource", this error occur:
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection object cannot be null
    what im doing wrong? i look everywhere and i cant find solution to my problem...hope you can help me.
    Thanks,
    Krystian

    Amit wrote:
    >
    "whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driverHi. If you can successfully use that driver with one of it's simple
    JDBC example programs, then show me that example, at least the
    part that makes the connection, and I'll show you how to define a pool.
    Joe
    PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
    for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
    We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
    Send resumes to [email protected]

  • Connection Pools for DB2 UDB 8.2 on a SUN AS 8.1

    Hi,
    has somebody experience or knows a place where I can get more information in setting up a connection pool to a DB2 UDB 8.2 database from a SUN AS 8.1 server?
    I'm struggling now for some weeks to get this working, but it doesn't work. I've tried the JDBC JAR's delivered with DB2 but get configuration errors. When I use the JDBC JAR's mentioned in the SUN AS documentation, it seems that the SUN AS 8.1 opens a connection, which is refused on the DB2 side.
    The setup of a connection pool to a Postgres DB worked directly. The connection pool is correctly setup in the SUN AS but the ping doesn't work.
    Hope somebody can help.
    Regards

    Hi Jagadish,
    added the finest to connector and resource-adapter. Here is the output:
    [#|2006-01-16T09:03:14.540+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ConnectorServiceImpl :: checkAndLoadResource resolved to load Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.587+0100|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|RAR6017 : Failed to get connection pool object via JNDI lookup : Db2Pool|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|
    com.sun.enterprise.connectors.ConnectorRuntimeException: This pool is not bound in JNDI :
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:949)
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1089)
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.testConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:507)
         at com.sun.enterprise.connectors.ConnectorRuntime.testConnectionPool(ConnectorRuntime.java:504)
         at com.sun.enterprise.admin.mbeans.ResourcesMBean.pingConnectionPool(ResourcesMBean.java:1908)
         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:585)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:302)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
         at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:272)
         at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:148)
         at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:46)
         at com.sun.enterprise.tools.admingui.handlers.CommonHandlers.invokeMBean(CommonHandlers.java:123)
         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:585)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandler(DescriptorViewHelper.java:863)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandlers(DescriptorViewHelper.java:800)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.dispatchEvent(DescriptorViewHelper.java:775)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.execute(DescriptorViewHelper.java:291)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.execute(DescriptorViewBeanBase.java:192)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:802)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:740)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:760)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:571)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:957)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:615)
         at com.sun.enterprise.tools.guiframework.view.BaseServlet.processRequest(BaseServlet.java:186)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:185)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
         at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
    Caused by: javax.naming.NameNotFoundException: Db2Pool not found
    |#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection :: obtainManagedConnectionFactory threw exception. SO doing checkAndLoadPoolResource|#]
    [#|2006-01-16T09:05:38.603+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|No classloader available with connector descriptor|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds loader :: null|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds ADDING to registry [email protected]0|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Added the active resource adapter to connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl:: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds env =server ? true|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds publishing descriptor __SYSTEM/descriptors/__ds|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|current RAConfig In Descriptor []|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Found/returing Connector descriptor in connector registry.|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourcesUtil :: isEnabled|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourcesUtil :: isEnabled JdbcConnectionPool is pool/config - enabled :true|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;| JdbcConnectionPoolDeployer - deployResource : JdbcConnectionPool calling actualDeploy|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;| JdbcConnectionPoolDeployer - actualDeployResource : JdbcConnectionPool|#]
    [#|2006-01-16T09:05:38.993+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|parseTransactionSupportString: passed in txSupport =>LocalTransaction|#]
    [#|2006-01-16T09:05:39.009+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setpassword(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , passwd ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdelimiter(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , # ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdriverProperties(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , setdriverType#2##setdeferPrepares#false## ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setvalidationMethod(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , table ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdatabaseName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , dataBaseName ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setvalidationTableName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , TABLE_ADDRESS ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setconnectionValidationRequired(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , false ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setguaranteeIsolationLevel(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , false ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setuser(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , user ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setclassName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , com.ibm.db2.jcc.DB2SimpleDataSource ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Created MCF object : |#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|poolName : Db2Pool : txSupport : 1|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Added MCF to connector registry.|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection:: checkAndLoadPoolResource is true|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection :: Now calling obtainManagedConnectionFactory again|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returning the MCF from connector registry.|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection:: done obtainManagedConnectionFactory again|#]
    [#|2006-01-16T09:05:39.071+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|using subject: Betreff:
         Principal: user
         Private Authentisierung: javax.resource.spi.security.PasswordCredential@26702a03
    |#]
    I think the exception is thrown because the pool was never allocated. So this exception should be okay.
    Then comes a lot of reflection stuff (at least in my opinion) and finally there is a try to open the connection. What I don't understand is why there is
    [#|2006-01-16T09:05:39.071+0100|FINE| ... |[b]using subject: Betreff:
    'Betreff' is normally the start for a german mail???
    But nevertheless I think I will realize your second suggestion and write a java client which opens a datasource. This make take some time (one or two days).
    THX a lot for your help.
    PS: There is some kind of syntax highlighting error within the exception code. So the rest of the text is also bold. Don't know how to reset that, but I hope it is readable.

  • Creating Connection Pool for DB2 V6.1

    Hi,
    I have created the Connection Pool to point to the DB2 database and has successfully
    created the entity bean jar file. However,
    when I encountered the following error:
    The pool TestPool could not be found. Please make sure that it is declared in
    your config.xml file.
    The following in from my config.xml file:
    <JDBCConnectionPool DriverName="COM.ibm.db2.jdbc.app.DB2Driver"
    Name="TestPool"
    Properties="user=mydata;server=examplesServer" URL="jdbc:db2:mydata"/>
    Hope to hear from you soon. Thanks.

    Hi Jimmy,
    You need to assign a target for your connection pool.
    You may do it by going to console, selecting Target
    tab on the pool and chose servers your want to run
    the connection pool. If you use pre-6.1 version of
    weblogic, you will need to reboot the server after you
    assigned targets to it.
    Regards,
    Slava Imeshev
    "Jimmy" <[email protected]> wrote in message
    news:3c04ad6b$[email protected]..
    >
    Hi,
    I have created the Connection Pool to point to the DB2 database and hassuccessfully
    created the entity bean jar file. However,
    when I encountered the following error:
    The pool TestPool could not be found. Please make sure that it is declaredin
    your config.xml file.
    The following in from my config.xml file:
    <JDBCConnectionPool DriverName="COM.ibm.db2.jdbc.app.DB2Driver"
    Name="TestPool"
    Properties="user=mydata;server=examplesServer" URL="jdbc:db2:mydata"/>
    Hope to hear from you soon. Thanks.

  • Help!!!  Connection Pool for DB2 problem !!

    I created a DB2 connection pool in the weblogic.properties, but when
    weblogic server starting, I got the following error message:
    Thursday August 24 14:26:47 CST 2000:<E> <WebLogicServer> Failed to invoke
    startup class
    weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.Jdbc
    Startup
    java.security.AccessControlException: access denied (java.sql.SQLPermission
    setLog)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :272)
    at
    java.security.AccessController.checkPermission(AccessController.java:399)
    at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
    at java.sql.DriverManager.setLogStream(DriverManager.java:397)
    at weblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:187)
    at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
    at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    I don't know how to solve it, and if I use Console to create a Connection
    pool, I can successful create it...........please help me !!! I have checked
    the weblogic.policy file, but I can not find any problem........
    the configuration in the weblogic.properties as below:
    weblogic.jdbc.connectionPool.ForumPool=\
    url=jdbc:db2:forum,\
    driver=COM.ibm.db2.jdbc.app.DB2Driver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=administrator.user,\
    props=user=db2admin;password=db2admin
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.ForumPool=everyone
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.JtsForumDS=ForumPool
    weblogic.jdbc.DataSource.NonJtsForumDS=ForumPool

    You may want to try the JDBC newsgroup.
    Michael Girdley
    BEA Systems Inc
    "DataL" <[email protected]> wrote in message news:[email protected]...
    I created a DB2 connection pool in the weblogic.properties, but when
    weblogic server starting, I got the following error message:
    Thursday August 24 14:26:47 CST 2000:<E> <WebLogicServer> Failed to invoke
    startup class
    weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.Jdbc
    Startup
    java.security.AccessControlException: access denied(java.sql.SQLPermission
    setLog)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :272)
    at
    java.security.AccessController.checkPermission(AccessController.java:399)
    at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
    at java.sql.DriverManager.setLogStream(DriverManager.java:397)
    at weblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:187)
    at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
    at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    I don't know how to solve it, and if I use Console to create a Connection
    pool, I can successful create it...........please help me !!! I havechecked
    the weblogic.policy file, but I can not find any problem........
    the configuration in the weblogic.properties as below:
    weblogic.jdbc.connectionPool.ForumPool=\
    url=jdbc:db2:forum,\
    driver=COM.ibm.db2.jdbc.app.DB2Driver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=administrator.user,\
    props=user=db2admin;password=db2admin
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.ForumPool=everyone
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.JtsForumDS=ForumPool
    weblogic.jdbc.DataSource.NonJtsForumDS=ForumPool

  • Set up DB Connection Pool for Oracle DataBase Using Java App Server8

    Hi,
    In the Admin Console of Java App Server 8, I tried to create a connection pool for the oracle database. I chose Resource Type to be "javax.sql.ConnectionPoolDataSource" and the Vendor is Oracle. So the Data Source Class Name is filled by the system to be "oracle.jdbc.pool.OracleConnectionPoolDataSource". Now, I set up the class path to point to the database driver class "sun.jdbc.odbc.JdbcOdbcDriver" and also the to the Data Source Class Name. Also I set up the JVM options in the console. Restart the server, and then try to ping to the database, but get the error:
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: No suitable driver
    I don't understand what else I should do and why this error is coming?
    Please help me out.
    Thank you
    Regards,
    Sarah

    Hi,
    I've already solve the problem. I did the following:
    set the Url to be: jdbc:oracle:thin:@hostname:port:SID
    set username
    set password
    add oracle.jdbc.drivers.OracleDriver into the JVM options -Djdbc.drivers
    restart the server
    test the connection
    it works :)

  • Has anyone run the connection pooling for mysql & tomcat successfully?

    I'm trying to set up connection pooling. I'm following the how-to page at
    http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
    But when i test the DBTest/test.jsp file, tomcat displays an error =
    could not load jdbc driver class 'null'(msdos)
    i have placed all the required .jar files in the tomcat lib.
    below is the cofiguration i did to the server.xml file
    <!-- Example Server Configuration File -->
    <!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other -->
    <!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances. The Server
    listens for a shutdown command on the indicated port.
    Note: A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <Server port="8005" shutdown="SHUTDOWN" debug="0">
    <!-- Uncomment these entries to enable JMX MBeans support -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
    debug="0"/>
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
    debug="0"/>
    <!-- Global JNDI resources -->
    <GlobalNamingResources>
    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <!-- Editable user database that can also be used by
    UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
    type="org.apache.catalina.UserDatabase"
    description="User database that can be updated and saved">
    </Resource>
    <ResourceParams name="UserDatabase">
    <parameter>
    <name>factory</name>
    <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
    </parameter>
    <parameter>
    <name>pathname</name>
    <value>conf/tomcat-users.xml</value>
    </parameter>
    </ResourceParams>
    </GlobalNamingResources>
    <!-- A "Service" is a collection of one or more "Connectors" that share
    a single "Container" (and therefore the web applications visible
    within that Container). Normally, that Container is an "Engine",
    but this is not required.
    Note: A "Service" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <!-- Define the Tomcat Stand-Alone Service -->
    <Service name="Tomcat-Standalone">
    <!-- A "Connector" represents an endpoint by which requests are received
    and responses are returned. Each Connector passes requests on to the
    associated "Container" (normally an Engine) for processing.
    By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
    You can also enable an SSL HTTP/1.1 Connector on port 8443 by
    following the instructions below and uncommenting the second Connector
    entry. SSL support requires the following steps (see the SSL Config
    HOWTO in the Tomcat 4.0 documentation bundle for more detailed
    instructions):
    * Download and install JSSE 1.0.2 or later, and put the JAR files
    into "$JAVA_HOME/jre/lib/ext".
    * Execute:
    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
    $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
    with a password value of "changeit" for both the certificate and
    the keystore itself.
    By default, DNS lookups are enabled when a web application calls
    request.getRemoteHost(). This can have an adverse impact on
    performance, so you can disable it by setting the
    "enableLookups" attribute to "false". When DNS lookups are disabled,
    request.getRemoteHost() will return the String version of the
    IP address of the remote client.
    -->
    <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8080" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="100" debug="0" connectionTimeout="20000"
    useURIValidationHack="false" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to -1 -->
    <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8443" minProcessors="5" maxProcessors="75"
    enableLookups="true"
         acceptCount="100" debug="0" scheme="https" secure="true"
    useURIValidationHack="false" disableUploadTimeout="true">
    <Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
    clientAuth="false" protocol="TLS" />
    </Connector>
    -->
    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8009" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" connectionTimeout="20000"
    useURIValidationHack="false"
    protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <!--
    <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
    port="8009" minProcessors="5" maxProcessors="75"
    acceptCount="10" debug="0"/>
    -->
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8082" minProcessors="5" maxProcessors="75"
    enableLookups="true" disableUploadTimeout="true"
    acceptCount="100" debug="0" connectionTimeout="20000"
    proxyPort="80" useURIValidationHack="false" />
    -->
    <!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
    port="8083" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" />
    -->
    <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
    <!--
    <Connector className="org.apache.catalina.connector.http10.HttpConnector"
    port="8084" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" />
    -->
    <!-- An Engine represents the entry point (within Catalina) that processes
    every request. The Engine implementation for Tomcat stand alone
    analyzes the HTTP headers included with the request, and passes them
    on to the appropriate Host (virtual host). -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Standalone" defaultHost="localhost" debug="0">
    <!-- The request dumper valve dumps useful debugging information about
    the request headers and cookies that were received, and the response
    headers and cookies that were sent, for all requests received by
    this instance of Tomcat. If you care only about requests to a
    particular virtual host, or a particular application, nest this
    element inside the corresponding <Host> or <Context> entry instead.
    For a similar mechanism that is portable to all Servlet 2.3
    containers, check out the "RequestDumperFilter" Filter in the
    example application (the source for this filter may be found in
    "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
    Request dumping is disabled by default. Uncomment the following
    element to enable it. -->
    <!--
    <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
    -->
    <!-- Global logger unless overridden at lower levels -->
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="catalina_log." suffix=".txt"
    timestamp="true"/>
    <!-- Because this Realm is here, an instance will be shared globally -->
    <!-- This Realm uses the UserDatabase configured in the global JNDI
    resources under the key "UserDatabase". Any edits
    that are performed against this UserDatabase are immediately
    available for use by the Realm. -->
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
    debug="0" resourceName="UserDatabase"/>
    <!-- Comment out the old realm but leave here for now in case we
    need to go back quickly -->
    <!--
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    -->
    <!-- Replace the above Realm with one of the following to get a Realm
    stored in a database and accessed via JDBC -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="org.gjt.mm.mysql.Driver"
    connectionURL="jdbc:mysql://localhost/authority"
    connectionName="test" connectionPassword="test"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="oracle.jdbc.driver.OracleDriver"
    connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
    connectionName="scott" connectionPassword="tiger"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="sun.jdbc.odbc.JdbcOdbcDriver"
    connectionURL="jdbc:odbc:CATALINA"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!-- Define the default virtual host -->
    <Host name="localhost" debug="0" appBase="webapps"
    unpackWARs="true" autoDeploy="true">
    <Context path="/my-jsp" docBase="c:\JSP-Files" debug="0"
    privileged="true" reloadable="true" />
         <Context path="" docBase="c:\Inetpub\wwwroot" debug="0" privileged="true" />
    <Context path="/sharon" docBase="C:\Tomcat 4.1\webapps\sharon" debug="0" privileged="true" />
    <!-- Normally, users must authenticate themselves to each web app
    individually. Uncomment the following entry if you would like
    a user to be authenticated the first time they encounter a
    resource protected by a security constraint, and then have that
    user identity maintained across all web applications contained
    in this virtual host. -->
    <!--
    <Valve className="org.apache.catalina.authenticator.SingleSignOn"
    debug="0"/>
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.AccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <!-- Logger shared by all Contexts related to this virtual host. By
    default (when using FileLogger), log files are created in the "logs"
    directory relative to $CATALINA_HOME. If you wish, you can specify
    a different directory with the "directory" attribute. Specify either a
    relative (to $CATALINA_HOME) or absolute path to the desired
    directory.-->
    <Logger className="org.apache.catalina.logger.FileLogger"
    directory="logs" prefix="localhost_log." suffix=".txt"
         timestamp="true"/>
    <!-- Define properties for each web application. This is only needed
    if you want to set non-default properties, or have web application
    document roots in places other than the virtual host's appBase
    directory. -->
    <!-- Tomcat Root Context -->
    <!--
    <Context path="" docBase="ROOT" debug="0"/>
    -->
    <!-- Tomcat Examples Context -->
    <Context path="/examples" docBase="examples" debug="0"
    reloadable="true" crossContext="true">
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="localhost_DBTest_log." suffix=".txt"
    timestamp="true"/>
    <Ejb name="ejb/EmplRecord" type="Entity"
    home="com.wombat.empl.EmployeeRecordHome"
    remote="com.wombat.empl.EmployeeRecord"/>
    <!-- If you wanted the examples app to be able to edit the
    user database, you would uncomment the following entry.
    Of course, you would want to enable security on the
    application as well, so this is not done by default!
    The database object could be accessed like this:
    Context initCtx = new InitialContext();
    Context envCtx = (Context) initCtx.lookup("java:comp/env");
    UserDatabase database =
    (UserDatabase) envCtx.lookup("userDatabase");
    -->
    <!--
    <ResourceLink name="userDatabase" global="UserDatabase"
    type="org.apache.catalina.UserDatabase"/>
    -->
    <!-- PersistentManager: Uncomment the section below to test Persistent
              Sessions.
    saveOnRestart: If true, all active sessions will be saved
    to the Store when Catalina is shutdown, regardless of
    other settings. All Sessions found in the Store will be
    loaded on startup. Sessions past their expiration are
    ignored in both cases.
    maxActiveSessions: If 0 or greater, having too many active
    sessions will result in some being swapped out. minIdleSwap
    limits this. -1 means unlimited sessions are allowed.
    0 means sessions will almost always be swapped out after
    use - this will be noticeably slow for your users.
    minIdleSwap: Sessions must be idle for at least this long
    (in seconds) before they will be swapped out due to
    maxActiveSessions. This avoids thrashing when the site is
    highly active. -1 or 0 means there is no minimum - sessions
    can be swapped out at any time.
    maxIdleSwap: Sessions will be swapped out if idle for this
    long (in seconds). If minIdleSwap is higher, then it will
    override this. This isn't exact: it is checked periodically.
    -1 means sessions won't be swapped out for this reason,
    although they may be swapped out for maxActiveSessions.
    If set to >= 0, guarantees that all sessions found in the
    Store will be loaded on startup.
    maxIdleBackup: Sessions will be backed up (saved to the Store,
    but left in active memory) if idle for this long (in seconds),
    and all sessions found in the Store will be loaded on startup.
    If set to -1 sessions will not be backed up, 0 means they
    should be backed up shortly after being used.
    To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
    and minIdleBackup all to -1, saveOnRestart to false, then restart
    Catalina.
    -->
              <!--
    <Manager className="org.apache.catalina.session.PersistentManager"
    debug="0"
    saveOnRestart="true"
    maxActiveSessions="-1"
    minIdleSwap="-1"
    maxIdleSwap="-1"
    maxIdleBackup="-1">
    <Store className="org.apache.catalina.session.FileStore"/>
    </Manager>
              -->
    <Environment name="maxExemptions" type="java.lang.Integer"
    value="15"/>
    <Parameter name="context.param.name" value="context.param.value"
    override="false"/>
    <Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
    type="javax.sql.DataSource"/>
    <Resource name="jdbc/TestDB"
         auth="Container"
         type="javax.sql.DataSource"/>
    <ResourceParams name="jdbc/TestDB">
    <parameter>
         <name>factory</name>
         <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
         </parameter>
         <!-- Maximum number of dB connections in pool. Make sure you
         configure your mysqld max_connections large enough to handle
         all of your db connections. Set to 0 for no limit.
         -->
         <parameter>
         <name>maxActive</name>
         <value>100</value>
         </parameter>
         <!-- Maximum number of idle dB connections to retain in pool.
         Set to 0 for no limit.
         -->
         <parameter>
         <name>maxIdle</name>
         <value>30</value>
         </parameter>
         <!-- Maximum time to wait for a dB connection to become available
         in ms, in this example 10 seconds. An Exception is thrown if
         this timeout is exceeded. Set to -1 to wait indefinitely.
         -->
         <parameter>
         <name>maxWait</name>
         <value>10000</value>
         </parameter>
    <!-- MySQL dB username and password for dB connections -->
    <parameter>
    <name>user</name>
    <value>javauser</value>
    </parameter>
    <parameter>
    <name>password</name>
    <value>javadude</value>
    </parameter>
    <!-- Class name for mm.mysql JDBC driver -->
    <parameter>
    <name>driverClassName</name>
    <value>org.gjt.mm.mysql.Driver</value>
    </parameter>
    <!-- The JDBC connection url for connecting to your MySQL dB.
         The autoReconnect=true argument to the url makes sure that the
         mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
         connection. mysqld by default closes idle connections after 8 hours.
         -->
         <parameter>
         <name>url</name>
         <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
    </parameter>
    </ResourceParams>
    <Resource name="mail/Session" auth="Container"
    type="javax.mail.Session"/>
    <ResourceParams name="mail/Session">
    <parameter>
    <name>mail.smtp.host</name>
    <value>localhost</value>
    </parameter>
    </ResourceParams>
    <ResourceLink name="linkToGlobalResource"
    global="simpleValue"
    type="java.lang.Integer"/>
    </Context>
    </Host>
    </Engine>
    </Service>
    <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
    as its servlet container. Please read the README.txt file coming with
    the WebApp Module distribution on how to build it.
    (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
    To configure the Apache side, you must ensure that you have the
    "ServerName" and "Port" directives defined in "httpd.conf". Then,
    lines like these to the bottom of your "httpd.conf" file:
    LoadModule webapp_module libexec/mod_webapp.so
    WebAppConnection warpConnection warp localhost:8008
    WebAppDeploy examples warpConnection /examples/
    The next time you restart Apache (after restarting Tomcat, if needed)
    the connection will be established, and all applications you make
    visible via "WebAppDeploy" directives can be accessed through Apache.
    -->
    <!-- Define an Apache-Connector Service -->
    <!--
    <Service name="Tomcat-Apache">
    <Connector className="org.apache.catalina.connector.warp.WarpConnector"
    port="8008" minProcessors="5" maxProcessors="75"
    enableLookups="true" appBase="webapps"
    acceptCount="10" debug="0"/>
    <Engine className="org.apache.catalina.connector.warp.WarpEngine"
    name="Apache" debug="0">
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="apache_log." suffix=".txt"
    timestamp="true"/>
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    </Engine>
    </Service>
    -->
    </Server>
    Pleas4 help!!!

    you have your driver jar in Tomcat\common\lib?
    if so, check your classpath, it could be that.

  • Setting up connection pool in MSSQL SERVER 2000

    hi,
    i m having too much trouble in setting up connection pool in TOMCAT 5.0.25 for MS SQL SERVER 2000...
    ......so plz guide me how to do that...
    TIA
    bhups

    i m having too much trouble in setting up connection
    pool in TOMCAT 5.0.25 for MS SQL SERVER 2000...Never done it for SQL Server, but setting up a connection pool in tomcat is basically the same no matter what DB you're using:
    http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html
    The two files you're interested in are server.xml and web.xml. You just need to look at the MYSQL and Oracle examples and "tweak" it ...

  • Read data using 2 diff connection pool for same DB folder in physical layer

    Hi All,
    i am using two connection pool which have different dsn connection information (both are directed to different database name or database server)..
    so if i view the data of any table, a prompt will come asking for the connection pool, so how do i automize it....?
    how do i set the different connection pool for different tables?
    please let me know if u need further informtaion to understand my problem..
    thnx...

    thnx Stijn..
    yupe that i know...
    actually i have total of around 300 tables in physical layer (in both the schemas..) , around 12 fact and 100 dimension tables in bmm and same in the presentation layer...
    so i think u can guess how many joins and other stuff, i have made in my bmm layer..
    if now i will start modifying all this it will take lot of time...
    i am just wondering that there is no alternative for this...
    as when i check my data from the physical layer then a prompt ask for the connection pool (i have already made two connection pool..) so there could be some alternative way to automize the default connection pool setting for the tables/schemas folders in case if more than one connection pool exits under the same database in the physical layer...
    isn't it?
    thnx again..

  • Problem creating a connection pool for mssql server

    Hi
    i downloaded the microsoft type 4 driver for JDBC and i have installed it. now i am trying to create a connection pool for MS Sql server but each time i ping i keep getting an error telling me
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket
    please can someone help out on this
    Ifeanyichukwu

    I assume that you installed the driver correctly. You did go into the app sever admin and set the JVM path? You do this by going to Application Server | JVM Settings | Path Settings and putting in an entry for Classpath Prefix.
    If that is done and it's not something basic like your database isn't turned on, then it must be your settings. To to Sun's site and search for dbping. http://developers.sun.com/prodtech/appserver/utilities/dbping/dbping_overview.html
    Deploy this program and run it. It is a very simple tool that lets you test different property settings. Play around with different settings until you get a ping.
    If that doesn't work post your connect pool settings.
    Good luck
    Mike

  • Create a dedicated connection pool for initialization blocks

    Hi,
    I'm using OBIEE11.6, then I set a session initialization block in RPD, and this block is based on connection pool '"My_DB".
    "My_CP"'.
    when Consistency Checking it warning as follow:
    Initialization Block 'Authorization' uses Connection Pool '"My_DB".
    "My_CP"' which is used for report queries. This may impact query performance.
    but there is no table under the connection pool "My_CP",so I don't know why it say it's used for report queries? and how to remove the warning?
    any one know it?
    Thank you!

    Hi Leo,
    Generally, when there is only one connection pool for a database in physical layer, the BI Server understands this to be the only connection pool for queries (I do not think this really checks if there are underlying tables. I think this is because there is a way to add tables to a database by right clicking on connection pool and choosing import metadata.).
    As a good practise, when you have init block pointing to a specific database please make sure that you create another connection pool just for the use by init blocks. This would make sure that the report queries and init blocks do not go on a single pool.
    So, for your case, create a second connection pool and point your init blocks to the second one. Yes, you cannot point to the first one as it is kind of reserved by BI Server for reports. (Unless you change this in the Options menu of .rpd)
    Hope this helps.
    Thank you,
    Dhar

  • Different connection pool for a report

    Hi experts,
    For one my reports using 'CLOBS' like explained (http://oraclebizint.wordpress.com/2007/11/12/oracle-bi-ee-101332-working-with-clob-fields/) I need to disable parallel processing because it's not supported.
    NO_PARALLEL and NO_INDEX_PARALLEL hints at the query level couldn't disable the parallelism.the optimizer still use it.
    I thought about having a new connection pool that contains 'before query' and 'after query' statements that will disable the parallelism.This will take me a lot of time to rebuild the whole Presentation and Business layers to point to a new physical tables.
    Any one has an idea about how I can use another connection pool for a specific report?
    Regards

    I have the problem. My issue is that I need to have a webservice use the 2 database connection pools I have created. Originally the pools were Non-XA. When I change them to XA I cannot get the JMS JDBC Store to work.
    java.lang.Exception: WebLogic Pool Driver doesn't support XA driver, Please change your config to use a Non-XA driver
    However, part of what you wrote below I don't understand. You said you configured a brand new JMS JDBC Store and was able to use an XA Connection Pool? I tried to delete my existing one and create it anew, but was not able to use an XA pool.
    Is there any solution around this? I need to have an XA Pool for a webservice but non-XA for my JMS Store.
    "After much digging I found documentation that you cannot configure an XA JDBC Connection Pool for use with a JMS JDBC Store: http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#1128929
    The only thing is that if I configure a brand new JMS JDBC Store and make it use the XA JDBC Connection Pool (instead of just selecting the new MySQLXAConnPool from the list that includes the non XA pool) it works without an error."

  • Help in creating the connection pool  for Oracle 8i using Jdriver

    Hi
    Iam pretty new to Weblogic and would be greatfull if some one can help me
    out in finding the parameters to be specified in Weblogic console for creating
    a Connection pool for Oracle 8i database running on solaris. I have installed
    necessary client libraries in weblogic machine.
    The details for my database are as follows
    database name : mydb
    database server : 173.24.24.1
    database port : 1521
    username : myuser
    I would appreciate if you can provide me the following details to be entered in
    weblogic console for creating the connection pool
    URL
    DRIVER CLASS NAME
    PROPERTIES
    ACL NAME
    PASSWORD
    Thanks,
    S Hari

    Hari
    Jdbc Connection Pool Configuration
    URL= jdbc:weblogic:oracle
    DRIVER CLASS NAME=weblogic.jdbc.oci.Driver
    PROPERTIES
    user=myuser
    password=<password in mydb>
    server=mydb
    After configuring Connection Pool Select Targets tab. Select Server from Available
    to Chosen.
    Deepak
    Hari wrote:
    Hi
    Iam pretty new to Weblogic and would be greatfull if some one can help me
    out in finding the parameters to be specified in Weblogic console for creating
    a Connection pool for Oracle 8i database running on solaris. I have installed
    necessary client libraries in weblogic machine.
    The details for my database are as follows
    database name : mydb
    database server : 173.24.24.1
    database port : 1521
    username : myuser
    I would appreciate if you can provide me the following details to be entered in
    weblogic console for creating the connection pool
    URL
    DRIVER CLASS NAME
    PROPERTIES
    ACL NAME
    PASSWORD
    Thanks,
    S Hari

  • Unable create Connection pool for Oracle apps Adapter.

    Hi All,
    We are trying to create a connection pool for Oracle Apps adapter in 11G SOA suite.
    However during the process getting the following error:
    An error occurred during activation of changes, please see the log for details.
    A <jndi-name> is specified for the resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is specified in ra.xml
    Can any one help us on this.
    Thanks
    Parker.

    Please refer section "Configuring Connection Information" at below link -
    http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10537/T430238T430340.htm#T464886
    Regards,
    Anuj

  • Steps to create Connection pool for Oracle apps Adapter.

    Hi All,
    Could please tel me the steps to create connection pool for Oracle Apps Adapter.
    Thanks,
    Parker

    Steps are given in section "Configuring Connection Information" in Apps Adapter User guide at below link -
    http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10537/T430238T430340.htm#T464886
    Regards,
    Anuj

Maybe you are looking for

  • SSIS Flat File Source not populating varchar column

    I have SSIS package that imports flat files with column separator | from "Flat File Source" into the database trough "OLE DB Destination". For one of the columns (file contains UIDs in curly brackets) destination column is varchar(250) null-able, whe

  • Key Figure calculation in Abap is not working correctly - Overlooping

    Hi, I wrote a logic to calculate the ratio of key figure but it is not working correctly For example I have a requirement to split 1 Product into Several new Products and also the Net Amount will be splitted to these several new products as well. The

  • Thread issue in jsp.....

    I understand that the j2ee container (tomcat or jrun...) creates ONE instance of the jsp page (i.e. compiled into servlet class) when the jsp page (let's say, myPage.jsp) is accessed the first time. All request for this jsp page will be done through

  • How to assign voided cheque to the new payment document no.

    Hi Experts, A cheque no 11111 was manually assigned to a payment document no. created for a vendor X but physically another cheque no. 22222 was issued to vendor X by  mistake. Later on the user issued the cheque no. 11111 phisycally lying with him t

  • Applescript help - print specific file type

    I keep getting error messages when trying to get this script to print only the PDFs in my Distiller "Out" folder: on adding folder items to this_folder after receiving added_items tell application "Finder" if file type is "PDF" then print end if end