> -----Original Message----- > From: Sergey Beryozkin [mailto:[email protected]] > Sent: Tuesday, November 30, 2010 1:25 AM > To: [email protected] > Subject: Re: Odd timing of request & response on Solaris VM > > Hi David > > Can you try to capture the requests on the wire and then we can compare > the > wget & SoapUI ones ? > It can be still a coincidence though, that wget is working ok, but > still, > capturing the headers can help...
I will do that, but afterwards I discovered that there are really two different behaviors here. I found that even after I brought down SoapUI, somehow I hit the breakpoint in my CXF app while I was apparently doing nothing with either wget or SoapUI. I'm going to experiment with it some more this morning. > On Mon, Nov 29, 2010 at 11:50 PM, KARR, DAVID (ATTSI) > <[email protected]>wrote: > > > > -----Original Message----- > > > From: KARR, DAVID (ATTSI) > > > Sent: Monday, November 29, 2010 1:25 PM > > > To: [email protected] > > > Subject: Odd timing of request & response on Solaris VM > > > > > > 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. > > > > Hmm, I'm confused. It appears to be just because of SoapUI. I tried > a > > plain "wget" call, and it behaves just as I would expect. With > "wget", > > it hits the breakpoint, and has no trouble with the Accept header. > >
