Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

java.rmi.UnmashalException

 
Holmes Wong
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, guys:
I am testing my remote server and my client. I am using RMI. I tried something not very logical,
but it may happen sometimes: I changed number of
seats and booked several times in one client session, the third or fourth time the GUI started to freeze, and got the above exception if I desconnect the server. It is not very logical for a client to book several times, but it may happen when a client needs more seats after he first time booked. Do we need to fix this? Thanks.
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's a tough one. I hope that there might be a way to not have your GUI freeze. The biggest and toughest part is to try and find where in the code it starts to freeze.
Does it freeze if you book 3 or 4 times on 3 or 4 different flights?
On the 3rd or 4th time are there still seats available? if not, maybe there is some kind of infinite loop in your overbooking code? Just a suggestion.
Mark
 
Holmes Wong
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mark Spritzler:
That's a tough one. I hope that there might be a way to not have your GUI freeze. The biggest and toughest part is to try and find where in the code it starts to freeze.
Does it freeze if you book 3 or 4 times on 3 or 4 different flights?
On the 3rd or 4th time are there still seats available? if not, maybe there is some kind of infinite loop in your overbooking code? Just a suggestion.
Mark

Thanks, Mark.
I was booking on one chosen flight several times. Yes, there are still seats available. Usually on the third or fourth time, the button does not bounce back, it looks like it needs more time to communicate with server. If I restart a client after I book once, there is no problem. Logically, a client will not book on the same flight several times, but in case she needs more seats afterwards, she may book on the same flight again. Maybe I have to consider this case.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic