Bug 751730

Summary: latest update break rmi
Product: Red Hat Enterprise Linux 5 Reporter: Levente Farkas <lfarkas>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7CC: asura, jvanek, omajid, psplicha, thoger
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 06:51:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Levente Farkas 2011-11-07 11:26:03 UTC
exactly the same true here es in rhel-6.1 #751203
the update
java-1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
break rmi. ie. even the simplest rmi tutorial example no longer works while it
was working on version:
java-1.6.0-openjdk-1.6.0.0-1.22.1.9.8.el5_6

as it's a regression imho it's critical!

Comment 1 Levente Farkas 2011-11-10 17:38:45 UTC
afert a long debugging it's turn out with the latest java update (el5 and el6 too) it's no longer enough to start 
rmiregistry &
in this way, but you've to explicitly specify the codebase which was not the case before (and take care about the correct " too) eg:
rmiregistry "-J-Djava.rmi.server.codebase=file:///usr/share/java/a.jar file:///usr/share/java/b.jar" &
imho at least a technical addon info would be useful for it...

Comment 2 Levente Farkas 2012-01-10 10:07:58 UTC
at least could you build an src.rm for me for rhel-5.7 to test?
thanks.

Comment 10 Andrei 2012-01-24 20:39:13 UTC
Why is access denied for viewing 
https://bugzilla.redhat.com/show_bug.cgi?id=751203 ?

Comment 11 errata-xmlrpc 2012-02-21 06:51:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0314.html