January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14334) Upgrade HAL to 3.2.13.Final

by Tomas Hofman (Jira)

Tomas Hofman created WFLY-14334: ----------------------------------- Summary: Upgrade HAL to 3.2.13.Final Key: WFLY-14334 URL: https://issues.redhat.com/browse/WFLY-14334 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Tomas Hofman Assignee: Lin Gao Fix For: 22.0.0.Beta1, 22.0.0.Final Tag: https://github.com/hal/console/releases/tag/3.2.12.Final Diff: https://github.com/hal/console/compare/3.2.11.Final...3.2.12.Final -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14277) Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14277?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-14277: ------------------------------ Labels: merged-to-feature-branch (was: ) > Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4 > ------------------------------------------------------------------------ > > Key: WFLY-14277 > URL: https://issues.redhat.com/browse/WFLY-14277 > Project: WildFly > Issue Type: Feature Request > Components: MP JWT, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Labels: merged-to-feature-branch > Fix For: 23.0.0.Beta1 > > > For spec changes see: > [https://github.com/eclipse/microprofile-jwt-auth/releases/tag/1.2] > and: > https://github.com/eclipse/microprofile-jwt-auth/compare/1.1...1.2 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14333) Upgrade wildfly-http-client from 1.1.5.Final

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFLY-14333?page=com.atlassian.jira.plugi... ] Tomas Hofman moved JBEAP-20881 to WFLY-14333: --------------------------------------------- Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.6.GA) Key: WFLY-14333 (was: JBEAP-20881) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Project: WildFly (was: JBoss Enterprise Application Platform) > Upgrade wildfly-http-client from 1.1.5.Final > -------------------------------------------- > > Key: WFLY-14333 > URL: https://issues.redhat.com/browse/WFLY-14333 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > Labels: downstream_dependency > > Tag: https://github.com/wildfly/wildfly-http-client/releases/tag/1.0.25.Final > Diff: https://github.com/wildfly/wildfly-http-client/compare/1.0.24.Final...1.0... > Commit hash: -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5250) Upgrade JBoss Remoting from 5.0.20 to 5.0.21

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFCORE-5250?page=com.atlassian.jira.plug... ] Tomas Hofman updated WFCORE-5250: --------------------------------- Summary: Upgrade JBoss Remoting from 5.0.20 to 5.0.21 (was: Upgrade JBoss Remoting from 5.0.20.Final-redhat-00001 to 5.0.21.Final-redhat-00001) > Upgrade JBoss Remoting from 5.0.20 to 5.0.21 > -------------------------------------------- > > Key: WFCORE-5250 > URL: https://issues.redhat.com/browse/WFCORE-5250 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > tag: https://github.com/jboss-remoting/jboss-remoting/releases/tag/5.0.21.Final > diff: https://github.com/jboss-remoting/jboss-remoting/compare/5.0.20.Final...5... > hash: -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5250) Upgrade JBoss Remoting from 5.0.20.Final-redhat-00001 to 5.0.21.Final-redhat-00001

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFCORE-5250?page=com.atlassian.jira.plug... ] Tomas Hofman moved JBEAP-20880 to WFCORE-5250: ---------------------------------------------- Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.6.GA) Key: WFCORE-5250 (was: JBEAP-20880) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Project: WildFly Core (was: JBoss Enterprise Application Platform) > Upgrade JBoss Remoting from 5.0.20.Final-redhat-00001 to 5.0.21.Final-redhat-00001 > ---------------------------------------------------------------------------------- > > Key: WFCORE-5250 > URL: https://issues.redhat.com/browse/WFCORE-5250 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > tag: https://github.com/jboss-remoting/jboss-remoting/releases/tag/5.0.21.Final > diff: https://github.com/jboss-remoting/jboss-remoting/compare/5.0.20.Final...5... > hash: -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12969) Include Openshift Instructions in EAP non-CD Quickstarts READMEs

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12969?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-12969: ---------------------------------------- [~szhantem] The 7.4 beta images and templates are not yet available. Actually at this point the templates names are not even yet defined. I will update the dev branch with the right names as soon as that info is available. Thanks for the pre-check :-) > Include Openshift Instructions in EAP non-CD Quickstarts READMEs > ---------------------------------------------------------------- > > Key: WFLY-12969 > URL: https://issues.redhat.com/browse/WFLY-12969 > Project: WildFly > Issue Type: Feature Request > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Attachments: app-client-eap-noncd-README.html, app-client-wfly-README.html, batch-processing-eap-cd-README.html, batch-processing-eap-noncd-README.html, batch-processing-wfly-README.html, parent-eap-cd-README.html, parent-eap-noncd-README.html, parent-wfly-README.html > > > Currently QS readmes include the openshift instructions only for CD releases. QS that run on Openshift (those included in CD releases) should contain openshift instructions for non-CD releases too, as the openshift image is released. > For example helloworld QS, which is also included in CD release: > https://raw.githubusercontent.com/wildfly/quickstart/master/helloworld/RE... -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14311) javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-14311?page=com.atlassian.jira.plugi... ] Lin Gao reassigned WFLY-14311: ------------------------------ Assignee: Sudeshna Sur (was: Lin Gao) > javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-14311 > URL: https://issues.redhat.com/browse/WFLY-14311 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: Lin Gao > Assignee: Sudeshna Sur > Priority: Major > Labels: downstream_dependency > Fix For: 23.0.0.Beta1 > > > The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI. > When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out. > {code:java} > 13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only > at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160) > at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66) > at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262) > at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289) > at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238) > at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > 13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only > at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160) > at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108) > at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301) > at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309) > at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236) > at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > {code} > From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities: > {quote} > The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts. > {quote} > For more information and reproducer, please refer to WFLY-13459 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14332) Upgrade messaging schema version to 13.0

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-14332: ---------------------------------------- Summary: Upgrade messaging schema version to 13.0 Key: WFLY-14332 URL: https://issues.redhat.com/browse/WFLY-14332 Project: WildFly Issue Type: Enhancement Components: JMS Affects Versions: 22.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Upgrade messaging schema version to 13.0 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5249) NoClassDefFoundError: Failed to link org/bouncycastle/openpgp/PGPEncryptedDataList: org/bouncycastle/util/Iterable

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5249?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5249: -------------------------------- Fix Version/s: 14.0.1.Final > NoClassDefFoundError: Failed to link org/bouncycastle/openpgp/PGPEncryptedDataList: org/bouncycastle/util/Iterable > ------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-5249 > URL: https://issues.redhat.com/browse/WFCORE-5249 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 14.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Sudeshna Sur > Priority: Major > Fix For: 14.0.1.Final, 15.0.0.Beta1 > > > Could you please add missing dependencies in Bouncycastle modules? > Problem (we got): > {code:java} > Caused by: java.lang.NoClassDefFoundError: Failed to link org/bouncycastle/openpgp/PGPEncryptedDataList (Module "org.bouncycastle.bcpg" version 1.66.00.0 from local module loader @1d1f7216 (finder: local module finder @423e4cbb (roots: /data/avoka/transact/manager/server/modules,/data/avoka/transact/manager/server/modules/system/layers/base))): org/bouncycastle/util/Iterable > {code} > > Solution (adding dependency from bcpg to bcprov modules solves the issue): > {code:java} > modules\system\layers\base\org\bouncycastle\bcpg\main\module.xml{code} > {code:java} > <dependencies> > <module name="org.bouncycastle.bcprov" export="true" services="export"/> > </dependencies> > {code} > -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-2462) kie-docs 6.5.x doesn't build offline

by Marek Novotny (Jira)

[ https://issues.redhat.com/browse/DROOLS-2462?page=com.atlassian.jira.plug... ] Marek Novotny closed DROOLS-2462. --------------------------------- Resolution: Won't Fix > kie-docs 6.5.x doesn't build offline > ------------------------------------ > > Key: DROOLS-2462 > URL: https://issues.redhat.com/browse/DROOLS-2462 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 6.5.0.Final > Reporter: Michael Biarnes Kiefer > Assignee: Marek Novotny > Priority: Major > > when the repository kie-docs 6.5.x is build offline > _man clean install -Dfull -o_ (and without internet connection) this error is thrown: [error|https://gist.github.com/mbiarnes/bb3a46bebf788225f663f249fc9dc361] > The general suspicion is that <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.76.1/fo/docbook.xsl"/> can't be downloaded and this causes the error. > We have on Jenkins each "some days" period that kie-docs fails, but when building again it builds successful. So when it fails it has no connection problems and this file can't be downloaded. > A build without internet connection is not possible. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021