ArtifactFactory could not be started exception after upgrading to 6.0.1

Hi, I upgraded my teamcity install from 5.1.3 to 6.0.1 today and everything went smoothly except at the end of the build (which builds successfully) I get this stacktrace http://pastebin.com/S2XdH4GR
I did some googling and found a discussion on this forum about someone having this problem while using an external mvn but we are not doing that.


Here is what the startup of the build looks like
http://pastebin.com/JBJPhzRt

any help would be appreciated.

7 comments
Comment actions Permalink

It appears that the last version of TC didn't have this in the maven opts
-javaagent:/usr/local/teamcity/plugins/mavenPlugin/maven-watcher/maven-watcher-agent.jar

Does anyone know how I can edit the maven_opts to remove that?

0
Comment actions Permalink

Hi Apaar,

Maven Watcher is a component that is started as a java agent and listens for Maven's internal events for reporting tests and build information. A failure in Maven Watcher doesn't affect the build, however no reports will be available.

You can disable watcher by setting system property teamcity.maven.enableWatcher = false for the build configuration.


Are you using the bundled Maven 2.2.1 for your builds?

0
Comment actions Permalink

Thanks Sergey, disabling it worked.

Yes we are using maven 2.2.1, the bundled maven that comes with the build agent. Is there a way to figure out why the maven-watcher plugin is failing? I've verified it exists in the correct path.

0
Comment actions Permalink

Hi, Appar.

I'm sorry for the late response. We had long new year vacations here.

This error looks very strange, currently I'm uncertain of what could be the cause.
Could you please describe your runner settings? A screenshot would be enough. Are you using any special maven plugins in your project?

Try to use another goal with the same project. Also try using the latest Maven instead of the bundled one.
I wonder if the error reappears.

Do you have other maven projects being built by TeamCity? Does this problem exist in their builds too?


Thank you

0
Comment actions Permalink

Fixed. Will be available in 6.0.2 (coming soon)

0
Comment actions Permalink

Oh great! Thanks Sergey, we just ended up disabling the plugin via the property. I'll be looking forward to 6.0.2.

0

Please sign in to leave a comment.