I configured one database pool with SQL Server. As I am experiencing problems
in deploying a persistence application, I went through the forum questions
on the topic. One possible solution seems to be creating another database
pool for non-jta-data-source. While configuring another database pool that
points to the same SQL Server database, there is one blank textfield "JDBC
Connect URL". I entered NoTxh in this field. When I tested it gave following
the error message:
java.sql.SQLException: Driver com.microsoft.sqlserver.jdbc.SQLServerDriver
does not accept URL NoTxhutue
        at
org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.attemptConnect(DatabasePoolPortlet.java:910)
        at
org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.processAction(DatabasePoolPortlet.java:351)
        at 
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
        at org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
        at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
        at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
        at
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
        at
org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
        at
org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219)
        at
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
        at
org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
        at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
        at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406)
        at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
Any ideas how to overcome this?
-- 
View this message in context: 
http://www.nabble.com/problem-in-non-jta-data-source-creation-tp21845619s134p21845619.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Reply via email to