January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5640) No EJB receiver available for handling

by Ivan Straka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5640?page=com.atlassian.jira.plugin.... ] Ivan Straka reopened WFLY-5640: ------------------------------- Still failing. I did some investigation yesterday and I figured out what the problem is. https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integration/clus... This should be set to 8180. Node1 is listening on this port. If you look into the configuration, you will find out that node0 is listening on 8080. Thats why you weren't able to reproduce it locally (neither were I). Due to the same ip addresses of node0 and node1 8080 was valid (node 0 is listening on 8080), on the other hand, if ip addresses are not same, noone is listening on node1_ip : 8080 I am just about to do a PR to EAP. > No EJB receiver available for handling > -------------------------------------- > > Key: WFLY-5640 > URL: https://issues.jboss.org/browse/WFLY-5640 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB, Test Suite > Affects Versions: 10.0.0.CR4 > Environment: hp-ux 11v3 - hpjdk1.8 > solaris 10,11 - x86 and x86_64, rhel 6 - x86 and x86_64, rhel 7 x86_64 - openjdk1.8, ibmjdk1.8, oraclejdk1.8 > Reporter: Ivan Straka > Assignee: Richard Achmatowicz > Fix For: 10.0.0.CR5 > > Attachments: logs > > > There are two tests failing in exteded tests in clusteringejb2 package in AS TS. > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceSpecifiedByDescriptor > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceAnnotatedBean > both with exception > {code} > Error Message > EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > Stacktrace > java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy28.create(Unknown Source) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.loadbalance(RemoteStatelessFailoverTestCase.java:262) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.testLoadbalanceAnnotatedBean(RemoteStatelessFailoverTestCase.java:224) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1341) Expose IO worker runtime data / statistics

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1341?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1341: -------------------------------- Summary: Expose IO worker runtime data / statistics (was: Remoting worker threads runtime current size, queue size, etc are not visible) > Expose IO worker runtime data / statistics > ------------------------------------------ > > Key: WFCORE-1341 > URL: https://issues.jboss.org/browse/WFCORE-1341 > Project: WildFly Core > Issue Type: Enhancement > Components: Remoting > Affects Versions: 2.0.7.Final > Reporter: Brad Maxwell > Assignee: Tomaz Cerar > > The remoting subsystem uses a worker-thread-pool which can be configured such as shown below. > The runtime thread pool information is not exposed when doing read-resource: > {code} > /subsystem=remoting:read-resource(include-runtime=true, recursive=true) > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:1.1"> > <worker-thread-pool > read-threads="1" > task-core-threads="4" > task-keepalive="60" > task-limit="16384" > task-max-threads="16" > write-threads="1" > /> > <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> > </subsystem> > {code} > In tuning and runtime diagnosis, it would be useful to see the thread pool information such as the current size, queue-size, largest-thread-count, etc similar to the ejb3 subsystem thread pool: > {code} > /subsystem=ejb3/thread-pool=default:read-resource(include-runtime=true, recursive=true) > "result" => { > "active-count" => 0, > "completed-task-count" => 0L, > "current-thread-count" => 0, > "keepalive-time" => { > "time" => 100L, > "unit" => "MILLISECONDS" > }, > "largest-thread-count" => 0, > "max-threads" => 10, > "name" => "default", > "queue-size" => 0, > "rejected-count" => 0, > "task-count" => 0L, > "thread-factory" => undefined > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1341) Remoting worker threads runtime current size, queue size, etc are not visible

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1341?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1341: ------------------------------------- it should be under /subsystem=io/worker=default:read-resource(include-runtime=true) but we don't currently expose any runtime data there either, that is why I didn't close issue as we should definitely improve that. > Remoting worker threads runtime current size, queue size, etc are not visible > ----------------------------------------------------------------------------- > > Key: WFCORE-1341 > URL: https://issues.jboss.org/browse/WFCORE-1341 > Project: WildFly Core > Issue Type: Enhancement > Components: Remoting > Affects Versions: 2.0.7.Final > Reporter: Brad Maxwell > Assignee: Tomaz Cerar > > The remoting subsystem uses a worker-thread-pool which can be configured such as shown below. > The runtime thread pool information is not exposed when doing read-resource: > {code} > /subsystem=remoting:read-resource(include-runtime=true, recursive=true) > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:1.1"> > <worker-thread-pool > read-threads="1" > task-core-threads="4" > task-keepalive="60" > task-limit="16384" > task-max-threads="16" > write-threads="1" > /> > <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> > </subsystem> > {code} > In tuning and runtime diagnosis, it would be useful to see the thread pool information such as the current size, queue-size, largest-thread-count, etc similar to the ejb3 subsystem thread pool: > {code} > /subsystem=ejb3/thread-pool=default:read-resource(include-runtime=true, recursive=true) > "result" => { > "active-count" => 0, > "completed-task-count" => 0L, > "current-thread-count" => 0, > "keepalive-time" => { > "time" => 100L, > "unit" => "MILLISECONDS" > }, > "largest-thread-count" => 0, > "max-threads" => 10, > "name" => "default", > "queue-size" => 0, > "rejected-count" => 0, > "task-count" => 0L, > "thread-factory" => undefined > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5522) split artemis journal in its own module

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5522?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5522: -------------------------------- Fix Version/s: 11.0.0.Alpha1 > split artemis journal in its own module > --------------------------------------- > > Key: WFLY-5522 > URL: https://issues.jboss.org/browse/WFLY-5522 > Project: WildFly > Issue Type: Enhancement > Components: JMS, Transactions > Affects Versions: 10.0.0.CR2 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > The org.jboss.jts is depending on the org.apache.activemq.artemis only for its journal functionality but get all the module dependencies (including messaging stuff) that is not used at all. > The org.apache.activemq.artemis should be split with a separate module for its journal containing the journal jar + commons jar + native lib required for libAIO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2009) TCP/TCP_NIO: make SO_REUSEADDR configurable

by Bela Ban (JIRA)

Bela Ban created JGRP-2009: ------------------------------ Summary: TCP/TCP_NIO: make SO_REUSEADDR configurable Key: JGRP-2009 URL: https://issues.jboss.org/browse/JGRP-2009 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.8, 4.0 Before binding a {{ServerSocket}} or {{ServerSocketChannel}}, let the user configure whether of not to reuse addresses by setting option {{SO_REUSEADDR}} (and possibly {{SO_REUSEPORT}}?). See https://issues.jboss.org/browse/ISPN-6099 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2008) Remove MuxRpcDispatcher

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2008?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2008. ---------------------------- Resolution: Done > Remove MuxRpcDispatcher > ----------------------- > > Key: JGRP-2008 > URL: https://issues.jboss.org/browse/JGRP-2008 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > Can be replaced by using fork stacks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2008) Remove MuxRpcDispatcher

by Bela Ban (JIRA)

Bela Ban created JGRP-2008: ------------------------------ Summary: Remove MuxRpcDispatcher Key: JGRP-2008 URL: https://issues.jboss.org/browse/JGRP-2008 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0 Can be replaced by using fork stacks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6015) Testing JDBC connection is causing it to be created

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-6015?page=com.atlassian.jira.plugin.... ] Heiko Braun resolved WFLY-6015. ------------------------------- Fix Version/s: 10.0.0.Final Resolution: Done > Testing JDBC connection is causing it to be created > --------------------------------------------------- > > Key: WFLY-6015 > URL: https://issues.jboss.org/browse/WFLY-6015 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.0.0.CR5 > Environment: Mac OS X El Captain with latest update > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > MariaDB - with MariaDB JDBC driver deployed > Reporter: Renann Prado > Assignee: Harald Pehl > Fix For: 10.0.0.Final > > > Testing JDBC connection is causing it to be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1334) Allow disabling audit log rotation

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1334?page=com.atlassian.jira.plugi... ] Tomas Hofman edited comment on WFCORE-1334 at 1/29/16 3:06 AM: --------------------------------------------------------------- Sure, here: https://github.com/wildfly/wildfly-core/blob/e737eff554ee433ca54835154fd6... was (Author: thofman): https://github.com/wildfly/wildfly-core/blob/e737eff554ee433ca54835154fd6... > Allow disabling audit log rotation > ---------------------------------- > > Key: WFCORE-1334 > URL: https://issues.jboss.org/browse/WFCORE-1334 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 2.0.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1301554 > org.jboss.as.controller.audit.FileAuditLogHandler always rotates audit-log.log at startup/reload. An option to disable log rotation is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1046) Threads blocking during ReteWorkingMemory initialization of facts

by Akshay Gehi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1046?page=com.atlassian.jira.plugi... ] Akshay Gehi updated DROOLS-1046: -------------------------------- Steps to Reproduce: Create a drools file with the following condition: {noformat} rule "slowWhenCondition" when eval(mySlowCondition(fact)) then end {noformat} Create a StatefulSession and fire all the rules from multiple threads. Observe the threads in Blocking state using JVisualVM or Stack Trace. was: Create a drools file with the following condition: rule "slowWhenCondition" when eval(mySlowConditionFromDatabase(fact)) then end Create a StatefulSession and fire all the rules from multiple threads. Observe the threads in Blocking state using JVisualVM or Stack Trace. > Threads blocking during ReteWorkingMemory initialization of facts > ----------------------------------------------------------------- > > Key: DROOLS-1046 > URL: https://issues.jboss.org/browse/DROOLS-1046 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Akshay Gehi > Assignee: Mario Fusco > > While initializing facts for the first time the following method in ReteWorkingMemory is invoked: > {code:java} > private final Integer syncLock = 42; > public void initInitialFact() { > if ( initialFactHandle == null ) { > synchronized ( syncLock ) { > if ( initialFactHandle == null ) { > // double check, inside of sync point incase some other thread beat us to it. > initInitialFact(kBase, null); > } > } > } > } > {code} > Since the synchronized lock is taken on a Integer constant variable, the same object gets used across different threads. This causes the initialization of all the ReteMemoryObjects to wait in the initInitialFact() method across different threads. > The lock should be taken on Object lock = new Object() instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016