Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Im not sure why the jars aren’t there.  I opened a jira

https://todos.internet2.edu/browse/GRP-2125

Though I don’t think many people use the EsbConsumer, they only use the 
EsbPublisher.  What are you looking to do?

You can get the jars in the API tarball, or for 2.4, here:

https://github.com/Internet2/grouper/tree/master/grouper/lib/jetty

thanks
Chris

-----Original Message-----
From:  
<> On Behalf Of Black, Carey M.
Sent: Wednesday, May 08, 2019 12:07 AM
To: Reid Watson <>
Cc: 
Subject: RE: [grouper-users] Caused by: java.lang.ClassNotFoundException: 
org.mortbay.jetty.HttpException - Missing jetty-6.1.26.jar

Reid,

I will also say this.... You likely need to install " 
grouperInstaller.autorun.installClient = t ".

The under pinning of the grouper messaging uses the grouper client for at 
least the "sending messages" part. And maybe the internal "messaging 
constructs as a whole? ( You end up configuring the grouper.client.properties 
to setup "a" [any?] messaging system(s). )
I have not looked at "receiving messages" yet... not on my current 
roadmap/plan.


FWIW: Which message system are you wanting to send/receive from?



If one of these then turn the right one(s) on, or just install them all if 
you want... 
( I only installed the AwsSqsMessaging because that is all I have current 
plans on using. )

grouperInstaller.autorun.installGrouperActiveMqMessaging = f
grouperInstaller.autorun.installGrouperAwsSqsMessaging = f
grouperInstaller.autorun.installGrouperRabbitMqMessaging = f

* NOTE: When you install the AwsSqsMessaging .. It looks for the 
grouperClient.jar... if not found.. it asks you where you want it installed 
again. ( loop, fail... loop, fail ..., restart installer and install the 
client then AwsSqsMessaging .. sigh....)



I think that will get you part of the way there...  
It should at least get you to a working way to send AwsSQS messages. Well it 
did for me. :)
But I doubt that just that will fix the ESB issues totally.


Maybe the SCIM install will? ( I have not done this.. just a guess. It might 
not help.  ) 
grouperInstaller.autorun.installGrouperWsScim = t

I think that might get you those jetty jars moved into a place .... ( a tomee 
install? https://tomee.apache.org/  Hum... maybe not?)

YMMV. Good luck. 

( Hopefully the "Grouper gods with smile upon you(and us)" and enlighten us 
all with the details. )

-- 
Carey Matthew 

-----Original Message-----
From: Reid Watson <> 
Sent: Tuesday, May 7, 2019 11:02 PM
To: Black, Carey M. <>
Cc: 
Subject: Re: Caused by: java.lang.ClassNotFoundException: 
org.mortbay.jetty.HttpException - Missing jetty-6.1.26.jar

Hi Carey, 

Thank you for the information 

> How did you install grouper? 

Grouper Jar with an installer file “grouper.installer.properties"

Command —> bin/java -cp .:grouperInstaller.jar 
edu.internet2.middleware.grouperInstaller.GrouperInstaller

Overview with grouper.installer.properties 

grouperInstaller.autorun.installUi = t
grouperInstaller.autorun.installClient = t
grouperInstaller.autorun.installPspng = t

grouperInstaller.autorun.deleteAndInitDatabase = t
grouperInstaller.autorun.addQuickstartData = f
grouperInstaller.autorun.installClient = f

grouperInstaller.autorun.installGrouperActiveMqMessaging = f
grouperInstaller.autorun.installGrouperAwsSqsMessaging = f
grouperInstaller.autorun.installGrouperRabbitMqMessaging = f

grouperInstaller.autorun.installUi = t
grouperInstaller.autorun.installClient = f
grouperInstaller.autorun.grouperClientErrorContinue = f
grouperInstaller.autorun.installPspng = t
grouperInstaller.autorun.installGrouperWsScim = f
grouperInstaller.autorun.installPsp = f

Patches 
grouper_v2_4_0_api_patch_45
grouper_v2_4_0_ui_patch_23
grouper_v2_4_0_ws_patch_5
grouper_v2_4_0_pspng_patch_6

> If grouperInstaller.jar
>       Did you install the SCIM server extension? ( I am guessing no. But I 
> have no knowledge that it would fix your error either. But maybe...)
>       Did you install the ESB extension? ( I am also guessing no. But I 
> have no knowledge that it would fix your error either. But maybe…)


No I didn’t 

Thank you for all the information — maybe my grouper.installer.properties 
file is incorrect, I will quickly install 2.4.0 manually just to see if there 
is a difference  

Cheers

Reid 


> On 8/05/2019, at 2:23 PM, Black, Carey M. <> wrote:
> 
> Reid,
> 
> Before someone else asks... How did you install grouper? 
> 
> Via the grouperInstaller.jar or using a docker container?
> 
> If grouperInstaller.jar
>       Did you install the SCIM server extension? ( I am guessing no. But I 
> have no knowledge that it would fix your error either. But maybe...)
>       Did you install the ESB extension? ( I am also guessing no. But I 
> have no knowledge that it would fix your error either. But maybe...)
> 
> If using a Docker container:
>       Which patch level are you using?
> 
> 
> 
> 
> 
> FWIW: (not exactly what you're looking for...)
> 
> I have managed to get the core grouper Messaging to work without those 
> extensions. 
> But found that the AWS SNS integration code nowhere to be found in my 
> install. ( I also had "missing classes" when I tried the esb.publisher that 
> was in my install. I don't remember what class it complained about at the 
> moment. Though I do not have SCIM server extension installed. Maybe that 
> was my error? )
> 
> I did get the AWS SQS integration working after installing the ESB 
> extension and fumbling with the configuration for a few days. ( Ugh. )
>       I resorted to using the .aws/config file to set the  [default] 
> region=<value> setting. ( Sigh )
>       Then I finally got a "bad password" error ( finally something kind of 
> worked)... ( Using capital "oh"'s and Zero's in a password is not a good 
> idea when a human needs to type them. Always. <-- fail )
>       Then I had miss read the code and thought the ".queueOrTopicName" 
> value needed to be the URL for the queue.
>               It only needs to be the name of the Queue for SQS. The 
> authenticated AWS session looks up the URL for the queue. DOH!  
>               I was getting an "unknown queue" error... "But the config 
> value looked 'right' to me". ( Sigh. A forehead flattener for sure. Really 
> self-inflicted, so don’t do that. :) )
>       Finally the messages were sent.
>       Lastly.. I had to enhance the ChangeLogConsumerToMessage.java to 
> support "obvious" features like ( I mostly "copied/altered" from the 
> src.esb.edu.internet2.middleware.grouper.changeLog.esb.consumer.EsbConsumer 
> code into my change log consumer) :
>               Filter the event sent ( It was sending all of them.)
>               Support adding Subject attributes. ( It did not have that 
> feature.)
>               Filter the attributes sent ( it was sending all of them.)
> 
>               Now that I am writing this I really should have also added a 
> setting for the AWS region and figured out how to add that to the AWS auth 
> process.... ( Feature enhancement! )
> 
> Sigh, another custom Change Log consumer.
> 
> 
> 
> Oh and if you are being told to install anything that is jetty-6.1. You 
> should likely just run away. 
> It looks like jetty 6 was deprecated/end of life in 2010.( About a decade 
> ago.)  9.2 was EOL'ed Jan 2018. ( Yikes! ) 
>       Jetty 9.3 or 9.4 are listed as "stable". 
>       
> And I have no idea why a "Jetty" jars would be needed. 
> Are you using Tomcat? ( as most default grouper installs would use? ) 
> 
> Maybe the SCIM server was only designed to run in a JETTY server?! Or needs 
> some libs that Tomcat did/does(?) not have?!
> 
> -- 
> Carey Matthew 
> 
> -----Original Message-----
> From:  
> <> On Behalf Of Reid Watson
> Sent: Tuesday, May 7, 2019 7:41 PM
> To: 
> Subject: [grouper-users] Caused by: java.lang.ClassNotFoundException: 
> org.mortbay.jetty.HttpException - Missing jetty-6.1.26.jar
> 
> Hi Everyone, 
> 
> Very quick question about “jetty-6.1.*.jar”, when installing Grouper 2.4.0. 
> (Default install) we noticed certain jar’s a missing from a specific path 
> “grouper.apiBinary-2.4.0/lib/grouper”, investigating further we found the 
> jar’s are located within
> 
> grouper.ws-2.4.0/grouper-ws-scim/targetBuiltin/grouper-ws-scim/WEB-INF/lib/jetty-6.1.26.jar
> grouper.ws-2.4.0/grouper-ws-scim/targetBuiltin/grouper-ws-scim/WEB-INF/lib/jetty-util-6.1.26.jar
> 
> Were currently attempting to run “EsbHttpPublisher / EsbConsumer” by 
> setting the following fields within “grouper-loader.properties" 
> 
> changeLog.consumer.esb.class = 
> edu.internet2.middleware.grouper.changeLog.esb.consumer.EsbConsumer
> changeLog.consumer.esb.publisher.class = 
> edu.internet2.middleware.grouper.changeLog.esb.consumer.EsbHttpPublisher
> 
> From the API logs we receive the following error message 
> 
> Caused by: java.lang.NoClassDefFoundError: org/mortbay/jetty/HttpException
>        at java.lang.Class.forName0(Native Method)
>        at java.lang.Class.forName(Class.java:186)
>        at 
> edu.internet2.middleware.grouper.util.GrouperUtil.forName(GrouperUtil.java:1590)
>        ... 26 more
> Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HttpException
> 
> When checking “/grouper.apiBinary-2.4.0/lib/grouper/“ the jar’s are 
> missing, reading an old thread from 2013 
> “https://lists.internet2.edu/sympa/arc/grouper-users/2013-06/msg00083.html” 
> an engineer stated the following comment 
> 
> “I assume I am missing some jar file in the api/lib/grouper directory? I 
> didn’t see anything about this in the wiki."
> 
> I would prefer someone from the grouper community review before I create a 
> Jira ticket 
> 
> Cheers
> 
> Reid 
> 
> 
> 
>