Issue Details (XML | Word | Printable)

Key: SAILFIN-1594
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Satish Kumar
Reporter: elnehoo
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
sailfin

problems with HA remote broker configuration

Created: 30/Jan/09 04:21 AM   Updated: 19/Aug/09 04:27 AM   Resolved: 19/Aug/09 04:27 AM
Component/s: deployment
Affects Version/s: 1.0
Fix Version/s: milestone 1

Time Tracking:
Not Specified

File Attachments: 1. Text File BrokerSetup_Sailfin.ppt (85 kB) 30/Jan/09 04:22 AM - elnehoo
2. Text File log.txt (8 kB) 30/Jan/09 04:24 AM - elnehoo
3. Text File logs_2009_01_09_15_46.tgz (432 kB) 30/Jan/09 04:27 AM - elnehoo

Environment:

Operating System: Linux
Platform: All


Issuezilla Id: 1,594
Tags:
Participants: elnehoo and Satish Kumar


 Description  « Hide

We are having problems with defining a High Available (HA) remote broker setup
(two payloads).

We have following configuration.

  • JMS Hosts (on a traffic instance)
    -> traffic_instance_PL_2_3_JMS_host
    -> traffic_instance_PL_2_4_JMS_host
  • Default JMS Host
    -> traffic_instance_PL_2_3_JMS_host

During startup of an instance ‘transaction-recovery’ is performed for JMS
(before EJBs are loaded).

The implementation in Glassfish is such that it tries to make a connection to
all hosts in the “JMS Hosts� list (also called ‘AddressList’).
So a PL will be waiting/blocking (for a certain time) until the broker on the
other PL is ready.

We have tested a scenario where PL_2_4 was shutdown.
During startup of PL_2_3 we see that the PL_2_3 tries to connect to broker
PL_2_4 for about 2.5 minutes (10 retries).
This happens twice because of 2 connection factories for EventQueue and
RegistrationQueue.
This means the traffic instance has a (max) delay of about 5 minutes before it
continues (with loading of EJB’s).

As far as can be see there are no configuration parameters to influence this
behavior for “transactions-recovery�.

Can you please indicate on how to setup a working REMOTE broker setup.
Attachments show more information.



elnehoo added a comment - 30/Jan/09 04:22 AM

Created an attachment (id=951)
Powerpoint sheet explaining problem in more detail.


elnehoo added a comment - 30/Jan/09 04:24 AM

Created an attachment (id=952)
logfile indicating long startup time remote broker


elnehoo added a comment - 30/Jan/09 04:27 AM

Created an attachment (id=953)
server.log PL_2_3 show the retry attempts to non active broker PL_2_4


elnehoo added a comment - 30/Jan/09 04:29 AM

Forgot to mention that startup of broker also can take quite a while. We would
like to know why this is the case (added special logfile which shows this).


Satish Kumar added a comment - 30/Jan/09 05:03 AM

Reassiging the issue to Satish


elnehoo added a comment - 03/Mar/09 07:32 AM

updated priority to P3, we still don't have a HA broker setup !!


Satish Kumar added a comment - 19/Aug/09 04:27 AM

The time required for the initial start up can be easily changed by reducing
the following values in the jms-service element of domain.xml

reconnect-interval-in-seconds to say 1 sec
reconnect-attempts to say 1
addresslist-iterations to a lower value of 1