[JBoss JIRA] (WFLY-5640) RemoteStatelessFailoverTestCase fails with "No EJB receiver available for handling"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5640?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-5640:
---------------------------------
Summary: RemoteStatelessFailoverTestCase fails with "No EJB receiver available for handling" (was: No EJB receiver available for handling)
> RemoteStatelessFailoverTestCase fails with "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)
10 years, 2 months
[JBoss JIRA] (DROOLS-963) Guava Version too old required by KIE-CI
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-963?page=com.atlassian.jira.plugin... ]
Petr Široký resolved DROOLS-963.
--------------------------------
Fix Version/s: 6.4.0.CR1
Assignee: Petr Široký (was: Mario Fusco)
Resolution: Done
This will be fixed in 6.4.0.Final. It got resolved as part of Maven upgrade from 3.2.2 to 3.2.5.
> Guava Version too old required by KIE-CI
> ----------------------------------------
>
> Key: DROOLS-963
> URL: https://issues.jboss.org/browse/DROOLS-963
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.3.0.Final
> Reporter: Mauricio Salatino
> Assignee: Petr Široký
> Fix For: 6.4.0.CR1
>
>
> This might not be fixable, but testing drools (6.3.0.Final) with Arquillian and KIE-CI I found that KIE-CI is using a very very old version of Guava (version 10.x). In order to get it working with Arquillian and Weld I needed to go to middle ground between Weld requirement (version 18) and KIE-CI to get it working. I ended up adding Guava 14 as a direct dependency and that gets the project working.
> I link the pom.xml file that I've used with all the versions: https://github.com/Salaboy/drools-workshop/blob/master/drools-kie-ci-exam...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time
by Richard Janík (JIRA)
[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ]
Richard Janík commented on WFLY-5484:
-------------------------------------
As with comment on WFLY-5932, I've tried with 1.3.16.Final, but I'm still not getting logged out on first try.
> Calling HttpServletRequest.logout() with single sign-on enabled only works every second time
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-5484
> URL: https://issues.jboss.org/browse/WFLY-5484
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Richard Janík
> Assignee: Stuart Douglas
> Priority: Blocker
> Fix For: 10.0.0.CR5
>
> Attachments: reproducer-jbeap-1282.zip
>
>
> See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect
> This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-1045) kie-ci 6.3.0.Final conflicts with newer versions of Guava
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1045?page=com.atlassian.jira.plugi... ]
Petr Široký edited comment on DROOLS-1045 at 1/29/16 6:51 AM:
--------------------------------------------------------------
-[~abaxter] could you please attach simple Maven-based reproducer for this issue? I could not reproduce this issue with 6.3.0.Final, 6.4.0-SNAPSHOT and 7.0.0-SNAPSHOT.-
Sorry, I was too quick. I added the creation of KieScanner object to your reproducer and can now see the issue.
was (Author: psiroky):
[~abaxter] could you please attach simple Maven-based reproducer for this issue? I could not reproduce this issue with 6.3.0.Final, 6.4.0-SNAPSHOT and 7.0.0-SNAPSHOT.
> kie-ci 6.3.0.Final conflicts with newer versions of Guava
> ---------------------------------------------------------
>
> Key: DROOLS-1045
> URL: https://issues.jboss.org/browse/DROOLS-1045
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Adam Baxter
> Assignee: Petr Široký
>
> When using kie-ci with Google's Guava library (v19), we hit the following error: http://stackoverflow.com/questions/32528042/maven-java-lang-illegalaccess...
> We solved this by excluding kie-ci's sisu-guice transitive dependency and including the 3.1.7 version released in 2014.
> Please update kie-ci's dependencies such that this is no longer an issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months