Announcement

**jay.l.fisher** · 1 Jan 2010, 15:18

I don't see anything in the catalina.out log on the server. Is there another log I should be looking at, or a setting to log more info? The only thing I see anywhere is in the SmartClient Developer Console which shows this.

Code:

16:37:36.585:WARN:RPCManager:Transport error - HTTP code: 404 for URL: sc/productSearch?q=chair, response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 12,
httpResponseCode: 404,
httpResponseText: "<html><head><title>Apache Tomcat/6.0.20 ..."[1021],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -90,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Transport error - HTTP code: 404 for URL..."[66]}

This is the latest mapping I've tried and still no luck.

Code:

    <servlet>
        <servlet-name>ProductSearch</servlet-name>
        <servlet-class>com.islandpacific.gui.server.search.ProductSearch</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>ProductSearch</servlet-name>
        <url-pattern>/sc/productSearch*</url-pattern>
    </servlet-mapping>

**timprice17** · 1 Jan 2010, 17:47

You've probably already tried this...

... but have you entered the URL for the servlet on tomcat into your web browser directly, just to see what happens? The servlet won't return data the browser can display, but at least you can verify if the same error occurs outside of SGWT.

One subtle problem I've encountered is permissions on the class/jar files. If they're read-only or no-read for the group running the process (sorry, can't be more specific than that), the web container acts the same as a bad URL or unknown servlet. Just letting you know it's worth checking what the permissions actually are on the deployed files. On unix, if I see -r-------- on the files, the servlet usually doesn't work.

And of course, search in Tomcat's docs and forums. ;)

HTH

**jay.l.fisher** · 1 Jan 2010, 20:34

Thanks for the tip! The problem was immediately made clear. I hadn't included the jars I needed for the solr search engine in my war/WEB-INF/lib, so the servlet *was* actually being called, but then crashing on a NoClassDefFoundError. Why wouldn't something like that show up in the Tomcat log?

Thanks again for the help!

Announcement

Comment

Comment

Comment