Richfaces error with weblogic 11

Has anyone encountered this error? I'm migrating a legacy application's weblogic 10 to 11G (10.3.5) but I can not resolve this error.
Caused By: java.lang.NoSuchMethodException: org.ajax4jsf.context.AjaxContextImpl.decode()
     at java.lang.Class.getDeclaredMethod(Class.java:1937)
     at weblogic.j2ee.injection.J2eeComponentContributor.getDeclaredMethod(J2eeComponentContributor.java:227)
     at weblogic.j2ee.injection.J2eeComponentContributor.addLifecycleMethods(J2eeComponentContributor.java:147)
     at weblogic.servlet.internal.WebComponentContributor.addLifecycleMethods(WebComponentContributor.java:328)
     at weblogic.j2ee.injection.J2eeComponentContributor.contribute(J2eeComponentContributor.java:57)
     at weblogic.servlet.internal.WebComponentContributor.contribute(WebComponentContributor.java:206)
     at weblogic.servlet.internal.WebComponentContributor.contribute(WebComponentContributor.java:183)
     at com.bea.core.repackaged.springframework.jee.server.Bootstrap.deploy(Bootstrap.java:217)
     at com.bea.core.repackaged.springframework.jee.spi.WLSBootstrap.deploy(WLSBootstrap.java:116)
     at com.bea.core.repackaged.springframework.jee.server.Bootstrap.deploy(Bootstrap.java:174)
     at com.bea.core.repackaged.springframework.jee.server.Bootstrap.deploy(Bootstrap.java:153)
     at com.bea.core.repackaged.springframework.jee.server.Bootstrap.deploy(Bootstrap.java:137)
     at com.bea.core.repackaged.springframework.jee.spi.WebComponentContributorBrokerImpl.initialize(WebComponentContributorBrokerImpl.java:45)
     at weblogic.servlet.internal.WebComponentContributor.initialize(WebComponentContributor.java:98)
     at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1386)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:449)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

this is a known issue.
Fixed in 61 SP3
Kumar
Mike Wiles wrote:
I am getting the following error when I try to run the command:
java weblogic.Admin -url t3://127.0.0.1:7001 -username system -password <system-password>
SERVERLOG
The error is:
Unable to get log file: null
I know the connect string is correct as I am able to shutdown the server using
the same string with SHUTDOWN and I can view the server log via the console just
fine. The log file is also configured and defined via the console as well. Anything
obvious that I am missing?

Similar Messages

  • Hyperion Shared Services Configuration Error with Weblogic 9.2

    Hi All,
    I have been trying to configure Hyperion Shared Services 9.3.1 with Weblogic Ver 9.2
    During configuration of the Database and the Application Server, I select Manual Configuration option on Weblogic 9
    However, it returns a configuration failure everytime of the Database.
    In my case, the DB used is SQL 2005.
    Can someone, please advise me.
    Thanks in advance
    Regards,
    Apo

    Hi Apo,
    Check the configtool.log in the logs/config folder and post the error message that is being returned.
    Thanks
    Nick

  • Stylesheet error with weblogic application server 9.1

    Hi ALL,
    I deployed my application on weblogic AS 9.1.
    i have created my own domain using sun JDK 1.5.
    i am able to log in into my application & able to do all the tasks.
    but when i click on a specific tab weblogic AS 9.1 waits for some time & give this error on its console :-
    <b>ERROR: 'Variable 'can-modify' is multiply defined in the same scope.'
    FATAL ERROR: 'Could not compile stylesheet'</b>
    i am not find any more details in the weblogic server error log.
    the same application works fine with weblogic 8.1 sp4 + jdk 1.4 & tomcat 5.0.27 + jdk 1.5( without any error)
    so i think the problem is not because of jdk, it something to do with weblogic!
    does anybody has info about this.
    it will be great help.
    regards
    Rahul

    I found that error is coming from this line.
    <b><xsl:variable name="can-modify" select="/dashboard/@can-save|/dashboard/@can-saveas" /></b>
    can somebody suggest why this happening, same code works is weblogic 8.1 & give error in 9.1.
    -Rahul

  • Custom Tag Error with Weblogic SP9

              Hi
              I seem to be having a problem with a custom tag that I wrote. When I run the JSP
              on WLS (without a service pack), the generated java code uses the weblogic.utils.StringUtils
              class to interprete jsp expressions that are passed into the custom tag's attribute
              (on the JSP). The method called on this StringUtils class is valueOf(). This method
              in essence makes sure that the result of the expression is not null and then subsequently
              calls a toString() on the value. Note that if the value is null it simply returns
              an empty string.
              The problem is that when we go to service pack 9, this method is not called (StringUtils.valueOf()).
              Now the problem arises if first of all the result of the expression statement
              in the custom tag definintion (on the JSP) is null. Secondly, it will also error
              out when the setter method is called within the custom tag, if the object returned
              from the expression does not match the one that is expected by the tag... in our
              case a String.
              Here's a sample usage of the tag:
              <wescombop:selectTag
              selectName="buildingNumber"
              selectedItem="<%= buildingJB.getBuildingNumber()%>"
              trimSelectedItem="true"
              selectTagDataName="buildingNumberDataAttribute" />
              Note: buildingJB.getBuildingNumber() returns BigDecimal
              Here's a snipett of the line generated java:
              * Without the service pack
              comwestfieldgrp_wescom_bop_view_tag_SelectTag_1.setSelectedItem(weblogic.utils.StringUtils.valueOf(buildingJB.getBuildingNumber()));
              *With Service Pack 9
              comwestfieldgrp_wescom_bop_view_tag_SelectTag_1.setSelectedItem(buildingJB.getBuildingNumber());
              Note: The setSelectedItem() method expects a String object as a parameter, so
              the code with service pack 9 will result in a compilation error, since buildingJB.getBuildingNumber()
              returns a BigDecimal.
              Let me know if you need more explanation.
              Has anyone experience this problem before... Any help would be deeply appreciated.
              Thanks all.
              Niran
              

              Modify the <cewolf:param> tag.
              <cewolf:chart id="confchart" title="Reports" type="bar3d" yaxislabel="Time"> <cewolf:data>
              <cewolf:producer id="report"> <cewolf:param name="type" value="all" > </cewolf:param>
              </cewolf:producer> </cewolf:data> </cewolf:chart>
              "Balakrishnan" <[email protected]> wrote:
              >
              >We are using cewolf charting library in weblogic 7.0. The charting library
              >is implemented
              >as custom jsp tag library module.
              >
              >However, when the use the tag for displaying the chart, weblogic is producing
              >this compiler error.
              >
              >/reports/reportsView.jsp(108): no corresponding open tag for tag extension
              >close:
              >//[ null; Line: 108]
              >
              >Here's the corresponding source of the jsp file:
              >
              > <cewolf:chart id="confchart" title="Reports" type="bar3d" yaxislabel="Time">
              > <cewolf:data>
              > <cewolf:producer id="report">
              > <cewolf:param name="type" value="all" /> (<-- Error occurs
              >here.
              >Line no: 108)
              > </cewolf:producer>
              > </cewolf:data>
              > </cewolf:chart>
              >
              >I've also checked the corresponding tld file and it is in place.
              >
              >The same code without any modifications is working fine in tomcat. Can
              >you please
              >let me know what needs to be corrected to make this work?
              

  • FrontEndHost Error with Weblogic Integration Domain

    We have created a WLI Domain with an Admin server and two managed servers in a cluster. We have deployed lot of applications on this. We had a release of these applications which was workin on Production mode. The release name was R500. After that when we did R600, it did not work on Prodcution but worked on Development mode with the following error.
    java.lang.RuntimeException: frontEndHost is not configured for the cluster and hostname is not set in wlw-config or wlw-runtime-config
            at com.bea.wlw.runtime.core.util.Util.getCallbackHttpUrl(Util.java:845)
            at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.getCallbackURL(ServiceHandleImpl.java:379)
            at com.bea.wlw.runtime.jws.dispatcher.JwsDispClass.<init>(JwsDispClass.java:170)
            at com.bea.wli.bpm.runtime.JpdDispClass.<init>(JpdDispClass.java:41)
            at com.bea.wli.bpm.runtime.JpdDispFile.createPrimaryDispClass(JpdDispFile.java:367)
            at com.bea.wlw.runtime.core.dispatcher.DispFile.<init>(DispFile.java:154)
            at com.bea.wlw.runtime.jws.dispatcher.JwsDispFile.<init>(JwsDispFile.java:44)
            at com.bea.wli.bpm.runtime.JpdDispFile.<init>(JpdDispFile.java:103)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
            at com.bea.wlw.runtime.core.dispatcher.DispUnit.loadDispFile(DispUnit.java:219)
            at com.bea.wlw.runtime.core.dispatcher.DispUnit.<init>(DispUnit.java:153)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:578)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:967)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:889)
            at com.bea.wli.broker.JWSSubscriber.getDispClass(JWSSubscriber.java:229)
            at com.bea.wli.broker.JWSSubscriber.getRequest(JWSSubscriber.java:188)
            at com.bea.wli.broker.JWSSubscriber.doDispatch(JWSSubscriber.java:356)
            at com.bea.wli.broker.JWSSubscriber.doDispatch(JWSSubscriber.java:346)
            at com.bea.wli.broker.SubscriptionDispatcher.doDispatch(SubscriptionDispatcher.java:87)
            at com.bea.wli.broker.MessageBroker$PrivilegedSubscriptionDispatcher.run(MessageBroker.java:167)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at com.bea.wli.security.authentication.AuthenticationService.runAs(AuthenticationService.java:109)
            at com.bea.wli.broker.MsgBrokerSecurityHelper.doDispatch(MsgBrokerSecurityHelper.java:232)
            at com.bea.wli.broker.MessageBroker$PrivilegedSubscriptionDispatcher.doDispatch(MessageBroker.java:153)
            at com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:966)
            at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.java:334)
            at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:466)
            at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
            at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)After this when we did R700 release, both the managed servers are continuously failing and the above error has been logged very frequently on both managed1 and managed 2 logs.
    Can anyone help me resolve this error or anyone who has faced this problem earlier, please reply.
    As per this error, we do not have wlw-runtime-config.xml file anywhere so we are unable to determine whether the problem is with host name of the proxy server in wlw-runtime-config.xml file.
    Brijesh Shah

    Your server is started in RUNNING mode :
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[8
    ]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[9
    ]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp,
    http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[3
    ]" is now listening on fe80:0:0:0:0:5efe:a22:516c:7001 for protocols iiop, t3, l
    dap, snmp, http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <WebLogicServer> <BEA-000331> <Started We
    bLogic Admin Server "AdminServer" for domain "base_domain" running in Developmen
    t Mode>
    <Dec 27, 2012 3:21:11 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to RUNNING>
    <Dec 27, 2012 3:21:11 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
    rted in RUNNING mode>
    Why are you saying that you are unable to start it? Make sure you are hitting http://<IP>:7001/console to view the Admin console.

  • OpenCMIS 0.6 and 0.8 error with Weblogic 12c

    When try to access OpenCMIS repository in webservices mode, got the following error :
    INFO: Connecting to CMIS using webservices, impersonating admin, URL http://host:port/alfresco/cmis
    Oct 18, 2012 12:43:27 PM jsp_servlet._lal._content.__browsecmis getBinding
    INFO: Binding: org.apache.chemistry.opencmis.client.bindings.impl.CmisBindingImpl@1d3a3bc
    javax.xml.bind.JAXBException:
    Descriptor Exceptions:
    +Exception [EclipseLink-110] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DescriptorException+
    +Exception Description: Descriptor is missing for class [org.apache.chemistry.opencmis.commons.impl.jaxb.EnumIncludeRelationships].+
    +Mapping: org.eclipse.persistence.oxm.mappings.XMLCompositeObjectMapping[includeRelationships]+
    +Descriptor: XMLDescriptor(org.apache.chemistry.opencmis.commons.impl.jaxb.GetDescendants --> [DatabaseTable(getDescendants)])+
    Runtime Exceptions:
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:535)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:476)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:435)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:676)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:634)
    at org.eclipse.persistence.oxm.XMLContext$XMLContextState.<init>(XMLContext.java:830)
    at org.eclipse.persistence.oxm.XMLContext$XMLContextState.<init>(XMLContext.java:770)
    at org.eclipse.persistence.oxm.XMLContext.<init>(XMLContext.java:177)
    at org.eclipse.persistence.jaxb.JAXBContext$TypeMappingInfoInput.createContextState(JAXBContext.java:860)
    at org.eclipse.persistence.jaxb.JAXBContext$TypeMappingInfoInput.createContextState(JAXBContext.java:830)
    +... 76 more+
    Added new Eclipselink MOXY and started getting the below error. This error seems to be resulting from module class loader not finding web classloader reference. The class is there in one of the openCMIS jar placed inside web-inf lib.
    Oct 23, 2012 2:26:35 PM jsp_servlet._lal._content.__browsecmis getBinding
    SEVERE: SPI cannot be initialized: null
    org.apache.chemistry.opencmis.commons.exceptions.CmisRuntimeException: SPI cannot be initialized: null
    at org.apache.chemistry.opencmis.client.bindings.impl.CmisBindingsHelper.getSPI(CmisBindingsHelper.java:81)
    at org.apache.chemistry.opencmis.client.bindings.impl.CmisBindingImpl.clearAllCaches(CmisBindingImpl.java:218)
    at org.apache.chemistry.opencmis.client.bindings.impl.CmisBindingImpl.<init>(CmisBindingImpl.java:129)
    at org.apache.chemistry.opencmis.client.bindings.CmisBindingFactory.createCmisWebServicesBinding(CmisBindingFactory.java:174)
    at org.apache.chemistry.opencmis.client.bindings.CmisBindingFactory.createCmisWebServicesBinding(CmisBindingFactory.java:139)
    at jsp_servlet._lal._content.__browsecmis.getBinding(__browsecmis.java:934)
    at jsp_servlet._lal._content.__browsecmis.getBinding(__browsecmis.java:957)
    at jsp_servlet._lal._content.__browsecmis._jspService(__browsecmis.java:1361)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:242)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:216)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:132)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:338)
    at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:453)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:364)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:368)
    at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
    at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:97)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:100)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:78)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:35)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:177)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:79)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
    at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:169)
    at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
    at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3288)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
    at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2163)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2089)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1513)
    at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.apache.chemistry.opencmis.client.bindings.impl.CmisBindingsHelper.getSPI(CmisBindingsHelper.java:77)
    +... 53 more+
    Caused by: java.lang.NoClassDefFoundError: org/apache/chemistry/opencmis/client/bindings/spi/webservices/PortProvider
    at org.apache.chemistry.opencmis.client.bindings.spi.webservices.CmisWebServicesSpi.<init>(CmisWebServicesSpi.java:65)
    +... 58 more+
    Caused by: java.lang.ClassNotFoundException: org.apache.chemistry.opencmis.client.bindings.spi.webservices.PortProvider
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
    ... 59 more
    Any help would be appreciated. I have tried several approaches of class loading like <prefer-web-inf-classes> to true and referred CAT tool to add <prefer-application-packages> and etc. All results in some or other error.
    Edited by: 967806 on Oct 30, 2012 2:20 AM

    I could get rid of above error if I hard code the below line in CmisWebServicesSpi class.
    AbstractPortProvider portProvider = new WebSpherePortProvider();
    However, the next set of error I get is RuntimeException resulting from EclipseLink MOXy.
    javax.xml.bind.JAXBException:
    Descriptor Exceptions:
    Runtime Exceptions:
    - with linked exception:
    [Exception [EclipseLink-0] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.IntegrityException
    Descriptor Exceptions:
    I have upgraded org.eclipse.persistence_2.0.0.0_2-3.jar in modules directory to org.eclipse.persistence_2.5. Then I get class not found error for classes in CMIS jars which are right inside the WEB-INF/lib folder of war.

  • Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

    Hello everybody,
              I get the error given below when calling a JSP in a WebLogic
              application which seems to work fine in all other (non-JSP) parts:
              java.lang.NullPointerException:
                   at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
                   at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
                   at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
                   at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
                   at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
                   at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
                   at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
                   at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              I know that this error has been reported more than once in these
              discussion groups, and all people who solved it say
              - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
              1.2.2
              - that it may also be caused by bad jsp code
              But in my case, it has to be another reason, because
              - I am using jdk 1.2.2
              - the same JSP file is running withour errors on WebLogic 6
              I wonder if it could have something to do with the operating system:
              the parsing error is produced on a Windows version of WL 5.1, while my
              WL 6 which doesn't cause errors is running with Linux.
              Many thanks in advance for any help,
              Eckhard Beisswenger
              

    Once again me!
              After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
              http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
              The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.
              

  • Error while deploying application with WebLogic server

    Hi,
    I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
    "There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
    Plz help me.
    Thx

    I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
    Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
    Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
    Cheers!

  • Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

    Hi Sudhir,
    If you do not know if upgrade or not, have a look here :
    http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
    Note that at the end of June SP3 will be released...
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    >
    Hi Sergi,
    Thanks a lot for the class file, I figured out what the problem was. Actually
    the
    database version I was working with was 8.0.6.0. The Oracle driver doesn't
    work with
    this but the JDriver worked. This is the output of running CheckDriver..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
    Production
    With the Partitioning and Objects options
    PL/SQL Release 8.0.6.0.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.1.0
    Then I tried on using the Oracle Driver on another instance which has the
    version
    8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
    database.
    The output of CheckDriver for this Oracle instance is..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
    Production
    With the Partitioning option
    JServer Release 8.1.7.1.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.0.0
    By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
    I upgrade
    Thanks once again,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir ,
    JDriver works well, you can work with it.
    Just for curiosity, can you run the class I attached using the "exact"classpath
    of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
    is the
    output ?
    On which platform are you running your WLSP2 ?
    Thanks
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    I just checked the things you mentioned. The connection pool starts correctly
    without
    any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
    I do have the JAVA_XA package installed and it has EXECUTE permission
    to
    PUBLIC.
    I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
    and
    it works perfect without any issue. The only consideration is that itis
    a Type 2
    Driver and needs to have the Oracle Client installed. But right now Ido
    have it
    installed on the same machine.
    Do you know any known issues with Weblogic JDriver. Do you think it'sa
    good idea
    to go with it ?
    Thanks,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    does your connection pool start correctly ?
    Check the setup of your Oracle server too:
    1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
    2) package JAVA_XA installed (with grant execute to PUBLIC)
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
    and put
    it in classpath in front of weblogic.jar. I still get the same problem.
    Is there
    another location where we can download the Oracle driver with the bug
    fixed
    Regards, Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    I think you are using Oracle JDBC drivers 8.1.6.
    They have a bug, they do not accept a foreign XID.
    Use 8.1.7 or higher to solve this problem.
    Sergi
    Sudhir Babu <[email protected]> wrote:
    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver.
    These
    are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I amnot
    sure where the problem is as I have configured Connection Pool and
    TXDataSource
    as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured in the transaction branch start() failed on resource 'myXAPool'
    Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

  • Deployment Manager Error with Oracle Weblogic Server 10.3.1

    I have installed Identity Manager 9.1.0.2 (patch upgraded from 9.1.0.1) on OEL 5.3 64bit and Weblogic 10.3.1
    Database:Oracle 11gR2 (remote machine).
    **I am aware that IM 9.1.0.2 is not certified on Weblogic 10.3.1 (it is only certified on 10.3),
    The installation was successful and OIManager is up and running. Able to create Users, Resources etc. as well.
    As part of configuring OIM Connectors tried to Import .xml file using Import option from Deployment Management section as below and the following error was displayed.
    "Either your session timed out or you are trying to access a page without logging in".
    Did all workarounds like enabling java, changing browsers, restarting machine etc as per the below discussion but in vain.
    Deployment Manager Error with Oracle Weblogic Server
    Can any one suggest any workaround or solution for this problem.
    Or atleast can any one confirm there is no Identity manager available on this date which is compatible with 10.3.1? and cannot be continued further.
    Thanks in Advance
    Sudheer
    Edited by: SudheerPrabhala on Oct 20, 2009 1:26 AM

    You are facing this issue because you're using a non certified combination.
    Other folks who tried to use OIM in 10.3.1 ended up in the same problem you're facing.

  • Error in configuring apache plug in with weblogic 8.1.5

    I tried to configure Apache 2.2 plugin with weblogic 8.1 SP 5 in Linux ES 4.0 . I am getting the following error while loading weblogic_module in httpd.conf file in Apache server (restarting apache server after putting entries in httpd.conf).. The error is httpd: Syntax error on line 414 of /usr/local/apache2/conf/httpd.conf: API module structure `weblogic_module' in file /usr/local/apache2/modules/mod_wl_20.so is garbled - perhaps this is not an Apache module DSO?
    Did anyone got this error before?

    The solution is for BEA to provide the plug-in. Probably a few minutes of a work for BEA developer. Weblogic 9.0 has it.
    Edited by muralive at 09/17/2007 10:08 PM

  • Deployment Manager Error with Oracle Weblogic Server

    Hi,
    Every time i try to open nexaweb client for Import/Export. I get the following error:-
    "Either your session timed out or you are trying to access a page without logging in." .
    Are there any other permission I'm suppose to grant nexaweb through Welogic admin control?

    I still had no luck with neither
    * Weblogic 10.3 (the import applet doesn't match the authentication in the web application, no matter which JDK 5/6 I set in the browser or if I use IE instead of FireFox)
    * OC4J (downloaded from the oracle.com): the install_server.sh script complains about the server not being running (while I can shutdown it by RMI console with no problem using the same username/password/RMI port).
    Instead I tried JBoss 4.2.3 (downloaded from jboss.com) and unzipped it:install_server.sh works without problem just saying
    You must copy the .xldatabasekey file from the \xellerate\config\ directory of the original installation to the \xellerate\config\ directory of the current installation.
    +.xldatabasekeyThe Oracle Identity Manager installation log file is located at /opt/oracle/app/middleware/oim/xellerate/logs.+
    Which is due to the fact that i previously configured weblogic: so I copied it from my OIM Weblogic installation:
    cp ./oim.weblogic/xellerate/config/.xldatabasekey oim/xellerate/config/
    Run the OIM-ized JBoss instance and, voila'!, the import applet now perfectly recognizes my logged in user and I can now proceed with my real work ... just thinking that I lost 4 days around configuring the OIM server with Weblogic ...

  • Pre_compiling jsp's with weblogic.jspc error

    Hi all,
    Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
    The jsp's do compile under OC4J's jsp compiler.
    Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
    I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
    This is on Windows XP SP4 box.
    So far I've tried:
    adding the -classpath option
    adding the -d option to specify a directory
    adding the -backwardcompatible option
    adding the -librarydir option
    here's my command line format:
    java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
    -backwardcompatible -d WEB-INF addNote.jsp
    heres a sample of output:
    jspc failed with errors :weblogic.servlet.jp.CompilationException:
    addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
    <template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
    addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
    <html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
    I couldn't add the jsp snippets becuase this input form is complaining about the tags.
    Any help would be greatly appreciated.

    Hi all,
    Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
    The jsp's do compile under OC4J's jsp compiler.
    Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
    I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
    This is on Windows XP SP4 box.
    So far I've tried:
    adding the -classpath option
    adding the -d option to specify a directory
    adding the -backwardcompatible option
    adding the -librarydir option
    here's my command line format:
    java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
    -backwardcompatible -d WEB-INF addNote.jsp
    heres a sample of output:
    jspc failed with errors :weblogic.servlet.jp.CompilationException:
    addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
    <template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
    addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
    <html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
    I couldn't add the jsp snippets becuase this input form is complaining about the tags.
    Any help would be greatly appreciated.

  • Error invoking WebService in Eclipse with WebLogic 12c plugin

    I am using Eclipse Indigo with WebLogic 12c plugin to create a standalone WebService Client which invokes a simple WebService. The WebService is protected by Security Policies Wssp1.2-2007-Wss1.0-X509-Basic256.xml and Wssp1.2-SignBody.xml.
    I get the following exception when I run the standalone client:
    h2. Exception in thread "main" java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider could not be instantiated: java.lang.ExceptionInInitializerError
    The same program works fine using JDeveloper 11g but not in Eclipse Indigo or in Juno. Has anyone faced this issue?
    Thanks,
    Madhav

    The stand-alone client JAR file does not, however, support invoking Web services that use the following advanced features:
    Web services reliable SOAP messaging
    Message-level security (WS-Security)
    http://docs.oracle.com/cd/E14571_01/web.1111/e13760/client.htm#i229632
    Can you try running by adding weblogic.jar. but if you run the client inside the wls Server it should work.
    Regards,
    Sunil P

  • Integration of ALBPM 5.7 with WebLogic 9.2 ::: Error

    Hi All,
    We are trying to configure ALBPM5.7 Enterprise Edition(with Weblogic) and WebLogic 9.2 Server. We have followed one particular document which states the use of Oracle as a Server.i.e ALBPM_5-7_WebLogic_9-2_Installation.pdf
    But we are using MS-SQL Server. We are also using Merlia.jar as a JDBC Driver.
    Now the issue is, we reach @ the end of the document by installing the jar file named "fuegoj2ee-lib-all.jar" through WebConsole. But we are getting stuck while installing the EAR file through Webconsole. Actually this file is neccessary to start the ALBPM 5.7 Engine to run.
    We get "Direcory Service could not be reached" on DOMAIN console.
    We are need and seeking a solution for the same.
    Thanks
    Shail

    Hi.
    We have tested the configuration of the engine. Its says "Directory Service has been found". So there is no issue of the directory service being null as such.
    This is the domain log ------->
    weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Too many connections :3
         at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:241)
         at weblogic.jdbc.jts.Driver.newConnection(Driver.java:918)
         at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:340)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:181)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:82)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:59)
         at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:129)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:280)
         at fuego.connector.JDBCHelper.getConnection(JDBCHelper.java:43)
         at fuego.directory.provider.jdbc.j2ee.RemoteJDBCConnectionProvider.getEntry(RemoteJDBCConnectionProvider.java:60)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:552)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:120)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:163)
         at fuego.directory.provider.Factory.startSession(Factory.java:488)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:167)
         at fuego.directory.Directory.startSession(Directory.java:674)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:335)
         at fuego.ejbengine.Engine.start(Engine.java:120)
         at fuego.ejbengine.servlet.SchedulerServlet.init(SchedulerServlet.java:107)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:278)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1715)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1692)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1612)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    We have large of active connections available on the MS SQL Server.
    Awaiting Reply.
    Thanks
    Shail.

Maybe you are looking for