May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12124) SSL certificate revocation list community docs

by Martin Mazanek (Jira)

Martin Mazanek created WFLY-12124: ------------------------------------- Summary: SSL certificate revocation list community docs Key: WFLY-12124 URL: https://issues.jboss.org/browse/WFLY-12124 Project: WildFly Issue Type: Feature Request Components: Security Reporter: Martin Mazanek Assignee: Martin Mazanek -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12123) Support SSL Certificate revocation using OCSP community docs

by Martin Mazanek (Jira)

[ https://issues.jboss.org/browse/WFLY-12123?page=com.atlassian.jira.plugin... ] Martin Mazanek moved WFCORE-4494 to WFLY-12123: ----------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-12123 (was: WFCORE-4494) Component/s: Security (was: Security) Affects Version/s: (was: 6.0.0.Alpha2) Fix Version/s: (was: 10.0.0.Beta1) > Support SSL Certificate revocation using OCSP community docs > ------------------------------------------------------------ > > Key: WFLY-12123 > URL: https://issues.jboss.org/browse/WFLY-12123 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Martin Mazanek > Assignee: Martin Mazanek > Priority: Major > > - Provide undertow's client certificate revocation capability when undertow is used as a load balancer using OCSP. > (CRL capability is provided in the earlier release as part of Elytron SSL Consolidation effort that this JIRA is cloned from) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4494) Support SSL Certificate revocation using OCSP community docs

by Martin Mazanek (Jira)

Martin Mazanek created WFCORE-4494: -------------------------------------- Summary: Support SSL Certificate revocation using OCSP community docs Key: WFCORE-4494 URL: https://issues.jboss.org/browse/WFCORE-4494 Project: WildFly Core Issue Type: Feature Request Components: Security Affects Versions: 6.0.0.Alpha2 Reporter: Martin Mazanek Assignee: Martin Mazanek Fix For: 10.0.0.Beta1 - Provide undertow's client certificate revocation capability when undertow is used as a load balancer using OCSP. (CRL capability is provided in the earlier release as part of Elytron SSL Consolidation effort that this JIRA is cloned from) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-755) Ask for more storage in PSI

by Filip Brychta (Jira)

Filip Brychta created SWSQE-755: ----------------------------------- Summary: Ask for more storage in PSI Key: SWSQE-755 URL: https://issues.jboss.org/browse/SWSQE-755 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Minimal ocp 4.1 cluster consumes 200 GB of storage and we only have available 2000GB in istio-dev project so it's for 10 clusters. Count how much more we need and ask for increase. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12121) Transaction JDBC object store CLI operation fails when set to false with information JDBC connection is needed

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12121?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFLY-12121: ----------------------------------------- Ok, I found out that this error does not come from the transaction code. Handlers there checks if the value is about to be set to {{true}} and only in such case, it shows the error. https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... {code} ... if (modelNode.hasDefined(USE_JDBC_STORE.getName()) && modelNode.get(USE_JDBC_STORE.getName()).asBoolean() ... {code} The error comes from the generic handler that checks what is defined by {{setRequires(...)}} https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... where it's defined {code} .setRequires(CommonAttributes.JDBC_STORE_DATASOURCE) {code} The handler where the exception is thrown from is at WFLY Core at {{ValidateModelStepHandler}} https://github.com/wildfly/wildfly-core/blob/9.0.0.Beta6/controller/src/m... Now I wonder if the generic handler {{ValidateModelStepHandler}} could be wrong that it does not allow the usage of the {{false}} and still requires what is defined as 'requires'. Or if in my case the {{seRequires}} should not be used as it's a specific logic which is expected to be done "manually" at {{TransactionSubsystemRootResourceDefinition}}? Would you have some tip for me on this [~kabirkhan][~brian.stansberry]? Thanks > Transaction JDBC object store CLI operation fails when set to false with information JDBC connection is needed > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12121 > URL: https://issues.jboss.org/browse/WFLY-12121 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > If the JDBC store is for to be disabled it's needed to be used CLI command > {code} > /subsystem=transactions:write-attribute(name=use-jdbc-store, value=false) > {code} > (see documentation https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...) > but when a data source is not configured then even when it's to be set to false there is an error that such operation is not possible > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0380: Attribute 'jdbc-store-datasource' needs to be set or passed before attribute 'use-jdbc-store' can be correctly set", > "rolled-back" => true > } > {code} > I would expect that when I want to disable the jdbc store I don't need to provide a data source for a connection before. Setting-up the {{false}} should not throw an error in CLI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3432) While using the same template key with difference objects/attributes causes an exception when switching to the Data tab in a Guided Rule Template

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3432?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3432: ------------------------------------- Coverage increase https://github.com/kiegroup/drools/pull/2364 > While using the same template key with difference objects/attributes causes an exception when switching to the Data tab in a Guided Rule Template > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3432 > URL: https://issues.jboss.org/browse/DROOLS-3432 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > When we use the same template in key for different object fields(different fields from the same fields from different objects), we get an exception after selecting the data tab, attaching the screen shot. > There is a workaround , we can give every template a unique name as a work around, but this slow down because we need to create different key names with the same information in the data table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12122) Upgrade to component matrix 1.0.3.Final

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-12122?page=com.atlassian.jira.plugin... ] Kabir Khan moved WFCORE-4493 to WFLY-12122: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-12122 (was: WFCORE-4493) > Upgrade to component matrix 1.0.3.Final > --------------------------------------- > > Key: WFLY-12122 > URL: https://issues.jboss.org/browse/WFLY-12122 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Priority: Major > > It basically contains a fix for a NPE > https://github.com/wildfly/wildfly-component-matrix-plugin/compare/1.0.2.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4493) Upgrade to component matrix 1.0.3.Final

by Kabir Khan (Jira)

Kabir Khan created WFCORE-4493: ---------------------------------- Summary: Upgrade to component matrix 1.0.3.Final Key: WFCORE-4493 URL: https://issues.jboss.org/browse/WFCORE-4493 Project: WildFly Core Issue Type: Component Upgrade Reporter: Kabir Khan Assignee: Jeff Mesnil It basically contains a fix for a NPE https://github.com/wildfly/wildfly-component-matrix-plugin/compare/1.0.2.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12090) Unknown service name jboss.ejb and txn

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/WFLY-12090?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on WFLY-12090: ----------------------------------------- I am not following precisely, if the remote server returns zero Xids then the local client could probably return zero Xids to the local transaction manager and delete it's file if it is certain the other side can never return an Xid? But I think that this discussion should be taking place on https://issues.jboss.org/browse/WFTC-64 rather than here if I am understanding the context correctly? > Unknown service name jboss.ejb and txn > -------------------------------------- > > Key: WFLY-12090 > URL: https://issues.jboss.org/browse/WFLY-12090 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 17.0.0.Alpha1 > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 17.0.0.Beta1 > > > When EJBRemoting service is not started (it is LAZY), but XA recovery has, we could have the following sort of error: > {code} > 16:51:46,785 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: WFTXN0034: Failed to acquire a connection for this operation > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:139) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.recover(RemotingRemoteTransactionPeer.java:202) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:201) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:197) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:634) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:226) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:171) > at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770) > at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382) > Caused by: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb > at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:429) > at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) > at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > Suppressed: org.jboss.remoting3.ServiceOpenException: Unknown service name txn > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4492) Upgrade to component matrix 1.0.3.Final

by Kabir Khan (Jira)

Kabir Khan created WFCORE-4492: ---------------------------------- Summary: Upgrade to component matrix 1.0.3.Final Key: WFCORE-4492 URL: https://issues.jboss.org/browse/WFCORE-4492 Project: WildFly Core Issue Type: Component Upgrade Reporter: Kabir Khan Assignee: Jeff Mesnil It basically contains a fix for a NPE https://github.com/wildfly/wildfly-component-matrix-plugin/compare/1.0.2.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019