• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Websocket works standalone but encoungters error when deployed to weblogic

 
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all.

I have a standalone Java websocket client that connects to a server and processes the messages returned. This is using the Tyrus-standalone-client 1.13.jar. I have 2 test endpoints. One which is a simple connection and another which requires an api key to be added in the before request method when the connection is established. Both these work standalone. When I deploy to Weblogic however, only the simple connect that does not require an api key , works. The other one fails with a deployment exception : "The HTTP request to initiate the the websocket connection failed"

So I know the handshake works for both connections in my standalone class but why would only one of them work in the Weblogic deployment? Has anyone seen this before?

I'm running Weblogic 12.1.3.

The error stack is as follows

 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic