I know this may be a bit of a slog, but look for places where catch blocks just drop or wrap exceptions. I've seen a few apps that return null instead of propagating up things like SQLException. Also check how your library handles contention and data locking. If Threads A & B ask for the same data and your app/library/datastore implements exlusive locking what happens to last thread to issue the request?
Also put a check in to see if null is being returned to whichever font end isn't showing the data, as I understand it when you access either one it works reliably, so if you're only getting no data when the two are used together it's pretty much certain it's a contention issue. -----Original Message----- From: Jeff Amiel [mailto:[EMAIL PROTECTED] Sent: 06 June 2007 16:15 To: Struts Users Mailing List Subject: Re: How can one servlet (ActionServlet) effect another servlet (AxisServlet)...? On 6/6/07, Al Sutton <[EMAIL PROTECTED]> wrote: > Are the soap methods and the actions your calling accessing the same > data and/or service classes? sure...under the hood....they all utilize the same service 'layer' (factory method pattern to acquire newly created serviceimpl classes) and use the same domain objects (uniquely instantiated per servlet request) The only thing the individual requests should be 'sharing' is session information....... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
