IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Error While adding Database Pool Configuration in MWS

    Posted Thu December 31, 2009 12:54 PM

    I am getting an error while adding a database pool in environments for MWS,

    I am using oracle 10g XE and i supplied url perfectly and username and password also are valid ones to Oracle Database,

    After entering DB pool configuration fields with all appropriate values,

    when I click the " Test " button it is giving error as follows

    Unexpected exception caught: java.sql.SQLException: [wm-cjdbc36-0039][Oracle JDBC Driver][Oracle]Connection refused, (DESCRIPTION=(TMP=)(VSNNUM=169869568)(ERR=12516)(ERROR_STACK=(ERROR=(CODE=12516)(EMFI=4))))

    and the error details as follows

    com.webMethods.portlet.PoolConfiguratorException: Unexpected exception caught: java.sql.SQLException: [wm-cjdbc36-0039][Oracle JDBC Driver][Oracle]Connection refused, (DESCRIPTION=(TMP=)(VSNNUM=169869568)(ERR=12516)(ERROR_STACK=(ERROR=(CODE=12516)(EMFI=4))))
    at com.webMethods.wsclient.poolconfiguratorbean.PoolConfiguratorWSBean.testConnection(PoolConfiguratorWSBean.java:290)
    at com.webMethods.portlet.poolconfig.AddEditViewPage.testConnection(AddEditViewPage.java:270)
    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.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
    at com.webMethods.caf.faces.application.CAFMethodBinding.invoke(CAFMethodBinding.java:67)
    at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
    at javax.faces.component.UICommand.broadcast(UICommand.java:312)
    at com.webMethods.caf.faces.component.ViewRoot.broadcastEvents(ViewRoot.java:202)
    at com.webMethods.caf.faces.component.ViewRoot.processApplication(ViewRoot.java:116)
    at com.webMethods.caf.faces.portlet.PortletLifecycle$InvokeApplicationPhase.execute(PortletLifecycle.java:660)
    at com.webMethods.caf.faces.portlet.PortletLifecycle.phase(PortletLifecycle.java:247)
    at com.webMethods.caf.faces.portlet.PortletLifecycle.execute(PortletLifecycle.java:142)
    at com.webMethods.caf.faces.portlet.FacesPortlet.processAction(FacesPortlet.java:326)
    at com.webMethods.portal.framework.portletcontainer.impl.PortletApplicationHandler.process(PortletApplicationHandler.java:477)
    at com.webMethods.portal.framework.portletcontainer.servlet.PortletServlet.service(PortletServlet.java:58)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
    at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:286)
    at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:171)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.dispatch(PortletContainer.java:218)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.process(PortletContainer.java:129)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.processPortletAction(PortletContainer.java:107)
    at com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:182)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
    at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
    at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
    at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
    at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159)
    at org.mortbay.http.HttpServer.service(HttpServer.java:909)
    at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
    at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
    at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
    at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
    at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

    Even after getting errors, when i proceed to save this configuration , I got message as

    "
    JDBC pool name is limited to alphanumeric characters "

    I don’t understand y MWS is refusing this DB pool configuration?
    :(:(:frowning:

    Any help in this regard is appreciable

    Nag.


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 2.  RE: Error While adding Database Pool Configuration in MWS

    Posted Thu December 31, 2009 01:33 PM
    1. verify the oracle is running or not.
    2. and double check the Url which you supplied in the following format or not in JDBC connection pool in MWS
      SAMPLE FORMAT: jdbc:wm:oracle://:; ServiceName= [;connectOption=value…]

    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 3.  RE: Error While adding Database Pool Configuration in MWS

    Posted Thu December 31, 2009 02:51 PM

    Hello Arul

    I checked, oracle is running, and i gave the url according to SAMPLE FORMAT,

    Still i am getting the error,

    I don’t know y…and what went wrong in this case,

    :confused::confused::confused::confused::confused:

    Nag.


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 4.  RE: Error While adding Database Pool Configuration in MWS

    Posted Sat January 02, 2010 08:31 PM

    Hello Mr. Arul

    I don’t understand y this database pool configuration acting weird. With all same values , when i click " Test " button, it is giving " Test Passed "

    But when I tried to test it again , it is giving me error as follows "

    Unexpected exception caught: java.sql.SQLException: [wm-cjdbc36-0039][Oracle JDBC Driver][Oracle]Connection refused, (DESCRIPTION=(TMP=)(VSNNUM=169869568)(ERR=12516)(ERROR_STACK=(ERROR=(CODE=12516)(EMFI=4))))

    Error Details are:
    "com.webMethods.portlet.PoolConfiguratorException: Unexpected exception caught: java.sql.SQLException: [wm-cjdbc36-0039][Oracle JDBC Driver][Oracle]Connection refused, (DESCRIPTION=(TMP=)(VSNNUM=169869568)(ERR=12516)(ERROR_STACK=(ERROR=(CODE=12516)(EMFI=4))))
    at com.webMethods.wsclient.poolconfiguratorbean.PoolConfiguratorWSBean.testConnection(PoolConfiguratorWSBean.java:290)
    at com.webMethods.portlet.poolconfig.AddEditViewPage.testConnection(AddEditViewPage.java:270)
    at sun.reflect.GeneratedMethodAccessor578.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
    at com.webMethods.caf.faces.application.CAFMethodBinding.invoke(CAFMethodBinding.java:67)
    at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
    at javax.faces.component.UICommand.broadcast(UICommand.java:312)
    at com.webMethods.caf.faces.component.ViewRoot.broadcastEvents(ViewRoot.java:202)
    at com.webMethods.caf.faces.component.ViewRoot.processApplication(ViewRoot.java:116)
    at com.webMethods.caf.faces.portlet.PortletLifecycle$InvokeApplicationPhase.execute(PortletLifecycle.java:660)
    at com.webMethods.caf.faces.portlet.PortletLifecycle.phase(PortletLifecycle.java:247)
    at com.webMethods.caf.faces.portlet.PortletLifecycle.execute(PortletLifecycle.java:142)
    at com.webMethods.caf.faces.portlet.FacesPortlet.processAction(FacesPortlet.java:326)
    at com.webMethods.portal.framework.portletcontainer.impl.PortletApplicationHandler.process(PortletApplicationHandler.java:477)
    at com.webMethods.portal.framework.portletcontainer.servlet.PortletServlet.service(PortletServlet.java:58)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
    at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:286)
    at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:171)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.dispatch(PortletContainer.java:218)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.process(PortletContainer.java:129)
    at com.webMethods.portal.framework.portletcontainer.PortletContainer.processPortletAction(PortletContainer.java:107)
    at com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:182)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
    at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
    at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
    at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
    at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159)
    at org.mortbay.http.HttpServer.service(HttpServer.java:909)
    at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
    at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
    at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
    at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
    at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)"

    After some attempts by hitting " Test " button with all same values and URL , 8 ( I counted them) , Again i got " Test Passed " , but when i try again … Its throwing exception.

    What is wrong with this ? :eek: :eek: :eek: :eek: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :rolleyes: :confused: :confused: :confused: :confused: :confused:

    Have any idea on this behaviour??


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 5.  RE: Error While adding Database Pool Configuration in MWS

    Posted Sat March 06, 2010 07:55 PM

    Hi,

    I am also facing same problem. Did you ever found out what is the reason for it? :confused::confused::confused:


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 6.  RE: Error While adding Database Pool Configuration in MWS

    Posted Tue March 09, 2010 12:46 AM

    Oracle 10g XE needed some tunning, because it comes as default with limited 10 connections.

    Which tunning? can’t remeber now but you needed to modify some internal parameter.


    #MWS-CAF-Task-Engine
    #webMethods
    #webMethods-BPMS