[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Hi Nick, Apparently as this seems to be a long exisitng bug in JBoss, I have to look into handling the failover in the client as you have done for the time being. I am not too sure of the patch posted in JIRA nor have time to test it. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888498#3888498 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888498 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
http://wiki.jboss.org/wiki/Wiki.jsp?page=RetryInterceptor View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888581#3888581 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888581 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Created an issue for this case in JIRA. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888209#3888209 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888209 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
The status of the Jira issue can be tracked at the below URL http://jira.jboss.com/jira/browse/JBAS-2074 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888210#3888210 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888210 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
[EMAIL PROTECTED] wrote : If you keep having this probelm, you can open up a Jira issue under JBossAS/clustering component. Please attach your test case as well. | | Thanks, | | -Bem Ben this is very bad advice. Before anyone reports a bug that should: 1) Test the latest version 2) Identify what the problem exists, NOT I have a problem. 3) Make sure it is a bug and not some configuration issue with JBoss/network/os/other Just saying I have a problem getting it to work in some old version is not a bug report. It is a help request that belongs in the forums until the underlying issue is identified as a bug in the code. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888217#3888217 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888217 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
The alternative would be that we just ditch the forums and let people use JIRA to let people ask questions. Something we are not going to do. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888220#3888220 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888220 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Hi, Is it solved by using the latest JBoss version? Please clarify. Would appreactie if someone could give me pointers in the right direction towards getting this resolved. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888228#3888228 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888228 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Adrian, yes, it is a bit hasty. But in this case, I have read the question and I am giving Vignesh the benefit of the doubt since he has been able to help answering some forum posts. I seldom ask a user to create a Jira issue. (As a matter of fact, I don't encourage people to create a Jira unless it is necessary :-) -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888237#3888237 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888237 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
vignesh76 wrote : Hi, | | Is it solved by using the latest JBoss version? | Suck it and see. :-) anonymous wrote : | Please clarify. Would appreactie if someone could give me pointers in the right direction towards getting this resolved. | Read the twenty questions from the link I posted on the kind of questions you need to ask yourself to resolve your problem. Or post here to at least provide enough information that we can help you. You need to identify what the problem is, not post IT DOES NOT WORK. e.g. In this case, * Is the cluster rejoining? Show the cluster view changes in comparison to the client requests. * Did the client receive the up-to-date view of the cluster? i.e. When did the client know about the cluster view changes? * Are the dns/ip addresses that the client is told to contact correct? i.e. is the client even contacting the correct machines? * etc. We are not going to go through a long thread of request/response trying to get your configuration, logging, example code, etc. OFF TOPIC: AFAIK (my information may be out-of-date), there isn't a single JDK vendor that will support you on Fedora? They will support you Redhat EL. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888241#3888241 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888241 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Appreciate your help here. All I requested was a little help that too in a polite manner and did not expect sarcastic comments for responses. If the attitude is not to help, then people should rather ignore instead of posting such responses. Also the users cannot be expected to think at the same level as experts or developers and raise the same kind of questions an expert would raise, that would defeat the purpose of having this forum. If not for the JIRA issue, I wouldn't have had to hear all this. Anyway.. I believe my posts were quite reasonable and not dumb and had sufficent information to answer some if not all the questions raised. * Is the cluster rejoining? Show the cluster view changes in comparison to the client requests. --Shall provide more info such as console output for evidence that the cluster view was getting updated when a node left and joined the cluster. * Did the client receive the up-to-date view of the cluster? i.e. When did the client know about the cluster view changes? --Not fully clear what you are asking here. The client JBoss instance was running all the time when I stopped the active instance and then checked failover from the client bu making a new request. There were not active requests to the clustered nodes while stopping or starting a node again to join the cluster. * Are the dns/ip addresses that the client is told to contact correct? i.e. is the client even contacting the correct machine -- If the IP addresses had been wrong the initial failover, that I have cleary emphasized as working in my post would have not worked at all. I shall test the scenarios again with the latest verion of JBoss and all I asked was a clarification that whether this was a known issue in version 4.0.1 as the recent posts have been more diverted towards setting ethics while totally ignoring user issues for which the forum is meant to be. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888257#3888257 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888257 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
vignesh76 wrote : Appreciate your help here. All I requested was a little help that too in a polite manner and did not expect sarcastic comments for responses. | If you don't want sacrastic comments, I'll avoid responding to your posts in future :-) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888261#3888261 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888261 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Yeah, How would you react if someone mocked you just because he was in a superior technical position! Being superior doesn't give someone the authority to be arrogant and mock polite strangers. I shall continue to wait for an appropriate solution from the rest of the JBoss community if not from the Director of JBoss support team. Thanks for whatever assistance and leads you have provided so far.. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888263#3888263 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888263 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
vignesh76 wrote : | 1) I am not sure about whether they are cached or not as my role is more into system implementation but I shall try to find out. However could you tell me how does this caching affect the failover process. Also, what if the web application is not in use i.e. not in the midst of any ejb calls when the failover is needed. I tested with a scenario where the web application was totally idle (logged out) and after stopping the active instance, I tried to login to the application again when this error occurs. | The reason I asked you about the caching if the interfaces is because JBoss uses smart proxies to handle the failover to the different nodes in the cluster. Each time an invocation is passed to the server if the members of the cluster have changed the response will contain the new list of members so the smart proxy will have an up to date list of members for the next invocation. vignesh76 wrote : | 1) A and B running (B is active node) --OK | | 2) A running, shutdown B (A becomes active node) --OK | | 3) Restarted B, shutdown A (B should become active node now)--Service Unavailable | Looking at your example the list of nodes in the cluster has completely changed between invocation 2 and 3, it would help a lot to know where you obtain the references to the remote interfaces, where they are reused and if they are recreated at all. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888279#3888279 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888279 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
vignesh76; darranl has outlined exactly what we were experiencing making HA calls to our middleware servers. The scenario was this: 1) My servers start up and make an HA-JNDI lookup and acquire a remote to the already running middleware servers. 2) My servers issue several calls per minute all day long. During this time, provided at least one server in the middleware cluster remains running across two invocations by my servers, the calls never fail. At the same time, the middleware engineers can add or remove servers from the middleware cluster without issue, provided the stricture outlined above. 3) The traffic from my servers against the middleware servers slows down around 11 PM and cease all together around 2 PM, and do not pick up again until around 6 AM. 4) The middleware engineers decided to reboot all their servers starting at 4:30 AM. They think that if they stagger the reboots, there will be no interruption, but since there are no calls from my servers during that time, when 6 AM rolls around, all my server's middleware calls fail with a ServiceUnavailable exception. Our resolution was to always trap the invocation exception, determine if the cause was ServiceUnavailable, and if so, we reinitialized the [cached] remote and poof. Problem solved. There was a little bit of overhead when the re-init occured, on account of the HA-JNDI lookup, but since it only occured once per server per day, it was negligible. If the call failed again after the re-init, then we throw a fatal exception and the bat-phone rings. //Nicholas View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888295#3888295 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888295 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
nickman wrote : | darranl has outlined exactly what we were experiencing making HA calls to our middleware servers. | What it describes is an orphaned client. It only affects protocols like RMI where the stub can be invalidated by a server reboot. i.e. the RMI server is available, but it is no longer accepting requests from previous clients. Rebooting the entire cluster will invalidate JBoss's JRMPHA proxy, i.e. all the stubs are broken. :-( anonymous wrote : | Our resolution was to always trap the invocation exception, determine if the cause was ServiceUnavailable, and if so, we reinitialized the [cached] remote and poof. Problem solved. | That is the well known solution to the rmi issue, clustered or otherwise. For JBoss working around the problem for you automagically http://www.jboss.org/?module=bbop=viewtopict=58984 http://docs.jboss.org/jbossas/javadoc/4.0.2/org/jboss/proxy/ejb/RetryInterceptor.html http://jira.jboss.com/jira/browse/JBAS-1330 Of course, you could always use another protcol like HTTP(S) HA which doesn't have the stub invalidation problem at server reboot. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888300#3888300 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888300 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Hi Guys, Thanks, really appreciate your inputs. Nick, I am facing the exact same problem as you have described and I believe the failover should be transparent rather than the client having to handle it. We are not caching the interfaces as well. In fact I have just tested with the latest production version of JBoss (4.0.2) and this problem does not happen in that version. Just needed a straight forward answer from the guys who knew it without the big hoo-ha! The problem happens in JBoss (MX MicroKernel) [4.0.1 (build: CVSTag=JBoss_4_0_1date=200412230944)] and I do not know whether it's due to a bug, OS, JVM or some other issue but it's definitely not a configuration problem as I used the exact same configuration while testing with 4.0.2. This could have been fixed in 4.0.1 sp1 though I don't know nor have time to test in that version. Probably someone who has already done could clarify. Thanks again. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888305#3888305 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888305 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Hey Guys, I still encounter that error even with the latest release [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)]. I got to go now though I shall do detailed testing tomorrow to confim my results and post my detailed analysis. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3888307#3888307 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3888307 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Thanks Ben and Darran, Forgot to mention the JBoss version, it is 4.0.1. 1) I am not sure about whether they are cached or not as my role is more into system implementation but I shall try to find out. However could you tell me how does this caching affect the failover process. Also, what if the web application is not in use i.e. not in the midst of any ejb calls when the failover is needed. I tested with a scenario where the web application was totally idle (logged out) and after stopping the active instance, I tried to login to the application again when this error occurs. 2) Yes, I ensured that one of the nodes was always up and that the clustering info maintained by this node had been updated after I shut down the active instance and beforing using the web application again to make ejb calls. 3) Yes, one of the nodes was up and ready with updated clustering info after I shutdown the active node and before making the next request from the web application to test failover. I would like to emphasize here that intially it worked, i.e suppose I haves 2 clustered nodes A and B, below are the test cases tested and the results I observed. I tested with one browser instance accessing the web app running on a 3rd instance C. Also, for each test I used the same 2 use cases in the web app to check failover. 1) A and B running (B is active node) --OK 2) A running, shutdown B (A becomes active node) --OK 3) Restarted B, shutdown A (B should become active node now)--Service Unavailable 4) Restarted instance C (B becomes active node now)-- OK 5) Restarted A, B running (B is active, from step 4)--OK 6) A running, Shutdown B (A should become active)--Service unavailable. I hope this brings more clarity to this issue and leads to a quick solution. Otherwise I guess I would need to create a Jira issue as Ben has suggested. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3887952#3887952 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3887952 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
If you keep having this probelm, you can open up a Jira issue under JBossAS/clustering component. Please attach your test case as well. Thanks, -Bem View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3887797#3887797 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3887797 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Failover problem
Does your web application cache the interfaces that are being used or do you perform the lookups each time? As part of your testing did you make sure at least one of the nodes was up all the time so when each node is started it can join the original cluster or at some points were all of the nodes shut down? Finally for the next access from the web application was one of the nodes up during the previous request still available? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3887804#3887804 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3887804 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
