more 500 Servlet Exception

[vance]

Hi everyone!

Sorry, I'm not really that familiar with this 500 Servlet Exception,
but anyway, I'm getting a different 500 Exception this time. Can
somebody help me with this please?

Thank you again for all the help!



500 Servlet Exception
com.trw.dts.wl.security.FilterVerifySig.makeP7(FilterVerifySig.java:215)
Servlet.service(HttpServlet.java:126)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
Connection.run(TcpConnection.java:139)

 

[John C. Bollinger]

Hi everyone!

Sorry, I'm not really that familiar with this 500 Servlet Exception,
but anyway, I'm getting a different 500 Exception this time. Can
somebody help me with this please?

Thank you again for all the help!



500 Servlet Exception
com.trw.dts.wl.security.FilterVerifySig.makeP7(FilterVerifySig.java:215)
Servlet.service(HttpServlet.java:126)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
Connection.run(TcpConnection.java:139)

An HTTP 500 error from a servlet means either (1) the servlet explicitly
sent a 500 error response [which is unlikely] or (2) the servlet threw
an exception that was not caught within the web application and
therefore propagated all the way out to the container. The latter case
is generally caused by a programming or configuration error, and that is
the case that appears to apply here. You seem to have trimmed off all
the useful parts of the stack trace, however: the actual exception
class, its detail message (if any), and the part of the stack trace that
gets back to your own code. It's not clear whether you have included
the very top of the stack trace, which can also be important, or the
topmost public method on the call stack. There may also be one or more
"root cause" stack traces after main stack trace. The key information
for diagnosing the problem is somewhere in amongst all that stuff.


John Bollinger
(e-mail address removed)

 

[Sudsy]

vance wrote:

500 Servlet Exception
com.trw.dts.wl.security.FilterVerifySig.makeP7(FilterVerifySig.java:215)
Servlet.service(HttpServlet.java:126)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
Connection.run(TcpConnection.java:139)

Again, you're not going us very much to go on. Based on the package
name, would it be fair to assume that you're trying to perform lookups
on credit records? TRW is one of the "big three" credit bureaus and
look at the package name: com.trw....
The class name is FilterVerifySig and the method is makeP7. Again, if
my crystal ball isn't cloudy that is probably a short form of PKCS#7.
I'll go out on a limb and suggest that they've provided you with an
X.509 certificate to use to encrypt and/or sign your requests. They
keep the private key and use it for decryption.
So why are you asking on this ng for help? You should be contacting
customer support at TRW. They're the authors of the code and can
probably tell you where the configuration is in error.
But what do I know? ;-)

 

[vance]

Hi!
Thank you for the responses.

What is happening here is that I am trying to run this PL/SQL script
that contains a signature. This signature is then passed into a
servlet that checks it for validity and what not. The servlet will
then call the database and returns an error code if needed. I was
successful so far with returning the error codes. However, when I try
to play around with the signature (such as removing a character or
interchanging them), it gives me the 500 Servlet Exception, which is
not what should happen. It should actually return an error code from
the db. The error below is the complete error that appears on the
result pane whenever I run it in SQL Station(PL/SQL).



500 Servlet Exception
com.trw.dts.wl.security.FilterVerifySig.makeP7(FilterVerifySig.java:188)
Servlet.service(HttpServlet.java:126)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
Connection.run(TcpConnection.java:139)


Thanks again!

 

[Sudsy]

vance wrote:

to play around with the signature (such as removing a character or
interchanging them), it gives me the 500 Servlet Exception, which is
not what should happen. It should actually return an error code from
the db. <snip>

Why? It looks like it never even gets to the servlet. It's failing
within the servlet container, specifically in a filter. It appears
that you're using Resin. Best suggestion would be to ask the question
on one of their newsgroups/mailing lists.

The error below is the complete error that appears on the
result pane whenever I run it in SQL Station(PL/SQL).

We've already seen the error but it doesn't provide enough information
to draw any concrete conclusions (save for the fact that com.caucho is
an indicator of the servlet container).