April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1374) add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1374?page=com.atlassian.jira.plugin... ] Scott Marlow commented on JBJCA-1374: ------------------------------------- [http://www.ironjacamar.org/doc/userguide/1.2/en-US/pdf/IronJacamarUserGui...] > add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1374 > URL: https://issues.jboss.org/browse/JBJCA-1374 > Project: IronJacamar > Issue Type: Enhancement > Components: Core > Reporter: Scott Marlow > > In my internal testing with Hibernate, I hit a problem with IronJacamar throwing "javax.resource.ResourceException: IJ000459: Transaction is not active" error when called to get a database connection from pool from a thread that has an active transaction marked for rollback only. > The Hibernate jira is [https://hibernate.atlassian.net/browse/HHH-12472], which we are talking about changing. As well as WildFly jira [https://issues.jboss.org/browse/WFLY-10229] for a related bug. > Independent of the HHH-12472 + WFLY-10229 issues, I think it would be useful if there was a data source deployment option (in WildFly standalone*.xml) or system property, for disabling the IJ000459 check for rollback only transactions, as the IJ000459 check is not always expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-816) Support for masked passwords in client XML config

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-816?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-816: -------------------------------- [~dmlloyd] is the hashed-password-type already define somewhere? Is somewhere defined format for modular crypt for masked passwords, or should be created new? > Support for masked passwords in client XML config > ------------------------------------------------- > > Key: ELY-816 > URL: https://issues.jboss.org/browse/ELY-816 > Project: WildFly Elytron > Issue Type: Task > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Critical > Fix For: 1.3.0.CR1 > > > We need a way to support masked passwords in the auth configuration file, either as: > * A dedicated masked-password-type XML type > * Adding necessary fields to hashed-password-type > * Adding a modular crypt format > Needs to be supported anywhere passwords are allowed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1374) add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error

by Scott Marlow (JIRA)

Scott Marlow created JBJCA-1374: ----------------------------------- Summary: add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error Key: JBJCA-1374 URL: https://issues.jboss.org/browse/JBJCA-1374 Project: IronJacamar Issue Type: Enhancement Components: Core Reporter: Scott Marlow In my internal testing with Hibernate, I hit a problem with IronJacamar throwing "javax.resource.ResourceException: IJ000459: Transaction is not active" error when called to get a database connection from pool from a thread that has an active transaction marked for rollback only. The Hibernate jira is [https://hibernate.atlassian.net/browse/HHH-12472], which we are talking about changing. As well as WildFly jira [https://issues.jboss.org/browse/WFLY-10229] for a related bug. Independent of the HHH-12472 + WFLY-10229 issues, I think it would be useful if there was a data source deployment option (in WildFly standalone*.xml) or system property, for disabling the IJ000459 check for rollback only transactions, as the IJ000459 check is not always expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-159) Communicty Available Kiali Build - Latest and Greatest

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-159?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-159: ------------------------------------ Will not be building another Openshift cluster at this time, due to the blade resources needed. Instead, Kiali on b21 is available to explore latest-and-greatest. > Communicty Available Kiali Build - Latest and Greatest > ------------------------------------------------------ > > Key: SWSQE-159 > URL: https://issues.jboss.org/browse/SWSQE-159 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Development requests for making the latest Kiali version (aka: latest PR) available for community use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-159) Communicty Available Kiali Build - Latest and Greatest

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-159?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-159: ------------------------------- Sprint: (was: Kiali QE Sprint 4) > Communicty Available Kiali Build - Latest and Greatest > ------------------------------------------------------ > > Key: SWSQE-159 > URL: https://issues.jboss.org/browse/SWSQE-159 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Development requests for making the latest Kiali version (aka: latest PR) available for community use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and reject

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ] Romain Pelisse reopened WFLY-7085: ---------------------------------- Assignee: Romain Pelisse (was: Tomasz Adamski) > Server should verify EJB business methods during deployment and reject > ---------------------------------------------------------------------- > > Key: WFLY-7085 > URL: https://issues.jboss.org/browse/WFLY-7085 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Romain Pelisse > Labels: downstream_dependency > Fix For: 12.0.0.Beta1, 12.0.0.Final > > > The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static. > But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances. > To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2263) GRAVE: JGRP000225: failed unmarshalling buffer into return value

by rama rama (JIRA)

[ https://issues.jboss.org/browse/JGRP-2263?page=com.atlassian.jira.plugin.... ] rama rama commented on JGRP-2263: --------------------------------- i don't think it will work, the value of code its not assigned during serialization. even if I don't get the exception the obj.code will be null. > GRAVE: JGRP000225: failed unmarshalling buffer into return value > ---------------------------------------------------------------- > > Key: JGRP-2263 > URL: https://issues.jboss.org/browse/JGRP-2263 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.11 > Environment: jdk1.8.0_66.jdk > osx 10.10 & ubuntu 17.10 > Reporter: rama rama > Assignee: Bela Ban > Attachments: SimpleChat.java > > > trying to send a class that previous work with 3.x return > "failed unmarshalling buffer into return value" > jgroups instance it's configured with the default settings > i create a test case to reproduce it, executing this class on my 2 boxes return > ---- > GRAVE: JGRP000225: failed unmarshalling buffer into return value > java.lang.InstantiationException: com.eg.util.comm.SimpleChat$EError > at java.lang.Class.newInstance(Class.java:427) > at org.jgroups.util.Util.readException(Util.java:899) > at org.jgroups.util.Util.exceptionFromStream(Util.java:843) > at org.jgroups.util.Util.exceptionFromStream(Util.java:831) > at org.jgroups.util.Util.objectFromStream(Util.java:782) > at org.jgroups.util.Util.objectFromStream(Util.java:742) > at org.jgroups.blocks.RequestCorrelator.replyFromBuffer(RequestCorrelator.java:463) > at org.jgroups.blocks.RequestCorrelator.handleResponse(RequestCorrelator.java:408) > at org.jgroups.blocks.RequestCorrelator.dispatch(RequestCorrelator.java:363) > at org.jgroups.blocks.RequestCorrelator.receiveMessageBatch(RequestCorrelator.java:326) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:589) > at org.jgroups.JChannel.up(JChannel.java:837) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:896) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.RSVP.up(RSVP.java:233) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:196) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:293) > at org.jgroups.protocols.UNICAST3.deliverBatch(UNICAST3.java:1024) > at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:833) > at org.jgroups.protocols.UNICAST3.handleBatchFromSelf(UNICAST3.java:520) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:435) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:697) > at org.jgroups.protocols.BARRIER.up(BARRIER.java:195) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:212) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.TP.passBatchUp(TP.java:1274) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.passBatchUp(MaxOneThreadPerSender.java:284) > at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.run(MaxOneThreadPerSender.java:273) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoSuchMethodException: com.eg.util.comm.SimpleChat$EError.<init>() > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.newInstance(Class.java:412) > ... 37 more > ----- -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10286) Consider to add secmgr options to CLI and JDR

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10286?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10286: ----------------------------------------- Whatever is done should be aligned with the overall approach decided upon for https://issues.jboss.org/browse/WFLY-10242. > Consider to add secmgr options to CLI and JDR > --------------------------------------------- > > Key: WFLY-10286 > URL: https://issues.jboss.org/browse/WFLY-10286 > Project: WildFly > Issue Type: Bug > Components: CLI, Scripts > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > > Wildfly standalone/domain/appclient scripts allows two ways for start EAP with security manager: > * -secmgr command line argument ({{./standalone.sh -secmgr}}) > ** This is described in documentation only in Configuration guide in "A.1. Server Runtime Arguments" > * SECMGR=true env property > ** This is not described in documentation at all. > Does it make sence to add secmgr parameter to CLI script? CLI allows to start embedded server, and standalone.sh (non-embedded server) script has the secmgr option. Does it make sence to add secmgr parameter to the jdr script too? JDR tool uses embedded cli server too in some cases. > Cc: [~eduda], [~mnovak]) > See [this my command|https://issues.jboss.org/browse/WFLY-10242?focusedCommentId=13561...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10288) Remove ee8.preview.mode support

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10288?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10288: ------------------------------------ Description: Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property. The following modules will need to be updated: * {{javax.enterprise.api}} * {{javax.validation.api}} * {{javax.json.bind.api}} * {{javax.json.api}} * {{javax.annotation.api}} * {{javax.servlet.api}} * {{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed) * {{org.eclipse.yasson}} * {{org.glassfish.javax.json}} * {{javax.persistence.api}} * {{javax.ws.rs.api}} * {{javax.faces.api}} * {{javax.mail.api}} * {{javax.xml.bind.api}} * {{org.wildfly.cdi-api-bridge}} * {{org.jboss.resteasy.resteasy-json-binding-provider}} * {{org.jboss.resteasy.resteasy-jaxrs}} * {{org.hibernate.validator}} * {{org.hibernate.validator.cdi}} * {{com.sun.jsf-impl}} The following configuration needs to be removed: * {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}} The following source files should be updated: * {{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}} * {{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}} Any solution for WFLY-10289 should be reverted. The following documentation needs to be updated: * {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}} was: Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property. The following modules will need to be updated: * {{javax.enterprise.api}} * {{javax.validation.api}} * {{javax.json.bind.api}} * {{javax.json.api}} * {{javax.annotation.api}} * {{javax.servlet.api}} * {{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed) * {{org.eclipse.yasson}} * {{org.glassfish.javax.json}} * {{javax.persistence.api}} * {{javax.ws.rs.api}} * {{javax.faces.api}} * {{javax.mail.api}} * {{javax.xml.bind.api}} * {{org.wildfly.cdi-api-bridge}} * {{org.jboss.resteasy.resteasy-json-binding-provider}} * {{org.jboss.resteasy.resteasy-jaxrs}} * {{org.hibernate.validator}} * {{org.hibernate.validator.cdi}} * {{com.sun.jsf-impl}} The following configuration needs to be removed: * {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}} The following source files should be updated: * {{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}} * {{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}} The following documentation needs to be updated: * {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}} > Remove ee8.preview.mode support > ------------------------------- > > Key: WFLY-10288 > URL: https://issues.jboss.org/browse/WFLY-10288 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: James Perkins > > Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property. > The following modules will need to be updated: > * {{javax.enterprise.api}} > * {{javax.validation.api}} > * {{javax.json.bind.api}} > * {{javax.json.api}} > * {{javax.annotation.api}} > * {{javax.servlet.api}} > * {{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed) > * {{org.eclipse.yasson}} > * {{org.glassfish.javax.json}} > * {{javax.persistence.api}} > * {{javax.ws.rs.api}} > * {{javax.faces.api}} > * {{javax.mail.api}} > * {{javax.xml.bind.api}} > * {{org.wildfly.cdi-api-bridge}} > * {{org.jboss.resteasy.resteasy-json-binding-provider}} > * {{org.jboss.resteasy.resteasy-jaxrs}} > * {{org.hibernate.validator}} > * {{org.hibernate.validator.cdi}} > * {{com.sun.jsf-impl}} > The following configuration needs to be removed: > * {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}} > The following source files should be updated: > * {{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}} > * {{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}} > Any solution for WFLY-10289 should be reverted. > The following documentation needs to be updated: > * {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10289) Log something at INFO to reflect the ee8.preview.mode setting

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10289: --------------------------------------- Summary: Log something at INFO to reflect the ee8.preview.mode setting Key: WFLY-10289 URL: https://issues.jboss.org/browse/WFLY-10289 Project: WildFly Issue Type: Enhancement Components: EE Reporter: Brian Stansberry Assignee: Brian Stansberry When users set (or don't set) ee8.preview.mode the effect thereof is very obscure. So we should log something, just to make it a bit clearer that the setting has been noticed. I think the EE subsystem seems like a reasonable place to add this. Subsystem root add handler. WFLY-10288 is the JIRA for cleaning out ee8.preview.mode behavior so I'll add reverting any change for this to the task list there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 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 April 2018