Hi again,

this is the log on the server side:

INFO  [10:44:42,450] QOSPRequestURIBasedDispatcher:findService - Target
service is [Service1]
INFO  [10:44:42,452] QOSPRequestURIBasedDispatcher:findService1 - The
target service is available
INFO  [10:44:42,453] QOSPRequestURIBasedDispatcher:forwardMessage -
Target service is [Service1]
INFO  [10:44:42,454] QOSPRequestURIBasedDispatcher:forwardMessage - Axis
service set properly
TRACE [10:44:42,455] QOSPRequestURIBasedDispatcher:forwardMessage - Null
axis operation
TRACE [10:44:42,456] QOSPRequestURIBasedDispatcher:invoke - forward
executed
Mar 15, 2007 10:44:42 AM org.apache.axis2.transport.http.AxisServlet
doPost
SEVERE: java.util.MissingResourceException: Can't find resource for
bundle org.apache.axis2.i18n.ProjectResourceBundle, key
spec.FAULT_ACTION_NOT_SUPPORTED_REASON


The QOSPRequestURIBasedDispatcher is a handler which replaces the
RequestURIBasedDispatcher handler. The invoke method is:

public InvocationResponse invoke(MessageContext messageContext) throws
AxisFault {

        if (log.isDebugEnabled()) {
            log.debug("Received message");
        }

        // Tries to get the header block identifying a QOSP message
        SOAPHeaderBlock qospBlock = null;
        try {
            final SOAPEnvelope envelope = messageContext.getEnvelope();
            qospBlock =
DispatchersHelper.getQoSPHeaderBlock(envelope.getHeader());
        } catch (OMException e) {
            throw new AxisFault("Unable to get the message header", e);
        }

        if (qospBlock == null) {
            if (log.isEnabledFor(Level.WARN)) {
                log.warn("Empty QoSP block found.");
            }
            throw new AxisFault("The QoSP message header is empty.");
        }

        // If the incoming message is a forward message saves some
informations
        if (DispatchersHelper.isForwardMessage(qospBlock)) {
            if (log.isTraceEnabled()) {
                log.trace("Received forward message");
            }

            // this.networkTS = System.currentTimeMillis();
            try {
                forwardMessage(messageContext);
                if (log.isTraceEnabled()) {
                    log.trace("forward executed");
                }
            } catch (AxisFault e) {

                if (log.isEnabledFor(Level.ERROR)) {
                    StringWriter sw = new StringWriter();
                    PrintWriter pw = new PrintWriter(sw);
                    e.printStackTrace(pw);
                    log.error(sw.toString());
                }
                throw e;
            }

        } else if (isResponseFromCodestore(qospBlock)) {
            if (log.isDebugEnabled()) {
                log.debug("Received codestore message");
            }
        } else {
            throw new AxisFault("Malformed header block. Is it a forward
message?");
        }

        return InvocationResponse.CONTINUE;
    } // -- invoke()

So it seems to me that the error is thrown after the invoke method
returns.

Michele

On Wed, 2007-03-14 at 19:55 +0000, Michele Mazzucco wrote:
> Glen,
> 
> this is one the the messages sent from the client but I don't see any  
> problem.
> 
> POST / HTTP/1.1
> User-Agent: Axis2
> Transfer-Encoding: chunked
> Content-Type: application/soap+xml; charset=UTF-8;action="urn:test2";
> 
> 28b
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope  
> xmlns:wsa="http://www.w3.org/2005/08/addressing";  
> xmlns:soapenv="http://www.w3.org/2003/05/soap- 
> envelope"><soapenv:Header><wsa:To>http://host_name:8079</ 
> wsa:To><wsa:ReplyTo><wsa:Address>http://ip_address:6060/axis2/ 
> services/anonService142936511173901574478/anonOutInOp</wsa:Address></ 
> wsa:ReplyTo><wsa:MessageID>urn:uuid:24A72ED40BFE16B93411739015745511</ 
> wsa:MessageID><wsa:Action>urn:test2</wsa:Action></ 
> soapenv:Header><soapenv:Body><stressTest:test  
> xmlns:stressTest="http://ncl.ac.uk/qosp";><stressTest:lenght>1652</ 
> stressTest:lenght></stressTest:test></soapenv:Body></soapenv:Envelope>
> 0
> 
> 
> Michele
> 
> On 14 Mar 2007, at 03:30, Glen Mazza wrote:
> 
> > I'm unsure but ProjectResourceBundle appears to be missing a key (a
> > string for a given constant); however, the error which is causing Axis
> > to need to search for "spec.FAULT_ACTION_NOT_SUPPORTED_REASON" is only
> > happening on one machine, most probably due to user inputs/requests.
> > This--the (apparent) fact that the key is missing--is probably a JIRA
> > issue.  Why your code is such that Axis needs to search for that error
> > message to begin with is something for this mailing list.
> >
> > In src/org/apache/axis2/addressing/i18n/resource.properties, however,
> > this warning *is* defined as "The [action] cannot be processed at the
> > receiver." which gives a hint to a potential problem with your
> > application code.
> >
> > (There is also a comment in that file warning translators about
> > translating the 'spec.*' message keys--I wonder if that is the problem
> > with one of your machines--are you running UK English or a foreign
> > language on that separate machine while running US English on the
> > others?  If so, the nightly code might be missing the translation for
> > that key for any non-US English default computers.  But just a guess
> > here.)
> >
> > Glen
> >
> >
> > Am Dienstag, den 13.03.2007, 16:56 +0000 schrieb Michele Mazzucco:
> >> Hi all,
> >>
> >> from the tomcat logs I can see this message:
> >>
> >> Mar 13, 2007 4:43:01 PM org.apache.axis2.transport.http.AxisServlet
> >> doPost
> >> SEVERE: java.util.MissingResourceException: Can't find resource for
> >> bundle org.apache.axis2.i18n.ProjectResourceBundle, key
> >> spec.FAULT_ACTION_NOT_SUPPORTED_REASON
> >>
> >> Oddly the configuration is the same on several machines (axis2  
> >> nightly
> >> build, sun jdk 1.5.0_04-b05, linux 2.6.14), but it happens only in  
> >> a few
> >> of them.
> >> Any clue?
> >>
> >>
> >> Thanks,
> >> Michele
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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]
> >
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to