|
Home > Archive > WebSphere Application Server > October 2006 > Strange issue running WAS 6.0.2.11 on HPUX 11...pls help!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Strange issue running WAS 6.0.2.11 on HPUX 11...pls help!
|
|
|
| Hi All
I'm experiencing a strange issue on installing WAS 6.0.2.11 on HPUX 11. Not sure if anyone else has seen such a problem before. I'm explaining from the start...
1. On first install, WAS installer complained that we didn't have adequate OS patches & cannot continue. So we went about installing all the OS patches & finally the installation succeeded.
2. After installation, the node had to be created & we weren't able to create the node neither using the admin console or using createNode.sh command from the command prompt. But somehow we managed to create a node after 2 days of WAS reinstalls & struggl
es.
3. Once the node was created, server is federated, HTTP server being added, Default Application installed & redirection verified using Snoop Servlet, using admin console we are no longer able to start or stop the server. There are several issues & one of
the below happens intermittently
a. Using admin console, we are unable to stop or start the server. Console says, its processing and after 3-4 minutes, a message is displayed saying that the server took too much time & couldn't complete the request.
b. Using admin console, if the server stops or starts, the reliability is lost. Even if the server is stopped, the console says its started or if the server is running, the console says that the server stopped.
c. Using command prompt ($), if the server is stopped, the port (9080) is not getting released. Note that, this also happens intermittently, but not all the time.
d. Once the server is restarted from the command prompt, the server sometimes is unable to deploy any application even from the command line. I'm unable to get the application stopped or started using Jython although the system is able to recognise the a
pplication that is being installed.
How is this affecting us? - We are installing a product that requires starting & stopping of WAS and the product related applications (.ear file). We are unable to carry out because of the strange behaviour of WAS. This occurs only on this system & not on
any of our AIX, Sun or Windows boxes. We are unable to test on any other HPUX box since we have only one.
Please help!
Regards
Ganesh .R
| |
| Ken Hygh 2006-10-28, 1:41 pm |
| aarganesh@rediffmail.com wrote:
> Hi All
> I'm experiencing a strange issue on installing WAS 6.0.2.11 on HPUX 11. Not sure if anyone else has seen such a problem before. I'm explaining from the start...
> 1. On first install, WAS installer complained that we didn't have adequate OS patches & cannot continue. So we went about installing all the OS patches & finally the installation succeeded.
>
> 2. After installation, the node had to be created & we weren't able to create the node neither using the admin console or using createNode.sh command from the command prompt. But somehow we managed to create a node after 2 days of WAS reinstalls & strug
gles.
>
> 3. Once the node was created, server is federated, HTTP server being added, Default Application installed & redirection verified using Snoop Servlet, using admin console we are no longer able to start or stop the server. There are several issues & one o
f the below happens intermittently
> a. Using admin console, we are unable to stop or start the server. Console says, its processing and after 3-4 minutes, a message is displayed saying that the server took too much time & couldn't complete the request.
> b. Using admin console, if the server stops or starts, the reliability is lost. Even if the server is stopped, the console says its started or if the server is running, the console says that the server stopped.
> c. Using command prompt ($), if the server is stopped, the port (9080) is not getting released. Note that, this also happens intermittently, but not all the time.
> d. Once the server is restarted from the command prompt, the server sometimes is unable to deploy any application even from the command line. I'm unable to get the application stopped or started using Jython although the system is able to recognise the
application that is being installed.
>
> How is this affecting us? - We are installing a product that requires starting & stopping of WAS and the product related applications (.ear file). We are unable to carry out because of the strange behaviour of WAS. This occurs only on this system & not
on any of our AIX, Sun or Windows boxes. We are unable to test on any other HPUX box since we have only one.
>
> Please help!
>
> Regards
> Ganesh .R
Should be some more details in the various log files.
Ken
| |
|
| Hmm, well the logs contains a lots & lots of Java exception. However, the problem is solved after 2 weeks. It was an issue with the the OS. The kernel had to be tuned to get this issue solved & its the fastest of all the WAS installed on all other boxes.
Regards
Ganesh .R
|
|
|
|
|