[JBoss JIRA] (WFLY-2081) IronJacamarResourceCreator Throws ConcurrentModificationException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2081?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2081:
-----------------------------------------------
Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 981093|https://bugzilla.redhat.com/show_bug.cgi?id=981093] from ASSIGNED to POST
> IronJacamarResourceCreator Throws ConcurrentModificationException
> -----------------------------------------------------------------
>
> Key: WFLY-2081
> URL: https://issues.jboss.org/browse/WFLY-2081
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.0.0.Alpha4, 8.0.0.Beta1
> Reporter: James Olsen
> Assignee: Ivo Studensky
> Fix For: 9.0.0.Beta1
>
>
> Recent wildfly-8.0.0.Beta1-SNAPSHOT (IronJacamar 1.1.0.Final) throws following error intermittently when there are multiple RARs in an EAR:
> 13:12:34,710 ERROR [org.jboss.msc.service] (MSC service thread 1-10) MSC000002: Invocation of listener "org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1@e7b3aee" failed: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) [rt.jar:1.7.0_25]
> at java.util.HashMap$KeyIterator.next(HashMap.java:928) [rt.jar:1.7.0_25]
> at org.jboss.as.connector.subsystems.resourceadapters.IronJacamarResourceCreator.getIronJacamarResource(IronJacamarResourceCreator.java:335) [wildfly-connector-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.connector.subsystems.resourceadapters.IronJacamarResourceCreator.execute(IronJacamarResourceCreator.java:350) [wildfly-connector-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1.registerIronjacamar(ParsedRaDeploymentProcessor.java:145) [wildfly-connector-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.connector.deployers.ra.processors.AbstractResourceAdapterDeploymentServiceListener.transition(AbstractResourceAdapterDeploymentServiceListener.java:244) [wildfly-connector-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1533) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:51) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:2095) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> 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]
> Older versions had a similar problem as detailed in JBJCA-933 (which also shows interleaving example with 3 RARs).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (AS7-1949) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
by David Hernández Tejada (JIRA)
[ https://issues.jboss.org/browse/AS7-1949?page=com.atlassian.jira.plugin.s... ]
David Hernández Tejada commented on AS7-1949:
---------------------------------------------
Check if you have another server started in the same computer with a port needed in your JBoss. For example if you have something in localhost:8080 tipically as a web server or perhaps a jenkings.
> JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-1949
> URL: https://issues.jboss.org/browse/AS7-1949
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.0.2.Final
> Environment: Windows 7, 64bit
> Reporter: u j
>
> On startup of jboss-as-7.0.2.Final with standalone-preview.xml on Windows 7, many of the following errors ocurr:
> 07:38:49,167 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> Hence, the startup is very slow.
> Complete startup log:
> 07:38:41,173 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA
> 07:38:41,777 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
> 07:38:41,826 INFO [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting
> 07:38:43,876 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
> 07:38:43,948 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
> 07:38:43,951 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
> 07:38:43,960 INFO [org.jboss.as.logging] Removing bootstrap log handlers
> 07:38:43,981 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
> 07:38:44,010 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
> 07:38:44,061 INFO [org.jboss.as.jacorb] (Controller Boot Thread) Activating JacORB Subsystem
> 07:38:44,127 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem
> 07:38:44,138 INFO [org.jboss.as.naming] (MSC service thread 1-9) JBAS011802: Starting Naming Service
> 07:38:44,144 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem
> 07:38:44,166 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
> 07:38:44,172 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2
> 07:38:44,187 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
> 07:38:44,203 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
> 07:38:44,455 INFO [org.jboss.as.webservices] (Controller Boot Thread) Activating WebServices Extension
> 07:38:44,461 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-8) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\java\jdk1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native
> 07:38:44,582 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
> 07:38:45,342 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.0.Beta3
> 07:38:46,162 INFO [org.jboss.as.remoting] (MSC service thread 1-8) Listening on /127.0.0.1:9999
> 07:38:46,165 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-9) Starting remote JMX connector
> 07:38:46,224 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-16) Starting Coyote HTTP/1.1 on http-127.0.0.1-127.0.0.1-8080
> 07:38:46,431 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingjournal,bindingsDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingpaging)
> 07:38:46,455 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
> 07:38:46,462 INFO [org.jboss.as.connector] (MSC service thread 1-13) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
> 07:38:46,505 WARN [jacorb.codeset] (MSC service thread 1-14) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
> 07:38:46,539 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS]
> 07:38:46,556 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) Registered connection factory java:/JmsXA
> 07:38:46,563 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) CORBA ORB Service Started
> 07:38:46,567 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-8) HornetQ resource adaptor started
> 07:38:46,568 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 07:38:46,680 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5455 for CORE protocol
> 07:38:46,693 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5445 for CORE protocol
> 07:38:46,695 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) Server is now live
> 07:38:46,696 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [1eee8233-e7bc-11e0-aa93-5442495fe54a] started
> 07:38:46,699 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-15) trying to deploy queue jms.queue.testQueue
> 07:38:46,711 INFO [org.jboss.as.jacorb] (MSC service thread 1-11) CORBA Naming Service Started
> 07:38:46,877 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:47,039 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:47,085 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:47,484 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:47,775 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:48,089 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:49,139 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:49,167 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:49,341 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:50,571 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:50,629 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:50,720 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:50,874 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:51,055 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:51,272 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:51,418 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:51,475 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:51,838 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:52,222 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:52,520 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:52,582 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:52,652 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:53,196 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:53,399 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:54,216 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:55,068 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:55,162 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:55,621 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:55,911 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:56,519 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:56,602 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:57,370 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:57,594 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:58,309 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:38:59,792 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:39:00,437 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.
> 07:39:00,630 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-15) Bound messaging object to jndi name java:/queue/test
> 07:39:00,646 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-7) Bound messaging object to jndi name java:/ConnectionFactory
> 07:39:00,647 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-4) Bound messaging object to jndi name java:/RemoteConnectionFactory
> 07:39:00,648 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-16) trying to deploy queue jms.topic.testTopic
> 07:39:00,676 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-16) Bound messaging object to jndi name java:/topic/test
> 07:39:00,694 INFO [org.jboss.as.deployment] (MSC service thread 1-13) Started FileSystemDeploymentService for directory C:\java\jboss\jboss-as-7.0.2.Final\standalone\deployments
> 07:39:00,772 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 19827ms - Started 126 of 185 services (59 services are passive or on-demand)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-587?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-587:
------------------------------------------------
Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1198186|https://bugzilla.redhat.com/show_bug.cgi?id=1198186] from ASSIGNED to POST
> Wildfly does not log stack trace of an exception
> ------------------------------------------------
>
> Key: WFCORE-587
> URL: https://issues.jboss.org/browse/WFCORE-587
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 1.0.0.Alpha19
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Copied from BZ 1198186:
> AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE.
> https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29...
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
> 2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default"),
> ("connector" => "tp4")
> ] failed handling operation rollback -- java.lang.NullPointerException
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-553?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-553:
------------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1199319|https://bugzilla.redhat.com/show_bug.cgi?id=1199319] from NEW to ASSIGNED
> ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-553
> URL: https://issues.jboss.org/browse/WFCORE-553
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha18
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up.
> In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel.
> Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3316:
-----------------------------------------------
Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1094380|https://bugzilla.redhat.com/show_bug.cgi?id=1094380] from POST to MODIFIED
> Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-3316
> URL: https://issues.jboss.org/browse/WFLY-3316
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Enrique González Martínez
> Labels: ejb, naming, remote-clients, remote-ejb-connection
> Attachments: reproducer.zip
>
>
> If a client run multi threads and each Thread use it's own InitialContext the behaviour is unexpected.
> The behaviour is as followed:
> if each invocation create it's own IC and lookup the EJB there is sometimes a EJBCLIENT000025 because one of the one thread has closed the IC until another thread try to invoke an EJB.
> If the IC is reused the failure might happen only if the first Thread has finished the invocations and close the IC during other Threads are still running.
> It looks that the underlying remote connection will be closed if the first IC is closed without respect that there are different IC's created and still in use.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months