- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: problem with symbolic link to java
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:15 AM
03-01-2005 06:15 AM
problem with symbolic link to java
When I invoke the symbolic link, got the coredump error. But if I call the java directly, it succeeded. See the example below.
Anybody has the same problem before? Please advise.
$ls -l mjava
lrwxr-xr-x 1 clarify dba 54 Mar 1 12:57 mjava -> /opt/bea/jdk131/jre/bin/PA_RISC2.0/native_threads/java
<>
$mjava
Memory fault(coredump)
<>
$/opt/bea/jdk131/jre/bin/PA_RISC2.0/native_threads/java -version
java version "1.3.1.01-release"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1.01-release-010816-12:37)
Java HotSpot(TM) Server VM (build 1.3.1 1.3.1.01-release-010816-13:34-PA_RISC2.0 PA2.0, mixed mode)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:20 AM
03-01-2005 06:20 AM
Re: problem with symbolic link to java
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:21 AM
03-01-2005 06:21 AM
Re: problem with symbolic link to java
Also, why are you using a symbollic link? You can set an environment variable to point various scripts and applications to the right version of JAVA.
JAVA_BIN=/opt/java
That kind of thing.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:32 AM
03-01-2005 06:32 AM
Re: problem with symbolic link to java
if file corrupt, why the java itself works?
>>Why do I use symbolic link?
To find and kill the Java process easily.
We have a few java process running at the same time. When you use ps to list process, all java process are named "/opt/..../jre/bin/PA_RISC2.0/native_threads/java -classpath...", you don't know which process is which. Symbolic Link is a good solution to this problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:36 AM
03-01-2005 06:36 AM
Re: problem with symbolic link to java
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:50 AM
03-01-2005 06:50 AM
Re: problem with symbolic link to java
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2005 06:56 AM
03-01-2005 06:56 AM