[JBoss JIRA] (WFLY-9261) Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9261?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9261:
-----------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Beta1)
> Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9261
> URL: https://issues.jboss.org/browse/WFLY-9261
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Flavia Rainone
> Assignee: Martyn Taylor
> Fix For: 12.0.0.CR1
>
>
> When rebooting a cluster node that uses singleton cluster mdbs, we get this error message:
> {noformat}
> 2017-07-25 16:08:54,426 ERROR [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.HelloWorldMDBQueuedea3e995-713c-11e7-85f2-b8f6b112daf7 on ClusterConnectionImpl@1129705701[nodeUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7, connector=TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7]
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294)
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029)
> at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9417?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9417:
-----------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Beta1)
> No default-response-code during deployment sent
> -----------------------------------------------
>
> Key: WFLY-9417
> URL: https://issues.jboss.org/browse/WFLY-9417
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 11.0.0.CR1
> Reporter: Nero M
> Assignee: Stuart Douglas
> Fix For: 12.0.0.CR1
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10.
> When a *.dodeploy file exists during server-start. The Default response code
> e.g.
> <host name="default-host" alias="localhost" default-response-code="503">
> Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout.
> If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete.
> (After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms
> I think the server should not "hang" during the deployment-time, just like it was on WF10.
> Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9415) Add test cases to cover EJB client clustered session creation
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9415?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9415:
-----------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Beta1)
> Add test cases to cover EJB client clustered session creation
> -------------------------------------------------------------
>
> Key: WFLY-9415
> URL: https://issues.jboss.org/browse/WFLY-9415
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 11.0.0.CR1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 12.0.0.CR1
>
>
> EJB client session creation involves creating a proxy for a SFSB deployed on a remote server, which has the side effect of creating a session instance on the chosen target node.
> Whether or not the operation is successful depends on three factors:
> * the connections defined in the EJB client configuration
> * the server environment in which the client is executing
> * any strong affinity set by the client
> These tests consider session creation in a clustered environment. The default server environment is a cluster called "ejb" with two nodes, "node-0" and "node-1".
> The following test scenarios are covered:
> 1. "normal" scenario
> * client configuration: points to node-0
> * server environment: module deployed on cluster "ejb" = {node-0, node-1}
> 2. "failover" scenario
> * client configuration: points to node-0
> * server environment: module deployed on cluster "ejb" = {node-1}
> 3. "bad connection" scenario
> * client configuration: points to node-2 (non-existent)
> * server environment: module deployed on cluster "ejb" = {node-0, node-1}
> As mentioned earlier, these tests operate in a single two-node cluster environment. A third singleton, non-clustered node added to the available environment would permit more complex scenarios (where we could test cluster affinity specification more directly).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9403) Unable to deploy clustered ejb in a mixed domain.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9403?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9403:
-----------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Beta1)
> Unable to deploy clustered ejb in a mixed domain.
> -------------------------------------------------
>
> Key: WFLY-9403
> URL: https://issues.jboss.org/browse/WFLY-9403
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 11.0.0.CR1
> Reporter: Brad Maxwell
> Assignee: Yeray Borges
> Fix For: 12.0.0.CR1
>
> Attachments: Clusterejb-0.0.1.jar, domain_EAP7.xml, host_EAP7.xml, host_slave_EAP6.xml
>
>
> Using a ha profile in a mixed domain( i.e EAP 7 as a domain controler and EAP 6.3 as a slave) it does not seem possible to deploy ejb successfully.
> While deploying a simple @clustered ejb on EAP 6.3 server below exception was thrown. This issue is easily replicated.
> {code:java}
> 19:12:11,886 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named CounterBean in deployment unit deployment "Clusterejb-0.0.1.jar" are as follows:
> java:global/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:app/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:module/CounterBean!com.test.Counter
> java:jboss/exported/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:global/Clusterejb-0.0.1/CounterBean
> java:app/Clusterejb-0.0.1/CounterBean
> java:module/CounterBean
> 19:12:12,089 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "Clusterejb-0.0.1.jar" (runtime-name : "Clusterejb-0.0.1.jar")
> 19:12:12,090 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.ejb.cache.cluster.simple (missing) dependents: [service jboss.ejb.cache.cluster]
> 19:12:12,093 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 2654ms - Started 185 of 293 services (14 services failed or missing dependencies, 117 services are lazy, passive or on-demand)
> {code}
> I have attached the configuration files for both EAP 7 and EAP 6.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9561) HttpServletRequest.login(username, password) not creating HttpSession if it doesn't already exist. (Elytron)
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9561?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9561:
-----------------------------
Fix Version/s: 12.0.0.CR1
(was: 12.0.0.Beta1)
> HttpServletRequest.login(username, password) not creating HttpSession if it doesn't already exist. (Elytron)
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9561
> URL: https://issues.jboss.org/browse/WFLY-9561
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 11.0.0.Final
> Reporter: Stanislav Grushevskiy
> Assignee: Darran Lofthouse
> Fix For: 12.0.0.CR1
>
> Attachments: test.zip
>
>
> If Elytron security domain (in WildFly 11, default "standalone.xml") is used for programmatic login, cookie "JSESSIONID" is not set in response. So following requests are sent without "JSESSIONID".
> @Path("login")
> public class LoginService {
> @Context
> private HttpServletRequest request;
> @POST
> public void login(LoginForm form) throws ServletException {
> request.login(form.getLogin(), form.getPassword());
> }
> }
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <security-domain>application-security-domain</security-domain>
> </jboss-web>
> If I add manual interaction with Session in login method, "JSESSIONID" is set.
> OR
> If I delete "jboss-web.xml" and default old "ApplicationRealm" is used, "JSESSIONID" is set.
> "JSESSIONID" is set in WildFly 10.0.0.Final and in 10.1.0.Final, because there is no Elytron there and "ApplicationRealm" is used.
> Test project is attached, create application user (add-user.sh) with username "wildfly" and password "wildfly".
> Run "mvn wildfly:deploy".
> Go to http://localhost:8080/test/test.html and press "Login" button and then "Check Auth".
> In this project you can uncomment code below (// uncomment the row below to get it working with elytron) to add session interaction or comment code below (<!-- comment the row below to use default ApplicationRealm from old security system, not elytron -->) to use old "ApplicationRealm".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months