Ok, I got it

I launched jetty with --create-files and this
1) created each missing directory and print a line like "MKDIR /path"
2) exit without any other output

Then I issue the same command without --create-files and jetty started
properly

So I suppose that the warning about missing directory in fact is a blocking
error..... or I'm wrong?

I'd prefer to skip these warning, but if it's not possibile I'll create
them empty



2014-02-01 Andrea Cappelli <[email protected]>:

> Hi Simone,
> thanks for your reply
>
> Here the info you requested (upstart script calls the same except that
> instead of --list-config there is --daemon)
>
> /usr/lib/jvm/java-1.7.0-oracle/bin/java -server -Xms256m -Xmx1024m
> -XX:+DisableExplicitGC -Djetty.home=/var/jolie/webreserv/jetty_9.1.1/
> -Djetty.base=/var/jolie/webreserv/jetty-instances-enabled/gc -jar
> /var/jolie/webreserv/jetty_9.1.1/start.jar --list-config
>
>
> Java Environment:
> -----------------
>  java.home = /usr/lib/jvm/jdk1.7.0_45/jre
>  java.vm.vendor = Oracle Corporation
>  java.vm.version = 24.45-b08
>  java.vm.name = Java HotSpot(TM) 64-Bit Server VM
>  java.vm.info = mixed mode
>  java.runtime.name = Java(TM) SE Runtime Environment
>  java.runtime.version = 1.7.0_45-b18
>  java.io.tmpdir = /tmp
>  user.dir = /root
>  user.language = en
>  user.country = US
>
> Jetty Environment:
> -----------------
>  jetty.home = /var/jolie/webreserv/jetty_9.1.1
>  jetty.base = /var/jolie/webreserv/jetty-instances-available/gc
>  jetty.version = 9.1.1.v20140108
>
> JVM Arguments:
> --------------
>  (no jvm args specified)
>
> System Properties:
> ------------------
>  jetty.base = /var/jolie/webreserv/jetty-instances-available/gc
>  jetty.home = /var/jolie/webreserv/jetty_9.1.1
>
> Properties:
> -----------
>  http.timeout = 15000
>  jetty.dump.start = false
>  jetty.dump.stop = false
>  jetty.groupname = mareteam
>  jetty.port = 8090
>  jetty.username = tomcat
>  threads.max = 200
>  threads.min = 20
>  threads.timeout = 20000
>
> Jetty Server Classpath:
> -----------------------
> Version Information on 36 entries in the classpath.
> Note: order presented here is how they would appear on the classpath.
>       changes to the --module=name command line options will be reflected
> here.
>  0:                    (dir) | ${jetty.home}/resources
>  1:                    3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
>  2:                 3.1.0.M0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
>  3:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-http-9.1.1.v20140108.jar
>  4:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-server-9.1.1.v20140108.jar
>  5:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-xml-9.1.1.v20140108.jar
>  6:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-util-9.1.1.v20140108.jar
>  7:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-io-9.1.1.v20140108.jar
>  8:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-jndi-9.1.1.v20140108.jar
>  9:      1.1.0.v201105071233 |
> ${jetty.home}/lib/jndi/javax.activation-1.1.0.v201105071233.jar
> 10:      1.4.1.v201005082020 |
> ${jetty.home}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar
> 11:                      1.2 |
> ${jetty.home}/lib/jndi/javax.transaction-api-1.2.jar
> 12:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-security-9.1.1.v20140108.jar
> 13:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-servlet-9.1.1.v20140108.jar
> 14:                    3.0.0 | ${jetty.home}/lib/jsp/javax.el-3.0.0.jar
> 15:      1.2.0.v201105211821 |
> ${jetty.home}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
> 16:                    2.3.2 |
> ${jetty.home}/lib/jsp/javax.servlet.jsp-2.3.2.jar
> 17:                    2.3.1 |
> ${jetty.home}/lib/jsp/javax.servlet.jsp-api-2.3.1.jar
> 18:                    2.3.3 |
> ${jetty.home}/lib/jsp/jetty-jsp-jdt-2.3.3.jar
> 19:      1.2.0.v201112081803 |
> ${jetty.home}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
> 20:   3.8.2.v20130121-145325 |
> ${jetty.home}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
> 21:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-plus-9.1.1.v20140108.jar
> 22:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-webapp-9.1.1.v20140108.jar
> 23:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-annotations-9.1.1.v20140108.jar
> 24:                      4.1 | ${jetty.home}/lib/annotations/asm-4.1.jar
> 25:                      4.1 |
> ${jetty.home}/lib/annotations/asm-commons-4.1.jar
> 26:                      1.2 |
> ${jetty.home}/lib/annotations/javax.annotation-api-1.2.jar
> 27:          9.1.1.v20140108 |
> ${jetty.home}/lib/jetty-deploy-9.1.1.v20140108.jar
> 28:                      1.0 |
> ${jetty.home}/lib/websocket/javax.websocket-api-1.0.jar
> 29:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/javax-websocket-client-impl-9.1.1.v20140108.jar
> 30:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/javax-websocket-server-impl-9.1.1.v20140108.jar
> 31:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/websocket-api-9.1.1.v20140108.jar
> 32:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/websocket-client-9.1.1.v20140108.jar
> 33:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/websocket-common-9.1.1.v20140108.jar
> 34:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/websocket-server-9.1.1.v20140108.jar
> 35:          9.1.1.v20140108 |
> ${jetty.home}/lib/websocket/websocket-servlet-9.1.1.v20140108.jar
>
> Jetty Active XMLs:
> ------------------
>  ${jetty.home}/etc/jetty.xml
>  ${jetty.home}/etc/jetty-http.xml
>  ${jetty.home}/etc/jetty-plus.xml
>  ${jetty.home}/etc/jetty-annotations.xml
>  ${jetty.base}/etc/jetty-deploy.xml
>
> And this is what I obtain
>
> WARNING: Required directory '${jetty.base}/lib' does not exist. Run with
> --create-files to create
> WARNING: Required directory '${jetty.base}/lib/ext' does not exist. Run
> with --create-files to create
> WARNING: Required directory '${jetty.base}/resources' does not exist. Run
> with --create-files to create
> WARNING: Required directory '${jetty.base}/webapps' does not exist. Run
> with --create-files to create
>
> This is my start.ini
> --module=server
> jetty.username=real_uer
> jetty.groupname=real_group
>
> ## Server Threading Configuration
> threads.min=20
> threads.max=200
> threads.timeout=20000
> jetty.dump.start=false
> jetty.dump.stop=false
>
> --module=deploy
> --module=websocket
> --module=jsp
> --module=ext
> --module=resources
>
> --module=http
> jetty.port=8090
> http.timeout=15000
>
> Looking closer the info provided by --list-config always seems correct, so
> I tried to createad the requested directory: the result is that now
> warnings are no more displayed, but jetty doesn't start
>
> No more output produced, so I suppose something in my configuration is ok
> in 9.1.0 but is wrong in 9.1.1
>
> Any hint?
>
> TIA
>
>
>
> 2014-02-01 Simone Bordet <[email protected]>:
>
> Ciao,
>>
>> On Sat, Feb 1, 2014 at 1:45 PM, Andrea Cappelli <[email protected]>
>> wrote:
>> > Hi,
>> > I started using Jetty from version 9.1.0.v20131115 as a replacement for
>> > Tomcat.
>> >
>> > I saw in start.jar help that lib and others directory where searched in
>> > jetty.base and (if not found) in jetty.home, so I set jetty.home to the
>> > jetty distribution and jetty.base to a directory which contains only a
>> > start.ini script with the configurations (modules and so on)
>>
>> Correct.
>>
>> > I use Upstart on Ubuntu Precise
>> >
>> > Now I would upgrade to jetty 9.1.1.v20140108, but seems that my upstart
>> > script doesn't works, the process stops saying that it can't find
>> >
>> > {jetty.base}/lib
>> > {jetty.base}/lib/ext
>> > {jetty.base}/resources
>> > {jetty.base}/logs
>> >
>> > So I suppose something changes in this release, but the help still says
>> that
>> > jetty.home is a fallback for jetty.base
>> >
>> > I'm doing something (obviously) wrong?
>> >
>> > Can anyone point me in the right direction?
>>
>> Ideally, 9.1.1 should be a drop-in replacement for 9.1.0.
>> That is what we experienced in updating our own web sites, for example.
>>
>> Try:
>>
>> java -jar start.jar --list-config
>>
>> It will tell you a number of things related to your current
>> configuration, and they should be helpful to understand what's wrong.
>>
>> Let us know.
>>
>> --
>> Simone Bordet
>> ----
>> http://cometd.org
>> http://webtide.com
>> http://intalio.com
>> Developer advice, training, services and support
>> from the Jetty & CometD experts.
>> Intalio, the modern way to build business applications.
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>
>
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to