- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Appserver does not start if KRNG11i patch is t...
Operating System - Linux
1757927
Members
2677
Online
108866
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО08-12-2005 02:02 AM
тАО08-12-2005 02:02 AM
Appserver does not start if KRNG11i patch is there
We have some issue with Patch named KRNG11i over HP-UX. When we have this patch installed on our machine,our appserver don't comes up giving Error something like shown below: ========================= java.lang.ExceptionInInitializerError
at com.sun.enterprise.admin.server.core.channel.AdminChannel.getPreviousSeed(AdminChannel.java:253)
at com.sun.enterprise.admin.server.core.channel.AdminChannel.createSharedSecret(AdminChannel.java:108)
at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:115)
at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.security.ProviderException: setSeed() failed
at sun.security.provider.NativePRNG$RandomIO.implSetSeed(NativePRNG.java:253)
at sun.security.provider.NativePRNG$RandomIO.access$100(NativePRNG.java:108)
at sun.security.provider.NativePRNG.engineSetSeed(NativePRNG.java:92)
at java.security.SecureRandom.setSeed(SecureRandom.java:400)
at com.sun.enterprise.server.J2EEServer.(J2EEServer.java:84)
... 4 more
Caused by: java.io.IOException: No such device (errno:19)
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:247)
at sun.security.provider.NativePRNG$RandomIO.implSetSeed(NativePRNG.java:251)
======================================
As it is clear from exception trace , origin of this exception is J2EEServer (line no. 84 ), where it is trying to do setSeed(). For this java use algorithm named "NativePRNG" in which it reads random bytes directly from /dev/urandom. Now the concern is this NativePRNG algorith is not implemented for HP-UX , so it dont works on HP-UX and it gives exception. Due to exsistence of KRNG11i , it always gives peference to urandom device for random no. generation which is installed by this patch , which is the cause of above exception.
Now we have one fix , for which we may need to change following : Fix suggestion : =====================================
Orginal code ~~~~~~~~~~~~~~~~
public static final SecureRandom secureRandom = new SecureRandom();
static {
secureRandom.setSeed(System.currentTimeMillis());
}
Suggested fix is : ~~~~~~~~~~~~~~~~
try{
SecureRandom random = SecureRandom.getInstance("SHAiPRNG");
random.setSeed(System.currentTimeMillis());
System.out.println("Executed Successfully");
} catch(Exception e){ System.out.println("No Such Algorithm");} ========================================
Implies we want to just change the algorithm used for random no. generation. But we dont know the actual impact.
Now my question is if we do as said above,
can anyone tell what could be the impact?
Any better solution than this?
Thanks
Saritha
at com.sun.enterprise.admin.server.core.channel.AdminChannel.getPreviousSeed(AdminChannel.java:253)
at com.sun.enterprise.admin.server.core.channel.AdminChannel.createSharedSecret(AdminChannel.java:108)
at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:115)
at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.security.ProviderException: setSeed() failed
at sun.security.provider.NativePRNG$RandomIO.implSetSeed(NativePRNG.java:253)
at sun.security.provider.NativePRNG$RandomIO.access$100(NativePRNG.java:108)
at sun.security.provider.NativePRNG.engineSetSeed(NativePRNG.java:92)
at java.security.SecureRandom.setSeed(SecureRandom.java:400)
at com.sun.enterprise.server.J2EEServer.
... 4 more
Caused by: java.io.IOException: No such device (errno:19)
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:247)
at sun.security.provider.NativePRNG$RandomIO.implSetSeed(NativePRNG.java:251)
======================================
As it is clear from exception trace , origin of this exception is J2EEServer (line no. 84 ), where it is trying to do setSeed(). For this java use algorithm named "NativePRNG" in which it reads random bytes directly from /dev/urandom. Now the concern is this NativePRNG algorith is not implemented for HP-UX , so it dont works on HP-UX and it gives exception. Due to exsistence of KRNG11i , it always gives peference to urandom device for random no. generation which is installed by this patch , which is the cause of above exception.
Now we have one fix , for which we may need to change following : Fix suggestion : =====================================
Orginal code ~~~~~~~~~~~~~~~~
public static final SecureRandom secureRandom = new SecureRandom();
static {
secureRandom.setSeed(System.currentTimeMillis());
}
Suggested fix is : ~~~~~~~~~~~~~~~~
try{
SecureRandom random = SecureRandom.getInstance("SHAiPRNG");
random.setSeed(System.currentTimeMillis());
System.out.println("Executed Successfully");
} catch(Exception e){ System.out.println("No Such Algorithm");} ========================================
Implies we want to just change the algorithm used for random no. generation. But we dont know the actual impact.
Now my question is if we do as said above,
can anyone tell what could be the impact?
Any better solution than this?
Thanks
Saritha
- Tags:
- Java
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 02:11 AM
тАО08-12-2005 02:11 AM
Re: Appserver does not start if KRNG11i patch is there
The error No such device (errno:19)
makes me think that do you have device files /dev/urandom and /dev/random with appropriate perms??
makes me think that do you have device files /dev/urandom and /dev/random with appropriate perms??
There is no substitute to HARDWORK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2005 12:54 AM
тАО08-29-2005 12:54 AM
Re: Appserver does not start if KRNG11i patch is there
we have /dev/random and /dev/urandom with appropriate permissions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2005 01:34 AM
тАО08-29-2005 01:34 AM
Re: Appserver does not start if KRNG11i patch is there
If you do not use KRNG for anything else, you may set KRNG driver to N and get rid of /dev/random and /dev/urandom.
(As I am aware latest version of ssh do use that) Check release for details.
This way your application server would use it's own PRNG machanism and should hev no problems.
Also, dos apps server have a setting that you can use to use it's native PRNG first, else KRNG??
(As I am aware latest version of ssh do use that) Check release for details.
This way your application server would use it's own PRNG machanism and should hev no problems.
Also, dos apps server have a setting that you can use to use it's native PRNG first, else KRNG??
There is no substitute to HARDWORK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP