February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1907) ENCRYPT: asymmetric encryption fails on merge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1907?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1907: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1187193|https://bugzilla.redhat.com/show_bug.cgi?id=1187193] from NEW to ASSIGNED > ENCRYPT: asymmetric encryption fails on merge > --------------------------------------------- > > Key: JGRP-1907 > URL: https://issues.jboss.org/browse/JGRP-1907 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.2 > > Attachments: encrypt.xml, EncryptKeyStore.xml > > > {{ENCRYPT}} fails to communicate after a network split and subsequent merge with asymmetric encryption. This works with symmetric encryption. > To reproduce: > * Members A and B > * Add {{<DISCARD use_gui="true"/>}} on top of {{UDP}} > * Form cluster {{(A,B)}} > * Create a network split: {{(A)}} and {{(B)}} > * Remove the network split > * Observe that with both symmetric and asymmetric encryption, the merge forms cluster {{(A,B)}} > * However, with asymmetric encryption, {{ENCRYPT}} fails to process any messages and rejects all messages, whereas with symmetric encryption, this works. > * Symmetric encryption: {{EncryptKeyStore.xml}} > * Asymmetric encryption: {{encrypt.xml}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4386) EJB annotations ignored if classes are packaged as JBOSS modules

by Tihomir Meščić (JIRA)

[ https://issues.jboss.org/browse/WFLY-4386?page=com.atlassian.jira.plugin.... ] Tihomir Meščić updated WFLY-4386: --------------------------------- Description: I have an EJB that writes something to the DB and I have a custom checked exception that is marked as @javax.ejb.ApplicationException(rollback=true), which means that when the exception is thrown, transaction should be rollbacked. {code:title=Test.java.java|borderStyle=solid} @ApplicationException(rollback=true) public class MyException extends Exception { {code} This exception is packaged in a separate JAR. When this JAR is included in the lib/ folder of the EAR with my EJB, everything works as expected (when the EJB throws MyException, the transaction is rollbacked). However, when this JAR is deployed as a JBOSS module (so, in jboss_folder/modules/... folder), and the EAR declares a dependency on this module (MANIFEST.MF -> Dependencies: ....) , then the transaction is NOT rollbacked. So the EJB container ignores the annotation. One workaround (that I don't really like) is to specify that this is an application exception in the jboss-ejb3.xml (then, the transaction will be rollbacked). was: I have an EJB that writes something to the DB and I have a custom checked exception that is marked as @javax.ejb.ApplicationException(rollback=true), which means that when the exception is thrown, transaction should be rollbacked. {code:title=Test.java.java|borderStyle=solid} @ApplicationException(rollback=true) public class MyException extends Exception { {code} This exception is packaged in a separate JAR. When this JAR is included in the lib/ folder of the EAR with my EJB, everything works as expected (when the EJB throws MyException, the transaction is rollbacked). However, when this JAR is deployed as a JBOSS module (so, in ${jboss}/modules/... folder), and the EAR declares a dependency on this module (MANIFEST.MF -> Dependencies: ....) , then the transaction is NOT rollbacked. So the EJB container ignores the annotation. One workaround (that I don't really like) is to specify that this is an application exception in the jboss-ejb3.xml (then, the transaction will be rollbacked). > EJB annotations ignored if classes are packaged as JBOSS modules > ---------------------------------------------------------------- > > Key: WFLY-4386 > URL: https://issues.jboss.org/browse/WFLY-4386 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EJB > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: Tihomir Meščić > Assignee: David Lloyd > > I have an EJB that writes something to the DB and I have a custom checked exception that is marked as @javax.ejb.ApplicationException(rollback=true), which means that when the exception is thrown, transaction should be rollbacked. > {code:title=Test.java.java|borderStyle=solid} > @ApplicationException(rollback=true) > public class MyException extends Exception { > {code} > > This exception is packaged in a separate JAR. > > When this JAR is included in the lib/ folder of the EAR with my EJB, everything works as expected (when the EJB throws MyException, the transaction is rollbacked). > However, when this JAR is deployed as a JBOSS module (so, in jboss_folder/modules/... folder), and the EAR declares a dependency on this module (MANIFEST.MF -> Dependencies: ....) , then the transaction is NOT rollbacked. So the EJB container ignores the annotation. > > One workaround (that I don't really like) is to specify that this is an application exception in the jboss-ejb3.xml (then, the transaction will be rollbacked). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4386) EJB annotations ignored if classes are packaged as JBOSS modules

by Tihomir Meščić (JIRA)

Tihomir Meščić created WFLY-4386: ------------------------------------ Summary: EJB annotations ignored if classes are packaged as JBOSS modules Key: WFLY-4386 URL: https://issues.jboss.org/browse/WFLY-4386 Project: WildFly Issue Type: Bug Components: Class Loading, EJB Affects Versions: JBoss AS7 7.1.1.Final Reporter: Tihomir Meščić Assignee: David Lloyd I have an EJB that writes something to the DB and I have a custom checked exception that is marked as @javax.ejb.ApplicationException(rollback=true), which means that when the exception is thrown, transaction should be rollbacked. {code:title=Test.java.java|borderStyle=solid} @ApplicationException(rollback=true) public class MyException extends Exception { {code} This exception is packaged in a separate JAR. When this JAR is included in the lib/ folder of the EAR with my EJB, everything works as expected (when the EJB throws MyException, the transaction is rollbacked). However, when this JAR is deployed as a JBOSS module (so, in ${jboss}/modules/... folder), and the EAR declares a dependency on this module (MANIFEST.MF -> Dependencies: ....) , then the transaction is NOT rollbacked. So the EJB container ignores the annotation. One workaround (that I don't really like) is to specify that this is an application exception in the jboss-ejb3.xml (then, the transaction will be rollbacked). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1005) SemaphoreArrayListManagedConnectionPool should FIFO

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1005?page=com.atlassian.jira.plugin... ] Jesper Pedersen commented on JBJCA-1005: ---------------------------------------- Select the MinPoolSize decrementer strategy in <capacity>. Use the forum in the future for discussions. > SemaphoreArrayListManagedConnectionPool should FIFO > --------------------------------------------------- > > Key: JBJCA-1005 > URL: https://issues.jboss.org/browse/JBJCA-1005 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > > Currently behaving in FILO manner -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.

by Elis Edlund (JIRA)

[ https://issues.jboss.org/browse/JASSIST-244?page=com.atlassian.jira.plugi... ] Elis Edlund edited comment on JASSIST-244 at 2/25/15 8:23 AM: -------------------------------------------------------------- Noticed that the access scope of the Base class matters. If its changed to public it will actually work. but private and "package private" and protected it does not still. Anyhow I'm in a position were I can't change the Base class anyway so it's not a workaround for me. was (Author: elis.edlund): Noticed that the access scope of the Base class matters. If its changed to public it will actually work. but private and "package private" and protected it does not still. Anyhow I'm in a position were I can't change the class anyway so it's not a workaround for me. > ProxyFactory will not invoke MethodHandler on method declared in parent classes. > -------------------------------------------------------------------------------- > > Key: JASSIST-244 > URL: https://issues.jboss.org/browse/JASSIST-244 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA, 3.19.0-GA > Environment: Windows 7, Java 1.7 and 1.8 > Reporter: Elis Edlund > Assignee: Shigeru Chiba > Attachments: IssueMethodsInParentShouldCallTheMethodHandler.java > > > ProxyFactory factory = new ProxyFactory(); > factory.setSuperclass(Extended.class); > Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER); > Does not work as intended with version newer than 3.17.0-GA > invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.

by Elis Edlund (JIRA)

[ https://issues.jboss.org/browse/JASSIST-244?page=com.atlassian.jira.plugi... ] Elis Edlund commented on JASSIST-244: ------------------------------------- Noticed that the access scope of the Base class matters. If its changed to public it will actually work. but private and "package private" and protected it does not still. Anyhow I'm in a position where I can't change the class so its not a workaround for me. > ProxyFactory will not invoke MethodHandler on method declared in parent classes. > -------------------------------------------------------------------------------- > > Key: JASSIST-244 > URL: https://issues.jboss.org/browse/JASSIST-244 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA, 3.19.0-GA > Environment: Windows 7, Java 1.7 and 1.8 > Reporter: Elis Edlund > Assignee: Shigeru Chiba > Attachments: IssueMethodsInParentShouldCallTheMethodHandler.java > > > ProxyFactory factory = new ProxyFactory(); > factory.setSuperclass(Extended.class); > Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER); > Does not work as intended with version newer than 3.17.0-GA > invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.

by Elis Edlund (JIRA)

[ https://issues.jboss.org/browse/JASSIST-244?page=com.atlassian.jira.plugi... ] Elis Edlund edited comment on JASSIST-244 at 2/25/15 8:22 AM: -------------------------------------------------------------- Noticed that the access scope of the Base class matters. If its changed to public it will actually work. but private and "package private" and protected it does not still. Anyhow I'm in a position were I can't change the class anyway so it's not a workaround for me. was (Author: elis.edlund): Noticed that the access scope of the Base class matters. If its changed to public it will actually work. but private and "package private" and protected it does not still. Anyhow I'm in a position where I can't change the class so its not a workaround for me. > ProxyFactory will not invoke MethodHandler on method declared in parent classes. > -------------------------------------------------------------------------------- > > Key: JASSIST-244 > URL: https://issues.jboss.org/browse/JASSIST-244 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA, 3.19.0-GA > Environment: Windows 7, Java 1.7 and 1.8 > Reporter: Elis Edlund > Assignee: Shigeru Chiba > Attachments: IssueMethodsInParentShouldCallTheMethodHandler.java > > > ProxyFactory factory = new ProxyFactory(); > factory.setSuperclass(Extended.class); > Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER); > Does not work as intended with version newer than 3.17.0-GA > invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.

by Elis Edlund (JIRA)

[ https://issues.jboss.org/browse/JASSIST-244?page=com.atlassian.jira.plugi... ] Elis Edlund updated JASSIST-244: -------------------------------- Attachment: IssueMethodsInParentShouldCallTheMethodHandler.java small class to reproduce the problem. > ProxyFactory will not invoke MethodHandler on method declared in parent classes. > -------------------------------------------------------------------------------- > > Key: JASSIST-244 > URL: https://issues.jboss.org/browse/JASSIST-244 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA, 3.19.0-GA > Environment: Windows 7, Java 1.7 and 1.8 > Reporter: Elis Edlund > Assignee: Shigeru Chiba > Attachments: IssueMethodsInParentShouldCallTheMethodHandler.java > > > ProxyFactory factory = new ProxyFactory(); > factory.setSuperclass(Extended.class); > Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER); > Does not work as intended with version newer than 3.17.0-GA > invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.

by Elis Edlund (JIRA)

Elis Edlund created JASSIST-244: ----------------------------------- Summary: ProxyFactory will not invoke MethodHandler on method declared in parent classes. Key: JASSIST-244 URL: https://issues.jboss.org/browse/JASSIST-244 Project: Javassist Issue Type: Bug Affects Versions: 3.19.0-GA, 3.18.0-GA Environment: Windows 7, Java 1.7 and 1.8 Reporter: Elis Edlund Assignee: Shigeru Chiba ProxyFactory factory = new ProxyFactory(); factory.setSuperclass(Extended.class); Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER); Does not work as intended with version newer than 3.17.0-GA invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-159) Discovery of available algorithms for credential types

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-159?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-159: -------------------------------------- Validation API also has a similar concern, i.e. the realm should support validating the most specific type and some form of translations should be possible. > Discovery of available algorithms for credential types > ------------------------------------------------------ > > Key: ELY-159 > URL: https://issues.jboss.org/browse/ELY-159 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha1 > > > The overall purpose of the getCredentialSupport calls is so that we can discover information about the supported credentials as authentication mechanisms are offered - the algorithm for the digest is just as important as knowing the general type. > May just be a part of ELY-151 or may be something in addition. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 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 February 2015