May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4576: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1217754 > JCE jar file inside a deployment fails the signature check > ------------------------------------------------------------ > > Key: WFLY-4576 > URL: https://issues.jboss.org/browse/WFLY-4576 > Project: WildFly > Issue Type: Bug > Components: VFS > Affects Versions: 9.0.0.Beta2 > Environment: Wildfly build from master on April 22, 2015 > Reporter: Tom Fonteyne > Assignee: Tomaz Cerar > Attachments: bouncycastle.zip > > > deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin.... ] Tom Fonteyne updated WFLY-4576: ------------------------------- Attachment: bouncycastle.zip > JCE jar file inside a deployment fails the signature check > ------------------------------------------------------------ > > Key: WFLY-4576 > URL: https://issues.jboss.org/browse/WFLY-4576 > Project: WildFly > Issue Type: Bug > Components: VFS > Affects Versions: 9.0.0.Beta2 > Environment: Wildfly build from master on April 22, 2015 > Reporter: Tom Fonteyne > Assignee: Tomaz Cerar > Attachments: bouncycastle.zip > > > deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-4576: ---------------------------------- Summary: JCE jar file inside a deployment fails the signature check Key: WFLY-4576 URL: https://issues.jboss.org/browse/WFLY-4576 Project: WildFly Issue Type: Bug Components: VFS Affects Versions: 9.0.0.Beta2 Environment: Wildfly build from master on April 22, 2015 Reporter: Tom Fonteyne Assignee: Tomaz Cerar deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861

by Tom Ross (JIRA)

[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ] Tom Ross closed WFLY-1391. -------------------------- Resolution: Duplicate Issue Fix in JBossTM code. > ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > ------------------------------------------------------------------------------------------- > > Key: WFLY-1391 > URL: https://issues.jboss.org/browse/WFLY-1391 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha1 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Jason Greene > > The expression value for node identifier is not being evaluated correctly. Setting it to: > {noformat} > /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}") > {noformat} > where jboss.tx.node.id is supplied on command line as > -Djboss.tx.node.id=111 > results in warning at start-up > {noformat} > 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861

by Tom Ross (JIRA)

[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ] Tom Ross commented on WFLY-1391: -------------------------------- Closing this issue since it has been fix in TM code. > ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > ------------------------------------------------------------------------------------------- > > Key: WFLY-1391 > URL: https://issues.jboss.org/browse/WFLY-1391 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha1 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Jason Greene > > The expression value for node identifier is not being evaluated correctly. Setting it to: > {noformat} > /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}") > {noformat} > where jboss.tx.node.id is supplied on command line as > -Djboss.tx.node.id=111 > results in warning at start-up > {noformat} > 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861

by Tom Ross (JIRA)

[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ] Tom Ross commented on WFLY-1391: -------------------------------- This is the fix for this issue. > ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > ------------------------------------------------------------------------------------------- > > Key: WFLY-1391 > URL: https://issues.jboss.org/browse/WFLY-1391 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha1 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Jason Greene > > The expression value for node identifier is not being evaluated correctly. Setting it to: > {noformat} > /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}") > {noformat} > where jboss.tx.node.id is supplied on command line as > -Djboss.tx.node.id=111 > results in warning at start-up > {noformat} > 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861

by Tom Ross (JIRA)

[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ] Tom Ross commented on WFLY-1391: -------------------------------- This has been fixed in JBTM-1341 > ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > ------------------------------------------------------------------------------------------- > > Key: WFLY-1391 > URL: https://issues.jboss.org/browse/WFLY-1391 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha1 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Jason Greene > > The expression value for node identifier is not being evaluated correctly. Setting it to: > {noformat} > /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}") > {noformat} > where jboss.tx.node.id is supplied on command line as > -Djboss.tx.node.id=111 > results in warning at start-up > {noformat} > 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4574) Upgrade Mojarra to 2.2.11

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4574?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-4574: ----------------------------- Fix Version/s: (was: 9.0.0.CR1) > Upgrade Mojarra to 2.2.11 > ------------------------- > > Key: WFLY-4574 > URL: https://issues.jboss.org/browse/WFLY-4574 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Cody Lerum > Assignee: Farah Juma > > Mojarra 2.2 now appears to be on a 4-6 month release cycle for 2.2.x and 2.2.11 is due for release on May 5th. https://java.net/jira/browse/JAVASERVERFACES/fixforversion/17193/?selecte... > It would be great if we could get this updated before 9.1.0.Final. > https://java.net/jira/browse/JAVASERVERFACES-3848 for example would be nice to pick up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1264) NullPointerException hides cause of PostgreSql Exception for getConnection call.

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1264?page=com.atlassian.jira.plugin... ] Jesper Pedersen closed JBJCA-1264. ---------------------------------- Fix Version/s: (was: 1.0.32.Final) Resolution: Duplicate Issue JBJCA-1257 > NullPointerException hides cause of PostgreSql Exception for getConnection call. > -------------------------------------------------------------------------------- > > Key: JBJCA-1264 > URL: https://issues.jboss.org/browse/JBJCA-1264 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.30.Final > Environment: All environments. > Reporter: Jeremy Whiting > Assignee: Jesper Pedersen > Labels: nullPointerException, pgsqlexception > > When a datasource using PostgreSql is configured with the "loglevel" property the JCA db server causes a PGSqlException. Besides that cause the exception is not displayed to the user. > org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. > The JCA code attempts to handle the exception in a catch block. Initially by logging a message. But the JCA code to log the message assumes the clw reference is not null. On this line > https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.30.Final/... > In my case clw is null. Which then causes an NullPointerException. Completely hiding the underlying exception to the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1264) NullPointerException hides cause of PostgreSql Exception for getConnection call.

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1264?page=com.atlassian.jira.plugin... ] Jesper Pedersen reopened JBJCA-1264: ------------------------------------ > NullPointerException hides cause of PostgreSql Exception for getConnection call. > -------------------------------------------------------------------------------- > > Key: JBJCA-1264 > URL: https://issues.jboss.org/browse/JBJCA-1264 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.30.Final > Environment: All environments. > Reporter: Jeremy Whiting > Assignee: Jesper Pedersen > Labels: nullPointerException, pgsqlexception > Fix For: 1.0.32.Final > > > When a datasource using PostgreSql is configured with the "loglevel" property the JCA db server causes a PGSqlException. Besides that cause the exception is not displayed to the user. > org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. > The JCA code attempts to handle the exception in a catch block. Initially by logging a message. But the JCA code to log the message assumes the clw reference is not null. On this line > https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.30.Final/... > In my case clw is null. Which then causes an NullPointerException. Completely hiding the underlying exception to the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 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 2015