Problems with TeamCity 4 and Glassfish 2.1

I'm trying to get TeamCity 4 installed on my development server, which is a zone on a Solaris 10 box. I'm using Java 6 and Glassfish 2.1. After deploying the TeamCity war file into Glassfish, the app refuses to start with errors like:

Failed to read attribute maxActive from MBean com.sun.appserv:type=Manager,path=/teamcity,host=server

javax.management.InstanceNotFoundException: This operation failed, because it could not be handled by this domain.
An example of such an operation is creating application server instances or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found: com.sun.appserv:type=Manager,path=/teamcity,host=server


I have clustering turned on for this domain.

I'm thinking about talking my employer into buying me IDEA 8.1, but I also wanted to try out TeamCity before I suggest they pull the trigger. If you need any more log messages or anything, please let me know and I'll do what I can to provide them.


3 comments
Comment actions Permalink

Hello,

   If there is some problem while starting TeamCity server, please investigate logs.

   TeamCity uses log4J to report own problems, it also prints errors to console (I suppose it is redirected to somewhere by Glassfish).

   In fact, TeamCity is known to work with Glassfish - we've had reports about this.

   Regards,
   KIR

0
Comment actions Permalink

Thanks for the reply, but I already investigated the logs and the error I posted (though it wasn't formatted as code) was cut-and-paste from the glassfish server log. There were a lot more messages (it looks like every property it tried to read from JMX on that bean was inaccessible). I just pasted one of them as an example.

I'm running a copy of TeamCity in Tomcat 6 on that Solaris zone right now and it works fine. The problem is, I'm using Glassfish 2.1 in my production application and I didn't want to have to run an entirely different server just because TeamCity runs "better" under Tomcat, especially when the product is packaged as a WAR file and the documentation basically states you can put it into any application server.

If you've had "reports" of TC 4 working in Glassfish 2.1, I'd love to know specifics. How was it configured that is different than Tomcat? etc...

0
Comment actions Permalink

Hello,

   I don't know details of the Glassfish operation, but I know for sure that TeamCity is not clasterable - you can run only one instance of TeamCity process per database.
   I tested simple default installation of the TeamCity war into Glassfish, simply installed Glassfish from scratch, with default options, and deployed war into the Glassfish.
   By "reports" I mean that some customers mentioned they run TeamCity under Glassfish server.

   The only important thing I have to mention is that TeamCity should be deployed in unpacked state, because it doesn't support running as a packed war file.
  
   In real production environment you should replace default database (HSQLDB) with MySQL, the instructions are available at
   http://www.jetbrains.net/confluence/display/TCD4/Setting+up+an+External+Database

   Hope this helps,
   KIR

0

Please sign in to leave a comment.