This application fails because it does not meet the application specifications. The sepcification states that "URLyBird" is a broker of discount hotel rooms. They take bookings only within 48 hours of the start of room occupancy. The submission does not meet this requirement. The application allows bookings for any rom an any time with no date checking. It even allows users to book rooms for dates in the past."
When you submit your assignment, each part (client and server) must be executable using a command of this exact form:
java -jar <path_and_filename> [<mode>]
Should I write user guide for server mode?
Can I change the DBAccess interface comments from sun?
The first point is that I don't understand why we should implement explicitly locking
Or the explicit locking is necessary to avoid deadlocks? Please clarify me
I have no idea how I can test the locking functionality.Please give me some advices and usefull links to read about this.
java.rmi.ServerException: RemoteException occurred in server thread; nested exce ption is:
java.rmi.AccessException: Registry.Registry.rebind disallowed; origin /192.168.1.1 is non-local host
java.rmi.ConnectException: Connection refused to host: 192.168.0.1; nested exception is: java.net.ConnectException: Connection timed out: connect
So you start your server in one window: java -jar runme.jar server
And then you start your network client in another window: java -jar runme.jar
Then you configure the network client to use localhost as the network server
Everything seems to work correctly, searches and bookings.
Then you kill the server (that is, the java -jar runme.jar server application), but the network client continues to work correctly?
You're still able to do searches and bookings?
Are you absolutely sure that your network client is running in network client mode rather than standalone mode. If it's running in standalone mode that would explain the symptoms (although not the logging?!?)