Re: Re: Re: Sling 12 issue

2023-04-18 Thread Eric Norman
Hi Rahul,


> the stdout log generated in sling 11 is missing in sling 12 do you have any
> idea about that?
>

I don't recollect the specific behavior of sling 11.  If the
explanation below doesn't resolve the problem perhaps you can provide some
more details?

In sling 12 any logging output that comes from any of the supported logging
apis (slf4j, log4j, juli, commons.logging), should end up in one of the log
files under the launcher/logs/* folder.

Any logging that is directly using the System.out or System.err PrintStream
apis should still be written to the console.

Regards,
Eric

On Tue, Apr 18, 2023 at 6:21 AM Rahul Rupani 
wrote:

> On 2023/04/12 15:49:23 Eric Norman wrote:
> > Hi Rahul,
> >
> > The launcher script allows you to utilize the JAVA_OPTS environment
> > variable to supply java remote debugging arguments to the jvm.
> >
> > For example, to set the env variable and run the launcher with a one-line
> > subshell, you can execute something like this to open port 5000 for
> remote
> > debugging:
> >
> > (export
> >
>
> JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
> > && target/dependency/org.apache.sling.feature.launcher/bin/launcher -f
> > target/slingfeature-tmp/feature-oak_tar.json)
> >
> >
> > One way to change the http port would be to supply an "
> > org.osgi.service.http.port" framework property value as an argument to
> the
> > launcher script.   For example, to use  as the http port use
> something
> > like this:
> >
> > (export
> >
>
> JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
> > && target/dependency/org.apache.sling.feature.launcher/bin/launcher *-D
> > org.osgi.service.http.port=* -f
> > target/slingfeature-tmp/feature-oak_tar.json)
> >
> >
> >
> > Hope that helps.
> > Eric
> >
> > On Wed, Apr 12, 2023 at 12:47 AM Rahul Rupani 
> > wrote:
> >
> > > On 2023/04/05 08:14:59 Robert Munteanu wrote:
> > > > Hi Rahul,
> > > >
> > > > On Wed, 2023-04-05 at 08:56 +0530, rahul rupani wrote:
> > > > > Hi, can anyone help me with turning on or creating a debug port for
> > > > > sling
> > > > > 12 as I'm having trouble doing it, Thanks.
> > > >
> > > > How are launching Sling?
> > > >
> > > > Thanks,
> > > > Robert
> > > >  using this command -
> > > target/dependency/org.apache.sling.feature.launcher/bin/launcher
> > > I've followed all the steps from here -
> > > https://github.com/apache/sling-org-apache-sling-starter
> > > I need to manipulate the port that sling starts on and add a debug port
> too
> > > but can't figure it out as it automatically launches using jetty..
> > > Thanks for your help.
> > >
> >  Thank you so much Eric, that's exactly what i needed, one last thing,
> the stdout log generated in sling 11 is missing in sling 12 do you have any
> idea about that?
>


RE: Re: Re: Sling 12 issue

2023-04-18 Thread Rahul Rupani
On 2023/04/12 15:49:23 Eric Norman wrote:
> Hi Rahul,
>
> The launcher script allows you to utilize the JAVA_OPTS environment
> variable to supply java remote debugging arguments to the jvm.
>
> For example, to set the env variable and run the launcher with a one-line
> subshell, you can execute something like this to open port 5000 for remote
> debugging:
>
> (export
>
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
> && target/dependency/org.apache.sling.feature.launcher/bin/launcher -f
> target/slingfeature-tmp/feature-oak_tar.json)
>
>
> One way to change the http port would be to supply an "
> org.osgi.service.http.port" framework property value as an argument to the
> launcher script.   For example, to use  as the http port use something
> like this:
>
> (export
>
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
> && target/dependency/org.apache.sling.feature.launcher/bin/launcher *-D
> org.osgi.service.http.port=* -f
> target/slingfeature-tmp/feature-oak_tar.json)
>
>
>
> Hope that helps.
> Eric
>
> On Wed, Apr 12, 2023 at 12:47 AM Rahul Rupani 
> wrote:
>
> > On 2023/04/05 08:14:59 Robert Munteanu wrote:
> > > Hi Rahul,
> > >
> > > On Wed, 2023-04-05 at 08:56 +0530, rahul rupani wrote:
> > > > Hi, can anyone help me with turning on or creating a debug port for
> > > > sling
> > > > 12 as I'm having trouble doing it, Thanks.
> > >
> > > How are launching Sling?
> > >
> > > Thanks,
> > > Robert
> > >  using this command -
> > target/dependency/org.apache.sling.feature.launcher/bin/launcher
> > I've followed all the steps from here -
> > https://github.com/apache/sling-org-apache-sling-starter
> > I need to manipulate the port that sling starts on and add a debug port
too
> > but can't figure it out as it automatically launches using jetty..
> > Thanks for your help.
> >
>  Thank you so much Eric, that's exactly what i needed, one last thing,
the stdout log generated in sling 11 is missing in sling 12 do you have any
idea about that?


Re: Re: Sling 12 issue

2023-04-12 Thread Eric Norman
Hi Rahul,

The launcher script allows you to utilize the JAVA_OPTS environment
variable to supply java remote debugging arguments to the jvm.

For example, to set the env variable and run the launcher with a one-line
subshell, you can execute something like this to open port 5000 for remote
debugging:

(export
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
&& target/dependency/org.apache.sling.feature.launcher/bin/launcher -f
target/slingfeature-tmp/feature-oak_tar.json)


One way to change the http port would be to supply an "
org.osgi.service.http.port" framework property value as an argument to the
launcher script.   For example, to use  as the http port use something
like this:

(export
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,address=5000,server=y,suspend=n"
&& target/dependency/org.apache.sling.feature.launcher/bin/launcher *-D
org.osgi.service.http.port=* -f
target/slingfeature-tmp/feature-oak_tar.json)



Hope that helps.
Eric

On Wed, Apr 12, 2023 at 12:47 AM Rahul Rupani 
wrote:

> On 2023/04/05 08:14:59 Robert Munteanu wrote:
> > Hi Rahul,
> >
> > On Wed, 2023-04-05 at 08:56 +0530, rahul rupani wrote:
> > > Hi, can anyone help me with turning on or creating a debug port for
> > > sling
> > > 12 as I'm having trouble doing it, Thanks.
> >
> > How are launching Sling?
> >
> > Thanks,
> > Robert
> >  using this command -
> target/dependency/org.apache.sling.feature.launcher/bin/launcher
> I've followed all the steps from here -
> https://github.com/apache/sling-org-apache-sling-starter
> I need to manipulate the port that sling starts on and add a debug port too
> but can't figure it out as it automatically launches using jetty..
> Thanks for your help.
>


RE: Re: Sling 12 issue

2023-04-12 Thread Rahul Rupani
On 2023/04/05 08:14:59 Robert Munteanu wrote:
> Hi Rahul,
>
> On Wed, 2023-04-05 at 08:56 +0530, rahul rupani wrote:
> > Hi, can anyone help me with turning on or creating a debug port for
> > sling
> > 12 as I'm having trouble doing it, Thanks.
>
> How are launching Sling?
>
> Thanks,
> Robert
>  using this command -
target/dependency/org.apache.sling.feature.launcher/bin/launcher
I've followed all the steps from here -
https://github.com/apache/sling-org-apache-sling-starter
I need to manipulate the port that sling starts on and add a debug port too
but can't figure it out as it automatically launches using jetty..
Thanks for your help.