My Oracle Support Banner

"more than 65535 bytes to encode in Utf8 format in the constant pool" When Deploying Application (Doc ID 1543645.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle WebLogic Server - Version 10.3.5 to 12.1.1.0
Information in this document applies to any platform.

Symptoms

On : 10.3.5 version, Web Container

After migration from weblogic 9.2 MP2 to weblogic 11g, when deploying an existing application, error with respect to jsp size is seen. The application was working fine in weblogic 9.2 MP2.

Below is the stack trace. 

^-----

------^
test.jsp:1:1: The type generates a string that requires more than 65535 bytes to encode in Utf8 format in the constant pool
^-----

When using appc to precompile the application, the following exception stack trace is seen: 

weblogic.utils.compiler.ToolFailureException: jspc failed with errors
:weblogic.servlet.jsp.CompilationException: test.jsp:1:1:
The type generates a string that requires more than 65535 bytes to encode in
Utf8 format in the constant pool
<html>
^-----
</html>
------^
test.jsp:1:1: The type generates a string that requires
more than 65535 bytes to encode in Utf8 format in the constant pool
<html>
^-----
</html>
------^
test.jsp:1:1: The type generates a string that requires
more than 65535 bytes to encode in Utf8 format in the constant pool
<html>
^-----
</html>
------^
test.jsp:1:1: The type generates a string that requires
more than 65535 bytes to encode in Utf8 format in the constant pool
<html>
^-----
</html>
------^


    at weblogic.servlet.jsp.jspc20.runBodyInternal(jspc20.java:458)
    at weblogic.servlet.jsp.jspc20.runJspc(jspc20.java:227)
    at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:236)
    at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
    at weblogic.application.compiler.WARModule.compile(WARModule.java:250)
    at
weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:19)
    at
weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
    at
weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
    at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:30)
    at
weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
    at
weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
    at
weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
    at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.Appc.runBody(Appc.java:203)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:116)
    at weblogic.application.compiler.Appc.main(Appc.java:263)
    at weblogic.appc.main(appc.java:15)

 

Changes

Migrated from WLS 9.2 to 11g. 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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