• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Glassfish GrizzlyContainerProvider not a subtype

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi There,

This might be a little vague question so take your precaution .
We have a web project deployed on a local Glassfish with several assets. When it initializes, it also tries to make a connection to a remote host using websockets. The websocket library we are using is Tyrus. It's bundled in one of the *.jar files which we deployed to the Glassfish.
The problem arises at this point and error is 'java.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.glassfish.tyrus.container.grizzly.client.GrizzlyContainerProvider not a subtype' . We tried to update the maven repo, but could not fix the problem.
By the way, Tyrus is made by glassfish, we deploy to the glassfish so might be a collision...

Our gradle dependencies contains the followings :
     org.glassfish.tyrus.bundles:tyrus-standalone-client-jdk:1.12
     org.glassfish.tyrus:tyrus-container-grizzly-client:1.13.1

I would like to hear any opinion or suggestion in this regard.

Thanks
 
Bartender
Posts: 4100
63
Hibernate Fedora Chrome
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you verified you have the correct and proper dependencies required, as I see you would only need a client implementation here?
 
a pazwant
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You are right, it's client implementation. We all verified the correct and proper dependencies but couldn't fix it. As a result we changed our client websocket library.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!