Grouper Users - Open Discussion List

[Chris Hyzer <>]

This could be chunking

http://en.wikipedia.org/wiki/Chunked_transfer_encoding

got this from the Axis SOAP list, obviously this is for the Axis client, but 
you just need to set the HTTP header in perl.

############
On the client side you can disable chunking, ie the 0 indicates the
size of the next chunk
(0) meaning the message is finished. You would then be using
content-length instead, IIRC.

        Options option = client.getOptions();
        option.setProperty(HTTPConstants.CHUNKED,false);
#############

Ive never tried not using chunked encoding, give it a try.

All the samples of grouper WS end in 0, and have the chunk size.  

http://anonsvn.internet2.edu/viewvc/viewvc.py/i2mi/tags/GROUPER_2_1_5/grouper-ws/grouper-ws/doc/samples/stemSave/WsSampleStemSave_soap.txt?revision=8390&view=co

Not really sure why that 0 is passed the xml parser in perl, the HTTP client 
should strip it out I would think.

Does this help or do you need more help?  :)

Thanks,
Chris




-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Mike Roszkowski
Sent: Wednesday, April 02, 2014 5:10 PM
To: 

Subject: [grouper-users] Occasional error after successful addMemberLite and 
deleteMemberLite ws calls

We have a script (perl using SOAP-Lite) that makes grouper ws calls to add 
and remove
members from groups.

We are running Grouper v2.1.1.

Sporadically, when we get the SOAP response from the addMemberLite or 
deleteMemberLite
call, there will be a trailing ascii "0" after the </soapenv:Envelope> close 
tag.
The SOAP-Lite parser complains of "junk after document element".

The SOAP response always indicates that the operation was successful (see an 
example, below).

This happens very infrequently.  For example, out of nearly 350,000 
addMemberLite calls,
we've seen about 5 of these failures and out of nearly 250,000 
deleteMemberLite calls,
we've seen about 7 of these failures (all in our production grouper instance).

We've seen identical failures in both our test system and our production 
system.

They do tend to happen in batches -- we had 5 of these failures in the last 2 
days in
production and test.

Has anyone seen anything similar? Given the infrequent nature of the problem 
and the
volume of ws calls, I haven't turned on logging of the requests/responses as 
outlined
in the wiki.

Any advice on how to isolate the problem?

Here's an example of the client (perl) side log of one of the errors:

Wed Apr  2 14:27:10 2014 soap_harvester.cgi [23236]: [2005 - DispatchGrouper] 
SO
AP error in add_member:
                                                     junk after document 
element
 at line 6, column 0, byte 2031 at 
/usr/local/reg_sync/perl/lib/site_perl/5.16.1
/x86_64-linux-thread-multi/XML/Parser.pm line 187.
                                                     <?xml version='1.0' 
encodin
g='utf-8'?><soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/enve
lope/"><soapenv:Body><ns:addMemberLiteResponse 
xmlns:ns="http://soap_v2_1.ws.gro
uper.middleware.internet2.edu/xsd"><ns:return 
xmlns:xsi="http://www.w3.org/2001/
XMLSchema-instance" xsi:type="ns:WsAddMemberLiteResult"><ns:responseMetadata 
xsi
:type="ns:WsResponseMeta"><ns:millis xsi:nil="true" /><ns:resultWarnings 
xsi:nil
="true" 
/><ns:serverVersion>2.1.0</ns:serverVersion></ns:responseMetadata><ns:re
sultMetadata xsi:type="ns:WsResultMeta"><ns:params xsi:nil="true" 
/><ns:resultCo
de>SUCCESS</ns:resultCode><ns:resultCode2 xsi:nil="true" 
/><ns:resultMessage>Suc
cess for: clientVersion: 2.1.0, wsGroupLookup: 
WsGroupLookup[pitGroups=[],groupN
ame=uw:ref:phraw:WISCARD|WISCARD_HOLDER], subjectLookups: Array size: 1: [0]: 
Ws
SubjectLookup[subjectId=000000339094]

                                                     , replaceAllExisting: 
false
, actAsSubject: null, fieldName: null, txType: NONE, includeGroupDetail: 
false,
includeSubjectDetail: false, subjectAttributeNames: null
                                                     , params: null
                                                     , disabledDate: null, 
enabl
edDate: 
null</ns:resultMessage><ns:success>T</ns:success></ns:resultMetadata><ns
:subjectAttributeNames xsi:nil="true" /><ns:wsGroupAssigned 
xsi:type="ns:WsGroup
"><ns:description>Auto-generated by regsync</ns:description><ns:detail 
xsi:nil="
true" 
/><ns:displayExtension>WISCARD|WISCARD_HOLDER</ns:displayExtension><ns:dis
playName>UW-Madison:ref:phraw:WISCARD|WISCARD_HOLDER</ns:displayName><ns:extensi
on>WISCARD|WISCARD_HOLDER</ns:extension><ns:name>uw:ref:phraw:WISCARD|WISCARD_HO
LDER</ns:name><ns:typeOfGroup>group</ns:typeOfGroup><ns:uuid>038d172b6c3f489aaba
d2a6362394c83</ns:uuid></ns:wsGroupAssigned><ns:wsSubject 
xsi:type="ns:WsSubject
"><ns:attributeValues xsi:nil="true" 
/><ns:id>000000339094</ns:id><ns:identifier
Lookup xsi:nil="true" 
/><ns:name>REMOVED-PII</ns:name><ns:resultCode>SUCCESS</ns
:resultCode><ns:sourceId>jdbc</ns:sourceId><ns:success>T</ns:success></ns:wsSubj
ect></ns:return></ns:addMemberLiteResponse></soapenv:Body></soapenv:Envelope>
                                                     0

                                                      at 
/usr/local/reg_sync/per
l/lib/site_perl/5.16.1/UWDS/Export/Dispatch/Output/Grouper.pm line 998.
Wed Apr  2 14:27:10 2014 soap_harvester.cgi [23236]: [2005 - DispatchGrouper] 
Er
ror adding member 000000339094 to group uw:ref:phraw:WISCARD|WISCARD_HOLDER


It all looks fine in the grouper logs; we just see the following in 
grouper_error.log:

2014-04-02 14:27:03,583: [TP-Processor2] INFO  EventLog.info(141) - < 
GrouperSystem - 144.92.104.50 > -
[75d3a7a103dc41fea6e1411d9eaac06a,'GrouperSystem','application'] add member: 
group='uw:ref:phraw:WISCARD|WISCARD_HOLDER' list='members'
subject='000000339094'/'person'/'jdbc' (43ms)

Thanks for any advice you can offer.
--Mike Roszkowski
University of Wisconsin-Madison