Re: WSE464: No policy could be found for this message.
- From: "Sami Vaaraniemi" <samivanospam@xxxxxxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 11:37:28 +0300
This is just a wild guess, but I'd check the event log for messages that the
web service process was recycled at the time the problem disappeared. If you
find such a message then this would suggest that the problem could have
something to do with low resource conditions.
Regards,
Sami
"Julie Lerman" <jlermanATNOSPAMPLEASEthedatafarm.com> wrote in message
news:eJ8c2BScFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
> We had a strange thing occur that I cannot duplicate and therefore debug
> and fix for next time.
> This is an app and web service that have been working together with WSE2
> for many many months. Last night I was told that on one particular
> function in teh application, they were getting the above message. Over and
> over again from numerous computers. This morning, when I tested it from MY
> computer , hitting the same webserver, I did not have the problem. They
> said the problem also disappeared this morning.
>
> I don't know where to start investigating this. This function was the 3rd
> in a series of WSE2 wired web services calls. So it wasn't that the
> webserver disappeared. They would always get past the first two and then
> get this on the third call (the particular function).
>
> What type of event would cause this to disappear and then reappear. These
> computers were all hitting the webserver through the internet and through
> an ISA Server. They endpoints have not changed. Nobody edited the policy
> config file.
>
> Can anybody get me pointed in the right direction?
>
> Thanks!!
>
> Julie Lerman
>
.
- Follow-Ups:
- Re: WSE464: No policy could be found for this message.
- From: Julie Lerman
- Re: WSE464: No policy could be found for this message.
- References:
- WSE464: No policy could be found for this message.
- From: Julie Lerman
- WSE464: No policy could be found for this message.
- Prev by Date: ResponseSoapContext
- Next by Date: Interoperability with WebSphere 5.11
- Previous by thread: WSE464: No policy could be found for this message.
- Next by thread: Re: WSE464: No policy could be found for this message.
- Index(es):
Relevant Pages
|