May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10385) TransactionInflowTestCase does not function correctly under security manager

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-10385?page=com.atlassian.jira.plugin... ] Ondra Chaloupka commented on WFLY-10385: ---------------------------------------- thanks [~dmlloyd]. I've added the permissions needed for the test pass. > TransactionInflowTestCase does not function correctly under security manager > ---------------------------------------------------------------------------- > > Key: WFLY-10385 > URL: https://issues.jboss.org/browse/WFLY-10385 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: David Lloyd > Assignee: Ondra Chaloupka > > Proactively assigning to [~ochaloup] as he is the original test author; feel free to adjust as necessary. > {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowTestCase}} does not function correctly under a security manager. The stack trace is like this: > {noformat} > Breakpoint reached > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192) > at java.lang.SecurityManager.checkConnect(SecurityManager.java:1048) > at org.wildfly.security.manager.WildFlySecurityManager.checkConnect(WildFlySecurityManager.java:390) > at java.net.InetAddress.getLocalHost(InetAddress.java:1477) > at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getXid(TransactionInflowXid.java:128) > at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getUniqueXid(TransactionInflowXid.java:102) > at org.jboss.as.test.integration.transaction.inflow.TransactionInflowResourceAdapter.endpointActivation(TransactionInflowResourceAdapter.java:65) > at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:194) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:277) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:235) > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Perm = ("java.net.SocketPermission" "behemoth.local" "resolve"), CS = (vfs:/content/inflow-txn-ra.rar/inflow-txn-inside.jar <no signer certificates>), CL = ModuleClassLoader for Module "deployment.inflow-txn-ra.rar" from Service Module Loader, ID = 824b419 > {noformat} > The cause is that {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid#getXid}} calls {{java.net.InetAddress#getLocalHost}} which requires a security manager permission. If the permission is denied (which it always is when running under a security manager), then it falls back through a {{catch (Exception ex)}} to a bogus IP address of "1.2.3.4". > For correct operation, the test archives which use this method should have the {{"*"}} {{"resolve"}} {{SocketPermission}} granted to them. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-201) Bookinfo reinstall step in pipeline

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-201?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-201: ----------------------------------- Assignee: Filip Brychta (was: Hayk Hovsepyan) > Bookinfo reinstall step in pipeline > ----------------------------------- > > Key: SWSQE-201 > URL: https://issues.jboss.org/browse/SWSQE-201 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > > Done: > In [Istio-and-Kiali-on-Openshift|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/] Pipeline in a step "Install Istio" it installs bookinfo app. But when It does not reinstall Istio, bookinfo will remain the old installed. We need clean installed Bookinfo for test purposes. > The [Istio-Features-Bookinfo|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-Features-Bookinfo/] job is a separate job which installs bookinfo only. > TODO: > Make sure that Istio-Features-Bookinfo job have an option to "Clean" and "Clean/Reinstall Bookinfo", which means that all Istio related objets are deleted from Bookinfo and Bookinfo is reinstalled. > Make sure that the above job is included in Istio-and-Kiali-on-Openshift pipeline with optional param to activate. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10381) AttributeConverter injection fails with EclipseLink if deploy-on-startup = true

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10381?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10381: ------------------------------------- [~jlukas] Any thoughts on this (WFLY-10381) issue? IMO, I think that EclipseLink implementing [https://github.com/javaee/jpa-spec/issues/83], could help avoid the need for the eclipselink.deploy-on-startup workaround. > AttributeConverter injection fails with EclipseLink if deploy-on-startup = true > ------------------------------------------------------------------------------- > > Key: WFLY-10381 > URL: https://issues.jboss.org/browse/WFLY-10381 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Scott Marlow > > As of 2.7, EclipseLink implements JPA 2.2 and therefore supports injection into AttributeConverters. Injection fails silently if the eclipselink.deploy-on-startup PU property is set to true, because the BeanManager is not available yet when EclipseLink tries to instantiate the AttributeConverter. > Workaround: don't set the deploy-on-startup property. > It would be nice if this could be made to work, but I'm guessing it will be a chicken/egg problem of dependencies between CDI and JPA. So if it can't be made to work, it would be good to at least detect that the PU property has been set, and warn about it in the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1583) Unsufficient TRACE messages in Keystore

by Jan Kalina (JIRA)

Jan Kalina created ELY-1583: ------------------------------- Summary: Unsufficient TRACE messages in Keystore Key: ELY-1583 URL: https://issues.jboss.org/browse/ELY-1583 Project: WildFly Elytron Issue Type: Enhancement Components: Realms Affects Versions: 1.3.2.Final Reporter: Jan Kalina Assignee: Jan Kalina When troubleshotting CLIENT-CERT, there is no info from keystore-realm, why was certificate rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2557) Unexpected rule fire by sharing From and pojo without hashCode/equals

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2557?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-2557: -------------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/1905 > Unexpected rule fire by sharing From and pojo without hashCode/equals > --------------------------------------------------------------------- > > Key: DROOLS-2557 > URL: https://issues.jboss.org/browse/DROOLS-2557 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > Under the conditions: > - "from" clause with multiple rules > - calling update() > - Pojo doesn't implement hashCode/equals (to be precise, only equals() seems to matter) > A rule is activated/fired unexpectedly. > Please see Unit test for details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2557) Unexpected rule fire by sharing From and pojo without hashCode/equals

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created DROOLS-2557: ----------------------------------------- Summary: Unexpected rule fire by sharing From and pojo without hashCode/equals Key: DROOLS-2557 URL: https://issues.jboss.org/browse/DROOLS-2557 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco Under the conditions: - "from" clause with multiple rules - calling update() - Pojo doesn't implement hashCode/equals (to be precise, only equals() seems to matter) A rule is activated/fired unexpectedly. Please see Unit test for details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3522) Module dependency order for a deployment is wrong

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3522?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3522: -------------------------------- Priority: Critical (was: Blocker) > Module dependency order for a deployment is wrong > ------------------------------------------------- > > Key: WFCORE-3522 > URL: https://issues.jboss.org/browse/WFCORE-3522 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.8.Final > Reporter: Ken Finnigan > Assignee: David Lloyd > Priority: Critical > > Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile. > With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... > After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead. > He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-201) Bookinfo reinstall step in pipeline

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-201?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-201: --------------------------------- Description: Done: In [Istio-and-Kiali-on-Openshift|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/] Pipeline in a step "Install Istio" it installs bookinfo app. But when It does not reinstall Istio, bookinfo will remain the old installed. We need clean installed Bookinfo for test purposes. The [Istio-Features-Bookinfo|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-Features-Bookinfo/] job is a separate job which installs bookinfo only. TODO: Make sure that Istio-Features-Bookinfo job have an option to "Clean" and "Clean/Reinstall Bookinfo", which means that all Istio related objets are deleted from Bookinfo and Bookinfo is reinstalled. Make sure that the above job is included in Istio-and-Kiali-on-Openshift pipeline with optional param to activate. > Bookinfo reinstall step in pipeline > ----------------------------------- > > Key: SWSQE-201 > URL: https://issues.jboss.org/browse/SWSQE-201 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Done: > In [Istio-and-Kiali-on-Openshift|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/] Pipeline in a step "Install Istio" it installs bookinfo app. But when It does not reinstall Istio, bookinfo will remain the old installed. We need clean installed Bookinfo for test purposes. > The [Istio-Features-Bookinfo|http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-Features-Bookinfo/] job is a separate job which installs bookinfo only. > TODO: > Make sure that Istio-Features-Bookinfo job have an option to "Clean" and "Clean/Reinstall Bookinfo", which means that all Istio related objets are deleted from Bookinfo and Bookinfo is reinstalled. > Make sure that the above job is included in Istio-and-Kiali-on-Openshift pipeline with optional param to activate. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-133) Configure passwordless ssh access from jenkins slaves

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-133?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-133: -------------------------------- Description: I would be nice to be able to use password-less ssh between all our machines. We need to install ssh keys everywhere. > Configure passwordless ssh access from jenkins slaves > ----------------------------------------------------- > > Key: SWSQE-133 > URL: https://issues.jboss.org/browse/SWSQE-133 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > I would be nice to be able to use password-less ssh between all our machines. We need to install ssh keys everywhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-69) Investigate RH-SSO continuous productization

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-69?page=com.atlassian.jira.plugin.s... ] Filip Brychta resolved SWSQE-69. -------------------------------- Resolution: Done > Investigate RH-SSO continuous productization > -------------------------------------------- > > Key: SWSQE-69 > URL: https://issues.jboss.org/browse/SWSQE-69 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > From meastman: > Whatever we come up with needs to be compatible or we at least know why we have to be > different. > From theute: > FYI, this describes the RH-SSO continuous productization: https://docs.engineering.redhat.com/display/JP/Design+document+RH-SSO+con... > RH-SSO is the guinea pig but we'll want to pick from their experience and tools to also get to a point where possibly each PR merge gets productized (means fully automated) and that would include testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018