I am trying to implement websocket using JBOSS and I understand for enterprise edition websockets are supported from JBOSS EAP 6.3. I am also trying to integrate websockets with spring. I was wondering, does JBOSS EAP 6.3 supports integration of websockets with spring?
I have followed and configured all the steps mentioned at
http://spring.io/guides/gs/messaging-stomp-websocket/
except that, the application is deployed in JBOSS EAP 6.3. When I execute and try to connect, I am hitting with the following error.
GET http://localhost:8080/hello/info 404 (Not Found)
sockjs-0.3.4.min.js:27 u._startsockjs-0.3.4.min.js:27 (anonymous function)
stomp.js:134 Whoops! Lost connection to undefined
the Atmosphere Framework supports JBoss 6.3. Just take a look at this:
https://github.com/Atmosphere/atmosphere/wiki/Installing-JBoss-WebSocket-Support
Just jump on our mailing list for more information.
-- Jeanfrancois
Related
I was trying to deploy a component on JBoss EAP 6.2 serever.My application listens to IBM Websphere MQ 6.I would like to know if MQ 6 is compatible with JBoss 6.2
There aren't any known issues with using IBM MQ 6 with JBoss EAP 6.2. Neither Red Hat nor IBM officially test and support this configuration, however.
i'm tryin to run an app that runs on jboss EAP , on jboss Wildfly , but i'm having problems with the standalone-full.xml because some services like hornetq aren't available on Wildfly
is there a possible way to migrate from eap to wildfly?
any help?
This depends on your app.
Wildfly 10 ships with ActiveMq rather than HornetQ.
If your app uses standard JMS then you can configure the WF10 standalone-full to have the same JMS endpoints as your old deployment. If however your app is using the HornetQ specific client you will have to do some more work. ActiveMQ artemis integrates HornetQ protocols but it probably won't work without some trial and error in the configuration.
I would suggest starting with standalone-full.xml from Wildfly 10 and compare it with your JBoss EAP configuration. There should be an analog for each service you need. Once that is set try running your app and see what happens.
I have been exploring options to provide websocket support on JBoss 6. WebSocket was added in Java EE 7 so JBoss 6 doesn't have native support for it.
I explored other options to get websocket support on JBoss 6. One of the commonly suggested approaches is to use Atmosphere library. But found that Atmosphere on JBoss 6 falls back to long polling (doesn't support websockets). Here is the reference,link. I need websocket support and no alternatives.
My investigation so far suggests that, websockets support requires changes in transport protocol mechanism. So we can't get native support for it on JBoss 6 even by adding external jars/libraries.
Any suggestion/opinion ??
Couldn't find any reference for websocket support on JBoss 6. JBoss supports it from EAP 6.3
So going ahead with HTTP.
Which version of JBoss are you using? 6.2+ works with https://github.com/Atmosphere/atmosphere/wiki/Installing-JBoss-WebSocket-Support
Does anyone know if its possible to re-configure CometD to use the WebSphere Application Server instead of using Jetty? If so, is there much effort involved in porting it over if I've already got CometD running with Jetty?
CometD runs in any Servlet 2.5 or later Servlet Container, see here.
You did not specify the WebSphere version, but I assume it's a recent enough one.
The only CometD feature that will not work in WebSphere is the WebSocket transport, which is Jetty specific due to lack of standard WebSocket API (now filled by JSR 356 and supported soon in CometD 3).
Your CometD application should deploy and run with no changes in WebSphere, unless you tied yourself explicitly to Jetty APIs.
Is it possible to programatically stop an MDB from listening to a queue in Weblogic 8.1?
I know this can be done in JBoss and later versions of Weblogic but I wasn't sure if it's possible in 8.x.
This is possible with Weblogic 9.x and Weblogic 10.x through the MessageDrivenEJBRuntimeMBean that exposes suspend/resume methods (see BEA WebLogic Server 9.0 API Reference or WebLogic Server 10.3 API Reference) as explained in this Thread: Suspending/Pausing a MDB's Consumption Programmatically. AFAIK, this feature has been introduced in version 9.0 and I don't know if it was backported to 8.1 (in a service pack or as a patch). You might want to check this with BEAOracle support.
You can undeploy the application that contains your MDB. You can use WLST to do that.