Confluence Docs 2.10 : Known Issues for WebLogic
This page last changed on Nov 18, 2008 by pcurren.
WebLogic Configuration tips
Deploying Confluence 2.8 on Weblogic 9.2In order to run Confluence under Weblogic 9.2, you will 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 Deploying Confluence on Weblogic 9.xIf 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 <container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
Confluence Deployment ContextDue to a bug in WebLogic's implementation of the J2EE ServletRequest certain deployment paths can lead to failed resource requests. You must avoid deploying Confluence to any of the following contexts -
See the JIRA issue CONF-13712 for further details. WebLogic 8.1 performance problemsCreating a weblogic.xml file can improve the performance of Confluence within the WebLogic 8.1 series. This is particularly suitable in cases where WebLogic continually seeks to reload files from jars - which can be noticed when profiling Confluence in WebLogic and encountering excessive calls to java.util.zip.ZipFile.getEntry() Find a typical example immediately below with an explanation of terms following: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd"> <weblogic-web-app> <jsp-descriptor> <jsp-param> <param-name>pageCheckSeconds</param-name> <param-value>-1</param-value> </jsp-param> <jsp-param> <param-name>precompile</param-name> <param-value>false</param-value> </jsp-param> <jsp-param> <param-name>workingDir</param-name> <param-value>./jsp_precompile_dir/confluence</param-value> </jsp-param> </jsp-descriptor> <container-descriptor> <servlet-reload-check-secs>-1</servlet-reload-check-secs> </container-descriptor> <context-root>confluence</context-root> </weblogic-web-app> The full weblogic.xml syntax is described in BEA's documentation. Here we describe some important parameters you should consider setting. Disabling JSP reload checksPerformance can be considerably affected by Weblogic's tendency to scan JSPs for changes on every page load. Disabling servlet reload checksSimilar to the JSP reload checks, Weblogic will scan servlets for modifications every second (by default), hurting performance. Avoiding JSP recompiles on redeployIf 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'. Site import fails when using PostgreSQL 8.1/8.2 data sourceDoing a full site import when using a PostgreSQL 8.1 or 8.2 data source configured in WebLogic results in an inconsistent database state which cannot be fixed. The following error is shown, even after restarting WebLogic:
The workaround for this issue is to use Confluence's built-in C3P0 connection pool (configured when setting up Confluence initially, or via confluence.cfg.xml), which does not experience this problem. This issue is being tracked at CONF-13726. Upgrading to PostgreSQL 8.3 may potentially fix the problem (as suggested by this PostgreSQL FAQ entry), but this has not been tested by Atlassian. Character EncodingA JIRA user has reported that the following configuration can ensure that Chinese character sets are displayed correctly - 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> Disabling the OSCache for Confluence 2.xConfluence 2.0 uses oscache 2.1.1, which causes problems when Confluence is deployed in a weblogic container. This problem will show up by the Confluence css file taking a very long time (upwards of 30mins) to load. To fix this, you will need to disable the oscache, by removing the following entry from the WEB-INF/web.xml file. <filter> <filter-name>CacheFilter</filter-name> <filter-class>com.opensymphony.oscache.web.filter.CacheFilter</filter-class> </filter> Custom templates (decorators) do not work on WebLogic 8.1 SP2.If, after creating a custom template, you see no result, check your velocity.log for a statement similar to: 2005-01-06 14:47:57,752 - ResourceManager : unable to find resource '/<space_key>/decorators/main.vmd' in any resource loader. This problem does not occur on WebLogic 8.1 SP3. WebLogic 8.1 Soap issuesAxis 1.2 is known to not work out of the box with WebLogic 8.1. Please refer to the AXIS installation instructions for details. The following excerpt was taken from the AXIS documentation.
WebLogic 8.1 & HTTP CompressionThere may be problems with WebLogic 8.1 and HTTP compression (by default disabled). This issue is being investigated and tracked at CONF-6304 ATT: HSQL or Embedded Database users - Webapp redeployment problemsA customer has reported that it is not possible to redeploy Confluence when it has been set up against a HSQL or embedded database. In general we do not recommend customers use the embedded database on production systems. If you want the ability to redeploy Confluence (particulary if you have other applications deployed in your weblogic server), you must use an external database in order for it to work. Thanks to Eric Black for this tip.
|
![]() |
Document generated by Confluence on Dec 03, 2008 15:05 |