Grouper Users - Open Discussion List

[Baron Fujimoto <>]

On Thu, Feb 11, 2016 at 01:54:39AM +0000, Hyzer, Chris wrote:
>Regarding utf-8, can you save a utf-8 string group in your UI and see it 
>back in the UI?

It doesn't appear so. I tried to adding the group "utf8_👍" which resulted
in the following error:

2016-02-10 16:27:30,346: [http-nio-0.0.0.0-8443-exec-4] ERROR 
JDBCExceptionReporter.logExceptions(234) -  - Incorrect string value: 
'\xF0\x9F\x91\x8D' for column 'string02' at row 1
2016-02-10 16:27:30,355: [http-nio-0.0.0.0-8443-exec-4] WARN  
UiV2Group.newGroupSubmit(1592) -  - Error creating group: 
'*****'/'person'/'*****', null
edu.internet2.middleware.grouper.exception.GroupAddException: cannot create 
child group: , stem name: hawaii.edu:custom:test:baron, group extension: 
utf8_<U+1F44D>, group dExtension: utf8_<U+1F44D>, uuid: null, typeOfGroup: 
nullProblem create child group: 
Stem[displayName=hawaii.edu:custom:test:baron,name=hawaii.edu:custom:test:baron,uuid=19cc5c173f3f41598f5a53eb059821d0,creator=27a474b062734dca8053407f93396ac1],
 child: 
Group[name=hawaii.edu:custom:test:baron:utf8_<U+1F44D>,uuid=e5b7b2572ad747408031a5fc6a81d90c],
 memberDto: 'e5b7b2572ad747408031a5fc6a81d90c'/'group'/'g:gsa', Problem in 
HibernateSession: HibernateSession (57f76d0b): notNew, notReadonly, 
READ_WRITE_NEW, activeTransaction, session (755b52c4),
Exception in save: edu.internet2.middleware.grouper.changeLog.ChangeLogEntry, 
ByObjectStatic, query: ', cacheable: null, cacheRegion: null, entityName: 
ChangeLogEntryTemp, tx type: null,
Exception in save: edu.internet2.middleware.grouper.Group, 
edu.internet2.middleware.grouper.hibernate.ByObject@4e3e1f87,
Problem in HibernateSession: HibernateSession (2e0669e3): notNew, 
notReadonly, READ_WRITE_NEW, activeTransaction, session (755b52c4),
Problem in HibernateSession: HibernateSession (6003acea): notNew, 
notReadonly, READ_WRITE_NEW, activeTransaction, session (755b52c4),
Problem in HibernateSession: HibernateSession (6455bbf5): new, notReadonly, 
READ_WRITE_NEW, notActiveTransaction, session (755b52c4),
Problem saving group: hawaii.edu:custom:test:baron:utf8_<U+1F44D>, thread: 
6b33f8ec
        at edu.internet2.middleware.grouper.Stem$5.callback(Stem.java:2383)
        [...]

>About the patching, you shouldn’t apply API patches to a UI, only apply UI 
>patches (it will do the API too).

Hmm, ok. So I should just patch the UI? There won't be similar conflicts if
you want to patch the WS as well? Perhaps the "Grouper patching" wiki could
add this info. Lacking guidance to the contrary, I assumed patching the API
first before the UI and WS was reasonable given the dependencies (and also
given that [api] is the default component to patch in the grouperInstaller).


>I opened a jira which will allow you to do it that way in the future...
>
>https://bugs.internet2.edu/jira/browse/GRP-1248

Thanks!

>Thanks
>Chris

Aloha,
-baron

>-----Original Message-----
>From: Baron Fujimoto 
>[mailto:]
> 
>Sent: Wednesday, February 10, 2016 8:33 PM
>To: Hyzer, Chris 
><>
>Subject: Re: [grouper-users] patched 2.2.2: jarfile mismatch warning, utf8 
>error?
>
>Hi Chris,
>
>I applied the latest set of patches. They appear to have addressed the
>jarfile mismatch issue (tnx!), but the UTF8 error remains.
>
>Speaking of patches though, the grouper patching mechanism has been
>somewhat fragile in my experience. I often find myself having to "fix"
>patches that have already been applied. This seems to stem from the
>patches for components such as the UI or WS not properly accounting for
>previously applied patches say, in the API, or even in the same component
>(but I'm speculating). I don't see others on the grouper-users list
>reporting these sorts of tribulations though, which suggests my
>experiences are atypical?
>
>Generally my procedure has been, given the dependencies of the UI and WS
>on the API, to first patch the API, then the UI and WS respectively.
>
>For example, I was most recently able to successfully apply the API
>patches, but when I attempted to apply the UI patches, it complained that
>the one of the API patches has not been successfully applied. Usually the
>subsequent patch attempt for another component often results in these
>sorts of errors:
>
>Cannot apply patch since this patch file:
>  
> /[...]/installer-archive/grouper_v2_2_2_ui_patch_0/old/classes/grouperText/grouper.text.en.us.base.properties
>  is not the same as what the patch expects:
>  
> /[...]/grouper.ui-2.2.2/dist/grouper/WEB-INF/classes/grouperText/grouper.text.en.us.base.properties
> - added to end of property file: grouper_v2_2_2_ui_patch_0.state = error
>
>I've been working around these errors using the method described in the
>section "What if patch doesnt work do[sic] to edited files?"
><https://spaces.internet2.edu/display/Grouper/Grouper+patching>
>
>I didn't want to make this part of the reponse any longer, but I've
>attached a transcript of my recent round of patching which illustrates
>this.
>
>Aloha,
>-baron
>
>On Tue, Feb 09, 2016 at 06:46:26AM +0000, Hyzer, Chris wrote:
>>This is fixed in patch grouper_v2_2_2_api_patch_7
>>
>>https://bugs.internet2.edu/jira/browse/GRP-1247
>>
>>Thanks,
>>Chris
>>
>>On Wed, Feb 3, 2016 at 5:22 PM, Baron Fujimoto 
>><<mailto:>>
>> wrote:
>>After my last usage of the grouperInstaller to bring our instances of
>>Grouper 2.2.2 to the current patch level, I'm now seeing the following
>>in our tomcat logs:
>>
>>Grouper warning: jarfile mismatch, expecting name: 'subject.jar' size: 
>>262091 manifest version: 2.2.2.  However the jar detected is: 
>>/home/grouper/grouper/grouper.ui-2.2.2/dist/grouper/WEB-INF/lib/subject.jar,
>> name: subject.jar size: 261985 manifest version: 2.2.2
>>Error: Cannot properly read UTF string from resource: grouperUtf8.txt: 
>>'ٹٺٻټكلل'
>>
>>I'm not actually sure what patches were installed, but I can see that
>>these warnings and errors weren't issued in previous log files.
>>
>>Googling seems to turn up numerous instances of the jarfile mismatch 
>>warning,
>>including this 2.2.1->2.2.2 upgrade example page:
>><https://spaces.internet2.edu/display/Grouper/Grouper+v2.2.1+upgrade+to+v2.2.2+example>
>>But I haven't found anything that actually discusses the warning itself.
>>
>>As far the UTF8 error, we have all of the recommendations on the
>>Internationalization page at
>><https://spaces.internet2.edu/display/Grouper/Grouper+internationalization>
>>and, as noted, afaik, it was working previously.
>
>-- 
>Baron Fujimoto 
><>
> :: UH Information Technology Services
>minutas cantorum, minutas balorum, minutas carboratum desendus pantorum

-- 
Baron Fujimoto 
<>
 :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum