Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Jetty Migration Issur

With that logging configuration, you'll be controlling the named loggers, their appenders, and their levels entirely within the log4j configuration setup you are using.  (Typically a log4j.xml or log4j.properties file you are managing)

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Thu, Sep 10, 2015 at 9:49 AM, Arun Kumar <arunkumarstay@xxxxxxxxx> wrote:
Hi Joakim ,

Thanks for the reply. I'm using slf4j-log4j12-1.6.6.jar , slf4j-api-1.6.6.jar and log4j1.2.7 for logging.
How to change log level from DEBUG to INFO of org.eclipse.Jetty in jetty9.
if I change log level from DEBUG to INFO it will print less log messages. I'm using embedded Jetty9.

Thanks,
Arun




On Tue, Sep 8, 2015 at 11:01 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
You have debug logging turned on, so you are seeing lots of logging lines.
Since you wanted to use the DeploymentManager you now have a Scanner.
Switch to the Jetty 9.3.2 and you'll have a different Scanner implementation (it uses Java's built-in File/Path Watcher Service instead)

OR don't use a DeploymentManager and a WebAppProvider and just hard code your WebAppContexts like we suggested in a prior email.


Joakim Erdfelt / joakim@xxxxxxxxxxx

On Tue, Sep 8, 2015 at 9:06 AM, Arun Kumar <arunkumarstay@xxxxxxxxx> wrote:
Hi Joakim/ Jesse,

Thanks for the reply. I have successfully deployed and the application is running in Jetty9.
But I have a query. In the logs below I can see the atEOF, parseNext, ishut, onClose ,Destroyed ,FILLING-->IDLE  are repeating . Also the [org.eclipse.jetty.util.Scanner] repeatedly showing scanned, scan accepted. Is this any issue? or new feature in Jetty9 ?.
Is it possible to disable this ?

2015-09-08 11:57:41,823 DEBUG [lipse.jetty.io.SelectorManager] [qtp11659892-27-selector-ServerConnectorManager@9c5521/1] - Running change org.eclipse.jetty.io.SelectChannelEndPoint$1@1e09cd3

2015-09-08 11:57:41,823 DEBUG [se.jetty.io.AbstractConnection] [qtp11659892-27-selector-ServerConnectorManager@9c5521/1] - FILL_INTERESTED-->FILLING HttpConnection@15d817e{FILLING}

2015-09-08 11:57:41,823 DEBUG [lipse.jetty.io.SelectorManager] [qtp11659892-27-selector-ServerConnectorManager@9c5521/1] - Selector loop waiting on select

2015-09-08 11:57:41,824 DEBUG [se.jetty.server.HttpConnection] [qtp11659892-53] - HttpConnection@15d817e{FILLING} onFillable HttpChannelState@157edea{s=IDLE i=true a=null}

2015-09-08 11:57:41,825 DEBUG [lipse.jetty.io.ChannelEndPoint] [qtp11659892-53] - filled -1 SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,Open,in,out,-,-,30000,HttpConnection}{io=0,kio=0,kro=1}

2015-09-08 11:57:41,825 DEBUG [lipse.jetty.io.ChannelEndPoint] [qtp11659892-53] - ishut SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,Open,in,out,-,-,30000,HttpConnection}{io=0,kio=0,kro=1}

2015-09-08 11:57:41,826 DEBUG [.eclipse.jetty.http.HttpParser] [qtp11659892-53] - atEOF HttpParser{s=START,0 of 0}

2015-09-08 11:57:41,826 DEBUG [.eclipse.jetty.http.HttpParser] [qtp11659892-53] - parseNext s=START HeapByteBuffer@bd297b[p=0,l=0,c=16384,r=0]={<<<>>>?????????????????...???????????????}

2015-09-08 11:57:41,826 DEBUG [ipse.jetty.io.AbstractEndPoint] [qtp11659892-53] - onClose SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,CLOSED,ISHUT,out,-,-,30000,HttpConnection}{io=0,kio=0,kro=1}

2015-09-08 11:57:41,826 DEBUG [lipse.jetty.io.ChannelEndPoint] [qtp11659892-53] - close SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,CLOSED,ISHUT,out,-,-,30000,HttpConnection}{io=0,kio=0,kro=1}

2015-09-08 11:57:41,827 DEBUG [lipse.jetty.io.SelectorManager] [qtp11659892-53] - Destroyed SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,CLOSED,ISHUT,OSHUT,-,-,30000,HttpConnection}{io=0,kio=-1,kro=-1}

2015-09-08 11:57:41,827 DEBUG [se.jetty.io.AbstractConnection] [qtp11659892-53] - onClose HttpConnection@15d817e{FILLING}

2015-09-08 11:57:41,827 DEBUG [ipse.jetty.io.AbstractEndPoint] [qtp11659892-53] - onClose SelectChannelEndPoint@bfd1a8{/10.235.1.202:55452<->14101,CLOSED,ISHUT,OSHUT,-,-,30000,HttpConnection}{io=0,kio=-1,kro=-1}

2015-09-08 11:57:41,827 DEBUG [.eclipse.jetty.http.HttpParser] [qtp11659892-53] - START --> CLOSED

2015-09-08 11:57:41,828 DEBUG [se.jetty.io.AbstractConnection] [qtp11659892-53] - FILLING-->IDLE HttpConnection@15d817e{IDLE}

2015-09-08 11:57:41,996 DEBUG [org.eclipse.jetty.util.Scanner] [Scanner-0] - scan accepted /pab/max/assume/msc/DEV/check/7.1.2_EV/webapps/axis2

2015-09-08 11:57:41,996 DEBUG [org.eclipse.jetty.util.Scanner] [Scanner-0] - scanned [/pab/max/assume/msc/DEV/check/7.1.2_EV/webapps]: {}

2015-09-08 11:57:43,016 DEBUG [org.eclipse.jetty.util.Scanner] [Scanner-0] - scan accepted /pab/max/assume/msc/DEV/check/7.1.2_EV/webapps/axis2

2015-09-08 11:57:43,017 DEBUG [org.eclipse.jetty.util.Scanner] [Scanner-0] - scanned [/pab/max/assume/msc/DEV/check/7.1.2_EV/webapps]: {}

Thanks,
Arun

On Tue, Sep 8, 2015 at 6:52 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
also, if you are migrating from Jetty 6, don't migrate to a Jetty 9 version that is already over 20 releases behind

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx

On Tue, Sep 8, 2015 at 8:06 AM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
WebAppProvider is something that the DeploymentManager object needs.
And the DeploymentManager is just a Bean on the Server object.

Let the normal LifeCycle management handle the start/stop process.
You should only ever have 1 call to *.start(), and that's the one for the Server.start().

See LikeJettyXml.java example for how this DeploymentManager is setup and configured.


Joakim Erdfelt / joakim@xxxxxxxxxxx

On Mon, Sep 7, 2015 at 9:31 AM, Arun Kumar <arunkumarstay@xxxxxxxxx> wrote:
Hi ,

I'm migrating Jetty6.1.19  to  Jetty9.1.1. I'm using the jetty-all-9.1.1.jar.

I'm facing NullPointerException in WebAppProvider.start() method. Below is the code snippet where I'm facing exception. Since there is no  setContext() method, I have not set context explicitly.
Here the value of warpath is 'webapps'. In my application the WAR file exists in the path ' pab/max/assume/msc/DEV/check/7.1.2_EV/webapps/axis2/WEB-INF/services/App.war '. I have attached the log. While scanning it throws NullPointer.
 
         this.jettyWebServer =new Server();

         WebAppProvider webAppDeployer=new WebAppProvider();

       

        //webAppDeployer.setContexts(this.jettyWebServer); ->commented setcontext

     

        webAppDeployer.setMonitoredDirName(warpath); -->warpth is 'webapps'

        webAppDeployer.setExtractWars(true);

        webAppDeployer.setParentLoaderPriority(true);

        webAppDeployer.start(); -->NullPointerException while scanning.

 

        this.jettyWebServer.setStopAtShutdown(true);

        this.jettyWebServer.start();        

        this.jettyWebServer.join();


Could someone please help me what is wrong in this?. Do I need to setContext manually.Please see the log attached.


Thanks,

Arun

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top