[JBoss JIRA] (WFLY-3439) Websockets not working
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ]
Veli Cris updated WFLY-3439:
----------------------------
Description:
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")
was:
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: ...
> Websockets not working
> ----------------------
>
> Key: WFLY-3439
> URL: https://issues.jboss.org/browse/WFLY-3439
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Sockets
> Affects Versions: 8.1.0.Final
> Reporter: Veli Cris
> Assignee: Stuart Douglas
>
> 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.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3439) Websockets not working
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ]
Veli Cris updated WFLY-3439:
----------------------------
Description:
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: ...
was:
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.
[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: ...
> Websockets not working
> ----------------------
>
> Key: WFLY-3439
> URL: https://issues.jboss.org/browse/WFLY-3439
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Sockets
> Affects Versions: 8.1.0.Final
> Reporter: Veli Cris
> Assignee: Stuart Douglas
>
> 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: ...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3439) Websockets not working
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ]
Veli Cris updated WFLY-3439:
----------------------------
Description:
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.
[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: ....
was:
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.
[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:
> Websockets not working
> ----------------------
>
> Key: WFLY-3439
> URL: https://issues.jboss.org/browse/WFLY-3439
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Sockets
> Affects Versions: 8.1.0.Final
> Reporter: Veli Cris
> Assignee: Stuart Douglas
>
> 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.
> [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: ....
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3439) Websockets not working
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ]
Veli Cris updated WFLY-3439:
----------------------------
Description:
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.
[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: ...
was:
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.
[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: ....
> Websockets not working
> ----------------------
>
> Key: WFLY-3439
> URL: https://issues.jboss.org/browse/WFLY-3439
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Sockets
> Affects Versions: 8.1.0.Final
> Reporter: Veli Cris
> Assignee: Stuart Douglas
>
> 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.
> [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: ...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3439) Websockets not working
by Veli Cris (JIRA)
Veli Cris created WFLY-3439:
-------------------------------
Summary: Websockets not working
Key: WFLY-3439
URL: https://issues.jboss.org/browse/WFLY-3439
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Sockets
Affects Versions: 8.1.0.Final
Reporter: Veli Cris
Assignee: Stuart Douglas
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.
[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:
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3438) Eliminate use of optional dependencies for LocalEJBReceiver
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-3438?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated WFLY-3438:
--------------------------------------
Description:
This issue was initially raised on stackoverflow (see below).
When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
This results in the exception
.java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
The solution described in the forum post works to ensure that the dependencies are established correctly, but we need to factor into this what the spec says about the web profile.
was:
This issue was initially raised on stackoverflow (see below).
When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
This results in the exception
.java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
> Eliminate use of optional dependencies for LocalEJBReceiver
> -----------------------------------------------------------
>
> Key: WFLY-3438
> URL: https://issues.jboss.org/browse/WFLY-3438
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Final, 9.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.CR1
>
>
> This issue was initially raised on stackoverflow (see below).
> When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
> As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
> This results in the exception
> .java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
> The solution described in the forum post works to ensure that the dependencies are established correctly, but we need to factor into this what the spec says about the web profile.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3438) Eliminate use of optional dependencies for LocalEJBReceiver
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-3438?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-3438 at 6/3/14 10:53 AM:
--------------------------------------------------------------------
If the Remoting Endpoint and the EJBRemotingConnectorService are indeed optional, and may be excluded from the server profile, a better way to handle this would be to check the state of the models for the Remoting and EJB subsystems at start up, see if the elements are present, and if they are both present, add them in as REQUIRED dependencies; otherwise leave them out. Also, if one of them is added in via the management interface, set the handler to force a reload so the check at start up may be performed anew.
The use cases where both are left out could correspond to a single node accepting HTTP based servlet requests which accessed a local stateful session bean or a cluster of such nodes.
was (Author: rachmato):
If the Remoting Endpoint and the EJBRemotingConnectorService are indeed optional, and may be excluded from the server profile, a better way to handle this would be to check the state of the models for the Remoting and EJB subsystems at start up, see if the elements are present, and if they are both present, add them in as REQUIRED dependencies; otherwise leave them out. Also, if one of them is added in via the management interface, set the handler to force a reload so the check at start up may be performed anew.
> Eliminate use of optional dependencies for LocalEJBReceiver
> -----------------------------------------------------------
>
> Key: WFLY-3438
> URL: https://issues.jboss.org/browse/WFLY-3438
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Final, 9.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.CR1
>
>
> This issue was initially raised on stackoverflow (see below).
> When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
> As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
> This results in the exception
> .java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3438) Eliminate use of optional dependencies for LocalEJBReceiver
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-3438?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-3438:
-------------------------------------------
If the Remoting Endpoint and the EJBRemotingConnectorService are indeed optional, and may be excluded from the server profile, a better way to handle this would be to check the state of the models for the Remoting and EJB subsystems at start up, see if the elements are present, and if they are both present, add them in as REQUIRED dependencies; otherwise leave them out. Also, if one of them is added in via the management interface, set the handler to force a reload so the check at start up may be performed anew.
> Eliminate use of optional dependencies for LocalEJBReceiver
> -----------------------------------------------------------
>
> Key: WFLY-3438
> URL: https://issues.jboss.org/browse/WFLY-3438
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Final, 9.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.CR1
>
>
> This issue was initially raised on stackoverflow (see below).
> When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
> As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
> This results in the exception
> .java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (WFLY-3438) Eliminate use of optional dependencies for LocalEJBReceiver
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created WFLY-3438:
-----------------------------------------
Summary: Eliminate use of optional dependencies for LocalEJBReceiver
Key: WFLY-3438
URL: https://issues.jboss.org/browse/WFLY-3438
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 8.0.0.Final, 9.0.0.Alpha1
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 9.0.0.CR1
This issue was initially raised on stackoverflow (see below).
When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile.
As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.
This results in the exception
.java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months