Hi Juerg, On Sun, 2021-01-10 at 22:23 +0100, JCR wrote: > Thanks, Paul! > > By the wording here: > https://sling.apache.org/documentation/development/slingstart.html#debugging-1 > > , I was under the impression that the launchpad.debug option would > add > these parameters implicitly.
That page refers to the slingstart-maven-plugin, not to the launcher jar itself. "Since version 1.2.0 of this plugin it is possible to easily start a Sling server in debug mode..." So if you're launching the application using the slingstart-maven- plugin from within a Maven project, you only need to pass - Dlaunchpad.debug. Otherwise you need to pass the full set of options. Hope that helps, Robert > > Works now, thanks a lot! > Juerg > > On 08.01.21 13:44, Paul Bjorkstrand wrote: > > Sounds like you are missing the debugging jvm arg: > > -agentlib:jdwp=transport=dt_socket,address=30303,server=y,suspend=n > > > > Take a look at the debugging > > instructions: > > https://sling.apache.org/documentation/development/getting-and-building-sling.html#debug-sling-in-eclipse-1 > > > > Happy debugging! > > > > On Fri, Jan 8, 2021, 06:22 JCR <j...@proxymit.net> wrote: > > > > > Hello > > > > > > I tried starting up Sling standalone in debug mode, by either > > > providing > > > the debug-param on the command line (java -Dlaunchpad.debug=true > > > -jar > > > org.apache.sling.starter-11.jar) and modifying sling.properties > > > respectively (by adding line launchpad.debug=true). In either > > > case, > > > Eclipse is unable to connect, reporting that port 30303 is not > > > available. > > > > > > What's missing? > > > > > > Thanks, > > > Juerg > > > > > >
