ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaliya Ekanayake" <jnekanay...@gmail.com>
Subject Re: Reliability Handler
Date Thu, 05 Jan 2006 02:03:44 GMT
Hi,

I corrected the NPE. Please get an update of the code. However the way you 
used to simulate a message loss will generate a fault in Sandesha since it 
is a message without any content. A better way to test message loss is use 
SOAP Monitor to redirect messages to somewhere else and start it before the 
InactivityTimOut is reached with correct url.

Thanks,
Jaliya

----- Original Message ----- 
From: "Benjamin Schmeling" <Benjamin_Schmeling@gmx.de>
To: "Jaliya Ekanayake" <jnekanayake@gmail.com>
Sent: Wednesday, January 04, 2006 1:08 PM
Subject: Re: Reliability Handler


> Hi,
>
> I modified the sandesha .properties as to see in the attached file.
>
> Thanks,
>
> Benjamin
>
>> Hi Benjamin,
>>
>> Please send the changes you made to the sandesha.properties in the
>> client and the server side. It seems that the change you have done is
>> between Sandesha 1st handler and the middle handler. So there we
>> expect the RM headers.
>>
>> Thanks,
>>
>> Jaliya
>> ----- Original Message ----- From: "Benjamin Schmeling"
>> <Benjamin_Schmeling@gmx.de>
>> To: "Jaliya Ekanayake" <jnekanayake@gmail.com>
>> Cc: <jaliya@opensource.lk>; <sandesha-dev@ws.apache.org>
>> Sent: Tuesday, January 03, 2006 11:53 AM
>> Subject: Re: Reliability Handler
>>
>>
>>> java.lang.NullPointerException
>>>    at
>>> org.apache.sandesha.server.RMMessageProcessorIdentifier.getMessageProcessor(RMMessageProcessorIdentifier.java:57)
>>>
>>>    at
>>> org.apache.sandesha.server.SenderWorker.processResponseMessage(SenderWorker.java:371)
>>>
>>>    at
>>> org.apache.sandesha.server.SenderWorker.sendServiceRequest(SenderWorker.java:356)
>>>
>>>    at
>>> org.apache.sandesha.server.SenderWorker.sendMessage(SenderWorker.java:213)
>>>
>>>    at org.apache.sandesha.server.SenderWorker.run(SenderWorker.java:144)
>>>    at java.lang.Thread.run(Thread.java:595)
>>>
>>>> Hi Benjamin,
>>>>  Oops, Please send a stack trace so that we can fix it soon.
>>>>  Thanks,
>>>>  Jaliya
>>>>  On 1/3/06, *Benjamin Schmeling* <Benjamin_Schmeling@gmx.de
>>>> <mailto:Benjamin_Schmeling@gmx.de>> wrote:
>>>>
>>>>     Hi,
>>>>
>>>>     I put my handler to the listenerRequestHandlers before the
>>>>     RMHandler and
>>>>     to the responseHandlers
>>>>     before the RMHandler (defined in sandesha properties). Now I am
>>>>     tracking
>>>>     the messages that are exchanged. I wanted to test what happens when
>>>>     message gets lost, so I change the soapmessage to an empty message
>>>>     (for
>>>>     request and currentmessage of the message context) that I got in my
>>>>     Handler. Then I get an ERROR SenderWorker:158 -
>>>>     java.lang.NullPointerException.
>>>>
>>>>     Thanks,
>>>>
>>>>     Benjamin
>>>>
>>>>     >Hi Benjamin,
>>>>     >
>>>>     >Applying a particular handler for a particular method in a Web
>>>>     service is
>>>>     >not possible with Axis1.x however if you use Sandesha2 that is
>>>>     build on
>>>>     >top of Axis2 that has the support for operation specific handlers
>>>>     you can
>>>>     >do it.
>>>>     >
>>>>     >The exception may be generated by axis since sandesha is using
>>>>     axis to
>>>>     >send the messages. What is the exception you are getting?
>>>>     >
>>>>     >Thanks,
>>>>     >
>>>>     >Jaliya
>>>>     >
>>>>     >
>>>>     >
>>>>     >
>>>>     >>Hi,
>>>>     >>
>>>>     >>when I add the ReliabilityHandler to a web service this web
>>>>     service only
>>>>     >>accepts reliable calls. Is it possible to define reliability
to
>>>>     single
>>>>     >>methods of that web service? If it is possible how must the web
>>>>     service
>>>>     >>and the handler be configured.
>>>>     >>
>>>>     >>Another question. I need to block particular messages being sent
>>>>     by the
>>>>     >>reliable sender. I tried to realize this by putting my own
>>>>     handler to
>>>>     >>the listenerRequestHandlers and deleting the request message,
>>>>     but this
>>>>     >>did not work because sandesha has an exception. Any advices?
>>>>     >>
>>>>     >>Thanks,
>>>>     >>
>>>>     >>Benjamin
>>>>     >>
>>>>
>>>> 
>>>>  >>---------------------------------------------------------------------

>>>>
>>>>     >>To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>>>>     <mailto:sandesha-dev-unsubscribe@ws.apache.org>
>>>>     >>For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>>     <mailto:sandesha-dev-help@ws.apache.org>
>>>>     >>
>>>>     >>
>>>>     >>
>>>>     >>
>>>>     >
>>>>     >
>>>>     >
>>>>     >
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>>     To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>>>>     <mailto:sandesha-dev-unsubscribe@ws.apache.org>
>>>>     For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>>>     <mailto:sandesha-dev-help@ws.apache.org>
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>
>>
>
>


--------------------------------------------------------------------------------


># This is the port in which client side listener listens.
> CLIENT_LISTENER_PORT = 9090
>
> # This is the SimpleAxisServerImpl running port. Only for testing 
> purposes.
> SIMPLE_AXIS_SERVER_PORT = 8080
>
> # Any number of handlers can be included as shown below for the response 
> path of the Sender.
> responseHandler1 = 
> de.tud.ao4bpel.services.reliability.test.RMTestRequestHandler
> responseHandler2 = 
> org.apache.axis.message.addressing.handler.AddressingHandler
> responseHandler3 = 
> org.apache.sandesha.ws.rm.handlers.RMServerRequestHandler
>
> # If there are additional handlers that needs to be included in the 
> Senders request path
> # then use the following configuration.
> # requestHandler1 = package.name.DummyHandler
>
> # These are the handlers for the Listener's request path. Listener's 
> request path is used to
> # retrieve asynchronous responses and other RM protocol messages and hence 
> the handlers we put here
> # should be the RESPONSE handlers with respect to normal invocation.
> listenerRequestHandler1 = 
> de.tud.ao4bpel.services.reliability.test.RMTestRequestHandler
> listenerRequestHandler2 = 
> org.apache.axis.message.addressing.handler.AddressingHandler
> listenerRequestHandler3 = 
> org.apache.sandesha.ws.rm.handlers.RMServerRequestHandler
>
> # Define the strategy for executing web service invokes.
> # This impl uses the apache axis thread pool and configures
> # it to the given size.
> invokeStrategy=org.apache.sandesha.server.ThreadPoolInvokeStrategy:threadPoolSize=10
>
> # Define the invoke handler that will execute the web service invokes.
> # This impl simply delegates to the handler specified by the "invoker" 
> param.
> invokeHandler=org.apache.sandesha.server.DelegateInvokeHandler:invoker=org.apache.axis.providers.java.RPCProvider



---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


Mime
View raw message