January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14258) The first websocket that gets triggered from any deployed war file on server prevents all websockets in all other deployed war files from working

by Ronald Feicht (Jira)

[ https://issues.redhat.com/browse/WFLY-14258?page=com.atlassian.jira.plugi... ] Ronald Feicht edited comment on WFLY-14258 at 1/11/21 2:31 AM: --------------------------------------------------------------- When you click the Push button it should also show a message in the javascript console and of course in the message tab of the websocket entry of the browser's developer tools -> network. While debugging on the server (Java) I could see the websocket's id which indicates it was created but it does not process any messages leading me to assume it may be closed? was (Author: scsynergy): When you click the Push button it should also show a message in the javascript console and of course in the message tab of the websocket entry of the browser's developer tools -> network. While debugging I could see the websocket's id which indicates it was created but it does not process any messages leading me to assume it may be closed? > The first websocket that gets triggered from any deployed war file on server prevents all websockets in all other deployed war files from working > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-14258 > URL: https://issues.redhat.com/browse/WFLY-14258 > Project: WildFly > Issue Type: Bug > Components: JSF, Web Sockets > Reporter: Ronald Feicht > Assignee: Farah Juma > Priority: Major > Attachments: ws1.tar.gz, ws2.tar.gz > > > *Two* war files are deployed on the same Wildfly instance and both use websockets. The *first* page with f:websocket that gets loaded by the browser works perfectly well. Any websocket on any other page of the *same* war file also works perfectly well. Yet, any websocket of the *second* war file will not work until the server is restartet. Then the first page with a websocket that gets loaded determines which war file's websockets will work. > Example: > # WS1/index.xhtml --> websocket works > # WS2/index.xhtml --> websocket does not work (because it seems to be closed on the server side?) > # restart Wildfly > # WS2/index.xhtml --> websocket works > # WS1/index.xhtml --> websocket does not work (because it seems to be closed on the server side?) > # if we had a WS3/index.xhtml its websockets would also not work > issue found on: Mojarra 2.3.9.SP11 on WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) > Example war files attached for you to easily confirm this issue: > ws1.tar.gz > ws2.tar.gz > > Created the same bug report here because I cannot tell whether the bug is in Mojarra or the Wildfly integration of Mojarra: [https://github.com/eclipse-ee4j/mojarra/issues/4799] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14275) Large job repository is blocking deployment

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-14275?page=com.atlassian.jira.plugi... ] Cheng Fang moved JBERET-505 to WFLY-14275: ------------------------------------------ Component/s: Batch (was: jberet-wildfly) Key: WFLY-14275 (was: JBERET-505) Affects Version/s: (was: 1.3.7.Final) Project: WildFly (was: JBeret) > Large job repository is blocking deployment > ------------------------------------------- > > Key: WFLY-14275 > URL: https://issues.redhat.com/browse/WFLY-14275 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: Gunther vw > Assignee: Cheng Fang > Priority: Critical > Attachments: jberet-deploy.zip > > > We are updating from WildFly 13 (jberet 1.2.4) to WildFly 21.0.2 (jberet 1.3.7). > In our production environment we are running about 50 jobs, some of them in a frequency of 2 or 4 minutes. For documentation reasons we only can delete job information older than 3 months. So we have 20000 and more jobinstances per job in our job repository - an oracle database job repo. > Deploying of our Job-Module to WildFly 21 is never finished - sometimes a out of memory exception is thrown. > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Zbyněk Červinka resolved WFLY-13031. ------------------------------------ Fix Version/s: 22.0.0.Beta1 (was: 19.0.0.Beta2) (was: 19.0.0.Final) Resolution: Done > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 22.0.0.Beta1 > > Attachments: Problems view.png, Project Explorer.png, error-1-1.png, error-1.png, error-2.png, error.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Zbyněk Červinka reassigned WFLY-13031: -------------------------------------- Assignee: Zbyněk Červinka (was: Parul Sharma) > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 19.0.0.Beta2, 19.0.0.Final > > Attachments: Problems view.png, Project Explorer.png, error-1-1.png, error-1.png, error-2.png, error.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Zbyněk Červinka commented on WFLY-13031: ---------------------------------------- [~rchakrab] You are right - I have added this comment some time ago, today I have checked this issue with updated quickstarts, the issue is gone (in quickstart-22.0.0.Beta1). h3. Red Hat CodeReady Studio version: Version: 12.18.0.GA Build id: GA-v20210106-1009-B7391 Build date: 20210106-1009 > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Parul Sharma > Priority: Major > Fix For: 19.0.0.Beta2, 19.0.0.Final > > Attachments: Problems view.png, Project Explorer.png, error-1-1.png, error-1.png, error-2.png, error.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14274) Validation Issues With jboss-ejb3.xml

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-14274?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-14274: ----------------------------------- So this happened in IDE during development, not when deploying to WildFly? This is probably because the tool cannot find the schema definition for urn:security:1.1, either through its internal registry, or public internet location. I think the app should deploy fine to WildFly, and it's just a tool's failure to resolve the relevant schema segment. Can you make sure these schemas are all added into your IDE's schema registry? > Validation Issues With jboss-ejb3.xml > ------------------------------------- > > Key: WFLY-14274 > URL: https://issues.redhat.com/browse/WFLY-14274 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 18.0.1.Final > Reporter: Patrick Buchheit > Assignee: Cheng Fang > Priority: Major > > When attempting to add a <s:security> section to the <assembly-descriptor> of jboss-ejb3.xml I get the following error: > {code:java} > Invalid element name: - security One of the following is expected: - security-role - method-permission - container-transaction - interceptor-binding - message-destination - exclude-list - application-exception - assembly-descriptor-entry Error indicated by: {urn:security:1.1} with code:{code} > I copied and pasted the exact text given in the example here: [https://docs.wildfly.org/18/Developer_Guide.html#jboss-ejb3] so I'm not quite sure what the issue is. I found several bugs that seemed to describe the same behaviour, but they were all marked as fixed. See: https://issues.redhat.com/browse/JBIDE-18316 and [https://bugzilla.redhat.com/show_bug.cgi?id=1302544] for examples. > > Is there something wrong with the given documentation or is there still a bug in the schemas? > > Environment: > Eclipse Photon (4.17) > Jboss Tools plugin > Wildfly 18.0.1 Final -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14272) Upgrade to RestEasy 3.15

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-14272?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-14272: ------------------------------------- Hey [~kabirkhan] , Do you need anything in particular for 3.15.x? Btw, it has come to our attention that I was wrong when I claimed that RESTEasy 3.x would be OK with MicroProfile Config. We're working on a fix, so that could go in 3.15.x. [And Happy New Year :) ] -Ron > Upgrade to RestEasy 3.15 > ------------------------ > > Key: WFLY-14272 > URL: https://issues.redhat.com/browse/WFLY-14272 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Major > Labels: merged-to-feature-branch > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14262) Nightly test jobs Galleon linux Alt FP - JDK 8 and Master - Linux - Alt Dist- JDK 8 are failing

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14262?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14262: ------------------------------------ Description: https://ci.wildfly.org/viewLog.html?buildId=236272&buildTypeId=WF_Galleon... https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 I haven't looked closely but at a glance the MP TCK modules for the MP observability specs are failing. My guess is this job is still trying to run these against the ee-build, which will no longer work. was: https://ci.wildfly.org/viewLog.html?buildId=236272&buildTypeId=WF_Galleon... I haven't looked closely but at a glance the MP TCK modules for the MP observability specs are failing. My guess is this job is still trying to run these against the ee-build, which will no longer work. > Nightly test jobs Galleon linux Alt FP - JDK 8 and Master - Linux - Alt Dist- JDK 8 are failing > ----------------------------------------------------------------------------------------------- > > Key: WFLY-14262 > URL: https://issues.redhat.com/browse/WFLY-14262 > Project: WildFly > Issue Type: Bug > Components: Build System, Test Suite > Reporter: Brian Stansberry > Priority: Major > > https://ci.wildfly.org/viewLog.html?buildId=236272&buildTypeId=WF_Galleon... > https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 > I haven't looked closely but at a glance the MP TCK modules for the MP observability specs are failing. My guess is this job is still trying to run these against the ee-build, which will no longer work. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14262) Nightly test jobs Galleon linux Alt FP - JDK 8 and Master - Linux - Alt Dist- JDK 8 are failing

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14262?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14262: ------------------------------------ Summary: Nightly test jobs Galleon linux Alt FP - JDK 8 and Master - Linux - Alt Dist- JDK 8 are failing (was: Nightly test job Galleon linux Alt FP - JDK 8 is failing) > Nightly test jobs Galleon linux Alt FP - JDK 8 and Master - Linux - Alt Dist- JDK 8 are failing > ----------------------------------------------------------------------------------------------- > > Key: WFLY-14262 > URL: https://issues.redhat.com/browse/WFLY-14262 > Project: WildFly > Issue Type: Bug > Components: Build System, Test Suite > Reporter: Brian Stansberry > Priority: Major > > https://ci.wildfly.org/viewLog.html?buildId=236272&buildTypeId=WF_Galleon... > I haven't looked closely but at a glance the MP TCK modules for the MP observability specs are failing. My guess is this job is still trying to run these against the ee-build, which will no longer work. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12881: ------------------------------------ Issue Type: Feature Request (was: Bug) > Cannot customize split behavior and merge policy for Infinispan partition handling > ---------------------------------------------------------------------------------- > > Key: WFLY-12881 > URL: https://issues.redhat.com/browse/WFLY-12881 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final, 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 23.0.0.Beta1 > > > Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs. > Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

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 January 2021