September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-78) Intermittent failures in RespawnTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-78?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration updated WFLY-78: ---------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012809 > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: WFLY-78 > URL: https://issues.jboss.org/browse/WFLY-78 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2261) Allow application exceptions to be defined when using the throws clause.

by Carlo de Wolf (JIRA)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2261) Allow application exceptions to be defined when using the throws clause.

by Carlo de Wolf (JIRA)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1707) MergeView: marshalling fails when subgroups are not a subset of members

by Bela Ban (JIRA)

Bela Ban created JGRP-1707: ------------------------------ Summary: MergeView: marshalling fails when subgroups are not a subset of members Key: JGRP-1707 URL: https://issues.jboss.org/browse/JGRP-1707 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.4 When we have 2 partitions \{A,B,C\} and \{X,Y,Z\} and they merge, but one of the members (e.g. Z) is excluded from the merge (e.g. because it is involved in a different merge already), we create the following MergeView: {noformat} MergeView: view={A,B,C,X,Y} subgroups={A,B,C} {X,Y,Z} {noformat} Because the members of the subgroups refer to the merge view via index, the index for Z is -1, and thus - when unmarshalled - Z points to a null creator, which triggers the following stack trace: {noformat} 00631037-49819: failed handling incoming message java.lang.IllegalArgumentException: creator cannot be null at org.jgroups.ViewId.<init>(ViewId.java:32) at org.jgroups.ViewId.<init>(ViewId.java:42) at org.jgroups.View.create(View.java:90) at org.jgroups.MergeView.readFrom(MergeView.java:119) at org.jgroups.protocols.pbcast.GMS$GmsHeader.readFrom(GMS.java:1285) at org.jgroups.Message.readHeader(Message.java:889) at org.jgroups.Message.readFrom(Message.java:803) at org.jgroups.protocols.TP.readMessageBatch(TP.java:1796) at org.jgroups.protocols.TP.receive(TP.java:1463) at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:683) at java.lang.Thread.run(Unknown Source) {noformat} SOLUTION: * When marshalling a MergeView, and a subgroup member has no corresponding member in {{members}}, then send the *address* instead of the index * OR: remove all members from subgroups which are not in {{members}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1706) Build process: publish artifact to Nexus via ant+ivy

by Bela Ban (JIRA)

Bela Ban created JGRP-1706: ------------------------------ Summary: Build process: publish artifact to Nexus via ant+ivy Key: JGRP-1706 URL: https://issues.jboss.org/browse/JGRP-1706 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Optional Fix For: 3.5 Add publish and publish-local tasks to build.xml to publish the artifacts (JAR, soirce-JAR and readme) to Nexus or the local repo. Linke by Sanne: http://books.sonatype.com/nexus-book/reference/staging-sect-deployment.ht... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2170) Intermittent failure in ReloadWSDLPublisherTestCase

by Joe Wertz (JIRA)

Joe Wertz created WFLY-2170: ------------------------------- Summary: Intermittent failure in ReloadWSDLPublisherTestCase Key: WFLY-2170 URL: https://issues.jboss.org/browse/WFLY-2170 Project: WildFly Issue Type: Bug Affects Versions: 8.0.0.Alpha4 Reporter: Joe Wertz Assignee: Joe Wertz Priority: Minor Fix For: 8.0.0.Beta1 Intermittent failure reconnecting to the server after it is restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2168) Forward port urn:jboss:domain:transactions:1.4 schema and parser from EAP 6

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2168?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-2168: ------------------------------------- A new XSD had been firstly introduced in WildFly by WFLY-789 as a {{urn:jboss:domain:transactions:2.0}} which was then backported to EAP as a {{urn:jboss:domain:transactions:1.4}}. The change was the same, the only difference was in the version of that schema. See the discussion on the WildFly's PR for details. > Forward port urn:jboss:domain:transactions:1.4 schema and parser from EAP 6 > --------------------------------------------------------------------------- > > Key: WFLY-2168 > URL: https://issues.jboss.org/browse/WFLY-2168 > Project: WildFly > Issue Type: Task > Components: Domain Management, Transactions > Reporter: Brian Stansberry > Assignee: Ivo Studensky > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The backport of WFLY-789 introduced a new XSD version in EAP that does not exist in WildFly. It needs to be forward ported to WildFly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1776) resource-adapter id attribute is forced to match rar name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1776?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1776: ----------------------------------------------- Vladimir Rastseluev <vrastsel(a)redhat.com> changed the Status of [bug 996971|https://bugzilla.redhat.com/show_bug.cgi?id=996971] from ON_QA to VERIFIED > resource-adapter id attribute is forced to match rar name > --------------------------------------------------------- > > Key: WFLY-1776 > URL: https://issues.jboss.org/browse/WFLY-1776 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Alpha3 > Reporter: Johnathon Lee > Assignee: Stefano Maestri > Attachments: JBJCA-1066-reproducer.zip > > > If the id of the resource adapter element does not match the name of the > RAR file, the CLI will throw the following error on RA activation: > { > "outcome" => "failed", > "failure-description" => "rar not yet deployed", > "rolled-back" => true > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1776) resource-adapter id attribute is forced to match rar name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1776?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1776: ----------------------------------------------- Vladimir Rastseluev <vrastsel(a)redhat.com> made a comment on [bug 996971|https://bugzilla.redhat.com/show_bug.cgi?id=996971] Verified on EAP 6.2.0 ER3 > resource-adapter id attribute is forced to match rar name > --------------------------------------------------------- > > Key: WFLY-1776 > URL: https://issues.jboss.org/browse/WFLY-1776 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Alpha3 > Reporter: Johnathon Lee > Assignee: Stefano Maestri > Attachments: JBJCA-1066-reproducer.zip > > > If the id of the resource adapter element does not match the name of the > RAR file, the CLI will throw the following error on RA activation: > { > "outcome" => "failed", > "failure-description" => "rar not yet deployed", > "rolled-back" => true > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1916) Deployer role within domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1916?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1916: ----------------------------------------------- Heiko Braun <hbraun(a)redhat.com> made a comment on [bug 1012592|https://bugzilla.redhat.com/show_bug.cgi?id=1012592] Why do you think it's the opposite of WFLY-1916? > Deployer role within domain > --------------------------- > > Key: WFLY-1916 > URL: https://issues.jboss.org/browse/WFLY-1916 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.Beta1 > > > There seems to be a problem with the deplyer role within the domain. In order to operate on doamin deployments, the deplyer requires write access to: > a) /server-group=* > b) /deployment=* > But currently only the later seems to be given. This basically reduces the deployer role to just the abillity to upload contents, but not assign them to server-groups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 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 2013