June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4725) Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets>

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4725?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4725: ----------------------------------- Fails how? can you post stacktrace? > Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets> > ---------------------------------------------------------------------------------------- > > Key: WFLY-4725 > URL: https://issues.jboss.org/browse/WFLY-4725 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow), Web Sockets > Affects Versions: 10.0.0.Alpha2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Minor > > When deploying application with WebSockets used in EAP 6 to EAP 7, deployment will fail due EAP7 not supporting [1] in jboss-web.xml. The {{<enable-websockets>}} element is required in EAP 6 to enable the WebSockets functionality in JBoss Web. > This element should be also allowed in EAP 7 in order to simplify migration from EAP 6. Functionality of {{ <enable-websockets>true</enable-websockets>}} can be ignored as in EAP 7 and in Undertow there is no need to enable WebSockets explicitly. > [1] > {code:xml} > <jboss-web version="7.2" > xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee schema/jboss-web_7_2.xsd"> > <enable-websockets>true</enable-websockets> > </jboss-web> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4725) Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets>

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-4725?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka moved JBEAP-241 to WFLY-4725: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-4725 (was: JBEAP-241) Workflow: GIT Pull Request workflow (was: CDW v1) Affects Version/s: 10.0.0.Alpha2 (was: EAP 7.0.0.DR2) Component/s: Web (Undertow) Web Sockets (was: Web (Undertow)) (was: Web Sockets) Target Release: (was: EAP 7.0.0.GA) > Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets> > ---------------------------------------------------------------------------------------- > > Key: WFLY-4725 > URL: https://issues.jboss.org/browse/WFLY-4725 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow), Web Sockets > Affects Versions: 10.0.0.Alpha2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Minor > > When deploying application with WebSockets used in EAP 6 to EAP 7, deployment will fail due EAP7 not supporting [1] in jboss-web.xml. The {{<enable-websockets>}} element is required in EAP 6 to enable the WebSockets functionality in JBoss Web. > This element should be also allowed in EAP 7 in order to simplify migration from EAP 6. Functionality of {{ <enable-websockets>true</enable-websockets>}} can be ignored as in EAP 7 and in Undertow there is no need to enable WebSockets explicitly. > [1] > {code:xml} > <jboss-web version="7.2" > xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee schema/jboss-web_7_2.xsd"> > <enable-websockets>true</enable-websockets> > </jboss-web> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1931) Don't drop UNICAST3 message when the window is not created

by Radim Vansa (JIRA)

Radim Vansa created JGRP-1931: --------------------------------- Summary: Don't drop UNICAST3 message when the window is not created Key: JGRP-1931 URL: https://issues.jboss.org/browse/JGRP-1931 Project: JGroups Issue Type: Bug Reporter: Radim Vansa Assignee: Bela Ban When an application sends first two (or more) messages in parallel and the the second one is marked as DONT_BUNDLE, usually this one arrives as the first one and is dropped (see https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/...). After first message arrives, the connection is properly set up, but we need to wait until retransmission for the message (and other non-OOB) messages to be delivered. In practice this behaviour should be acceptable, but it causes failures in some time-sensitive tests (particularly in Hibernate ORM 2nd level cache). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1931) Don't drop UNICAST3 message when the window is not created

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1931?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1931: ------------------------------ Affects Version/s: 3.6.3 > Don't drop UNICAST3 message when the window is not created > ----------------------------------------------------------- > > Key: JGRP-1931 > URL: https://issues.jboss.org/browse/JGRP-1931 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.3 > Reporter: Radim Vansa > Assignee: Bela Ban > > When an application sends first two (or more) messages in parallel and the the second one is marked as DONT_BUNDLE, usually this one arrives as the first one and is dropped (see https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/...). After first message arrives, the connection is properly set up, but we need to wait until retransmission for the message (and other non-OOB) messages to be delivered. > In practice this behaviour should be acceptable, but it causes failures in some time-sensitive tests (particularly in Hibernate ORM 2nd level cache). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4724) Port SingletonTunnelTestCase from EAP6 to Wildfly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4724?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4724: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1223665 > Port SingletonTunnelTestCase from EAP6 to Wildfly > ------------------------------------------------- > > Key: WFLY-4724 > URL: https://issues.jboss.org/browse/WFLY-4724 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Test Suite > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > The test case is simulating cluster split & merge and checking that only one provider of a singleton service is elected after merge. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-202) Use wildfly-common for common asserts including null method parameters

by David Lloyd (JIRA)

David Lloyd created ELY-202: ------------------------------- Summary: Use wildfly-common for common asserts including null method parameters Key: ELY-202 URL: https://issues.jboss.org/browse/ELY-202 Project: WildFly Elytron Issue Type: Task Reporter: David Lloyd Several common assertions and checks are made available in wildfly-common. Use them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4724) Port SingletonTunnelTestCase from EAP6 to Wildfly

by Tomas Hofman (JIRA)

Tomas Hofman created WFLY-4724: ---------------------------------- Summary: Port SingletonTunnelTestCase from EAP6 to Wildfly Key: WFLY-4724 URL: https://issues.jboss.org/browse/WFLY-4724 Project: WildFly Issue Type: Enhancement Components: Clustering, Test Suite Reporter: Tomas Hofman Assignee: Tomas Hofman The test case is simulating cluster split & merge and checking that only one provider of a singleton service is elected after merge. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-804) KieProjectDefaultClasspathTest.createMultpleJarAndFileResources() fails sometimes when run on IBM JDK

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-804: ------------------------------------ Summary: KieProjectDefaultClasspathTest.createMultpleJarAndFileResources() fails sometimes when run on IBM JDK Key: DROOLS-804 URL: https://issues.jboss.org/browse/DROOLS-804 Project: Drools Issue Type: Bug Reporter: Tibor Zimányi Assignee: Mark Proctor Priority: Minor KieProjectDefaultClasspathTest.createMultpleJarAndFileResources() uses KieServicesEventListerner which is referenced as WeakReference in KieServicesImpl and ClasspathKieProject. IBM JDK handles garbage collection differently than Oracle JDK and sometimes frees the listener during test run so the test fails. The test should hold the reference to the listener during whole test run. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4680) Fork and JChannel names need to be unique

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4680?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4680: -------------------------------------- The naming change part is merged. > Fork and JChannel names need to be unique > ----------------------------------------- > > Key: WFLY-4680 > URL: https://issues.jboss.org/browse/WFLY-4680 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > The point is to > * recreate the channels as ee-web (with web fork on it) instead of channel web with fork web on it > * also investigate why without the fix for https://issues.jboss.org/browse/WFLY-4435 (and WFLY-4680) naming fork channels and jchannels the same (e.g. web) doesn't just result in duplicated service warning, but instead fails badly e.g. NPE in Infinispan https://issues.jboss.org/browse/ISPN-5483 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4723) Make jgroups protocols support indexed adds

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4723?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4723: ----------------------------- Issue Type: Feature Request (was: Task) > Make jgroups protocols support indexed adds > ------------------------------------------- > > Key: WFLY-4723 > URL: https://issues.jboss.org/browse/WFLY-4723 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 10.0.0.Alpha3 > > > With the work done on WFCORE-401 it is important that if a protocol is added to a master that it appears in the correct location on the slave when the slave reconnects. This is made possible by the indexed adds introduced by WFCORE-598. If not set up as ordered children, a new protocol added to the middle of a stack would appear at the end, which is not what we want -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015