Skip to main content

xhp hangs in all examples

3 replies [Last post]
Joined: 2008-07-21

Hi all -

Just trying to get some of the jmaki examples working so I can learn more. I tried both the Craigslist mashup and the mapit example, in Tomcat and Glassfish, under 1.0.3 (and some in 1.0.8 beta) and in all cases, calls to /xhp hang. It doesn't matter what the arguments are. If I wget the URL that's hanging, here's the result I get:

$ wget 'http://localhost:8080/jmaki-cl-mashup/xhp?key=cl' -O foo
--17:15:32-- http://localhost:8080/jmaki-cl-mashup/xhp?key=cl
=> `foo'
Resolving localhost..., ::1
Connecting to localhost||:8080... connected.
HTTP request sent, awaiting response... 403 Forbidden
17:15:32 ERROR 403: Forbidden.

It doesn't matter if it's localhost or the fully qualified name of the host. Both Tomcat and Glassfish are installed in my home directory (so it's unlikely to be a file permission problem), and I'm using stock installations (5.5.26 in the case of Tomcat, whatever the current release build is for Glassfish). In both cases, the logs for the application server show nothing.

Obviously, this could easily be my particular environment (I'm doing this on a Solaris x86 box, and I'm behind a firewall). But I'm hoping that someone can think of something else stupid I may be doing.

Thanks in advance -
Sam Bayer
The MITRE Corporation

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2008-07-21

Followup: I tried the same configuration (Tomcat 5.5.26, jmaki 1.0.3) on a MacOS 10.5 box and got an almost identical result, except in this case the Tomcat log recorded the 403 error and returned, rather than hanging. I've noticed this in the context of trying to load the application, so all the other URLs associated with the example up to the point that this URL is loaded work fine, e.g.,


So I'm kind of mystified.

Joined: 2008-07-21

Less mystified. A closer study of the logs suggests that the problem is my firewall; xhp seems to fail because it's trying to contact an external URL. So I modified web/java/WEB-INF/web.xml in the relevant example as described here:

but there was no change in behavior. Since I'm pretty sure that this is the problem, and the title for this thread doesn't reflect it, I'll mark this thread as answered and try again.

Joined: 2003-07-31

Hi Sam,

Could you confirm the jMaki version and the class name you are pointing to with the servlet?

It should be:


Hopefully you are using the latest jMaki (we are in release candidates of 1.8.0)

We do test on Tomcat so I suspect it might be something with the firewall.