Quantcast

SQL Server connection with Open ESB

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
I am using below context.xml and have pasted sqljdbc4-2.0.jar into the \OE-Instance\lib\ext\ folder. But I keep getting an error when the server starts. The error message is given below. Please help me with this and let me know what is wrong. I have been able to connect to Oracle Database successfully. From Open ESB application, SQL server is connected as well. But the Open ESB standaalone server is not able to connect.

<dataSource-pool-properties>
        <dbConnector-name>Gradatim_UAT</dbConnector-name>
        <datasource-classname>com.microsoft.sqlserver.jdbc.SQLServerDriver</datasource-

classname>       
        <resource-type>Datasource</resource-type>
        <database-name>Microsoft SQL Server</database-name>       
        <database-vendor>MS</database-vendor>
        <database-version>10.50.1617</database-version>               
        <dbconnector-description>DBConnector for SQL</dbconnector-description>
        <dataSource-properties>
            <property>
                <name>user</name>
                <value>sa</value>
                <description></description>
            </property>
            <property>
                <name>password</name>
                <value>****</value>
                <description></description>
            </property>
            <property>
                <name>serverName</name>
                <value>10.4.1.43</value>
                <description></description>
            </property>
            <property>
                <name>portNumber</name>
                <value>1443</value>
                <description></description>
            </property>
            <property>
                <name>databaseName</name>
                <value>Oct2014</value>
                <description></description>
            </property>
            <property>
                <name>driverType</name>
                <value>javax.sql.DataSource</value>
                <description></description>
            </property>
        </dataSource-properties>
        <pool-properties>
            <property>
                <name>initialSize</name>
                <value>1</value>
                <description></description>
            </property>
            <property>
                <name>maxActive</name>
                <value>50</value>
                <description></description>
            </property>
            <property>
                <name>maxIdle</name>
                <value>2</value>
                <description></description>
            </property>
            <property>
                <name>minIdle</name>
                <value>2</value>
                <description></description>
            </property>
        </pool-properties>
    </dataSource-pool-properties>

ERROR:

INFO: OESE-1502: Trying to create datasource Gradatim_UAT
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property driverType not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property databaseName not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property portNumber not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property serverName not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property password not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
WARNING: OESE-1507: Datasource property user not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 24, 2015 4:59:15 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
INFO: OESE-1506: Datasource properties have been settled for Gradatim_UAT
Jun 24, 2015 4:59:15 PM org.apache.tomcat.jdbc.pool.ConnectionPool init
SEVERE: Unable to create initial connections of pool.
java.sql.SQLException: DataSource is of unknown class:class com.microsoft.sqlserver.jdbc.SQLServerDriver
        at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDataSource(PooledConnection.java:236)
        at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:180)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
        at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.registerMBean(TomcatDataSourcePoolFactory.java:79)
        at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.getDataSource(TomcatDataSourcePoolFactory.java:50)
        at net.openesb.standalone.naming.jndi.InitialContexFactoryImpl.getInitialContext(InitialContexFactoryImpl.java:152)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
        at javax.naming.InitialContext.init(InitialContext.java:242)
        at javax.naming.InitialContext.<init>(InitialContext.java:216)
        at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:61)
        at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:23)
        at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:55)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.Scopes$1$1.get(Scopes.java:65)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
        at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
        at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
        at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
        at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
        at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.Scopes$1$1.get(Scopes.java:65)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
        at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
        at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
        at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:75)
        at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:73)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
        at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:73)
        at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:147)
        at com.google.inject.internal.Initializer.injectAll(Initializer.java:92)
        at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:173)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
        at com.google.inject.Guice.createInjector(Guice.java:95)
        at com.google.inject.Guice.createInjector(Guice.java:72)
        at net.openesb.standalone.inject.ModulesBuilder.createInjector(ModulesBuilder.java:42)
        at net.openesb.standalone.node.internal.InstanceNode.<init>(InstanceNode.java:74)
        at net.openesb.standalone.node.NodeBuilder.build(NodeBuilder.java:24)
        at net.openesb.standalone.startup.Container.<init>(Container.java:21)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at java.lang.Class.newInstance(Class.java:374)
        at net.openesb.standalone.startup.Bootstrap.init(Bootstrap.java:76)
        at net.openesb.standalone.startup.Bootstrap.start(Bootstrap.java:122)
        at net.openesb.standalone.startup.Bootstrap.main(Bootstrap.java:201)

Jun 24, 2015 4:59:16 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory getDataSource
SEVERE: OESE-1503: Unable to create datasource Gradatim_UAT
java.sql.SQLException: DataSource is of unknown class:class com.microsoft.sqlserver.jdbc.SQLServerDriver
        at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDataSource(PooledConnection.java:236)
        at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:180)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
        at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
        at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.registerMBean(TomcatDataSourcePoolFactory.java:79)
        at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.getDataSource(TomcatDataSourcePoolFactory.java:50)
        at net.openesb.standalone.naming.jndi.InitialContexFactoryImpl.getInitialContext(InitialContexFactoryImpl.java:152)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
        at javax.naming.InitialContext.init(InitialContext.java:242)
        at javax.naming.InitialContext.<init>(InitialContext.java:216)
        at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:61)
        at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:23)
        at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:55)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.Scopes$1$1.get(Scopes.java:65)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
        at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
        at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
        at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
        at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
        at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.Scopes$1$1.get(Scopes.java:65)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
        at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
        at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
        at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:75)
        at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:73)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
        at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:73)
        at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:147)
        at com.google.inject.internal.Initializer.injectAll(Initializer.java:92)
        at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:173)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
        at com.google.inject.Guice.createInjector(Guice.java:95)
        at com.google.inject.Guice.createInjector(Guice.java:72)
        at net.openesb.standalone.inject.ModulesBuilder.createInjector(ModulesBuilder.java:42)
        at net.openesb.standalone.node.internal.InstanceNode.<init>(InstanceNode.java:74)
        at net.openesb.standalone.node.NodeBuilder.build(NodeBuilder.java:24)
        at net.openesb.standalone.startup.Container.<init>(Container.java:21)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at java.lang.Class.newInstance(Class.java:374)
        at net.openesb.standalone.startup.Bootstrap.init(Bootstrap.java:76)
        at net.openesb.standalone.startup.Bootstrap.start(Bootstrap.java:122)
        at net.openesb.standalone.startup.Bootstrap.main(Bootstrap.java:201)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

David BRASSELY
Administrator
This post has NOT been accepted by the mailing list yet.
Hello Mitrabhanu,

Please have a try to define datasource URL as below:

<dataSource-properties>
    <property>
                                <name>dataSourceURL</name><value>jdbc:sqlserver://10.4.1.43:1443;databaseName= Oct2014;user=sa;password=*******</value>
                                <description></description>
                        </property>
                </dataSource-properties>

Please let us know.

Regards,
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
Hi David,

Thanks for replying. I tried the approach you suggested, but I am still getting the below error.
Looking forward to some suggestion on this.

WARNING: OESE-1507: Datasource property dataSourceURL not found for datasource Gradatim_UAT (in com.microsoft.sqlserver.jdbc.SQLServerDriver)
Jun 26, 2015 2:34:35 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory createNativeDataSource
INFO: OESE-1506: Datasource properties have been settled for Gradatim_UAT
Jun 26, 2015 2:34:35 PM org.apache.tomcat.jdbc.pool.ConnectionPool init
SEVERE: Unable to create initial connections of pool.
java.sql.SQLException: DataSource is of unknown class:class com.microsoft.sqlserver.jdbc.SQLServerDriver
at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDataSource(PooledConnection.java:236)
at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:180)
at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.registerMBean(TomcatDataSourcePoolFactory.java:79)
at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.getDataSource(TomcatDataSourcePoolFactory.java:50)
at net.openesb.standalone.naming.jndi.InitialContexFactoryImpl.getInitialContext(InitialContexFactoryImpl.java:152)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:61)
at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:23)
at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:55)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:75)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:73)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:73)
at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:147)
at com.google.inject.internal.Initializer.injectAll(Initializer.java:92)
at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:173)
at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
at com.google.inject.Guice.createInjector(Guice.java:95)
at com.google.inject.Guice.createInjector(Guice.java:72)
at net.openesb.standalone.inject.ModulesBuilder.createInjector(ModulesBuilder.java:42)
at net.openesb.standalone.node.internal.InstanceNode.<init>(InstanceNode.java:74)
at net.openesb.standalone.node.NodeBuilder.build(NodeBuilder.java:24)
at net.openesb.standalone.startup.Container.<init>(Container.java:21)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at net.openesb.standalone.startup.Bootstrap.init(Bootstrap.java:76)
at net.openesb.standalone.startup.Bootstrap.start(Bootstrap.java:122)
at net.openesb.standalone.startup.Bootstrap.main(Bootstrap.java:201)

Jun 26, 2015 2:34:35 PM net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory getDataSource
SEVERE: OESE-1503: Unable to create datasource Gradatim_UAT
java.sql.SQLException: DataSource is of unknown class:class com.microsoft.sqlserver.jdbc.SQLServerDriver
at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDataSource(PooledConnection.java:236)
at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:180)
at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.registerMBean(TomcatDataSourcePoolFactory.java:79)
at net.openesb.standalone.naming.jndi.ds.tomcat.TomcatDataSourcePoolFactory.getDataSource(TomcatDataSourcePoolFactory.java:50)
at net.openesb.standalone.naming.jndi.InitialContexFactoryImpl.getInitialContext(InitialContexFactoryImpl.java:152)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:61)
at net.openesb.standalone.naming.ContextProvider.get(ContextProvider.java:23)
at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:55)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:75)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:73)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:73)
at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:147)
at com.google.inject.internal.Initializer.injectAll(Initializer.java:92)
at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:173)
at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
at com.google.inject.Guice.createInjector(Guice.java:95)
at com.google.inject.Guice.createInjector(Guice.java:72)
at net.openesb.standalone.inject.ModulesBuilder.createInjector(ModulesBuilder.java:42)
at net.openesb.standalone.node.internal.InstanceNode.<init>(InstanceNode.java:74)
at net.openesb.standalone.node.NodeBuilder.build(NodeBuilder.java:24)
at net.openesb.standalone.startup.Container.<init>(Container.java:21)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at net.openesb.standalone.startup.Bootstrap.init(Bootstrap.java:76)
at net.openesb.standalone.startup.Bootstrap.start(Bootstrap.java:122)
at net.openesb.standalone.startup.Bootstrap.main(Bootstrap.java:201)


On Thu, Jun 25, 2015 at 8:30 PM, David BRASSELY [via OpenESB Community Forum] <[hidden email]> wrote:
Hello Mitrabhanu,

Please have a try to define datasource URL as below:

<dataSource-properties>
    <property>
                                <name>dataSourceURL</name><value>jdbc:sqlserver://10.4.1.43:1443;databaseName= Oct2014;user=sa;password=*******</value>
                                <description></description>
                        </property>
                </dataSource-properties>

Please let us know.

Regards,


If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581008.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

Paul Perez
Administrator
Mitrabhanu

Did you add MSSQL JDBC Driver in lib/ext ?

Copy it and restart your OE instance

regards

Paul
www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.

Hi Paul,

Yes I have added it to both lib and lib/ext folders same as Oracle jdbc driver. Either the version is incorrect or I have done some other mistake. Can you guide me to the correct driver to be downloaded?

On Jun 26, 2015 6:59 PM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Mitrabhanu

Did you add MSSQL JDBC Driver in lib/ext ?

Copy it and restart your OE instance

regards

Paul
www.pymma.com The best services on OpenESB



If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581010.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
In reply to this post by Paul Perez
Dear Paul,

Please help me with this.

Regards,

Mitrabhanu Panda

On Fri, Jun 26, 2015 at 11:30 PM, mitrabhanu panda <[hidden email]> wrote:

Hi Paul,

Yes I have added it to both lib and lib/ext folders same as Oracle jdbc driver. Either the version is incorrect or I have done some other mistake. Can you guide me to the correct driver to be downloaded?

On Jun 26, 2015 6:59 PM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Mitrabhanu

Did you add MSSQL JDBC Driver in lib/ext ?

Copy it and restart your OE instance

regards

Paul
www.pymma.com The best services on OpenESB



If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581010.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

Paul Perez
Administrator
Hi
One comment first.
We recently made tests with MS SQLondon and we successed. Except bad configuration somewhere you must success in your connection.  

Questions:
Did you use the configuration proposed by David.  

When your instance start up have you some error message about context.XML?

Could you provide me with more detail on your project. Some projects could receive additional support. If you match criteria.  
Please contact me on paul(dot)perez(at)pymma(dot)com
Let me know
Regards
Paul

www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

Ivan0328
This post has NOT been accepted by the mailing list yet.
In reply to this post by mitrabhanu
hi,

Were you able  find the solution to this problem?

Thank you.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

David BRASSELY
Administrator
This post has NOT been accepted by the mailing list yet.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
Hi,

Actually No, even after trying several permutations and combinations. I shifted to Mulesoft and it seems to be working better for me now.

Regards,

Mitrabhanu Panda

On Tue, Jul 28, 2015 at 12:32 PM, David BRASSELY [via OpenESB Community Forum] <[hidden email]> wrote:
Hi Ivan,

Please have a look to this post :
http://openesb-community-forum.794670.n2.nabble.com/OpenESB-Standalone-Edition-MS-SQL-Connection-td7581031.html

Regards,


If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581035.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

David BRASSELY
Administrator
This post has NOT been accepted by the mailing list yet.
Hi Mitrabhanu,

It's just because you did not set the correct classname for datasource, it must be :
<datasource-classname>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-classname>

Regards,
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
Thankyou David,

I will try this and get back.

Regards,

Mitrabhanu Panda

On Tue, Jul 28, 2015 at 2:44 PM, David BRASSELY [via OpenESB Community Forum] <[hidden email]> wrote:
Hi Mitrabhanu,

It's just because you did not set the correct classname for datasource, it must be :
<datasource-classname>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-classname>

Regards,


If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581037.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
In reply to this post by David BRASSELY
Yes, it worked. Thanks a lot!!

On Tue, Jul 28, 2015 at 2:58 PM, mitrabhanu panda <[hidden email]> wrote:
Thankyou David,

I will try this and get back.

Regards,

Mitrabhanu Panda

On Tue, Jul 28, 2015 at 2:44 PM, David BRASSELY [via OpenESB Community Forum] <[hidden email]> wrote:
Hi Mitrabhanu,

It's just because you did not set the correct classname for datasource, it must be :
<datasource-classname>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-classname>

Regards,


If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581037.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

Paul Perez
Administrator
In reply to this post by mitrabhanu
Dear mitrabhanu

Please feel free to shift to MuleSoft if your main requirement is to access to MS SQL and not having a real service oriented integration tool.
Visibly you failed where many  of OE users success with the same documentation and forum.  
So you act such as a spoiled child who challenges his parents when you write I shifted to MuleSoft please do not an give us your feedback.
 
Please note that the community is here to help OE users and we are very happy to do it but not solve personal issues and bug. Many companies proposes support and consulting for these problemes
Again we are very happy to help you on OpenESB but not in that way
Good luck in your project and sorry for this naughty answer.

King regard

Paul
www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL Server connection with Open ESB

mitrabhanu
This post has NOT been accepted by the mailing list yet.
Hi Paul,

Sorry to have kindled the wrong kind of emotions in you. The purpose was not to hurt your feelings, but to inform you that I couldn't on my own solve the issue and hence had to try out alternatives. The answer from David today did solve the issue and I have restarted on Open ESB. :)

But a genuine feedback is that the documentation available on the internet on Open ESB is not as good as on Mulesoft, including questions and solutions on StackOverflow.

Regards,

Mitrabhanu Panda

On Tue, Jul 28, 2015 at 4:31 PM, Paul Perez [via OpenESB Community Forum] <[hidden email]> wrote:
Dear mitrabhanu

Please feel free to shift to MuleSoft if your main requirement is to access to MS SQL and not having a real service oriented integration tool.
Visibly you failed where many  of OE users success with the same documentation and forum.  
So you act such as a spoiled child who challenges his parents when you write I shifted to MuleSoft please do not an give us your feedback.
 
Please note that the community is here to help OE users and we are very happy to do it but not solve personal issues and bug. Many companies proposes support and consulting for these problemes
Again we are very happy to help you on OpenESB but not in that way
Good luck in your project and sorry for this naughty answer.

King regard

Paul
www.pymma.com The best services on OpenESB



If you reply to this email, your message will be added to the discussion below:
http://openesb-community-forum.794670.n2.nabble.com/SQL-Server-connection-with-Open-ESB-tp7581007p7581040.html
To unsubscribe from SQL Server connection with Open ESB, click here.
NAML

Loading...