Setup development environment using java-idp-testbed

Fri Apr 13 00:05:40 EDT 2018

>  Jetty version. I didn't even think to compare what the POM for the
testbed mentions, and I had grabbed the latest Jetty 9.3 to stick in /opt.
They presumably would have to match.

When I tried using 9.3.23.v20180228 instead of 9.3.16.v20170120, Jetty just
worked.
But Shibboleth IdP returns "No services are available at this location."
error in web browser.

1. Change java-idp-testbed/pom.xml to use jetty-9.3.23.v20180228
-        <jetty.version>9.3.16.v20170120</jetty.version>
+        <jetty.version>9.3.23.v20180228</jetty.version>

2. Get dependent packages to local maven directory.
$ cd java-idp-testbed
$ mvn dependency:go-offline

3.  Run Main.java in java-idp-testbed as Java Application again.

Here is the logs from
java-idp-jetty-base\src\main\resources\jetty-base\logs\2018_04_13.stderrout.log:
> WARN [org.eclipse.jetty.xml.XmlConfiguration:983] - Property 'jetty.host'
is deprecated, value from 'jetty.nonhttps.host' used
> 11:18:08,895 |-INFO in null - Will use configuration file
[C:\Users\<username>\Documents\pleiades-4.7.2-java-win-64bit-jre_20171225\shib\java-idp-jetty-base\src\main\resources\jetty-base/resources/logback-access.xml]
> 11:18:08,910 |-INFO in
ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute
not set
> 11:18:08,913 |-INFO in
ch.qos.logback.core.joran.action.StatusListenerAction - Added status
listener of type [ch.qos.logback.core.status.OnConsoleStatusListener]
> 11:18:08,922 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
About to instantiate appender of type
[ch.qos.logback.core.rolling.RollingFileAppender]
> 11:18:08,926 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
Naming appender as [FILE]
> 11:18:08,946 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy at 225290371
- Will use gz compression
> 11:18:08,948 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy at 225290371
- Will use the pattern
C:/Users/<username>/Documents/pleiades-4.7.2-java-win-64bit-jre_20171225/shib/java-idp-jetty-base/src/main/resources/jetty-base/logs/access-%d{yyyy-MM-dd}.log
for the active file
> 11:18:08,955 |-INFO in
c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date
pattern is 'yyyy-MM-dd' from file name pattern
'C:/Users/<username>/Documents/pleiades-4.7.2-java-win-64bit-jre_20171225/shib/java-idp-jetty-base/src/main/resources/jetty-base/logs/access-%d{yyyy-MM-dd}.log.gz'.
> 11:18:08,956 |-INFO in
c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy -
Roll-over at midnight.
> 11:18:08,957 |-INFO in
c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting
initial period to Fri Apr 13 09:48:18 JST 2018
> 11:18:08,957 |-INFO in
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default
type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property
> 11:18:08,989 |-INFO in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file
name:
C:\Users\<username>\Documents\pleiades-4.7.2-java-win-64bit-jre_20171225\shib\java-idp-jetty-base\src\main\resources\jetty-base/logs/access.log
> 11:18:08,989 |-INFO in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is
set to
[C:\Users\<username>\Documents\pleiades-4.7.2-java-win-64bit-jre_20171225\shib\java-idp-jetty-base\src\main\resources\jetty-base/logs/access.log]
> 11:18:08,989 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction
- Attaching appender named [FILE] to null
> 11:18:09,004 |-INFO in
ch.qos.logback.access.joran.action.ConfigurationAction - End of
configuration.
> 11:18:09,004 |-INFO in
ch.qos.logback.access.joran.JoranConfigurator at ba8d91c - Registering current
configuration as safe fallback point
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.AsyncContext scanned from multiple locations:
[jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncContext.class,
jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/AsyncContext.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.AsyncEvent scanned from multiple locations:
[jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/AsyncEvent.class,
jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.Filter scanned from multiple locations:
[jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/Filter.class,
jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/Filter.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.ServletOutputStream scanned from multiple locations:
[jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/ServletOutputStream.class,
jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/ServletOutputStream.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.annotation.HttpMethodConstraint scanned from multiple
locations:
[jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/annotation/HttpMethodConstraint.class,
jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/annotation/HttpMethodConstraint.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.http.HttpUtils scanned from multiple locations:
[jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/http/HttpUtils.class,
jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/http/HttpUtils.class]
> WARN [org.eclipse.jetty.annotations.AnnotationParser:572] -
javax.servlet.http.NoBodyResponse scanned from multiple locations:
[jar:file:///C:/Users/<username>/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar!/javax/servlet/http/NoBodyResponse.class,
jar:file:///C:/jetty-9.3/lib/servlet-api-3.1.jar!/javax/servlet/http/NoBodyResponse.class]
> WARN [org.eclipse.jetty.security.SecurityHandler:806] -
ServletContext at o.e.j.w.WebAppContext@96def03{/idp,[file:///C:/Users/<username>/Documents/pleiades-4.7.2-java-win-64bit-jre_20171225/shib/java-idp-jetty-base/src/main/resources/jetty-base/tmp/jetty-0.0.0.0-9443-webapp-_idp-any-3463708866813710343.dir/webinf/,
file:///C:/Users/<username>/Documents/pleiades-4.7.2-java-win-64bit-jre_20171225/shib/java-identity-provider/idp-war/src/main/webapp/],STARTING}{../../../../../java-identity-provider/idp-war/src/main/webapp}
has uncovered http methods for path: /*
Thanks,

--
------------------------------------------------------
    Kohei Moriya

    Software Engineer
    Application Consulting Group
    Engineering Dept. 2
    SIOS Technology, Inc.
------------------------------------------------------

2018-04-13 5:11 GMT+09:00 Cantor, Scott <cantor.2 at osu.edu>:

> > > Here is the messages from Eclipse console:
> > >
> > > > WARNING: Nothing to start, exiting ...
> > > > Usage: java -jar start.jar [options] [properties] [configs]
> > > >        java -jar start.jar --help  # for more information
> >
> > FWIW I have a new laptop and when I finally got around to working on
> > setting up the testbed there I got the same message. I haven't bottomed
> it
> > out yet. I did have it working on another Windows laptop so I need to
> > compare my setup.
>
> Jetty version. I didn't even think to compare what the POM for the testbed
> mentions, and I had grabbed the latest Jetty 9.3 to stick in /opt. They
> presumably would have to match.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20180413/3652a6d5/attachment-0001.html>