Teamcity 4.5 causing errors on Glassfish

Gday all

I am attempting to run Teamcity 4.5 on Sun Java System Application Server 9.1_02 (build b04-fcs).

Upgrade from 3.1 worked perfectly till I started using the web application then we started getting the following error.

[2009-05-04 16:42:15,342]   WARN -   jetbrains.buildServer.SERVER - java.lang.RuntimeException: java.lang.ClassCastException: java.lang.Thread cannot be cast to com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread
java.lang.RuntimeException: java.lang.ClassCastException: java.lang.Thread cannot be cast to com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread
        at jetbrains.buildServer.web.ResponseFragmentFilter$XmlFragmentResponseWrapper$1.run(ResponseFragmentFilter.java:2)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: java.lang.Thread cannot be cast to com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread
        at com.sun.enterprise.web.connector.grizzly.ssl.SSLOutputWriter.flushChannel(SSLOutputWriter.java:61)
        at com.sun.enterprise.web.connector.grizzly.ssl.SSLOutputBuffer.flushChannel(SSLOutputBuffer.java:69)
        at com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:202)
        at com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flush(SocketChannelOutputBuffer.java:178)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.action(DefaultProcessorTask.java:1041)
        at com.sun.enterprise.web.connector.grizzly.ssl.SSLProcessorTask.action(SSLProcessorTask.java:151)
        at org.apache.coyote.Response.action(Response.java:221)
        at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:364)
        at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:336)
        at org.apache.coyote.tomcat5.CoyoteWriter.flush(CoyoteWriter.java:135)
        at org.cyberneko.html.filters.Writer.printAttributeValue(Writer.java:292)
        at jetbrains.buildServer.web.ResponseFragmentFilter$XmlFragmentResponseWrapper$1$1.printAttributeValue(ResponseFragmentFilter.java)
        at org.cyberneko.html.filters.Writer.printStartElement(Writer.java:372)
        at org.cyberneko.html.filters.Writer.startElement(Writer.java:200)
        at org.cyberneko.html.filters.DefaultFilter.startElement(DefaultFilter.java:179)
        at jetbrains.buildServer.web.ResponseFragmentFilter$FragmentSerializer.startElement(ResponseFragmentFilter.java:21)
        at org.cyberneko.html.filters.DefaultFilter.startElement(DefaultFilter.java:179)
        at org.cyberneko.html.filters.NamespaceBinder.startElement(NamespaceBinder.java:286)
        at org.cyberneko.html.HTMLTagBalancer.callStartElement(HTMLTagBalancer.java:1009)
        at org.cyberneko.html.HTMLTagBalancer.startElement(HTMLTagBalancer.java:639)
        at org.cyberneko.html.HTMLScanner$ContentScanner.scanStartElement(HTMLScanner.java:2407)
        at org.cyberneko.html.HTMLScanner$ContentScanner.scan(HTMLScanner.java:1881)
        at org.cyberneko.html.HTMLScanner.scanDocument(HTMLScanner.java:809)
        at org.cyberneko.html.HTMLConfiguration.parse(HTMLConfiguration.java:478)
        at org.cyberneko.html.HTMLConfiguration.parse(HTMLConfiguration.java:431)
        at jetbrains.buildServer.web.ResponseFragmentFilter$XmlFragmentResponseWrapper$1.run(ResponseFragmentFilter.java:1)
        ... 6 more

And also getting the following error then a similar stack trace.

[2009-05-04 16:49:18,092]  ERROR -   jetbrains.buildServer.SERVER - Exception occured in response fragment filter

Any insight in how to resolve this would be great.

Regards,

Mark Wolfe

2 comments
Comment actions Permalink

Hello Mark,

  It looks like our changes in response filter made it incompatible with Glassfish.
  Could you please file this issue to our tracker at http://jetbrains.net/tracker and post the issue link here?

  Thanks,
  KIR

0
Comment actions Permalink

Issue added and to close the loop here is the link http://jetbrains.net/tracker/issue2/TW-8150

I am happy to test any proposed changes ect. if needed.

Just to clarify my environment is as follows:
- Clean installation of glassfish downloadable from https://glassfish.dev.java.net/downloads/v2ur2-b04.html
- Postgres 8.2 JDBC driver copied to global lib directory in glassfish
- Postgres 8.2 database for backend database
- CIFS for authentication

Thanks for your assistance so far.

Mark Wolfe

0

Please sign in to leave a comment.