January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-510) Fix filtering in domain mode

by Harald Pehl (JIRA)

Harald Pehl created WFCORE-510: ---------------------------------- Summary: Fix filtering in domain mode Key: WFCORE-510 URL: https://issues.jboss.org/browse/WFCORE-510 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Harald Pehl Assignee: Brian Stansberry The overall result for query operations in domain mode does not filter undefined results. Executing the following operation, will yield three results. However the last result needs to be filtered: {code} [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name, status, auto-start], where={auto-start=>true}) { "outcome" => "success", "result" => [ { "address" => [ ("host" => "master"), ("server-config" => "server-one") ], "outcome" => undefined, "result" => { "name" => "server-one", "status" => "STARTED", "auto-start" => true } }, { "address" => [ ("host" => "master"), ("server-config" => "server-two") ], "outcome" => undefined, "result" => { "name" => "server-two", "status" => "STARTED", "auto-start" => true } }, { "address" => [ ("host" => "master"), ("server-config" => "server-three") ], "outcome" => undefined, "result" => undefined } ], "server-groups" => undefined } {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4255) Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4255?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4255: -------------------------------------- We might as well add suspend/resume operations. Unfortunatelly ControllerContainer API is not reasonably extensible, problably best is to extend that API with WildFly-specific methods. > Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4255 > URL: https://issues.jboss.org/browse/WFLY-4255 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Radoslav Husar > > Wildfly has a clean shutdown mechanism which can be used to shutdown a server from the command line so that requests active at the time of shutdown get a chance to complete: > {code} > [standalone@localhost:9990 /] :shutdown(timeout=5) > {"outcome" => "success"} > {code} > Provide access to this feature from an Arquillian test case so that test cases may test with or without clean shutdown enabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4255) Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4255?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4255: --------------------------------- Affects Version/s: 9.0.0.Alpha1 > Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4255 > URL: https://issues.jboss.org/browse/WFLY-4255 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Radoslav Husar > > Wildfly has a clean shutdown mechanism which can be used to shutdown a server from the command line so that requests active at the time of shutdown get a chance to complete: > {code} > [standalone@localhost:9990 /] :shutdown(timeout=5) > {"outcome" => "success"} > {code} > Provide access to this feature from an Arquillian test case so that test cases may test with or without clean shutdown enabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4255) Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4255?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4255: --------------------------------- Summary: Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server (was: Allow Arquillian to specify a timeout value for the Wildfly clean shutdown mechanism when shutting down a server.) > Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4255 > URL: https://issues.jboss.org/browse/WFLY-4255 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Richard Achmatowicz > Assignee: Radoslav Husar > > Wildfly has a clean shutdown mechanism which can be used to shutdown a server from the command line so that requests active at the time of shutdown get a chance to complete: > {code} > [standalone@localhost:9990 /] :shutdown(timeout=5) > {"outcome" => "success"} > {code} > Provide access to this feature from an Arquillian test case so that test cases may test with or without clean shutdown enabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1876: --------------------------- Attachment: (was: JGRP-1876-1.pdf) > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, JGRP-1876-1.pdf, karim-logs-files.zip, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4263) IIOP Subsystem: Invalid logger category creation

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4263?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-4263: --------------------------------- Summary: IIOP Subsystem: Invalid logger category creation (was: IIOP Subsystem: Wrong logger configuration) > IIOP Subsystem: Invalid logger category creation > ------------------------------------------------ > > Key: WFLY-4263 > URL: https://issues.jboss.org/browse/WFLY-4263 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 9.0.0.Alpha1 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > > Frank Langelage wrote: > {quote} > Now with wildfly.iiop in place, I see DEBUG messages, although category "org.wildfly" is set to INFO. To get rid of the debug messages a category with name "package org.wildfly.iiop" needs to be defined. > I think the Logger creation > IIOPLogger ROOT_LOGGER = Logger.getMessageLogger(IIOPLogger.class, IIOPLogger.class.getPackage().toString()); > in > iiop-openjdk/src/main/java/org/wildfly/iiop/openjdk/logging/IIOPLogger.java > should be changed, aligned with those in other subsystems. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4264) Update ejb-client version to 2.1.0.Final

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created WFLY-4264: --------------------------------------------- Summary: Update ejb-client version to 2.1.0.Final Key: WFLY-4264 URL: https://issues.jboss.org/browse/WFLY-4264 Project: WildFly Issue Type: Component Upgrade Components: EJB Affects Versions: 9.0.0.Alpha1 Reporter: Panagiotis Sotiropoulos Assignee: David Lloyd Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2732) Injected EJB not available to MDB @PreDestroy methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2732?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2732: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1160575|https://bugzilla.redhat.com/show_bug.cgi?id=1160575] from ON_QA to VERIFIED > Injected EJB not available to MDB @PreDestroy methods > ----------------------------------------------------- > > Key: WFLY-2732 > URL: https://issues.jboss.org/browse/WFLY-2732 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.CR1 > Reporter: Mustafa Musaji > Assignee: Stuart Douglas > Fix For: 8.0.0.Final > > Attachments: MDBLifeCycleJAR.zip > > > MDB with method annotated with @PreDestroy and injected EJB. In this method we are calling an EJB. When the application is undeployed the PreDestroy method is called but it fails on the call to the injected EJB as it's already been undeployed. > This was fixed in an RFE for Session Beans but does not seem to work for MDB. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[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 1127593|https://bugzilla.redhat.com/show_bug.cgi?id=1127593] 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4254) Symbolic links within web applications do not work

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4254?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4254: --------------------------------- Assignee: Stuart Douglas (was: Bartosz Baranowski) > Symbolic links within web applications do not work > -------------------------------------------------- > > Key: WFLY-4254 > URL: https://issues.jboss.org/browse/WFLY-4254 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Kris Iyer > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > Symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. > Here is what I tried under an exploded war: > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" > version="8.0"> > <symbolic-linking-enabled>true</symbolic-linking-enabled> > </jboss-web> > Does not follow links and results in a 404. > HTTP/?.? 404 Not Found > Connection: keep-alive > X-Powered-By: Undertow/1 > Server: WildFly/8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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