January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-507) Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-507?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet updated WFCORE-507: ------------------------------------- Description: Always on IBM JDK org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: - java.net.ConnectException: Connection refused - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment was: org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: - java.net.ConnectException: Connection refused - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment Version-Release number of selected component (if applicable): EAP 6.4.0.ER1 How reproducible: Always on IBM JDK Steps to Reproduce: 1. ./build.sh -pl deployment-scanner -am -Dtest=FileSystemDeploymentServiceUnitTestCase -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -DfailIfNoTests=false Actual results: java.net.ConnectException: Connection refused java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment java.lang.reflect.InvocationTargetException Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK > -------------------------------------------------------------------- > > Key: WFCORE-507 > URL: https://issues.jboss.org/browse/WFCORE-507 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 1.0.0.Alpha15 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Trivial > > Always on IBM JDK org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: > - java.net.ConnectException: Connection refused > - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-507) Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-507: ---------------------------------------- Summary: Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK Key: WFCORE-507 URL: https://issues.jboss.org/browse/WFCORE-507 Project: WildFly Core Issue Type: Bug Components: Test Suite Affects Versions: 1.0.0.Alpha15 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Priority: Trivial Description of problem: org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: - java.net.ConnectException: Connection refused - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment Version-Release number of selected component (if applicable): EAP 6.4.0.ER1 How reproducible: Always on IBM JDK Steps to Reproduce: 1. ./build.sh -pl deployment-scanner -am -Dtest=FileSystemDeploymentServiceUnitTestCase -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -DfailIfNoTests=false Actual results: java.net.ConnectException: Connection refused java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment java.lang.reflect.InvocationTargetException Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment Expected results: No failures in test case. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-507) Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-507?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-507: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1182466 > Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK > -------------------------------------------------------------------- > > Key: WFCORE-507 > URL: https://issues.jboss.org/browse/WFCORE-507 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 1.0.0.Alpha15 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Trivial > > Description of problem: > org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: > - java.net.ConnectException: Connection refused > - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment > Version-Release number of selected component (if applicable): > EAP 6.4.0.ER1 > How reproducible: > Always on IBM JDK > Steps to Reproduce: > 1. ./build.sh -pl deployment-scanner -am -Dtest=FileSystemDeploymentServiceUnitTestCase -Dmaven.repo.local=${MAVEN_REPO_LOCAL} -DfailIfNoTests=false > Actual results: > java.net.ConnectException: Connection refused > java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment > java.lang.reflect.InvocationTargetException > Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > Expected results: > No failures in test case. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4250) Manually created CDI producer methods in the Extension are not injected

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-4250?page=com.atlassian.jira.plugin.... ] Jozef Hartinger commented on WFLY-4250: --------------------------------------- Whether a bean is injectable in a deployment is determined by whether Bean.getBeanClass() is loadable by the deployment classloader. What is the bean class (Bean.getBeanClass()) for your beans that which are not injected? > Manually created CDI producer methods in the Extension are not injected > ----------------------------------------------------------------------- > > Key: WFLY-4250 > URL: https://issues.jboss.org/browse/WFLY-4250 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.2.0.Final > Environment: Happened on Linux environment > Reporter: Sebastian Łaskawiec > Assignee: Jozef Hartinger > > h2. Issue description: > During migration from Wildfly 8.1 to 8.2 (Weld 2.1.2.Final -> 2.2.6.Final) in Infinispan we discovered a problem with injecting beans created programmatically in Infinispan-cdi integration module. The problem appeared in {{GreetingServiceIT}} and {{GreetingCacheManagerIT}} test. Both those tests use the following modules integrated into Wildfly: > * org.infinispan.cdi (slot: ispn-7.1, which has dependency to "org.infinispan" slot="ispn-7.1" export="true") > * org.infinispan.jcache (slot: ispn-7.1, which has dependency to "org.infinispan" slot="ispn-7.1" and "org.infinispan.cdi" slot="ispn-7.1" services="import") > [Infinispan's CDI Extension|https://github.com/infinispan/infinispan/blob/master/cdi/src/ma...] invokes [{{embeddedExtension.registerCacheBeans(event, beanManager)}}|https://github.com/infinispan/infinispan/blob/master/cdi/s...], which registers custom {{Cache}} and {{AdvancedCache}} producer beans. Those beans are being successfully added to {{BeanManager}} but are never chosen for injection. All tests fail because of unsatisfied dependencies for {{Cache<CacheKey, String>}} with qualifiers {{@GreetingCache}}. > h2. Steps to reproduce: > * Download and unzip [https://github.com/slaskawi/infinispan/archive/upgrade_to_wf_8_2_failed_t...] > * Run {{./build.sh clean install -pl cdi,as-modules/embedded,integrationtests/as-integration-embedded -am -DskipTests}} > * Modify Arquillian xml if breakpoint is needed {{./integrationtests/as-integration-embedded/src/test/resources/arquillian.xml}} > * Run test (using IDE or Maven: {{./build.sh test -pl integrationtests/as-integration-embedded -Dtest=GreetingServiceIT}}) > h2. Finding during debugging: > At first I would suggest creating conditional breakpoints: > * {{org.jboss.weld.bootstrap.Validator}} line 370 (WF 8.2) or 366 (WF 8.1), condition {{"[BackedAnnotatedField] @Inject @GreetingCache private org.infinispan.test.integration.as.cdi.GreetingServiceIT.greetingCache".equals(ij.toString())}} - this will stop debugger when validating injection points for {{{GreetingCache}}. > * {{org.jboss.weld.resolution.TypeSafeResolver.ResolvableToBeanCollection}} line 51, condition {{from.toString().startsWith("Types: [org.infinispan.Cache<javax.cache.annotation.CacheKey, java.lang.String>]") || from.toString().contains("org.infinispan.Cache")}} - this stops debugger on loading {{Cache}} producer methods (created in Infinispan CDI Extension) to {{resolved}} Loading Cache in Wildfly 8.1. > During debugging session we discovered that the beans from Infinispan's CDI Extension are created but never used for injection. This is because {{beanManager.getBeans(ij)}} in {{Validator.java}} always return empty list. In Wildfly 8.1 beans are properly resolved using {{ResolvableToBeanCollection#load}} method, but for some reason it never happens in Wildfly 8.2, because those beans are already preset in {{resolved}} Loading Cache with empty collection value. Unfortunately we couldn't find answer why. > h2. Workaround: > In order to fix CDI Producer Beans accessibility we need to add a new dependency to our test: {{META-INF/MANIFEST.MF: Dependencies: org.infinispan:ispn-7.1}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-874) CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/SECURITY-874?page=com.atlassian.jira.plug... ] Bartosz Baranowski reassigned SECURITY-874: ------------------------------------------- Assignee: Bartosz Baranowski (was: Stefan Guilhen) > CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions > ------------------------------------------------------------------------------------------------- > > Key: SECURITY-874 > URL: https://issues.jboss.org/browse/SECURITY-874 > Project: PicketBox > Issue Type: Bug > Components: Identity > Affects Versions: PicketBox_4_0_21.Final > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > > org.jboss.security.identity.extensions.CredentialIdentityFactory.NULL_IDENTITY does not get initialized to an empty identity due to initialization method returning a reference to NULL_IDENTITY, which has not initialized yet, resulting in null pointer. This causes NullPointerException in org.jboss.security.SecurityContextUtil.clearIdentities() and org.jboss.security.SecurityContextUtil.getIdentities() methods. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-874) CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created SECURITY-874: ------------------------------------------- Summary: CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions Key: SECURITY-874 URL: https://issues.jboss.org/browse/SECURITY-874 Project: PicketBox Issue Type: Bug Components: Identity Affects Versions: PicketBox_4_0_21.Final Reporter: Bartosz Baranowski Assignee: Stefan Guilhen org.jboss.security.identity.extensions.CredentialIdentityFactory.NULL_IDENTITY does not get initialized to an empty identity due to initialization method returning a reference to NULL_IDENTITY, which has not initialized yet, resulting in null pointer. This causes NullPointerException in org.jboss.security.SecurityContextUtil.clearIdentities() and org.jboss.security.SecurityContextUtil.getIdentities() methods. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-154) Patching does not process subdirectories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-154?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-154: ------------------------------------------------ Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1136365|https://bugzilla.redhat.com/show_bug.cgi?id=1136365] from MODIFIED to ON_QA > Patching does not process subdirectories > ---------------------------------------- > > Key: WFCORE-154 > URL: https://issues.jboss.org/browse/WFCORE-154 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 1.0.0.Alpha9 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha10 > > > If patched resource is in subdirectory of moduleRoot, it is not included as part of patch, even though it is present in patch zip. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3974) Move 'Channel end notification received, closing channel' to DEBUG

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3974?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3974: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1147506|https://bugzilla.redhat.com/show_bug.cgi?id=1147506] from MODIFIED to ON_QA > Move 'Channel end notification received, closing channel' to DEBUG > ------------------------------------------------------------------ > > Key: WFLY-3974 > URL: https://issues.jboss.org/browse/WFLY-3974 > Project: WildFly > Issue Type: Enhancement > Components: Naming > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > When a remote jms queue is located the following is seen: > 2014-09-25 16:48:29,327 INFO [org.jboss.as.naming] (Remoting "jeev6dev01_200" task-1) JBAS011806: Notification de fin de canal reçue, fermeture du canal Channel ID 0cb79bd5 (inbound) of Remoting connection 53a1933a to /10.23.132.245:57733 > This is due to org.jboss.as.naming.NamingLogger where the following is used: > @LogMessage(level=Logger.Level.INFO) > @Message(id=11806, value="Channel end notification received, closing channel %s") > public abstract void closingChannelOnChannelEnd(Channel paramChannel); > Changin this to > @LogMessage(level=Logger.Level.DEBUG) > Would ensure that an INFO log event is not seen every time a jms message is sent to the server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3779) IllegalAccessException when a built-in normal-scoped bean defines a package-private no-arg constructor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3779?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3779: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1133962|https://bugzilla.redhat.com/show_bug.cgi?id=1133962] from MODIFIED to ON_QA > IllegalAccessException when a built-in normal-scoped bean defines a package-private no-arg constructor > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-3779 > URL: https://issues.jboss.org/browse/WFLY-3779 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 8.2.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-112) Long server shut-dow with unresponsive client with opened JNDI Context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-112?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-112: ------------------------------------------------ Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1139197|https://bugzilla.redhat.com/show_bug.cgi?id=1139197] from MODIFIED to ON_QA > Long server shut-dow with unresponsive client with opened JNDI Context > ---------------------------------------------------------------------- > > Key: WFCORE-112 > URL: https://issues.jboss.org/browse/WFCORE-112 > Project: WildFly Core > Issue Type: Bug > Reporter: Miroslav Novak > Assignee: David Lloyd > Labels: remoting > Attachments: JNDIContext.java, testcase.zip > > > Description of problem: > If client with opened JNDI context is disconnected from network, then clean shutdown (ctrl-c) of server takes 15 minutes. > This scenario takes place, when network connections is lost between JMS clients with JNDI context and server. > Version-Release number of selected component (if applicable): > jboss-remoting-3.3.3.Final-redhat-1.jar > How reproducible: > always > Steps to Reproduce: > 1. Start EAP 6.3.1.CP.CR1 on first machine > 2. Start client which creates JNDI context on second machine (use attached JNDIContext.java) > 3. Disconnect network between client and server > 4. Try to cleanly shutdown EAP 6.3.1.CP.CR1 server (by ctrl-c) > Actual results: > It takes 15 minutes for server to shutdown. > Expected results: > Server should shutdown almost immediately. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015