AnsweredAssumed Answered

Activiti REST - Not working in Oracle  12.1.2.0.0

Question asked by prakashm88 on Jan 26, 2016
Latest reply on Jan 26, 2016 by prakashm88
We are trying to deploy Activiti-REST in Oracle 12.1.2.0.0, and as insisted it supports Servlet 3.0.

After completion of the application deployment, when trying to acesss the REST URL, I am getting the following error.


####<Jan 25, 2016 8:58:19 PM EST> <Info> <Deployer> <salsa> <myserver> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1453773499051> <BEA-149060> <Module activiti-rest.war of application activiti-rest successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server myserver.>
####<Jan 25, 2016 8:58:19 PM EST> <Info> <Deployer> <salsa> <myserver> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1453773499069> <BEA-149074> <Successfully completed deployment task: [Deployer:149026]deploy application activiti-rest on myserver..>
####<Jan 25, 2016 8:58:40 PM EST> <Error> <HTTP> <salsa> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1453773520821> <BEA-101020> <[ServletContext@698589730[app:activiti-rest module:activiti-rest.war path:null spec-version:3.0]] Servlet failed with an Exception
java.lang.IllegalArgumentException: ServletContext must not be null
        at org.springframework.util.Assert.notNull(Assert.java:112)
        at org.springframework.web.context.support.WebApplicationContextUtils.getWebApplicationContext(WebApplicationContextUtils.java:108)
        at org.springframework.web.context.support.WebApplicationContextUtils.getWebApplicationContext(WebApplicationContextUtils.java:98)
        at org.springframework.web.filter.DelegatingFilterProxy.findWebApplicationContext(DelegatingFilterProxy.java:305)
        at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:250)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3367)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3333)
        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:2220)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2146)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2124)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1564)
        at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)


It seems the Weblogic Security handler is failing eventhough the application is deployed successfully, is there a way to resolve the same. Is there a way to disable the secutiry and test the application asa well.

Any help is appreciated, Thanks !.

Outcomes