Known Issues for WebLogic

On this page:

Installation Instructions

Check out the step by step guide for help installing Weblogic.

Check the Supported Versions

Check the List Of Supported Application Servers.

Important Configuration Information

Configuring weblogic.xml

If you are seeing the following error -- or other NoSuchMethodErrors -- then this tip is for you!

java.lang.NoSuchMethodError: org.objectweb.asm.ClassVisitor.visit(ILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V

It appears that WLS 9 ships with an incompatible version of org.objectweb.asm.* packages which clash with the ones required by Hibernate. You can fix this by adding to the weblogic.xml deployment descriptor the settings.

<container-descriptor>
  <prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>

Configuring web.xml

In order to run Confluence under Weblogic 9.2, you need to use a 2.4 servlet compatible version of web.xml.

This has been bundled in the main Confluence download as:

confluence/WEB-INF/web.servlet2-4.xml

To enable it, simply remove the default confluence/WEB-INF/web.xml and then rename web.servlet2-4.xml to web.xml. Now restart.

If you do not use the 2.4 servlet compatible version, Confluence will not be able to display its pages in a nice URL format and will render blank instead.

You will also see this error in the log file:

[confluence.util.velocity.VelocityUtils] getRenderedTemplate Error occurred rendering template: /decorators/main.vmd
org.apache.velocity.exception.MethodInvocationException: Invocation of method 'requireResource' in  class $Proxy566 threw exception java.lang.NullPointerException @ /decorators/main.vmd[1,25]
	at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)

Confluence Deployment Context

Due to a bug in WebLogic's implementation of the J2EE ServletRequest, certain deployment paths can lead to failed resource requests. Hence, you should avoid deploying Confluence to any of the following contexts:

/confluence
/resources
/download

See the JIRA issue CONF-13712 for further details.

Exploded War

Confluence must be deployed as an exploded war file to WebLogic. Otherwise you may experience errors as such:

java.lang.IllegalStateException: Spring Application context has not been set
  at bucket.container.SpringContainerContext.getComponent(SpringContainerContext.java:98)

WebLogic Configuration tips

Enabling logging

Confluence sends its log output to standard out, so by default Weblogic does not record it. To redirect Confluence's log output to a file follow these instructions Redirecting System.out and System.err to a File

Disabling JSP reload checks

Performance can be considerably affected by Weblogic's tendency to scan JSPs for changes on every page load.
This can be disabled by setting pageCheckSeconds to -1.

Disabling servlet reload checks

Similar to the JSP reload checks, Weblogic will scan servlets for modifications every second (by default), hurting performance.
This can be prevented by setting the servlet-reload-check-secs element to -1.

Avoiding JSP recompiles on redeploy

If you Weblogic instance is often restarted, performance can be improved by explicitly setting a directory to save compile JSPs to (the workingDir parameter), and setting precompile to 'false'.

Configuring Character Encoding

A user has reported that the following configuration can ensure that Chinese character sets are displayed correctly. To correct this, add the following entry to the weblogic.xml file.

<weblogic-web-app>
            <jsp-descriptor>
              <jsp-param>
                <param-name>encoding</param-name>
                <param-value>UTF-8</param-value>
              </jsp-param>
              <jsp-param>
                <param-name>compilerSupportsEncoding</param-name>
                <param-value>false</param-value>
              </jsp-param>
            </jsp-descriptor>
          </weblogic-web-app>

Most of this page duplicates JIRA documentation - you might also like to read http://www.atlassian.com/software/jira/docs/latest/servers/weblogic.html.

Configuring HTTP BASIC Auth

If you wish to use HTTP BASIC Auth for Confluence (this is currently required for authenticated RSS feeds), you will need to modify your config.xml
for your WebLogic domain as by default WebLogic will direct all BASIC Auth requests to its admin console.

Modify {WEBLOGIC_DOMAIN_LOCATION}\config\config.xml to include

<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

to correct this.

Knowledge Base Articles

Page:

Site Import Fails on Weblogic when Using PostgreSQL

Page tree