[JBoss JIRA] (WFLY-4757) ConfigurationPersistenceException when persisting mod_cluster subsystem's "proxies" attribute
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4757?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-4757:
---------------------------------
Component/s: Clustering
> ConfigurationPersistenceException when persisting mod_cluster subsystem's "proxies" attribute
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-4757
> URL: https://issues.jboss.org/browse/WFLY-4757
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2
> Reporter: Michal Babacek
> Assignee: Radoslav Husar
> Priority: Blocker
> Labels: mod_cluster
> Fix For: 9.0.0.CR2, 10.0.0.Alpha4
>
>
> If one takes a vanilla EAP 7 DR build and starts it with {{./standalone.sh -c standalone.ha}}, i.e. with mod_cluster subsystem loaded, but without any static proxies configuration directives, the server registers with mod_cluster load balancers and accepts hot deployments without any error.
> If one sets a static proxy configuration, e.g.:
> {code:xml}
> +++
> <mod-cluster-config advertise-socket="modcluster" connector="ajp" proxies="my-proxy-one">
> +++
> <outbound-socket-binding name="my-proxy-one">
> <remote-destination host="10.40.4.50" port="6666"/>
> </outbound-socket-binding>
> +++
> {code}
> then the server processes hot deployments only as long as it's not registered with any mod_cluster load balancer. As soon as it registers with a load balancer, any hot deployment causes the following exception:
> {noformat}
> 14:39:13,475 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found simplecontext.war in deployment directory. To trigger deployment create a file called simplecontext.war.dodeploy
> 14:39:13,520 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "simplecontext.war" (runtime-name: "simplecontext.war")
> 14:39:14,028 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /simplecontext
> 14:39:14,080 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0008: Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0084: Failed to marshal configuration
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:49)
> at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.<init>(ConfigurationFilePersistenceResource.java:45)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.store(BackupXmlConfigurationPersister.java:109)
> at org.jboss.as.controller.ModelControllerImpl.writeModel(ModelControllerImpl.java:738)
> at org.jboss.as.controller.OperationContextImpl.createPersistenceResource(OperationContextImpl.java:403)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:643)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354)
> at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:918)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:885)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1170)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:363)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:219)
> at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:716)
> at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:710)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.as.controller.ModelControllerImpl$3$1.run(ModelControllerImpl.java:710)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0089: Failed to write configuration
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:100)
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:42)
> ... 26 more
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at org.jboss.staxmapper.FormattingXMLStreamWriter$4.run(FormattingXMLStreamWriter.java:249)
> at org.jboss.staxmapper.FormattingXMLStreamWriter.runAttrQueue(FormattingXMLStreamWriter.java:221)
> at org.jboss.staxmapper.FormattingXMLStreamWriter.writeStartElement(FormattingXMLStreamWriter.java:96)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemXMLWriter.writeDynamicLoadProvider(ModClusterSubsystemXMLWriter.java:104)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemXMLWriter.writeModClusterConfig(ModClusterSubsystemXMLWriter.java:69)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemXMLWriter.writeContent(ModClusterSubsystemXMLWriter.java:51)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemXMLWriter.writeContent(ModClusterSubsystemXMLWriter.java:42)
> at org.jboss.as.server.parsing.StandaloneXml_4.writeServerProfile(StandaloneXml_4.java:695)
> at org.jboss.as.server.parsing.StandaloneXml_4.writeContent(StandaloneXml_4.java:613)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:77)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:47)
> at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:88)
> at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:83)
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:94)
> ... 27 more
> Caused by: javax.xml.stream.XMLStreamException: Trying to write an attribute when there is no open start element.
> at com.ctc.wstx.sw.BaseStreamWriter.throwOutputError(BaseStreamWriter.java:1537)
> at com.ctc.wstx.sw.BaseStreamWriter.reportNwfStructure(BaseStreamWriter.java:1566)
> at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.java:226)
> at org.jboss.staxmapper.FormattingXMLStreamWriter$4.run(FormattingXMLStreamWriter.java:247)
> ... 40 more
> 14:39:14,085 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0021: Deploy of deployment "simplecontext.war" was rolled back with the following failure message: "WFLYCTL0086: Failed to persist configuration change: WFLYCTL0084: Failed to marshal configuration"
> 14:39:14,095 INFO [org.jboss.modcluster] (MSC service thread 1-3) MODCLUSTER000021: All pending requests drained from default-host:/simplecontext in 0.0 seconds
> 14:39:14,098 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /simplecontext
> 14:39:14,142 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.1.3.Final
> 14:39:14,177 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment simplecontext.war (runtime-name: simplecontext.war) in 92ms
> {noformat}
> The problem is IMHO related to the new configuration attribute WFLY-457.
>
> Note that this issue affects *hot deployments only*. If the server starts with deployments already present, no exception is thrown and everything works as expected. I find this issue being of {color:red}critical{color} severity, because it breaks core functionality of the application server -- hot deployments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4779) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4779?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-4779:
---------------------------------
Tester: Michal Babacek
> Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4779
> URL: https://issues.jboss.org/browse/WFLY-4779
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.0.CR2, 10.0.0.Alpha2
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 9.0.0.Final, 10.0.0.Alpha4
>
>
> Affects at least infinispan aliases and modcluster proxies...
> (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23
> (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list
> (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String..
> (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases
> (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([
> (20:23:24) rhusar: ("subsystem" => "infinispan"),
> (20:23:24) rhusar: ("cache-container" => "hibernate")
> (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90)
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117)
> (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
> (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745)
> (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4779) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4779?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-4779:
---------------------------------
Fix Version/s: 9.0.0.Final
> Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4779
> URL: https://issues.jboss.org/browse/WFLY-4779
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.0.CR2, 10.0.0.Alpha2
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 9.0.0.Final, 10.0.0.Alpha4
>
>
> Affects at least infinispan aliases and modcluster proxies...
> (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23
> (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list
> (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String..
> (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases
> (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([
> (20:23:24) rhusar: ("subsystem" => "infinispan"),
> (20:23:24) rhusar: ("cache-container" => "hibernate")
> (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90)
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117)
> (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
> (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745)
> (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4792) Undertow deployment-level session statistics not available
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-4792?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-4792:
------------------------------------
Correction - org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager is only used for <distributable/> web applications. Non-distributable web applications (regardless of server profile) will use Undertow's InMemorySessionManager.
> Undertow deployment-level session statistics not available
> ----------------------------------------------------------
>
> Key: WFLY-4792
> URL: https://issues.jboss.org/browse/WFLY-4792
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Web (Undertow)
> Affects Versions: 9.0.0.CR2
> Reporter: Martin Kouba
> Assignee: Paul Ferraro
>
> {{org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager}} which is used by default even for non-HA configurations in WildFly 9.0.0.CR2 (e.g. {{standalone.xml}} in app server distribution) does not implement {{io.undertow.server.session.SessionManagerStatistics}} and so no stats except for {{activeSessions}} are available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4799) cancelled ejb timers persist in data/timer-service-data
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-4799?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-4799:
------------------------------------
[~jrwhitley], this JIRA is missing the .ear attachment that you note in your steps to reproduce. Could you please attach it (hopefully along with the source)?
> cancelled ejb timers persist in data/timer-service-data
> -------------------------------------------------------
>
> Key: WFLY-4799
> URL: https://issues.jboss.org/browse/WFLY-4799
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.CR2
> Environment: linux 4.0.4-303.fc22.x86_64, java jdk1.8.0_45 and wildfly-9.0.0.CR2
> Reporter: John Whitley
> Labels: jboss
>
> I have a Singleton bean which creates a ejb.timer on deployment. Before doing so it cancels any existing timers previously created by the bean for completeness.
> In wildfly 8 the cancelled timers were removed from data/timer-service-data/'bean'. In wildfly 9 CR2, they stay in data/timer-service-data/'bean' and appear to be re-instated on re-deployment
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4778) WebSocket connection failed because of Unexpected response code: 501
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4778?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4778:
--------------------------------------
It is more likely that I will be able to look at this sooner if you provide an example application. If I have to build my own Vaadin application to try and reproduce it then it may be a while before I can look at this.
> WebSocket connection failed because of Unexpected response code: 501
> --------------------------------------------------------------------
>
> Key: WFLY-4778
> URL: https://issues.jboss.org/browse/WFLY-4778
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Mike Mike
> Assignee: Stuart Douglas
>
> I am trying to use Wilfly 9 RC with Vaadins Server Push. The Push works but I get always following message in the java script log:
> Vaadin push loaded
> vaadinPush.js:21 WebSocket connection to 'ws://localhost:8080/abc-ui/PUSH/?v-uiId=0&v-csrfToken=9592bfe8-549f-4713-85b4-8ddae0163407&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.0.3.vaadin2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8' failed: Error during WebSocket handshake: Unexpected response code: 501
> vaadinPush.js:21 Websocket failed. Downgrading to Comet and resending
> The HTTP 501 (Not Implemented) is really irritating. Which side is implementing and who specifies?
> I found this topic related here: http://atmosphere-framework.2306103.n4.nabble.com/Websocket-Connection-Fa...
> Does anybody know here, if it is a bug in WildFly or atmosphere?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4778) WebSocket connection failed because of Unexpected response code: 501
by Mike Mike (JIRA)
[ https://issues.jboss.org/browse/WFLY-4778?page=com.atlassian.jira.plugin.... ]
Mike Mike commented on WFLY-4778:
---------------------------------
I will open a thread in Vaadin's forum..
> WebSocket connection failed because of Unexpected response code: 501
> --------------------------------------------------------------------
>
> Key: WFLY-4778
> URL: https://issues.jboss.org/browse/WFLY-4778
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Mike Mike
> Assignee: Stuart Douglas
>
> I am trying to use Wilfly 9 RC with Vaadins Server Push. The Push works but I get always following message in the java script log:
> Vaadin push loaded
> vaadinPush.js:21 WebSocket connection to 'ws://localhost:8080/abc-ui/PUSH/?v-uiId=0&v-csrfToken=9592bfe8-549f-4713-85b4-8ddae0163407&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.0.3.vaadin2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8' failed: Error during WebSocket handshake: Unexpected response code: 501
> vaadinPush.js:21 Websocket failed. Downgrading to Comet and resending
> The HTTP 501 (Not Implemented) is really irritating. Which side is implementing and who specifies?
> I found this topic related here: http://atmosphere-framework.2306103.n4.nabble.com/Websocket-Connection-Fa...
> Does anybody know here, if it is a bug in WildFly or atmosphere?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4778) WebSocket connection failed because of Unexpected response code: 501
by Mike Mike (JIRA)
[ https://issues.jboss.org/browse/WFLY-4778?page=com.atlassian.jira.plugin.... ]
Mike Mike commented on WFLY-4778:
---------------------------------
The error appears only in firefox. Chrome throws another log message:
"Websocket closed, reason: Normal closure; the connection successfully completed whatever purpose for which it was created.
vaadinPush.js?v=7.4.8:25 Websocket closed, wasClean: true"
> WebSocket connection failed because of Unexpected response code: 501
> --------------------------------------------------------------------
>
> Key: WFLY-4778
> URL: https://issues.jboss.org/browse/WFLY-4778
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Mike Mike
> Assignee: Stuart Douglas
>
> I am trying to use Wilfly 9 RC with Vaadins Server Push. The Push works but I get always following message in the java script log:
> Vaadin push loaded
> vaadinPush.js:21 WebSocket connection to 'ws://localhost:8080/abc-ui/PUSH/?v-uiId=0&v-csrfToken=9592bfe8-549f-4713-85b4-8ddae0163407&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.0.3.vaadin2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8' failed: Error during WebSocket handshake: Unexpected response code: 501
> vaadinPush.js:21 Websocket failed. Downgrading to Comet and resending
> The HTTP 501 (Not Implemented) is really irritating. Which side is implementing and who specifies?
> I found this topic related here: http://atmosphere-framework.2306103.n4.nabble.com/Websocket-Connection-Fa...
> Does anybody know here, if it is a bug in WildFly or atmosphere?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4778) WebSocket connection failed because of Unexpected response code: 501
by Mike Mike (JIRA)
[ https://issues.jboss.org/browse/WFLY-4778?page=com.atlassian.jira.plugin.... ]
Mike Mike commented on WFLY-4778:
---------------------------------
I tried the newest version of vaadin 7.4.8 with athmosphere 2.2.4.vaadin5 now. The error in the log file is away, but the server push does also not work anymore:
"Websocket closed, reason: The endpoint is going away, either because of a server failure or because the browser is navigating away from the page that opened the connection." vaadinPush.js:25:141275
"Websocket closed, wasClean: true" vaadinPush.js:25:141275
> WebSocket connection failed because of Unexpected response code: 501
> --------------------------------------------------------------------
>
> Key: WFLY-4778
> URL: https://issues.jboss.org/browse/WFLY-4778
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Mike Mike
> Assignee: Stuart Douglas
>
> I am trying to use Wilfly 9 RC with Vaadins Server Push. The Push works but I get always following message in the java script log:
> Vaadin push loaded
> vaadinPush.js:21 WebSocket connection to 'ws://localhost:8080/abc-ui/PUSH/?v-uiId=0&v-csrfToken=9592bfe8-549f-4713-85b4-8ddae0163407&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.0.3.vaadin2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8' failed: Error during WebSocket handshake: Unexpected response code: 501
> vaadinPush.js:21 Websocket failed. Downgrading to Comet and resending
> The HTTP 501 (Not Implemented) is really irritating. Which side is implementing and who specifies?
> I found this topic related here: http://atmosphere-framework.2306103.n4.nabble.com/Websocket-Connection-Fa...
> Does anybody know here, if it is a bug in WildFly or atmosphere?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month