My Oracle Support Banner

InvocationTargetException When Configure JOLT POOL In Weblogic Version 12.2.1 (Doc ID 2202815.1)

Last updated on FEBRUARY 05, 2018

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Configure JOLT connection pool in Weblogic domain version 12.2.1.

See the following exception in server log:

<Info> <WebLogicServer> <BEA-000256> <Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)>
<Notice> <Stdout> <BEA-000000><java.lang.reflect.InvocationTargetException>

 Some other case NullPointerException:

####<Jan 22, 2018, 3:43:02,879 PM CET> <Error> <HTTP> <hdmmi056> <AdminLmx> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1516632182879> <[severity-value: 8] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101020> <[ServletContext@990746786[app:simpapp module:simpapp.war path:null spec-version:3.1]] Servlet failed with an Exception
java.lang.NullPointerException
at examples.jolt.servlet.simpapp.SimpAppServlet.doPost(SimpAppServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:286)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:350)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:247)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3679)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3649)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)

 

Changes

 Upgrade from WLS 12.1.1 to WLS 12.2.1

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.