September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1291) IronJacamar 1.2.6.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1291?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1291. ------------------------------------ Resolution: Done > IronJacamar 1.2.6.Final > ----------------------- > > Key: JBJCA-1291 > URL: https://issues.jboss.org/browse/JBJCA-1291 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.6.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1291) IronJacamar 1.2.6.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1291: -------------------------------------- Summary: IronJacamar 1.2.6.Final Key: JBJCA-1291 URL: https://issues.jboss.org/browse/JBJCA-1291 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.2.6.Final Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1269) rar-info: Exceptions during scan

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1269?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1269: ----------------------------------- Fix Version/s: 1.2.7.Final (was: 1.2.6.Final) > rar-info: Exceptions during scan > -------------------------------- > > Key: JBJCA-1269 > URL: https://issues.jboss.org/browse/JBJCA-1269 > Project: IronJacamar > Issue Type: Task > Components: AS > Reporter: Jesper Pedersen > Assignee: Johnathon Lee > Fix For: 1.2.7.Final > > > The rar-info tool may display exceptions during its scan for certain conditions > {noformat} > t.printStackTrace(System.err); > {noformat} > These stack traces should in addition be appended to a <rar-file>-exceptions.txt file for easier attachment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1285) rar-info: CCI interface information missing

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1285?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1285: ----------------------------------- Fix Version/s: 1.2.7.Final (was: 1.2.6.Final) > rar-info: CCI interface information missing > ------------------------------------------- > > Key: JBJCA-1285 > URL: https://issues.jboss.org/browse/JBJCA-1285 > Project: IronJacamar > Issue Type: Bug > Components: AS > Reporter: Jesper Pedersen > Assignee: Johnathon Lee > Fix For: 1.2.7.Final > > > If a resource adapter is using CCI then the ConnectionFactory and Connection information isn't included in the report. > The information should be based directly on the actual interface classes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1954) SWIFT_PING discovery protocol fatal error on OpenStack Kilo

by Thomas Segismont (JIRA)

[ https://issues.jboss.org/browse/JGRP-1954?page=com.atlassian.jira.plugin.... ] Thomas Segismont commented on JGRP-1954: ---------------------------------------- [~belaban] No I'm not against it. > SWIFT_PING discovery protocol fatal error on OpenStack Kilo > ----------------------------------------------------------- > > Key: JGRP-1954 > URL: https://issues.jboss.org/browse/JGRP-1954 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Environment: JGroups client running on Mac OS X - Yosemite > JDK 1.7.71 > OpenStack Kilo > Reporter: Nick Sawadsky > Assignee: Bela Ban > Fix For: 3.6.5 > > > I'm attempting to use the SWIFT_PING discovery protocol on the most recent version of OpenStack, "Kilo". An error occurs during initialization of the protocol stack, the stack trace is provided below. > The problem appears to be that support for XML-formatted responses has been removed in the OpenStack Identity API (http://developer.openstack.org/api-ref-identity-v2.html). Even though SWIFT_PING sends an Accept header of application/xml, the response still comes back as JSON (around line 286 of SWIFT_PING.java). > I've been able to repro the issue using Postman in Chrome. I tried providing the *request* in XML , with a Content-Type header of application/xml, but Swift returns an error: "Expecting to find application/json in Content-Type header". > It seems like the resolution would be for SWIFT_PING to be modified so it can parse the JSON response that it is receiving. If that sounds like a reasonable approach, I can try to create a patch that fixes the issue. > Stack Trace: > 2015-08-21 14:30:16,123 FATAL [com.pingidentity.common.util.ErrorHandler] Problem creating factory for multiplexed cluster communications > org.xml.sax.SAXParseException: Content is not allowed in prolog. > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) ~[?:1.8.0_25] > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348) ~[?:1.8.0_25] > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) ~[?:1.8.0_25] > at org.jgroups.protocols.SWIFT_PING$Keystone_V_2_0_Auth.authenticate(SWIFT_PING.java:307) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING$SwiftClient.authenticate(SWIFT_PING.java:443) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING.init(SWIFT_PING.java:68) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.init(JChannel.java:854) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:159) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:120) ~[jgroups.jar:3.6.4.Final] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-3248: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3248: --------------------------------- Fix Version/s: (was: 10.0.0.CR1) > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3248: --------------------------------- Priority: Minor (was: Major) > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-818) Listeners declared in kmodule.xml are not registered in StatelessKieSession

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-818?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-818: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1233197|https://bugzilla.redhat.com/show_bug.cgi?id=1233197] from ON_QA to VERIFIED > Listeners declared in kmodule.xml are not registered in StatelessKieSession > --------------------------------------------------------------------------- > > Key: DROOLS-818 > URL: https://issues.jboss.org/browse/DROOLS-818 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.Beta2 > > > Listener declared in kmodule.xml as in the following snippet of XML works on stateful KieSession, but are not registered on stateless ones. > {code} > <ksession name="statelessKieSession1" type="stateless"> > <listeners> > <ruleRuntimeEventListener type="com.esrx.ref.testproject.TestRuleRuntimeEventListener"/> > </listeners> > </ksession> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1954) SWIFT_PING discovery protocol fatal error on OpenStack Kilo

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1954?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1954: -------------------------------- Hi Nick, Java 6 is absolutely *not* a requirement as 3.6.5 is already on Java 7 as base line. If you think the cleaner approach is to move SWIFT_PING into its own separate project, that's a valid choice, too. But Thomas kind of seemed against it, or did I only imply this Thomas ? > SWIFT_PING discovery protocol fatal error on OpenStack Kilo > ----------------------------------------------------------- > > Key: JGRP-1954 > URL: https://issues.jboss.org/browse/JGRP-1954 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Environment: JGroups client running on Mac OS X - Yosemite > JDK 1.7.71 > OpenStack Kilo > Reporter: Nick Sawadsky > Assignee: Bela Ban > Fix For: 3.6.5 > > > I'm attempting to use the SWIFT_PING discovery protocol on the most recent version of OpenStack, "Kilo". An error occurs during initialization of the protocol stack, the stack trace is provided below. > The problem appears to be that support for XML-formatted responses has been removed in the OpenStack Identity API (http://developer.openstack.org/api-ref-identity-v2.html). Even though SWIFT_PING sends an Accept header of application/xml, the response still comes back as JSON (around line 286 of SWIFT_PING.java). > I've been able to repro the issue using Postman in Chrome. I tried providing the *request* in XML , with a Content-Type header of application/xml, but Swift returns an error: "Expecting to find application/json in Content-Type header". > It seems like the resolution would be for SWIFT_PING to be modified so it can parse the JSON response that it is receiving. If that sounds like a reasonable approach, I can try to create a patch that fixes the issue. > Stack Trace: > 2015-08-21 14:30:16,123 FATAL [com.pingidentity.common.util.ErrorHandler] Problem creating factory for multiplexed cluster communications > org.xml.sax.SAXParseException: Content is not allowed in prolog. > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) ~[?:1.8.0_25] > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348) ~[?:1.8.0_25] > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) ~[?:1.8.0_25] > at org.jgroups.protocols.SWIFT_PING$Keystone_V_2_0_Auth.authenticate(SWIFT_PING.java:307) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING$SwiftClient.authenticate(SWIFT_PING.java:443) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING.init(SWIFT_PING.java:68) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.init(JChannel.java:854) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:159) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:120) ~[jgroups.jar:3.6.4.Final] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 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 September 2015