[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-28210 FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Change By: William Gautier Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier resolved as Fixed I tried a few things, but unfortunately I did not manage to find the cause of this yet. This problem appeared with the internal dependency changes from v1.3.1, so I've decided to revert those changes for now That change had real convenience benefits for future work and I'm not satisfied with having to revert it, but this way the current version is not broken. I will be able to find a way to get the dependency changes back later, especially now that I know that this problem exists and how to test it. The revert is in version 1.3.3. Please update your plugin and this problem should be gone. Jenkins / JENKINS-28210 FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Change By: William Gautier Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Itriedafewthings,butunfortunatelyIdidnotmanagetofindthecauseofthisyet.Thisproblemappearedwiththeinternaldependencychangesfromv1.3.1,soI'vedecidedtorevertthosechangesfornow . ThatchangehadrealconveniencebenefitsforfutureworkandI'mnotsatisfiedwithhavingtorevertit,butthiswaythecurrentversionisnotbroken.Iwillbeabletofindawaytogetthedependencychangesbacklater,especiallynowthatIknowthatthisproblemexistsandhowtotestit.Therevertisinversion1.3.3.Pleaseupdateyourpluginandthisproblemshouldbegone. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier started work on JENKINS-28210 Change By: William Gautier Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Just an update, 3 people have reported this now so I've confirmed it. I haven't been able to reproduce it myself, but somebody gave me access to a Jenkins instance where this problem happens. I'll be taking a look as soon as I have some free cycles. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi,Ihaveexperiencedanalmostidenticalerror.AHelloWorldwebapplicationthathasasingleindex.jsppage.Itdeploysproperlyusingcfpush.ThejobfailsinJenkinsandthisistheconsoleoutput:[JENKINS]Archiving/home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xmltoie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom[JENKINS]Archiving/home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.wartoie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.warchannelstoppedPushingHelloWorldWebapptohttp://api.117.78.6.213.xip.ioAppalreadyexists,resetting.Appdeleted.Creatingnewapp.Pushingappbits.Startingapplication.FATAL:javax.websocket.ContainerProvider:Providerorg.apache.tomcat.websocket.WsContainerProvidernotasubtypejava.util.ServiceConfigurationError:javax.websocket.ContainerProvider:Providerorg.apache.tomcat.websocket.WsContainerProvidernotasubtype atjava.util.ServiceLoader.fail(ServiceLoader.java:239) atjava.util.ServiceLoader.access$300(ServiceLoader.java:185) atjava.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) atjava.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) atjava.util.ServiceLoader$1.next(ServiceLoader.java:480) atjavax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) atorg.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) atorg.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) atorg.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) atorg.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) athudson.model.Run.execute(Run.java:1766) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374)Finished:FAILURETheappiscreatedbutdoesn'tstart.Thisisacompanyinternalcloudfoundryimplementationratherthanthepivotalonebutcfpushandthecfpluginforeclipsecanbothdeploythisprojectwhilethejenkinscfpluginfails.I amusing upgradedto Jenkins1. 613from1. 610 and tonoavail.Andamusing tomcat7.0.47IfIcansupplymoreinfoIwouldbehappytodoso.bestregardsAidan Add Comment
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi, I have experienced an almost identical error. A HelloWorld web application that has a single index.jsp page. It deploys properly using cf push. The job fails in Jenkins and this is the console output: [JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xml to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom [JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.war to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.war channel stopped Pushing HelloWorldWeb app to http://api.117.78.6.213.xip.io App already exists, resetting. App deleted. Creating new app. Pushing app bits. Starting application. FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype java.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) at org.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) at org.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Finished: FAILURE The app is created but doesn't start. This is a company internal cloud foundry implementation rather than the pivotal one but cf push and the cf plugin for eclipse can both deploy this project while the jenkins cf plugin fails. If I can supply more info I would be happy to do so. best regards Aidan
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi,Ihaveexperiencedanalmostidenticalerror.AHelloWorldwebapplicationthathasasingleindex.jsppage.Itdeploysproperlyusingcfpush.ThejobfailsinJenkinsandthisistheconsoleoutput:[JENKINS]Archiving/home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xmltoie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom[JENKINS]Archiving/home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.wartoie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.warchannelstoppedPushingHelloWorldWebapptohttp://api.117.78.6.213.xip.ioAppalreadyexists,resetting.Appdeleted.Creatingnewapp.Pushingappbits.Startingapplication.FATAL:javax.websocket.ContainerProvider:Providerorg.apache.tomcat.websocket.WsContainerProvidernotasubtypejava.util.ServiceConfigurationError:javax.websocket.ContainerProvider:Providerorg.apache.tomcat.websocket.WsContainerProvidernotasubtype atjava.util.ServiceLoader.fail(ServiceLoader.java:239) atjava.util.ServiceLoader.access$300(ServiceLoader.java:185) atjava.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) atjava.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) atjava.util.ServiceLoader$1.next(ServiceLoader.java:480) atjavax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) atorg.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) atorg.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) atorg.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) atorg.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) atcom.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) athudson.model.Run.execute(Run.java:1766) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374)Finished:FAILURETheappiscreatedbutdoesn'tstart.Thisisacompanyinternalcloudfoundryimplementationratherthanthepivotalonebutcfpushandthecfpluginforeclipsecanbothdeploythisprojectwhilethejenkinscfpluginfails. IamusingJenkins1.610andtomcat7.0.47 IfIcansupplymoreinfoIwouldbehappytodoso.bestregardsAidan Add Comment
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title f gun commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype pushing via the command line client works I reproduce the very same error deploying the same app on run.pivotal.io using the plugin (and I can deploy the app via cmd line on run.pivotal.io) checking the Reset app if already exists does not make the difference it fails as well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Lookslikeit'shavingproblemsconnectingtoLoggregator.ButIcan'tseemtoreproduceyourissue.*DoespushingyourapptoyourtargetviatheCloudFoundrycommandlineclientwork?*Haveyoutriedadifferentapplication,oradifferentcloudtarget(suchasafreetrial form from run.pivotal.io)?*DoescheckingResetappifalreadyexistschangeanything? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype ItriedagainbutIcan'treproducethis.Usingyourownapplication,thesameJenkinsversion,andabrandnewrun.pivotal.iotrial,yourapplicationpushesfinewithme. Isit It's possiblethatthiscomesfromyourTomcatinstallation ? . Googlingtheexception,Ifound[thisthread|https://groups.google.com/forum/#!topic/cometd-users/0V5YmtrAHi8]whichcouldindicatetheproblemcomesfromadependencyconflict. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype I tried again but I can't reproduce this. Using your own application, the same Jenkins version, and a brand new run.pivotal.io trial, your application pushes fine with me. Is it possible that this comes from your Tomcat installation? Googling the exception, I found this thread which could indicate the problem comes from a dependency conflict. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title f gun created an issue Jenkins / JENKINS-28210 FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Issue Type: Bug Assignee: William Gautier Components: cloudfoundry-plugin Created: 04/May/15 4:28 PM Environment: Jenkins 1.611 deployed on apache-tomcat-7.0.53 Priority: Critical Reporter: f gun Hi, first time using this plugin. Deploying a very simple https://code.google.com/p/gwt-examples/downloads/detail?name=Calendar.war returns the error below. I have the same result whether I use the manifest file or enter the enter the parameter in Enter configuration in Jenkins section. Note the same application gets deployed using the CLI. WARNING: No manifest value for hostname. Using app name: calendar Pushing calendar app to https://api.cf.##.com App already exists, skipping creation. Pushing app bits. Restarting application. FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype java.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:231) at java.util.ServiceLoader.access$300(ServiceLoader.java:181) at
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Looks like it's having problems connecting to Loggregator. But I can't seem to reproduce your issue. Does pushing your app to your target via the Cloud Foundry command line client work? Have you tried a different application, or a different cloud target (such as a free trial form run.pivotal.io)? Does checking Reset app if already exists change anything? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
