[JBoss JIRA] (WFLY-3439) Websockets not working
by Kadhem Kacem (JIRA)
[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ]
Kadhem Kacem commented on WFLY-3439:
------------------------------------
For this issue. In my case, websocket is working fine with glassfish, and not with wildfly 8.0.0/8.1.0/8.2.0. I can connect to websocket but javascript onmessage event is not fired event that the server side is working fine.
> Websockets not working
> ----------------------
>
> Key: WFLY-3439
> URL: https://issues.jboss.org/browse/WFLY-3439
> Project: WildFly
> Issue Type: Bug
> Components: Web Sockets
> Affects Versions: 8.1.0.Final
> Reporter: Veli Cris
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Alpha1
>
>
> Hi,
> I deployed a .war file containing a single endpoint definition (Websocket). I can see following lines in console but nothing happens when trying to open connection from a websocket client. Same .war deployed in WildFly 8.0.0 is working. Please investigate!
> The configuration is standalone.
> [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
> [io.undertow.websockets.jsr] (MSC service thread 1-4) UT026003: Adding annotated server endpoint ...
> [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: ...
> [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "web.war" (runtime-name : "web.war")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
- 1
- 0
[JBoss JIRA] (WFLY-4707) Can't use WildFly 9 CR1 and WildFly Arquillian 1.0.0.CR1 together
by John Ament (JIRA)
John Ament created WFLY-4707:
--------------------------------
Summary: Can't use WildFly 9 CR1 and WildFly Arquillian 1.0.0.CR1 together
Key: WFLY-4707
URL: https://issues.jboss.org/browse/WFLY-4707
Project: WildFly
Issue Type: Bug
Components: Logging
Affects Versions: 9.0.0.CR1
Reporter: John Ament
Assignee: James Perkins
You cannot use WildFly 9 CR1 and the Arquillian adapter v1.0.0.CR1 together. In my configuration, you get the following stack after deploying
{code}
Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V
at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158)
at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:386)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
Note that I'm using JDK 1.8 u45. Switching to 1.0.0.Alpha1 works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
- 1
- 0
[JBoss JIRA] (WFLY-4706) Support for -P multiple times
by John Ament (JIRA)
John Ament created WFLY-4706:
--------------------------------
Summary: Support for -P multiple times
Key: WFLY-4706
URL: https://issues.jboss.org/browse/WFLY-4706
Project: WildFly
Issue Type: Feature Request
Affects Versions: 9.0.0.CR1
Reporter: John Ament
Assignee: Jason Greene
In 8.2.0 and 8.1, we had the ability to invoke (in an arquilian test in my case) the startup with -P multiple times, e.g.
{code}
-P=../standalone/configuration/dev.properties -P=../standalone/configuration/integ.properties -P=../standalone/configuration/custom.properties
{code}
This doesn't seem to work in WF 9 CR1. It seems like only the last option is read.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
- 1
- 0