-
1. Re: Transactions getting failed
rvansa Jul 29, 2015 3:19 AM (in response to rameshprml)Please provide more verbose description of those failures, logs and your configuration.
-
2. Re: Transactions getting failed
rameshprml Jul 29, 2015 8:53 AM (in response to rvansa)Hi radim,
Thanks for your reply, We have formed cluster with the three nodes (dl360x4500, dl360x3826, dl360x2868) and we have down the machine (dl360x3826) from the cluster and then we have saw transaction failure for 4-5 seconds across the cluster nodes. Also, I have attached the log file for the same issue.
Requesting you to provide guidance to resolve this.
Thanks,
Ramesh P
-
gc.log.0_dl360x4500.current.zip 762 bytes
-
is_dl360x2868.log.zip 11.0 KB
-
is_dl360x3826_Down.log.zip 2.7 KB
-
is_dl360x4500.log.zip 10.9 KB
-
server_dl360x2868.log.zip 39.3 KB
-
server_dl360x3826.log.zip 12.3 KB
-
server_dl360x4500.log.zip 35.8 KB
-
-
3. Re: Transactions getting failed
rvansa Jul 29, 2015 9:49 AM (in response to rameshprml)Those logs contain multiple server restarts with some errors as the server is restarted without killing another instance first - could you isolate the issue? Anyway, I can't find any exception thrown to the user code - what exactly is your issue?
-
4. Re: Transactions getting failed
rameshprml Jul 29, 2015 1:25 PM (in response to rvansa)Hi,
I have attached the updated log files for the same scenario for your review. Kindly do let me know if you need any information on this.
Regards,
Ramesh P
-
gc.log.0_4500.current.zip 750 bytes
-
is_2868.log.zip 8.2 KB
-
is_3826.log.zip 7.7 KB
-
is_4500.log.zip 6.2 KB
-
server_2868.log.zip 8.2 KB
-
server_3826.log.zip 6.0 KB
-
server_4500.log.zip 3.1 KB
-
5. Re: Transactions getting failed
rvansa Jul 30, 2015 3:03 AM (in response to rameshprml)Seems like a message was sent to the killed node, but the mapping from symbolic to physical addresses was lost and some reliable delivery protocol is trying to deliver that without success. No harm done, probably. If you want to find the root cause, we would need to see who sent that message - set on trace logging for org.jgroups, please.