Re: [opensuse] Removing SUSE java?
Randall R Schulz wrote:
Adam,
On Wednesday 26 October 2005 08:13, Adam Schuett wrote:
I am encountering java issues that someone informed me was because I am using the SUSE java distribution, when I need to be using Sun's direct distribution.
How might I go about removing the SUSE distribution, and what residual files will I need to watch for after the fact so that it does not cause problems after installing Sun's package?
I, and perhaps others, would appreciate hearing what kinds of problems you're having and why you think they're related to SuSE's packaging of Sun's Java software.
Could you elaborate a bit?
The problems go very deep, and I was not the author of the code. The basic problem is from communication via DSL lines using VPN, and then accessing the java program on a remote server and the java program then uses an RMI server on an AS400. We tried several things, and since the author refused to admit it was a coding issue (what's so hard about admitting our code could pack a flaw?), someone had tried this on their 9.3 machine and it worked with no more issues. Adam
For the record, I've had no trouble running Java software on my SuSE 10.0 system now (and my 9.3 before it), including Azureus, Tomcat, Eclipse, jEdit, JUDE and a large Java program of my own authorship.
Randall Schulz
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Wednesday 26 October 2005 17:10, Adam Schuett wrote:
The problems go very deep, and I was not the author of the code. The basic problem is from communication via DSL lines using VPN, and then accessing the java program on a remote server and the java program then uses an RMI server on an AS400.
We tried several things, and since the author refused to admit it was a coding issue (what's so hard about admitting our code could pack a flaw?), someone had tried this on their 9.3 machine and it worked with no more issues.
I don't think you mentioned what the symptoms where, but problems with RMI can often be down to bad DNS resolving. You probably already know this, but RMI works in a 2 step process similar to unix RPC. You first connect to a registry and ask for a service and the response is the actual location of the service. If that response contains a bad hostname/ip then your client can end up at a dead-end. For example if you have an entry like 127.0.0.1 myhostname in the hosts file on the RMI server instead of 127.0.0.1 localhost (earlier versions of yast were guilty of this esp. on 9.1) then the response to the service lookup can sometimes resolve to your own machine instead of the server you wanted resulting in either an instant connection refusal, or a lengthy timeout if there are firewalls in place. In short, check that 127.0.0.1 <-> localhost and real ip <-> hostname mappings resolve correctly in both directions on all machines taking part. On the other hand, if its not an RMI problem then I've got no idea ;-) Mike
Adam, On Wednesday 26 October 2005 09:10, Adam Schuett wrote:
Randall R Schulz wrote:
Adam,
On Wednesday 26 October 2005 08:13, Adam Schuett wrote:
I am encountering java issues that someone informed me was because I am using the SUSE java distribution, when I need to be using Sun's direct distribution.
How might I go about removing the SUSE distribution, and what residual files will I need to watch for after the fact so that it does not cause problems after installing Sun's package?
...
Could you elaborate a bit?
The problems go very deep, and I was not the author of the code. The basic problem is from communication via DSL lines using VPN, and then accessing the java program on a remote server and the java program then uses an RMI server on an AS400.
We tried several things, and since the author refused to admit it was a coding issue (what's so hard about admitting our code could pack a flaw?), someone had tried this on their 9.3 machine and it worked with no more issues.
Well, that's not much to go on, but nothing in it suggests that running the Sun JVM as packaged by Sun will differ from running that JVM as packaged and delivered with SuSE Linux. Now, if you haven't installed the Sun (via SuSE) packages and are instead using gcj and / or gij, then you should not expect a very high degree of compatibility. Are you sure your SuSE installation is using their (SuSE / Novell's) Sun JVM and not the GCJ one?
Adam
Randall Schulz
On Wednesday 26 October 2005 11:10, Adam Schuett wrote:
Randall R Schulz wrote:
Adam,
On Wednesday 26 October 2005 08:13, Adam Schuett wrote:
I am encountering java issues that someone informed me was because I am using the SUSE java distribution, when I need to be using Sun's direct distribution.
How might I go about removing the SUSE distribution, and what residual files will I need to watch for after the fact so that it does not cause problems after installing Sun's package?
I, and perhaps others, would appreciate hearing what kinds of problems you're having and why you think they're related to SuSE's packaging of Sun's Java software.
Could you elaborate a bit?
The problems go very deep, and I was not the author of the code. The basic problem is from communication via DSL lines using VPN, and then accessing the java program on a remote server and the java program then uses an RMI server on an AS400.
We tried several things, and since the author refused to admit it was a coding issue (what's so hard about admitting our code could pack a flaw?), someone had tried this on their 9.3 machine and it worked with no more issues.
The reason "the author" (me) won't admit it's a coding issue is that these are stable programs that have had little or no changes in a year or more, while our network has undergone a number of significant changes in recent months (e.g. a remote location switching from T1 to DSL and VPN, network usage tracking hardware, servers moved to DMZ, etc.). In addition, the problems being seen are of an intermittent nature and there is no repro case for them. The symptoms include: a) program loads failing due to ClassNotFoundException when we know that the class files are present on the file server b) "connection dropped unexpectedly" messages from JDBC drivers against both Postgres and AS/400 databases What you mean about 9.3, I'm not sure... are you saying that someone replaced SUSE's 1.5.0_03 with a download from Sun and the problems magically went away? If that's what you're saying, how much stress testing did you do (bearing in mind the fact that the problem is not reproducible)? One of the first things I tried this summer when we were having what turned out to be NFS problems was to replace the SUSE JVM with the more recent 1.5.0_05, downloaded from Sun. It didn't make a difference, so I backed it out after running it for several days on four machines. It seems to me that the answers you are getting here, Adam, are the same ones I gave you at the office. -- ====================================================== Glenn Holmer (Linux registered user #16682) ====================================================== "Greater coherence cannot be achieved. Not even the Netherlanders have managed this." -Anton Webern ======================================================
participants (4)
-
Adam Schuett -
Glenn Holmer -
Mike Atkin -
Randall R Schulz