[Xen-bugs] [Bug 55] New: JavaRMI and Xen problem

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=55

           Summary: JavaRMI and Xen problem
           Product: Xen
           Version: 2.0
          Platform: x86
               URL: http://lists.xensource.com/archives/html/xen-devel/2005-
                    04/msg00860.html
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: sai.dharanikota@xxxxxxxxx


http://lists.xensource.com/archives/html/xen-devel/2005-04/msg00915.html
The detailed problem and the discussion is explained in the archives with the
name "JavaRMI and Xen problem".
----------------------------------------------------------------------------------
I am facing a strange problem with Java RMI and Xen. I will describe the problem
as well as the experimental results.

 

Setup:

 

I have taken 2 machines, machine1 and machine2. Machine1 is the client and
Machine2 is the server. The RMI registry is available on Machine2. I have a RMI
application (a kind of service) that is running on Machine2 on port 4001. An
init script starts the service at boot time on port 4001.

 

Scenario1: Machine2 is booted with xen as the kernel

The client on Machine1 tries to look up the object that it needs to contact in
the registry on Machine2. The object to be available in the RMI registry on
Machine2 takes around 2 minutes.

 

Scenario2: Machine2 is booted with Linux kernel (Xen is not involved at all)

The client on Machine1 tries to look up the object that it needs to contact in
the registry on Machine2. The object to be available in the RMI registry on
Machine2 takes around 21 seconds.

 

In scenario1 I am not starting any virtual machines. The service is available in
Domain0 (Machine2). Nothing is changed except the kernel to boot. But, the
results look strange. The Xen and Java RMI stuff looks very strange. The problem
here is, on a Xen machine the Java object to be available in the RMI registry
takes very long time. According to our experiments it shows that it is
approximately 6 times slow. 
--------------------------------------------------------------------------------



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs