3.1.1 fails to start in BEA WL 10.3 container - help?

I am trying to run the 3.1.1 war file in a BEA WebLogic "10.3 Tech Preview" container, but it fails with the exception shown below during autodeploy. Can anyone hazard a guess? Some config file I need to set up manually perhaps? Thanks in advance ...

log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader).
log4j:WARN Please initialize the log4j system properly.
TeamCity data path directory: C:/Documents and Settings/jberkowi/.BuildServer
Cannot find C:\Documents and Settings\jberkowi\.BuildServer\config\database.properties.
Use database settings from buildServerSpring.xml
WARN - l.AgentDistributionMonitorImpl -
Unable to fetch local Build Agent distribution Version.
Build Agents won't upgrade: File not found
TeamCity 3.1.1 (build 6828) initialized, OS: Windows XP, JRE: 1.6.0_02-b06
TeamCity is running in professional mode
ERROR - jetbrains.buildServer.SERVER -

at java.io.File.]]>(File.java:222)
at jetbrains.buildServer.web.impl.BuildServerConfigurator.loadConfiguration(BuildServerConfigurator.java:1)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Comment actions Permalink

BEA Weblogic is not in the list of supported by TeamCity servlet containers. I would suggest to install TeamCity in Tomcat (or in Jetty). You can also submit a feature request to our tracker to support BEA Weblogic: http://jetbrains.net/tracker.

Pavel Sher

Comment actions Permalink

Thanks, understand. Will also check with the BEA folks to see if they are interested in the exception.

Comment actions Permalink

Hello Jeff,

That's true that BEA's WebLogic is not supported, but regarding to this particular exception, please ensure that
deployed WAR file was expanded by the container.

TeamCity works only when war file is unpacked upon deployment.

Kind regards,

Comment actions Permalink

Kirill, thanks very much. I tried your suggestion, and it did get past the previous failure. But it failed later with an exception that seems likely to be specific to BEA's server (the "edit lock" is a feature of WLS, I believe). I updated my post in their forum if you're curious: http://forums.bea.com/thread.jspa?threadID=570001074

I'm proceeding with Tomcat. BTW TeamCity is a great looking product - Jeff


Please sign in to leave a comment.