Problem with WeblogicWebSocketHandler

[frezelth]

Hi,

I have a problem using atmosphere (websockets) with Weblogic 12.1.2.
In WeblogicWebSocketHandler line 153 in the configure() method there is a call to the config object.
This config object is null at this moment, giving a NullPointerException:

config = config.getBroadcasterFactory().lookup(ROOT_MASTER).getBroadcasterConfig().getAtmosphereConfig();

Regards,

Thomas

[jfarcand]

Please paste the complete satck trace. Thanks!

[frezelth]

I'm using it through Vaadin and for any reason I don't see the stacktrace, it might be lost somewhere...

But for sure it fails, because the call to the configure() method is done if config == null in the onOpen() method.

And if config is null, the call to config.getBroadcasterFactory().lookup(ROOT_MASTER).getBroadcasterConfig().getAtmosphereConfig(); fails with a NPE.

I saw that in the first version of the class this line was replaced by: config = BroadcasterFactory.getDefault().lookup("/*").getBroadcasterConfig().getAtmosphereConfig();

Thanks!

[jfarcand]

Ok Vaadin uses a fork of Atmosphere and install it differently. @jdahlstrom, can you help with this?

[frezelth]

I already opened a support request to Vaadin for push with weblogic :) But I also investigated myself and thought there was an issue on the atmosphere side with this class.
Thanks

[jfarcand]

@frezelth Have you tested it outside Vaaadin? For me everything works as expected.

[frezelth]

I tried the atmosphere chat sample with a brand new weblogic 12.1.2.1 domain.

I downloaded the sources both versions 2.1.1 and latest version 2.2.2. I made a clean install and in both cases I made the changes you mentioned here:
https://github.com/Atmosphere/atmosphere/wiki/WebLogic-12.1.2-WebSocket-Support

What I found is that it works with version 2.1.1 and it does not work with version 2.2.2.

A printscreen of chrome network monitor gives me this:

In the working version I get this:

No stracktrace available in the console.

Thanks,

Thomas

[jfarcand]

OK thanks. Fixed in 2.3.x and 2.2.3