January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3266) Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3266?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3266: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1088463|https://bugzilla.redhat.com/show_bug.cgi?id=1088463] from ON_QA to VERIFIED > Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3266 > URL: https://issues.jboss.org/browse/WFLY-3266 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Panagiotis Sotiropoulos > Priority: Critical > Fix For: 9.0.0.CR1 > > > In case of large parameter input for EJB invocations the ejb-client throw the Exception below. > The underlying OutOfMemory is complete hidden, neither in the server.log nor in the ejb-client with TRACE a hint will be found. > java.lang.IllegalStateException: EJBCLIENT000032: Cannot retry a request which hasn't previously been completed > at org.jboss.ejb.client.EJBClientInvocationContext.retryRequest(EJBClientInvocationContext.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:256) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:265) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) > at com.sun.proxy.$Proxy6.uploadData(Unknown Source) > at de.info.biene.konsens.TestServiceWithAPITest.testUploadData(TestServiceWithAPITest.java:81) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1878) Multicast discovery does not work on JDK8

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1878?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1878: ----------------------------------------------- Marek Kopecky <mkopecky(a)redhat.com> changed the Status of [bug 1167666|https://bugzilla.redhat.com/show_bug.cgi?id=1167666] from ON_QA to VERIFIED > Multicast discovery does not work on JDK8 > ----------------------------------------- > > Key: JGRP-1878 > URL: https://issues.jboss.org/browse/JGRP-1878 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.12, 3.5 > Environment: OpenJDK8, OracleJDK8u40 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 3.2.14, 3.6 > > Attachments: mcast.java > > > Multicast discovery does not work on JDK8 when using different bind IP addresses. This blocks EAP certification on JDK8. > Steps to reproduce with draw, switch to JDK8: > {noformat} > export IP_ADDR=127.0.0.1 > ./draw.sh > export IP_ADDR=192.168.1.10 > ./draw.sh > {noformat} > Everything works when binding to the same IP address or using JDK 6 or 7. Possibly a JDK8 bug.. -- 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: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1136365|https://bugzilla.redhat.com/show_bug.cgi?id=1136365] from ON_QA to VERIFIED > 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-4269) redelivery ResourceAdapter Config is not respected when defined in more than one config.

by Jay Kumar SenSharma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4269?page=com.atlassian.jira.plugin.... ] Jay Kumar SenSharma commented on WFLY-4269: ------------------------------------------- - If we uncomment the "maximumRedeliveries" and "initialRedeliveryDelay" @ActivationConfigProperty in the MDB then the "maximumRedeliveries" defined in MDB @ActivationConfigProperty works as expected, but the "initialRedeliveryDelay" goes back to 1 second which is default for the activemq resource adapter and ignores the {code} <config-property name="MaximumRedeliveries"> 3 </config-property>: {code} http://activemq.apache.org/redelivery-policy.html > redelivery ResourceAdapter Config is not respected when defined in more than one config. > ---------------------------------------------------------------------------------------- > > Key: WFLY-4269 > URL: https://issues.jboss.org/browse/WFLY-4269 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 9.0.0.Alpha1 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Jesper Pedersen > > - If the MDB defines the "initialRedeliveryDelay" and "maximumRedeliveries" ActivationConfigProperty via annotation OR using "ejb-jar.xml" file, As well as if the "initialRedeliveryDelay" "config-property" is defined inside the <resource-adapter> section of standalone.xml then *both* are ignored, and it starts taking the default value of initialRedeliveryDelay for Activemq resource adapter as 1 Second see [1] > [1] http://activemq.apache.org/redelivery-policy.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4269) redelivery ResourceAdapter Config is not respected when defined in more than one config.

by Jay Kumar SenSharma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4269?page=com.atlassian.jira.plugin.... ] Jay Kumar SenSharma edited comment on WFLY-4269 at 1/20/15 4:05 AM: -------------------------------------------------------------------- - If we uncomment the "maximumRedeliveries" and "initialRedeliveryDelay" @ActivationConfigProperty in the MDB then the "maximumRedeliveries" defined in MDB @ActivationConfigProperty works as expected, but the "initialRedeliveryDelay" goes back to 1 second which is default for the activemq resource adapter and ignores the {code} <config-property name="InitialRedeliveryDelay"> 2000 </config-property> {code} http://activemq.apache.org/redelivery-policy.html was (Author: jaysensharma): - If we uncomment the "maximumRedeliveries" and "initialRedeliveryDelay" @ActivationConfigProperty in the MDB then the "maximumRedeliveries" defined in MDB @ActivationConfigProperty works as expected, but the "initialRedeliveryDelay" goes back to 1 second which is default for the activemq resource adapter and ignores the {code} <config-property name="MaximumRedeliveries"> 3 </config-property>: {code} http://activemq.apache.org/redelivery-policy.html > redelivery ResourceAdapter Config is not respected when defined in more than one config. > ---------------------------------------------------------------------------------------- > > Key: WFLY-4269 > URL: https://issues.jboss.org/browse/WFLY-4269 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 9.0.0.Alpha1 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Jesper Pedersen > > - If the MDB defines the "initialRedeliveryDelay" and "maximumRedeliveries" ActivationConfigProperty via annotation OR using "ejb-jar.xml" file, As well as if the "initialRedeliveryDelay" "config-property" is defined inside the <resource-adapter> section of standalone.xml then *both* are ignored, and it starts taking the default value of initialRedeliveryDelay for Activemq resource adapter as 1 Second see [1] > [1] http://activemq.apache.org/redelivery-policy.html -- 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: ------------------------------------------------ Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 1149621|https://bugzilla.redhat.com/show_bug.cgi?id=1149621] from ON_QA to VERIFIED > 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

[JBoss JIRA] (WFCORE-161) JMX monitoring is extremely memory inefficient

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-161?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-161: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1154868|https://bugzilla.redhat.com/show_bug.cgi?id=1154868] from ON_QA to VERIFIED > JMX monitoring is extremely memory inefficient > ---------------------------------------------- > > Key: WFCORE-161 > URL: https://issues.jboss.org/browse/WFCORE-161 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Koen Janssens > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha11 > > > When reading any JMX attribute(s), I have noticed a noticeable impact on the performance of our system. After attaching a profiler, I see that getting a single attribute of a JMX bean (either using remoting or using jconsole) is generating thousands of objects, that have to cleaned up by the GC. For instance, 6000 instances of the ModelNode class are created. > A clone is made of the complete management model before executing any JMX operation. This happens in the OperationContextImpl.readResourceFromRoot class. > More background on associated forum thread -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4269) redelivery ResourceAdapter Config is not respected when defined in more than one config.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4269: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1183915 > redelivery ResourceAdapter Config is not respected when defined in more than one config. > ---------------------------------------------------------------------------------------- > > Key: WFLY-4269 > URL: https://issues.jboss.org/browse/WFLY-4269 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 9.0.0.Alpha1 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Jesper Pedersen > > - If the MDB defines the "initialRedeliveryDelay" and "maximumRedeliveries" ActivationConfigProperty via annotation OR using "ejb-jar.xml" file, As well as if the "initialRedeliveryDelay" "config-property" is defined inside the <resource-adapter> section of standalone.xml then *both* are ignored, and it starts taking the default value of initialRedeliveryDelay for Activemq resource adapter as 1 Second see [1] > [1] http://activemq.apache.org/redelivery-policy.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3942) Race condition with clean shutdown and mod_cluster session draining

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3942?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3942: ----------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1161079|https://bugzilla.redhat.com/show_bug.cgi?id=1161079] from ON_QA to VERIFIED > Race condition with clean shutdown and mod_cluster session draining > ------------------------------------------------------------------- > > Key: WFLY-3942 > URL: https://issues.jboss.org/browse/WFLY-3942 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > Probably same issue exists in WF as well, I will revalidate the logic for race conditions. > https://issues.jboss.org/browse/MODCLUSTER-399 > https://bugzilla.redhat.com/show_bug.cgi?id=1083563 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-31) The JBoss Modules schemas are missing from the build

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-31?page=com.atlassian.jira.plugin.... ] Eduardo Martins resolved WFCORE-31. ----------------------------------- Resolution: Done Fixed by the upgrade to WildFly Build Tools 1.0.0.Alpha8 https://github.com/wildfly/wildfly-core/commit/8d29f35c89eec65ae32be62d73... > The JBoss Modules schemas are missing from the build > ---------------------------------------------------- > > Key: WFCORE-31 > URL: https://issues.jboss.org/browse/WFCORE-31 > Project: WildFly Core > Issue Type: Bug > Reporter: Darran Lofthouse > Assignee: Eduardo Martins > Fix For: 1.0.0.Alpha16 > > -- 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