November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-962) Kie-CI integration with Applications using Guava

by Marek Winkler (JIRA)

[ https://issues.jboss.org/browse/DROOLS-962?page=com.atlassian.jira.plugin... ] Marek Winkler commented on DROOLS-962: -------------------------------------- Please be aware that JBPM-4798 has recently been filed for this issue. > Kie-CI integration with Applications using Guava > ------------------------------------------------ > > Key: DROOLS-962 > URL: https://issues.jboss.org/browse/DROOLS-962 > Project: Drools > Issue Type: Bug > Components: core engine, tools > Affects Versions: 6.2.0.Final > Environment: Drools WB - 6.2.0.Final > Tomcat 7/8 > Reporter: Jebuselwyn Martin > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > > Unable to start application with the 'kie-ci' dependency due to the older version of Guava transitively pulled from maven libraries. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class com.google.inject.internal.Annotations$AnnotationChecker > at com.google.inject.internal.Annotations$AnnotationChecker.<init>(Annotations.java:104) > at com.google.inject.internal.Annotations.<clinit>(Annotations.java:122) > at com.google.inject.Key.ensureRetainedAtRuntime(Key.java:362) > at com.google.inject.Key.strategyFor(Key.java:354) > at com.google.inject.Key.get(Key.java:222) > at org.eclipse.sisu.wire.ParameterKeys.<clinit>(ParameterKeys.java:28) > at org.eclipse.sisu.wire.DependencyAnalyzer.<init>(DependencyAnalyzer.java:92) > at org.eclipse.sisu.wire.ElementAnalyzer.<init>(ElementAnalyzer.java:87) > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:74) > at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:229) > at com.google.inject.spi.Elements.getElements(Elements.java:103) > at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) > at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) > at com.google.inject.Guice.createInjector(Guice.java:94) > at com.google.inject.Guice.createInjector(Guice.java:71) > at com.google.inject.Guice.createInjector(Guice.java:61) > More details here: > https://groups.google.com/forum/#!topic/drools-setup/Mq6dW_fhQ9I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications

by Priyanka Nag (JIRA)

[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ] Priyanka Nag updated WFLY-334: ------------------------------ Description: HASingleton deployer should be provided in standalone and domain mode. To be able to migrate such singleton applications from former AS versions. was: colored textA HASingleton deployer should be provided in standalone and domain mode. To be able to migrate such singleton applications from former AS versions. > HA Singleton deployer for applications > -------------------------------------- > > Key: WFLY-334 > URL: https://issues.jboss.org/browse/WFLY-334 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 10.0.0.Beta1 > > > HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications

by Priyanka Nag (JIRA)

[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ] Priyanka Nag updated WFLY-334: ------------------------------ Description: colored textA HASingleton deployer should be provided in standalone and domain mode. To be able to migrate such singleton applications from former AS versions. was: A HASingleton deployer should be provided in standalone and domain mode. To be able to migrate such singleton applications from former AS versions. > HA Singleton deployer for applications > -------------------------------------- > > Key: WFLY-334 > URL: https://issues.jboss.org/browse/WFLY-334 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 10.0.0.Beta1 > > > colored textA HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5521) Tests from IIOP module fails with security manager

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-5521?page=com.atlassian.jira.plugin.... ] Ivo Studensky reassigned WFLY-5521: ----------------------------------- Assignee: Ivo Studensky (was: Ondrej Kotek) > Tests from IIOP module fails with security manager > -------------------------------------------------- > > Key: WFLY-5521 > URL: https://issues.jboss.org/browse/WFLY-5521 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Ivo Studensky > Attachments: IIOP.tests.txt > > > *Description of problem:* > Tests from IIOP module fails with security manager. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.IIOP -Dts.noSmoke > *Actual results:* > See attached file > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3554) ejb-jar.xml interceptor-binding does not accept "*"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3554?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3554: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1114061|https://bugzilla.redhat.com/show_bug.cgi?id=1114061] from NEW to CLOSED > ejb-jar.xml interceptor-binding does not accept "*" > --------------------------------------------------- > > Key: WFLY-3554 > URL: https://issues.jboss.org/browse/WFLY-3554 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.1.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Bartosz Baranowski > Fix For: 8.2.0.Final, 9.0.0.Alpha1 > > > From the ejb3.1 specification (JSR 318) chapter 12.7 Specification of Interceptors in the Deployment Descriptor: > "" > In the interceptor-binding element, the target-name element must be the name of one of > the enterprise beans contained in the ejb-jar or the wildcard value “*”. > "" > But the "*" as ejb-name is ignored, only a bean name will result in binding the interceptor during deployment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5450) Update to Hibernate ORM 5.0.5.Final

by Martin Kamp Jensen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5450?page=com.atlassian.jira.plugin.... ] Martin Kamp Jensen commented on WFLY-5450: ------------------------------------------ I'm curious. Is there any kind of collaboration going on with the Hibernate guys to focus on the bugs that prevent WildFly from including the latest Hibernate ORM bug-fix release? The next bug-fix release is currently scheduled for December 9: https://hibernate.atlassian.net/projects/HHH?selectedItem=com.atlassian.j... > Update to Hibernate ORM 5.0.5.Final > ----------------------------------- > > Key: WFLY-5450 > URL: https://issues.jboss.org/browse/WFLY-5450 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Martin Kamp Jensen > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Please, if possible, include the latest Hibernate Core bugfix release in the final version of WildFly 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5606) ManagementOnlyModeTestCase uses non-standard reload idioms

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5606?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5606: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900065 Bugzilla Update: Perform > ManagementOnlyModeTestCase uses non-standard reload idioms > ---------------------------------------------------------- > > Key: WFLY-5606 > URL: https://issues.jboss.org/browse/WFLY-5606 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 11.0.0.Alpha1 > > > ManagementOnlyModeTestCase was recently reenabled after being turned off for a long time. But it has intermittent failures[1] so I'm going to re-disable it. > Looking at it, it's doing some reloads but in a custom way. Custom reloads have been the source of tons of problems, so my assumption is this one is just another case of that and it needs to use the standard approach. > [1] http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WildFlyCore_... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5606) ManagementOnlyModeTestCase uses non-standard reload idioms

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5606?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5606: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 900065|https://bugzilla.redhat.com/show_bug.cgi?id=900065] from NEW to ASSIGNED > ManagementOnlyModeTestCase uses non-standard reload idioms > ---------------------------------------------------------- > > Key: WFLY-5606 > URL: https://issues.jboss.org/browse/WFLY-5606 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 11.0.0.Alpha1 > > > ManagementOnlyModeTestCase was recently reenabled after being turned off for a long time. But it has intermittent failures[1] so I'm going to re-disable it. > Looking at it, it's doing some reloads but in a custom way. Custom reloads have been the source of tons of problems, so my assumption is this one is just another case of that and it needs to use the standard approach. > [1] http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WildFlyCore_... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2217) Enable reload tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2217?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2217: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 900065|https://bugzilla.redhat.com/show_bug.cgi?id=900065] from NEW to ASSIGNED > Enable reload tests > ------------------- > > Key: WFLY-2217 > URL: https://issues.jboss.org/browse/WFLY-2217 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > > Tests need not stay ignored any longer! > Some tests which :reload are still ignored, even though :reload has been fixed ( well, it seems there is more to it due to other code changes ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1984) NPE while creating a dynamic FORK channel

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/JGRP-1984?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on JGRP-1984: ------------------------------------ I only tested on 3.6.4, have not tested with 3.6.7 > NPE while creating a dynamic FORK channel > ----------------------------------------- > > Key: JGRP-1984 > URL: https://issues.jboss.org/browse/JGRP-1984 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Reporter: Ramesh Reddy > Assignee: Bela Ban > Fix For: 3.6.7 > > Attachments: RpcForkDispatcherTest.java, tcp-shared.xml > > > I am trying to create a ForkChannel based on the example in docs with code, when FORK protocol not present in the main stack > {code} > channel=new JChannel("tcp.xml")); > channel.connect("RpcDispatcherTestGroup"); > ForkChannel forkChannel = new ForkChannel(channel, "test-rpc", name, true, ProtocolStack.BELOW, FRAG2.class); > forkChannel.connect("test-rpc"); > {code} > this ends with > {code} > Exception in thread "main" java.lang.NullPointerException > at org.jgroups.protocols.FORK.createForkStack(FORK.java:199) > at org.jgroups.fork.ForkChannel.<init>(ForkChannel.java:79) > at org.teiid.systemmodel.RpcDispatcherTest.start(RpcDispatcherTest.java:32) > at org.teiid.systemmodel.RpcDispatcherTest.main(RpcDispatcherTest.java:54 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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