It's WebLogic Server's ServletContext.getServerInfo() implementation issue.
According to the Java EE's api
http://download.oracle.com/javaee/5/api/javax/servlet/ServletContext.html#getServerInfo()
getServerInfo
String getServerInfo()
Returns the name and version of the servlet container on which the servlet is running.
The form of the returned string is servername/versionnumber. For example, the JavaServer Web Development Kit may return the string JavaServer Web Dev Kit/1.0.
The servlet container may return other optional information after the primary string in parentheses, for example, JavaServer Web Dev Kit/1.0 (JDK 1.1.6; Windows NT 4.0 x86).
Returns:
a String containing at least the servlet container name and version number
Apache Tomcat's getServerInfo() return String is like the following:
Apache Tomcat/7.0.22
However, WebLogic Server's getServerInfo() return String is like the following:
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Feb 3 16:30:47 EST 2011
Since JForum 2.2.0 till JForum 2.3.2 only tested on Apache Tomcat, so you may not deploy JForum on WebLogic Server successfully.
I have committed a fix for this in JForum 2.3.3. So you may wait for the next release or fetch the code from the repository and build it yourself.
To install JForum on WebLogic Server, you have to explode the war file, and copy the JDBC driver file into WebLogic Server's user_projects\domains\base_domain\lib directory, for examples:
C:\Oracle\Middleware\user_projects\domains\base_domain\lib