[JBoss JIRA] Created: (JBAS-4893) JvmRouteValve (UseJK) for non session replication setup
by Takayoshi Kimura (JIRA)
JvmRouteValve (UseJK) for non session replication setup
-------------------------------------------------------
Key: JBAS-4893
URL: http://jira.jboss.com/jira/browse/JBAS-4893
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Takayoshi Kimura
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:
* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again
Enabling JvmRouteValve can prevent last failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBAS-3556) Add non-integration based testing to cluster module
by Brian Stansberry (JIRA)
Add non-integration based testing to cluster module
---------------------------------------------------
Key: JBAS-3556
URL: http://jira.jboss.com/jira/browse/JBAS-3556
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering, Test Suite
Reporter: Brian Stansberry
All the unit tests for the AS cluster module are run via the testsuite tests-clustering target, which starts two AS instances. This is painful and time consuming and discourages writing of simple unit tests that exercise a particular class, with no need for a larger integration.
Need to set up a src/tests tree in the cluster module, add simple unit tests to it, and integrate that into the overall testsuite run. The security module has this kind of setup; look to that to see how the overall testsuite integration is done.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JGRP-646) ConnectionTable problem after a while in 2 node cluster
by Martin Vecera (JIRA)
ConnectionTable problem after a while in 2 node cluster
-------------------------------------------------------
Key: JGRP-646
URL: http://jira.jboss.com/jira/browse/JGRP-646
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4.1 SP4
Environment: Two physical machines both running RHEL5, Sun JVM 1.5.0_12, full SOA-P 4.2.0.IR8 based on EAP 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200711291835), Orcale DB on a separate machine
Reporter: Martin Vecera
Assigned To: Bela Ban
Reproducible: 100%
1. I took full IR8 and used dbinstall (https://svn.corp.jboss.com/repos/soa/trunk/qa/dbinstall/) for the 'all' configuration to use Oracle DB.
2. I unsecured jmx-service-invoker.
3. I copied the SOA-P to the second node.
4. I changed the server peer id on the both copies to be different.
5. I started the first node, it was successful.
6. I started the second node successfully as well.
7. I let it be for half an hour.
8. This appeared in the log files:
Node 1:
2007-12-13 10:57:07,502 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg
2007-12-13 10:57:07,502 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too
Node 2:
2007-12-13 10:57:08,927 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg
2007-12-13 10:57:08,928 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too
It doesn't seem like there's anything related to the problems in the logs (no exceptions, no other JGroups related output...).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months