I have an app using CXF/JAX-RS.  I've tested it on my laptop using
SoapUI to send requests.  It works fine.  I've now deployed the app to a
Solaris 10 VM on another box.  It appears to be deployed fine.

Running the app is displaying some odd symptoms, however.  The first
time I sent the request to the server from SoapUI, it returned the
correct response.  However, I then noticed that it was refusing to
render JSON, as if it never saw the "Accept" header in the request.  At
that point, I set up the remote server for debugging and I connected to
it from Eclipse.  I verified it was connected.  I set a breakpoint in my
controller handler method.  I then resent the request from SoapUI, and
it immediately returned the correct response without hitting the
breakpoint.

That mystified me.  I sat there for a while thinking why this might be
happening.

I was even more mystified when a minute or two later, the debugger
stopped at my breakpoint.  I hadn't rerun the request from SoapUI, which
had returned the expected response when I ran it.  After this happened a
couple more times, with no obvious relationship to the requests I send
from SoapUI, I stepped through my controller handler method and made a
change to the resulting object it returned and then resumed.  Nothing
happened, of course.  I then resent the request from SoapUI, which
returned immediately.  I looked at the response it got, and it had the
change I made in the debugger.

It sure seems to me like there is some caching behavior going on here.
I'm pretty sure SoapUI wouldn't be doing this.

Occasionally it hits the breakpoint immediately when I send the request,
but usually it does not.

Another perhaps important fact is that the system date on the server is
wrong, as it is set one day early (time is correct).

I still have the other symptom of it not rendering JSON.  I'm going to
add some debug to see if it's not getting the "Accept" header.

Reply via email to