October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3920) Outbound LDAP connection in domain mode test case

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3920?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3920: ----------------------------------------------- Ondrej Kotek <okotek(a)redhat.com> changed the Status of [bug 1148400|https://bugzilla.redhat.com/show_bug.cgi?id=1148400] from NEW to ASSIGNED > Outbound LDAP connection in domain mode test case > ------------------------------------------------- > > Key: WFLY-3920 > URL: https://issues.jboss.org/browse/WFLY-3920 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Security, Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-86) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-86?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-86: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1113242|https://bugzilla.redhat.com/show_bug.cgi?id=1113242] from ON_QA to VERIFIED > RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts > -------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-86 > URL: https://issues.jboss.org/browse/REMJMX-86 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.0.Final > Reporter: Mustafa Musaji > Assignee: Brad Maxwell > Fix For: 1.1.3.Final, 2.0.1.CR1 > > > In [1] we have the following snippet of code which has a hardcoded value of 5 seconds. > {code:title=RemotingConnector.java} > // Now open the channel > final IoFuture<Channel> futureChannel = connection.openChannel(serviceName, OptionMap.EMPTY); > IoFuture.Status result = futureChannel.await(5, TimeUnit.SECONDS); > if (result == IoFuture.Status.DONE) { > channel = futureChannel.get(); > } else if (result == IoFuture.Status.FAILED) { > throw new IOException(futureChannel.getException()); > } else { > throw new RuntimeException("Operation failed with status " + result); > } > {code} > This should be a system property or the default value should be raised. > [1] https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jbo... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3920) Outbound LDAP connection in domain mode test case

by Ondrej Kotek (JIRA)

Ondrej Kotek created WFLY-3920: ---------------------------------- Summary: Outbound LDAP connection in domain mode test case Key: WFLY-3920 URL: https://issues.jboss.org/browse/WFLY-3920 Project: WildFly Issue Type: Feature Request Components: Domain Management, Security, Test Suite Affects Versions: 9.0.0.Alpha1 Reporter: Ondrej Kotek Assignee: Ondrej Kotek -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2210) fix message endpoint isDeliveryTransacted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2210?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2210: ----------------------------------------------- Martin Simka <msimka(a)redhat.com> changed the Status of [bug 1147284|https://bugzilla.redhat.com/show_bug.cgi?id=1147284] from ON_QA to VERIFIED > fix message endpoint isDeliveryTransacted > ----------------------------------------- > > Key: WFLY-2210 > URL: https://issues.jboss.org/browse/WFLY-2210 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The org.jboss.as.ejb3.inflow.MessageEndpointService#isDeliveryTransacted method is checking the transaction attribute of the method using the MethodIntf.BEAN while it should use the MethodIntf.MESSAGE_ENDPOINT type. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2515) JBAS014249 if a fire and forget asynchronous ejb call is made

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2515?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2515: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1030936|https://bugzilla.redhat.com/show_bug.cgi?id=1030936] from ON_QA to VERIFIED > JBAS014249 if a fire and forget asynchronous ejb call is made > ------------------------------------------------------------- > > Key: WFLY-2515 > URL: https://issues.jboss.org/browse/WFLY-2515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Beta1, 8.0.0.CR1 > Environment: Beta2 SNAPSHOT > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If an ejb method > @Asynchronous void fireAndForget(...) > is called remote and the client disconnect an Exception JBAS014249 will be thrown if the async method return. > {noformat} > ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014249: Error invoking method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname : java.lang.NullPointerException > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 11:30:20,242 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: org.jboss.remoting3.NotOpenException: Writes closed > at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:112) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:301) > at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:68) > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100) > ... 9 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-46) Fix intermittent failures in DeploymentOverlayCLITestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-46?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-46: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1144222|https://bugzilla.redhat.com/show_bug.cgi?id=1144222] from ON_QA to VERIFIED > Fix intermittent failures in DeploymentOverlayCLITestCase > --------------------------------------------------------- > > Key: WFCORE-46 > URL: https://issues.jboss.org/browse/WFCORE-46 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3600) TransactionRolledbackException doesn't reference the originating runtime-exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3600?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3600: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1109153|https://bugzilla.redhat.com/show_bug.cgi?id=1109153] from ON_QA to VERIFIED > TransactionRolledbackException doesn't reference the originating runtime-exception > ---------------------------------------------------------------------------------- > > Key: WFLY-3600 > URL: https://issues.jboss.org/browse/WFLY-3600 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If a RuntimeException is thrown by a business method this gets lost during propagation to the client. > The client is not able in this case to react appropriate to the cause. > Similar issue was fixed for the Local invocation, see AS7-5432 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Bela Ban commented on WFLY-1067: -------------------------------- Can't this information be injected into ENCRYPT ? > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-333) The value wait-time of the EJB bean statistic is not calculated

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-333?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-333: ---------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1126677|https://bugzilla.redhat.com/show_bug.cgi?id=1126677] from POST to MODIFIED > The value wait-time of the EJB bean statistic is not calculated > --------------------------------------------------------------- > > Key: WFLY-333 > URL: https://issues.jboss.org/browse/WFLY-333 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > If the statistic for EJB calls is enabled with > /subsystem=ejb3:write-attribute(name=enable-statistics, value=true) > call statistics are caclulated but the wait-time is never set even if a pool overload is forced. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-838) Can't get implementing classname for JSR77 MBean

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-838?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-838: ---------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1138628|https://bugzilla.redhat.com/show_bug.cgi?id=1138628] from POST to MODIFIED > Can't get implementing classname for JSR77 MBean > ------------------------------------------------ > > Key: WFLY-838 > URL: https://issues.jboss.org/browse/WFLY-838 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Priority: Minor > Fix For: Awaiting Volunteers > > > The following exception are thrown when asking the MBean server for the classname implementing "jboss.jsr77:j2eeType=WebModule,name=MyWar.war,J2EEServer=default". > It should be a legal call. Why are the code clearly states it's illegal? > > java.lang.IllegalStateException: JBAS019905: Should not get called > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers$J2EEModuleHandler.queryObjectNames(J2EEDeployedObjectHandlers.java:245) > at org.jboss.as.jsr77.managedobject.BaseHandler.getMBeanInfo(BaseHandler.java:64) > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers.getMBeanInfo(J2EEDeployedObjectHandlers.java:147) > at org.jboss.as.jsr77.managedobject.ManagedObjectHandlerRegistry.getMBeanInfo(ManagedObjectHandlerRegistry.java:112) > at org.jboss.as.jsr77.subsystem.JSR77ManagementMBeanServer.getMBeanInfo(JSR77ManagementMBeanServer.java:179) > at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:212) > > The error can easily be triggered by using JConsole to browse the same MBean. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 October 2014