Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28C97101E4 for ; Sat, 3 Aug 2013 19:52:44 +0000 (UTC) Received: (qmail 73395 invoked by uid 500); 3 Aug 2013 19:52:43 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 73246 invoked by uid 500); 3 Aug 2013 19:52:43 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 73238 invoked by uid 99); 3 Aug 2013 19:52:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Aug 2013 19:52:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Aug 2013 19:52:39 +0000 Received: by mail-we0-f175.google.com with SMTP id q58so1429980wes.20 for ; Sat, 03 Aug 2013 12:51:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=MmffosG6f5iug1x+sVKpPr2moUQuO/BNRFmCHTqrisU=; b=CY+oaGqRMmZCQNe0BcCg5lRjeLEz1VJUlpUrnYTatnT6FlcyYzuhZI0dZSaAsncROQ bnuS8keT8+igKQirLI54C8JIa+tirP4Nw8quMq2TvrWuzCPcMAeqUZV5nfewNVgV9xmz q47p+2F+FpGA4hDAUUI2SWPvydn3ubG4kzVCWgim4gbi1hVYjBlcCP8lzJSPKRzUxII/ stTicMEeXDfgF08IKAIzARcDAGkYeYHe0k6vbtXgFryclDUGpf1aRIgnXIptmQlGrV+O iTjtSPj+j9wO0SLfjd5JhZS5lLHA0d8V69dFjpZL67OJdm9LzggldiYNJgTGwYGVRjsJ Sx9g== X-Gm-Message-State: ALoCoQkkKBJLeI48JsdiGVhwO4Nv5gC3O4rda3iKj3mGSLkgRy0vXZ2dh/08vuEQcOC+rKdaC5R2 MIME-Version: 1.0 X-Received: by 10.180.75.110 with SMTP id b14mr2421680wiw.6.1375559517893; Sat, 03 Aug 2013 12:51:57 -0700 (PDT) Received: by 10.194.120.4 with HTTP; Sat, 3 Aug 2013 12:51:57 -0700 (PDT) In-Reply-To: <001501ce9081$3d392820$b7ab7860$@lampreynetworks.com> References: <000c01ce8f5a$b0556c60$11004520$@lampreynetworks.com> <010501ce8fb3$5a07ed70$0e17c850$@com> <001501ce8fe0$896384d0$9c2a8e70$@lampreynetworks.com> <001201ce903d$e2d97530$a88c5f90$@lampreynetworks.com> <001501ce9081$3d392820$b7ab7860$@lampreynetworks.com> Date: Sat, 3 Aug 2013 21:51:57 +0200 Message-ID: Subject: Re: retrieving message_id From: Walid Benkhelouf To: java-dev@axis.apache.org Content-Type: multipart/alternative; boundary=f46d043be2286e8d7b04e31068cf X-Virus-Checked: Checked by ClamAV on apache.org --f46d043be2286e8d7b04e31068cf Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Yes Brian ,but my first problem is to address problems when a web server goes down ,and figure a way to not loose requests which are in process,so the clients can have a response even if it is from another endpoint. when a web server goes down ,another hosted in another machine,will takes his place(designed as the primary)it will : 1-Update the endpoint reference in the repository(uddi,membrane,..etc) so he will be requested by the future clients. 2-Continue processing the requests not accomplished by the server who was down. 2013/8/3 Brian Reinhold > Walid,**** > > ** ** > > Sounds involved. Could the same be accomplished using the WS reliable > messaging protocol (Sandesha project in the Axis2/Apache hierarchy)? Woul= d > be almost no work; just add the module in your Axis2 xml. The main > difference (I think) from your proposal is that this protocol is still > point to point. Should an endpoint go down during a transaction it could > not be completed until the endpoint came back up. But at least there > wouldn=92t be all this duplication of resources and multiple databases. B= ut I > suppose you have probably looked at this.**** > > ** ** > > Brian**** > > ** ** > > *From:* Walid Benkhelouf [mailto:w_benkhelouf@esi.dz] > *Sent:* Saturday, August 03, 2013 3:09 PM > *To:* java-dev@axis.apache.org > *Subject:* Re: retrieving message_id**** > > ** ** > > hi brian,**** > > ** ** > > My goal is to achieve fault tolerance using replication in web services,*= * > ** > > ** ** > > -->I have a set of web services containers interconnected via a private > p2p network ,which are communicating with a specific protocol(the main > problematic of the project).**** > > ** ** > > -->When a problem occur(one server goes offline or restart),this problem > is detected by one of his neighbors which contains identical copies of > it's web services ,it will retrieve the uncomplicated tasks and return > them to the clients.**** > > ** ** > > -->To achieve this goal,every node of the network (so the server) is > notifying his incoming request to his neighbors ,so when the request is > delivered he(the server) notify it again and the requests will be dropped > from the databases.**** > > ** ** > > -->This database is located in every node of the network ,it contains > information about the current tasks in the neighborhood ,stored in one > table: [msg_ID,Client add,Request].the message_id is the auto-incremented > key retrieved from the database(when a message is inserted).**** > > **** > > -->So the purpose for which i want to use messageID is exclusively for th= e > server side ,tracing in/out message is only used for storing requests > properly ,what do you think about the approach Brian?**** > > ** ** > > Walid**** > > ** ** > > 2013/8/3 Brian Reinhold **** > > This one is a little tougher because it is not based upon protocol. You > want to maintain some kind of internal tracker. Clearly Axis2 does this > since it is able to generate a response to an incoming message. Thus it > must have something that tracks it (which may be based upon protocol). > However, setting the message Id is probably not a reliable way. The > messageID is part of the ws-addressing protocol. The message context obje= ct > is used by both clients and servers so the =91set=92 method is probably m= eant > for the client; setting it on the server side is likely ignored as Axis2 > constructs the ws-addressing response based upon protocol and who knows > where it stores its internal information (it may make a copy and pass tha= t > up to the user; that way Axis2 is sure to respond to the protocol correct= ly > which it can=92t do if the user corrupts the incoming message context).**= ** > > **** > > Without protocol, how are you intending to identify the incoming message > as one that you want to filter? As I understand your goal, you want to > block the response to certain incoming messages.**** > > **** > > Brian**** > > **** > > *From:* Walid Benkhelouf [mailto:w_benkhelouf@esi.dz] > *Sent:* Friday, August 02, 2013 9:00 PM**** > > > *To:* java-dev@axis.apache.org > *Subject:* Re: retrieving message_id**** > > **** > > Hi Brian,sorry for my misunderstanding :-)**** > > The solution that i'm developing (for academic purpose)is located in the > handlers levels,so i'm trying to be the most transparent as possible to t= he > client and the service writer ,so for this I've written two handlers one > for incoming and one for outgoing putted in an AXIS2 module.**** > > For now i was able to address the problem by activating "ws-addressing"in > the client side(and let the message_id blank), so when the message is > intercepted by the "incoming_handler",it will set the message_id "manuall= y" > msgctx.setMessageID (a random key).**** > > The outgoing handler can access to this value by "msgctx.getRelatesTo()).= * > *** > > it's addressing my problem when "ws_addressing"is activated in the client > side.**** > > But i was looking for a "more general"solution that can address the > problem where the client don't have the ws_addressing activated in the > request.**** > > Best Regards!**** > > **** > > 2013/8/3 Brian Reinhold **** > > Walid,**** > > **** > > I think you misunderstood my American slang comment and took it the wrong > way (it=92s kind of an expression); I am not saying that YOUR question wa= s > stupid. If you look below you will see *I am asking the =91stupid=92 ques= tion*which was =93did you check to see if the client sent you a message id?= =94. If > it hadn=92t, you looking for something that didn=92t exist and there was = never > anything wrong with your logic or code!**** > > **** > > Now if I understand you correctly, the client did NOT have a message ID > and you were able to add one. So now you are getting the message id at > least on the incoming. But NOT on the outgoing. Is that correct?**** > > **** > > If so, the outgoing maybe a lot more difficult. I have had some issues > with the ws addressing headers on the response. I do not know if it > affecting your results.**** > > **** > > Can you show the sent/incoming SOAP message? That would help answer some > of the other questions I asked.**** > > **** > > Brian**** > > **** > > **** > > *From:* Walid Benkhelouf [mailto:w_benkhelouf@esi.dz] > *Sent:* Friday, August 02, 2013 3:17 PM**** > > > *To:* java-dev@axis.apache.org > *Subject:* Re: retrieving message_id**** > > **** > > Sorry for my stupid question ,the thing is that i'm not an expert in axis > or java programming ,i was using SOAPUI to simulate the client, i can see > now that i can add messageID from SOAPUI ,it's addressing my problem for > the incoming,but i just wanna ask one more stupid question :) :**** > > -->is there any property in common between the incoming and outgoing > message ,that i can use as primary key in my database that is used to > store incoming messages.(and when a response occur without a problem ,thi= s > message will be drooped) . **** > > **** > > 2013/8/2 Brian Reinhold **** > > A stupid question: you are sure that the message id field is sent by the > client =85**** > > Is this null response only on the incoming message?**** > > And what version?**** > > Sending secure or unsecure?**** > > Is =91must understand=92 set by the client?**** > > I know I had to do some messing around with the addressing modules to get > the ws addressing headers to appear in the response. But it=92s been a lo= ng > time so I don=92t recall the details.**** > > **** > > Brian**** > > **** > > *From:* Walid Benkhelouf [mailto:w_benkhelouf@esi.dz] > *Sent:* Friday, August 02, 2013 2:33 PM > *To:* java-dev@axis.apache.org > *Subject:* Re: retrieving message_id**** > > **** > > hi Martin,**** > > yes i did this and i'm getting a null value in both incoming and outgoing= , > even if "ws-addressing" is engaged.**** > > **** > > 2013/8/2 Martin Gainty **** > > try > > mc.getMessageID() > > (case matters) > > does this help? > Martin > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugt= e > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > **** > ------------------------------ > > Date: Fri, 2 Aug 2013 18:55:18 +0200 > Subject: Re: retrieving message_id > From: w_benkhelouf@esi.dz > To: java-dev@axis.apache.org**** > > **** > > I need to know if there is a property shared between the two > messages(IN/OUT) ,**** > > I was thinking that this property is the message_id contained in > "messageContext.getmessageID()" ,but i'm getting a null value when trying > to retrieve it (ws-addressing module is engaged)**** > > **** > > **** > > 2013/8/2 Brian Reinhold **** > > Not sure I understand the problem ... is what you are trying to do is > retrieve the ws:addressing message id? > > Brian**** > > > -----Original Message----- > From: Walid Benkhelouf [mailto:w_benkhelouf@esi.dz] > Sent: Thursday, August 01, 2013 7:09 PM > To: java-dev@axis.apache.org > Subject: retrieving message_id > > Hello, > > I'm developping a module that handler in/out message from axis2 engine an= d > store them in a database. > I have two handlers :one for the incoming and one for the outgoing. > I need to store the incoming ,and drop the outgoing messages. > The problem is that i need to have the same message_id so i can access to > the database in the second time(the two messages needs to have the same > key). > Thanks;**** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > For additional commands, e-mail: java-dev-help@axis.apache.org > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.3392 / Virus Database: 3209/6543 - Release Date: 08/01/13 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > For additional commands, e-mail: java-dev-help@axis.apache.org**** > > **** > > **** > > **** > > No virus found in this message. > Checked by AVG - www.avg.com**** > > Version: 2013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13= * > *** > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com**** > > Version: 2013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13= * > *** > > **** > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com**** > > Version: 2013.0.3392 / Virus Database: 3209/6547 - Release Date: 08/02/13= * > *** > > ** ** > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.3392 / Virus Database: 3209/6548 - Release Date: 08/03/13= * > *** > > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.3392 / Virus Database: 3209/6548 - Release Date: 08/03/13= * > *** > > --f46d043be2286e8d7b04e31068cf Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Yes Brian ,but my first problem is to address problems whe= n a web server goes down ,and figure a way to not loose requests which are = in process,so the clients can have a response even if it is from another en= dpoint.
when a web server goes down ,another hosted in another machine,will takes h= is place(designed as the primary)it will :
1-Update the end= point reference in the repository(uddi,membrane,..etc) so he will be reques= ted by the future clients.
2-Continue processing the requests not accomplished by the serve= r who was down.


<= br>


2013/8/3 Brian Reinhold <brianreinhold@lampreynetworks.com= >

Walid,

=A0

Sounds involved. Could the same be accomplish= ed using the WS reliable messaging protocol (Sandesha project in the Axis2/= Apache hierarchy)? Would be almost no work; just add the module in your Axi= s2 xml. The main difference (I think) from your proposal is that this proto= col is still point to point. Should an endpoint go down during a transactio= n it could not be completed until the endpoint came back up. But at least t= here wouldn=92t be all this duplication of resources and multiple databases= . But I suppose you have probably looked at this.

=A0<= /p>

Brian

=A0<= /p>

From: Walid= Benkhelouf [mailto:w_benkhelouf@esi.dz]
Sent: Saturday, August 03, 2013 3:09 PM
To: java-dev@axis.apache.org
Subject: Re: retrieving message_id

=A0

hi brian,

=A0

My goal is to a= chieve fault tolerance using replication in web services,<= /u>

=A0

-->I have a set of web services containers interconn= ected via a private p2p network ,which are communicating with a specific pr= otocol(the main problematic of the project).

=A0

-->When a problem occur(one server goes offline or r= estart),this problem is detected by one of his neighbors =A0which contains = identical copies of it's web services ,it will retrieve the uncomplicat= ed tasks =A0and return them to the clients.

=A0

-->To achieve this goal,every node of the network (s= o the server) is notifying his incoming request to his neighbors ,so when t= he request is delivered he(the server) notify it again and the requests wil= l be dropped from the databases.

=A0

-->This database is located in every node of the net= work ,it contains information about the current tasks in the neighborhood ,= stored in one table: [msg_ID,Client add,Request].the message_id is the auto= -incremented key=A0retrieved=A0from the database(when a message is=A0insert= ed).

=A0

-->So the purpose for which i want to use= messageID is exclusively for the server side ,tracing in/out message is on= ly used for storing requests properly ,what do you think about the approach= Brian?

=A0

Walid

=

=A0=

2013/8/3 Brian Re= inhold <brianreinhold@lampreynetworks.com>

This one is a little toug= her because it is not based upon protocol. You want to maintain some kind o= f internal tracker. Clearly Axis2 does this since it is able to generate a = response to an incoming message. Thus it must have something that tracks it= (which may be based upon protocol). However, setting the message Id is pro= bably not a reliable way. The messageID is part of the ws-addressing protoc= ol. The message context object is used by both clients and servers so the = =91set=92 method is probably meant for the client; setting it on the server= side is likely ignored as Axis2 constructs the ws-addressing response base= d upon protocol and who knows where it stores its internal information (it = may make a copy and pass that up to the user; that way Axis2 is sure to res= pond to the protocol correctly which it can=92t do if the user corrupts the= incoming message context).

=A0<= /p>

Without protocol, how = are you intending to identify the incoming message as one that you want to = filter? As I understand your goal, you want to block the response to certai= n incoming messages.

=A0<= /p>

Brian=

=A0<= /p>

From: Walid Benkhelouf [mailto:w_benkhelouf@esi.dz]
Sent: Friday, August 02, 2013 9:00 PM

<= div>


To: java-dev@axis.ap= ache.org
Subject: Re: retrieving message_id

=A0

Hi Brian,sorry for my misunderstanding :-)

The solution that= i'm=A0developing (for=A0academic=A0purpose)is located in the handlers = levels,so i'm trying to be the most transparent as possible to the clie= nt and the service writer ,so for this=A0I've=A0written two handlers on= e for incoming and one for outgoing putted in an AXIS2 module.

For now i w= as able to address the problem by activating "ws-addressing"in th= e client side(and let the message_id=A0blank), so when the message is inter= cepted by the "incoming_handler",it will set the message_id "= ;manually" msgctx.setMessageID (a random key).

The outgoin= g handler can access to this value by "msgctx.getRelatesTo()).<= u>

it's addressing my problem when "ws_addressing"is activ= ated in the client side.

But i was l= ooking for a "more general"solution that can address the problem = where the client don't have the ws_addressing activated in the request.=

Best Regard= s!

=A0

2013/8/3 Brian Reinhol= d <brianreinhold@lampreynetworks.com>

Walid,

=A0

I think you misunderstood= my American slang comment and took it the wrong way (it=92s kind of an exp= ression); I am not saying that YOUR question was stupid. If you look below = you will see I am asking the =91stupid=92 question which was =93did = you check to see if the client sent you a message id?=94. If it hadn=92t, y= ou looking for something that didn=92t exist and there was never anything w= rong with your logic or code!

=A0<= /p>

Now if I understand yo= u correctly, the client did NOT have a message ID and you were able to add = one. So now you are getting the message id at least on the incoming. But NO= T on the outgoing. =A0Is that correct?

=A0<= /p>

If so, the outgoing ma= ybe a lot more difficult. I have had some issues with the ws addressing hea= ders on the response. I do not know if it affecting your results.=

=A0<= /p>

Can you show the sent/= incoming SOAP message? That would help answer some of the other questions I= asked.

=A0<= /p>

Brian=

=A0<= /p>

=A0

From: Walid Benkhelouf [mailto:w_benkhelouf@esi.dz]
Sent: Friday, August 02, 2013 3:17 PM

<= div>


To: java-dev@axis.ap= ache.org
Subject: Re: retrieving message_id

=A0

Sorry for my stupid question ,the thing is that i'm not an expert in = axis or java programming ,i was using SOAPUI to simulate the client, i can = see now that i can add messageID from SOAPUI ,it's addressing my proble= m for the incoming,but i just wanna ask one more stupid question :) =A0:

-->is there an= y=A0property in common between the incoming and outgoing message ,that i ca= n use as primary key in my database that is used to store=A0incoming=A0mess= ages.(and when a response=A0occur without a problem ,this message will be= =A0drooped)=A0.=A0

=A0

2013/8/2 Brian Reinhold <brianreinhold@= lampreynetworks.com>

A stupid questi= on: you are sure that the message id field is sent by the client =85=

Is this null response onl= y on the incoming message?

<= span style=3D"font-size:11.0pt;font-family:"Calibri","sans-s= erif";color:#444444">And what version?

Sending secure or unsecur= e?

I know I had to do some m= essing around with the addressing modules to get the ws addressing headers = to appear in the response. But it=92s been a long time so I don=92t recall = the details.

=A0<= /p>

Brian=

=A0<= /p>

From: Walid Benkhelouf [mailto:w_benkhelouf@esi.dz]
Sent: Friday, August 02, 2013 2:33 PM
To: java-dev@axis.apache.org<= br>Subject: Re: retrieving message_id

=A0

h= i Martin,

yes i did this and i'm getting a null value in both = incoming and outgoing, even if "ws-addressing" is engaged.=

=A0

2013/8/2 Martin Gainty <mgainty@hotmail.com>

try
=A0mc.getMessageID()

(case matters)
=A0
does this help?
Mart= in
______________________________________________
Verzicht und Vert= raulichkeitanmerkung

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empf= aenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weit= erleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient= lediglich dem Austausch von Informationen und entfaltet keine rechtliche B= indungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen= wir keine Haftung fuer den Inhalt uebernehmen.

=A0

Date: Fri, 2= Aug 2013 18:55:18 +0200
Subject: Re: retrieving message_id
From: w_benkhelouf@esi.dz
To: java-dev@axis.apache.org

=A0

= I need to know if there is a=A0property=A0sha= red between the two messages(IN/OUT) ,

I was thinking th= at this=A0property=A0is the message_id contained in "messageContext.ge= tmessageID()" ,but i'm getting a null value when trying to retriev= e it (ws-addressing module is engaged)

=A0<= u>

=A0

2013/8/2 Brian Reinhold <brianreinhold@lamprey= networks.com>

Not sure I understand the problem ... is what you ar= e trying to do is
retrieve the ws:addressing message id?

Brian


-----Original Message-----
From: Walid Benkhelou= f [mailto:w_benkhe= louf@esi.dz]
Sent: Thursday, August 01, 2013 7:09 PM
To: java-dev@axis.apache.org
Subject: = retrieving message_id

Hello,

I'm developping a module tha= t handler in/out message from axis2 engine and
store them in a database.
I have two handlers :one for the incoming and = one for the outgoing.
I need to store the incoming ,and drop the outgoin= g messages.
The problem is that i need to have the same message_id so i = can access to
the database in the second time(the two messages needs to have the same
= key).
Thanks;

-------------= --------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For addi= tional commands, e-mail: java-dev-help@axis.apache.org


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013= .0.3392 / Virus Database: 3209/6543 - Release Date: 08/01/13


---= ------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For addi= tional commands, e-mail: java-dev-help@axis.apache.org

=A0

=A0

=A0=

No virus found in this message.
Checked by AVG -= www.avg.com=

Version: 2= 013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13

No virus f= ound in this message.
Checked by AVG - www.avg.com

Version: 2013.0.= 3392 / Virus Database: 3209/6545 - Release Date: 08/02/13<= /u>

=A0

No virus found in this message.
Checked by AVG - www.avg.c= om

Version: 2013.0.3392 / Virus Database: 3209/6547 - Rel= ease Date: 08/02/13

=A0

<= /div>

No virus found= in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3209/6548 - Release Date= : 08/03/13

No virus found in this m= essage.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3209/6548= - Release Date: 08/03/13


--f46d043be2286e8d7b04e31068cf--