Tomcat problem.

[Steven E. Protter]

HPWS provided web suite, tomcat.

User/developer is using 5.5.9.01

Current version offered by HP is: 5.5.20.

Exception is:

Exception report

message >

description The server encountered an internal error () that p
revented it from fulfilling this request.

exception

java.l
ang.NullPointerException
        com.nds.xti.archive.ArchiveHandler.doArchiving(ArchiveHandler.java:90)
        com.nds.xti.servlet.ManageAsset.doArchiveAndOutput(ManageAsset.java:172)
 
        com.nds.xti.servlet.ManageAsset.handleRequest(ManageAsset.java:127)
        com.nds.xti.servlet.vam.BindAsset.doPost(BindAsset.java:16)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

note The full stack trace of the root cause is available
in the Apache Tomcat/5.0.28 logs.

---

Apac
he Tomcat/5.0.28

Has anyone seen this before and will updating to the new version help?

I see the message refers to a log, I'm gonna go RTFM it now.

SEP

[Alzhy]

Shalom SEP,

I am using the latest and greatest 2.17 HPWS Distro which contains the latest and SANS/CERT alert free release - http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXWSATW217

My users who use Apache, Tomcat, PHP, MySQL, etc. absolutely have no problems with it... Only the PHP piece was a bit difficult to set up specially the OCI8 piece.

To administer/configure HP Web Server Suite - it is best to use the bundled WEBMIN. After installation, set it to autostart in rc.config.d and start Apache svs, etc. and manage via via Webmin. Instructions on how to manage via Webmin and how to secure Webmin (it uses a default id and passwd which you MUST change) - visit the default URL for your web server.

Hope this helps!

You comin' to Vegas man?

[Steven E. Protter]

Shalom,

No, not coming to Vegas. My speaking proposal was not accepted. If I'm sent to the US for other reasons I may try and sell management on it.

Thanks for your post Nelson. I am correct in concluding it does not directly relate to our issue?

To revise the question:
1) Has anybody had the problem and fixed it by updating the suite?
2) Has anybody had the problem and fixed it by doing anything else.

Answering either question 1 or 2 is bunnyland for the poster.

sEP

[Heironimus]

NullPointerException is a very, very generic Java error, and "com.nds.xti.foo" doesn't sound like something bundled with Tomcat. I usually send the whole stack trace off to the developers because only they will know what their app does (hopefully - plenty of Java developers somehow don't how their own apps work). The most common cause by far is a coding error, but sometimes I have seen a mismatch in a Java library or container.

Either way, you probably want to have developers and servers using the same version of the container, especially since Tomcat bundles several libraries. Either have the developers roll back to 5.0 or push the server up to 5.5. And also make sure that everybody's using the same JDK versions, don't mix 1.4, 1.5, and 1.6 unless you're absolutely certain you know what you're getting into.

[Steven E. Protter]

Shalom,

JAVA is provided by the server and the JAVA_PATH variable. These are experienced developers so I assume they know the point about JAVA. Was wondering if patching JAVA or tomcat would help.

SEP

[Alzhy]

SEP,

Our HPWS implementation use Java 1.5... You may want to look at upgrading to this release.

[Steven E. Protter]

The developers decided not to touch tomcat and check their code.

Yea,I'm pretty amazed too.

SEP