Re: Tomcat 9.0.52 crashes with "java.util.zip.ZipException: invalid LOC header (bad signature)" when started in debug mode - any work-around?

2021-08-17 Thread Maxim Solodovnik
I would 'rm -rf ~/.m2/repository/*'
Much faster than investigating :)

from mobile (sorry for typos ;)


On Tue, Aug 17, 2021, 18:16  wrote:

> When trying to start Tomcat (9.0.52) in debug mode ("Debug on Server") from
> Eclipse (v2020-12 (4.18.0) / Build id: 20201210-1552) I get the following
> error:
>
> 16-Aug-2021 13:52:14.019 SEVERE [main]
> org.apache.catalina.core.ContainerBase.startInternal A child container
> failed during start
>
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to initialize component
> [org.apache.catalina.webresources.JarResourceSet@61322f9d]
>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>
> ...
>
> Caused by: org.apache.catalina.LifecycleException: Failed to initialize
> component [org.apache.catalina.webresources.JarResourceSet@61322f9d]
>
> at
>
> org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase
> .java:440)
>
> ...
>
> Caused by: java.lang.IllegalArgumentException:
> java.util.zip.ZipException: invalid LOC header (bad signature)
>
> at
>
> org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initIntern
> al(AbstractSingleArchiveResourceSet.java:143)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
>
> ... 33 more
>
> Caused by: java.util.zip.ZipException: invalid LOC header (bad
> signature)
>
> at java.util.zip.ZipFile.read(Native Method)
>
> ...
>
> Caused by: java.lang.IllegalArgumentException:
> java.util.zip.ZipException: invalid LOC header (bad signature)
>
> at
>
> org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initIntern
> al(AbstractSingleArchiveResourceSet.java:143)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
>
> ... 33 more
>
> Caused by: java.util.zip.ZipException: invalid LOC header (bad
> signature)
>
>
>
>
>
> Any idea how to identify what .jar file is causing this and/or how to
> possibly work around this?
>
>
>
> I added more details on StackOverflow
>
> https://stackoverflow.com/questions/68803170/tomcat-crashes-with-java-util-z
> ip-zipexception-invalid-loc-header-bad-signatu
> ,
> so I don't want to spam the
> mailing list with them here.
>
>
>
> Regards,
>
> Michael
>
>
>
>


Re: Unable to start Tomcat 10.0.4

2021-03-16 Thread Maxim Solodovnik
Please provide full stacktrace

On Tue, 16 Mar 2021 at 22:49,  wrote:
>
> >> Your more recent exception log didn't include the "caused by" exception
> > --
> >> which is the actual failure details. Double-check that and make sure
> > it's
> >> the same issue.
> >>
> >> Also, use netstat to confirm you aren't using the ports already.
> > Changing
> >> it may just find another conflict (although less likely). The first
> > error
> >> was quite clear about the port being unavailable.
> >>
> >> How are you starting Tomcat? Are you somehow starting it twice?
> > I start tomcat click on batch file. I have changed port 80 to 81 please
> > find both log below. Unable to find any port (80, 81, 443) in netstat.
> > Please suggest where I am doing wrong
> >
> > Old log with port 80 and 443
> > 16-Mar-2021 16:45:44.410 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
> > successfully initialized [OpenSSL 1.1.1i  8 Dec 2020]
> > 16-Mar-2021 16:45:44.704 INFO [main]
> > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
> > ["http-nio-80"]
> > 16-Mar-2021 16:45:44.716 SEVERE [main]
> > org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
> > initialize component [Connector[null-80]]
> >  org.apache.catalina.LifecycleException: Protocol handler
> > initialization failed
> >  at
> >
> org.apache.catalina.connector.Connector.initInternal(Connector.java:1055)
> >  at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> >  at
> >
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:558)
> >  at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> >
> > New log with change port 81 and 443
> > 16-Mar-2021 20:16:06.094 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
> > successfully initialized [OpenSSL 1.1.1i  8 Dec 2020]
> > 16-Mar-2021 20:16:06.380 INFO [main]
> > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
> > ["http-nio-81"]
> > 16-Mar-2021 20:16:06.411 INFO [main]
> > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
> > ["https-openssl-nio-443"]
> > 16-Mar-2021 20:16:06.413 SEVERE [main]
> > org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
> > initialize component
> > [Connector[org.apache.coyote.http11.Http11NioProtocol-443]]
> >  org.apache.catalina.LifecycleException: Protocol handler
> > initialization failed
> >  at
> >
> org.apache.catalina.connector.Connector.initInternal(Connector.java:1055)
> >  at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> >  at
> >
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:558)
> >  at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> >
> > On Tue, Mar 16, 2021 at 9:38 AM  wrote:
> >
> >>> Deepak,
> >>> You already have some service listening on port 80 (IIS maybe?)
> >>>
> >>>
> >>> from mobile (sorry for typos ;)
> >>>
> >>> We have changed the port still getting same error
> >>> Maybe you have the same port configured twice in your conf/server.xml?
> >>> Please post *all*  elements from your conf/server.xml file,
> >>> being careful to remove any secrets from your configuration.
> >> -chris
> >> please find conf/server.xml file
> >>
> >> 
> >> 
> >> > className="org.apache.catalina.startup.VersionLoggerListener"
> >> />
> >> >> SSLEngine="on" />
> >> >> className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
> >> >> className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
> > />
> >> >> className="org.apache.catalina.core.ThreadLocalLeakPreventionListener"
> > />
> >>
> >>   >>type="org.apache.catalina.UserDatabase"
> >>description="User database that can be updated and
> saved"
> >>   factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
> >>pathname="conf/tomcat-users.xml" />
> >>
> >>
> >>   >> maxThreads="150" minSpareThreads="25"
> >> enableLookups="false" redirectPort="445" acceptCount="100"
> >> connectionTimeout="302000"
> > disableUploadTimeout="true"
> >> compression="on" compressionMinSize="2048"
> >> noCompressionUserAgents="gozilla, traviata"
> >>
> >
> compressableMimeType="text/html,text/xml,text/javascript,application/x-javascript,application/javascript"
> >>   server=" " />
> >>   > ="org.apache.coyote.http11.Http11NioProtocol"
> >> port="445" maxHttpHeaderSize="8192" maxThreads="150"
> >>  minSpareThreads="25"
> > enableLookups="false"
> >> disableUploadTimeout="true" acceptCount="100" scheme="https"
> > secure="true"
> >>  clientAuth="false" sslProtocol="TLS"
> >> 

Re: Unable to start Tomcat 10.0.4

2021-03-16 Thread Maxim Solodovnik
You already have some service listening on port 80 (IIS maybe?)


from mobile (sorry for typos ;)


On Tue, Mar 16, 2021, 18:36  wrote:

> Dear All,
>
> Unable to start tomcat 10.0.4 and getting error Failed to initialize
> component.
> /conf/server.xml configuration as below.
>
>  minSpareThreads="25" enableLookups="false" redirectPort="443"
> acceptCount="100"
>connectionTimeout="302000" disableUploadTimeout="true"
> compression="on" compressionMinSize="2048"
> noCompressionUserAgents="gozilla, traviata"
>
> compressableMimeType="text/html,text/xml,text/javascript,application/x-javascript,application/javascript"
>
>  server=" " />
>
>  port="443" maxHttpHeaderSize="8192" maxThreads="150"
> minSpareThreads="25" enableLookups="false"
> disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true"
> clientAuth="false" sslProtocol="TLS"
> sslEnabledProtocols="TLSv1.2,TLSv1.1" SSLEnabled="true"
> allowUnsafeLegacyRenegotiation="false"
>  ciphers="TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA"
> keystoreFile="/conf/eNotice.key"
> keystorePass="eNotice@1" server=" " />
>
>
> Getting below error in catalina log
>
> Server version name:   Apache Tomcat/10.0.4
> Server built:  Mar 5 2021 11:07:15 UTC
> Server version number: 10.0.4.0
> OS Name:   Windows 10
> OS Version:10.0
> Architecture:  x86
> Java Home: C:\Program Files (x86)\Java\jdk1.8.0_271\jre
> JVM Version:   1.8.0_271-b09
> JVM Vendor:Oracle Corporation
> CATALINA_BASE: D:\apache-tomcat-10.0.4
> CATALINA_HOME: D:\apache-tomcat-10.0.4
> Command line argument:
>
> -Djava.util.logging.config.file=D:\apache-tomcat-10.0.4\conf\logging.properties
> Command line argument:
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
> Command line argument:
> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
> Command line argument: -Dignore.endorsed.dirs=
> Command line argument: -Dcatalina.base=D:\apache-tomcat-10.0.4
> Command line argument: -Dcatalina.home=D:\apache-tomcat-10.0.4
> Command line argument: -Djava.io.tmpdir=D:\apache-tomcat-10.0.4\temp
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache
> Tomcat Native library [1.2.26] using APR version [1.7.0].
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> capabilities: IPv6 [true], sendfile [true], accept filters [false], random
> [true], UDS [true].
> org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
> successfully initialized [OpenSSL 1.1.1i  8 Dec 2020]
> org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
> ["http-nio-80"]
> org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
> initialize component [Connector[null-80]]
> org.apache.catalina.LifecycleException: Protocol handler
> initialization failed
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:1055)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> at
>
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:558)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> at
>
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1045)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
> at
> org.apache.catalina.startup.Catalina.load(Catalina.java:747)
> at
> org.apache.catalina.startup.Catalina.load(Catalina.java:769)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)
> at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:472)
> Caused by: java.net.BindException: Address already in use: bind
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225)
> at
> org.apache.tomcat.util.net
> .NioEndpoint.initServerSocket(NioEndpoint.java:243)
> at
> org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:198)
> at
> org.apache.tomcat.util.net
> 

Re: Keeping a session active with ajax

2021-03-15 Thread Maxim Solodovnik
I was able to warm-up HttpSession by adding `fetch('...', {cache:
"no-store"})` to JS code
So there should be no problems with AJAX :)

On Tue, 16 Mar 2021 at 01:45, Martin Grigorov  wrote:
>
> Chris,
>
> On Mon, Mar 15, 2021, 18:28 Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> > Martin,
> >
> > On 3/15/21 04:08, Martin Grigorov wrote:
> > > Hi Maxim,
> > >
> > > On Mon, Mar 15, 2021 at 9:46 AM Maxim Solodovnik 
> > > wrote:
> > >
> > >> Maybe offtopic
> > >> but websocket requests seems to not warming up the HttpSession
> > >>
> > >
> > > The websocket messages do not bring the JSESSIONID cookie/request
> > parameter
> > > and there is no way to lookup the http session from the web container
> > > (Tomcat).
> > > Wicket creates a copy of the HttpSession at WebSocket connection creation
> > > time and uses it until the closing of the connection.
> > > So, yes, the real http session may expire if you use only websocket based
> > > communication.
> >
> > Yes, but that's not AJAX, as the OP mentioned. Perhaps "AJAX" just means
> > "communication using javascript without 'traditional' navigation".
> >
>
> Did you read my first answer and Maxim's email?
>
>
> > Thanks,
> > -chris
> > >> Tomcat 9.0.44
> > >> Wicket 9.2.0 :)
> > >>
> > >> On Mon, 15 Mar 2021 at 14:43, Martin Grigorov 
> > >> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> Which version of Tomcat ?
> > >>>
> > >>> On Mon, Mar 15, 2021 at 8:25 AM Jerry Malcolm 
> > >>> wrote:
> > >>>
> > >>>> In my app a logged in user will access a page.  But then all of the
> > >>>> interaction on the page is done back and forth with ajax calls to the
> > >>>> server.  The ajax activities within the page could last well over the
> > >> 30
> > >>>> minute session timeout. Even though the user has been actively working
> > >>>> for 30-45 minutes with lots of server calls, all of a sudden they
> > >> aren't
> > >>>> logged in any more.  The ajax calls are definitely successfully
> > >>>> accessing the session since the ajax APIs utilize the logged on user,
> > >>>> roles, etc.  They just aren't pinging the keep-alive bit in the
> > session
> > >>>> for some reason.  I'm not really sure what would be different in the
> > >>>> calls from a regular page call from the browser vs an ajax call.  They
> > >>>> both make a request that goes to a servlet or jsp and they both get
> > >>>> response data back from tomcat.  But the session times out if I don't
> > >> do
> > >>>> a real page call.  What am I missing?
> > >>>>
> > >>>
> > >>> Nothing!
> > >>> Any request that uses the HttpSession
> > >>> (HttpServletRequest.getHttpSession(true)) will "touch" the session and
> > >>> update its "lastUsed" time, so it should not time out during active
> > usage
> > >>> of the application.
> > >>> There must be something else that invalidates the http session.
> > >>>
> > >>>
> > >>>>
> > >>>> I really don't want to change the 'inactivity' timeout.  I just need
> > to
> > >>>> figure out how to tell tomcat with all of the ajax calls that the
> > >>>> session is still very active.  Is there an easy solution?
> > >>>>
> > >>>> Thx
> > >>>>
> > >>>> Jerry
> > >>>>
> > >>>> BTW... TC 8.5
> > >>>>
> > >>>>
> > >>>> -
> > >>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > >>>> For additional commands, e-mail: users-h...@tomcat.apache.org
> > >>>>
> > >>>>
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >> Maxim
> > >>
> > >> -
> > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > >> For additional commands, e-mail: users-h...@tomcat.apache.org
> > >>
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Keeping a session active with ajax

2021-03-15 Thread Maxim Solodovnik
Maybe offtopic
but websocket requests seems to not warming up the HttpSession

Tomcat 9.0.44
Wicket 9.2.0 :)

On Mon, 15 Mar 2021 at 14:43, Martin Grigorov  wrote:
>
> Hi,
>
> Which version of Tomcat ?
>
> On Mon, Mar 15, 2021 at 8:25 AM Jerry Malcolm 
> wrote:
>
> > In my app a logged in user will access a page.  But then all of the
> > interaction on the page is done back and forth with ajax calls to the
> > server.  The ajax activities within the page could last well over the 30
> > minute session timeout. Even though the user has been actively working
> > for 30-45 minutes with lots of server calls, all of a sudden they aren't
> > logged in any more.  The ajax calls are definitely successfully
> > accessing the session since the ajax APIs utilize the logged on user,
> > roles, etc.  They just aren't pinging the keep-alive bit in the session
> > for some reason.  I'm not really sure what would be different in the
> > calls from a regular page call from the browser vs an ajax call.  They
> > both make a request that goes to a servlet or jsp and they both get
> > response data back from tomcat.  But the session times out if I don't do
> > a real page call.  What am I missing?
> >
>
> Nothing!
> Any request that uses the HttpSession
> (HttpServletRequest.getHttpSession(true)) will "touch" the session and
> update its "lastUsed" time, so it should not time out during active usage
> of the application.
> There must be something else that invalidates the http session.
>
>
> >
> > I really don't want to change the 'inactivity' timeout.  I just need to
> > figure out how to tell tomcat with all of the ajax calls that the
> > session is still very active.  Is there an easy solution?
> >
> > Thx
> >
> > Jerry
> >
> > BTW... TC 8.5
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: [ANN] Apache Tomcat 9.0.34 available

2020-05-12 Thread Maxim Solodovnik
There is typo in title: should be 9.0.35

(from mobile, sorry for typos)

On Tue, May 12, 2020, 22:09 Mark Thomas  wrote:

> The Apache Tomcat team announces the immediate availability of Apache
> Tomcat 9.0.35.
>
> Apache Tomcat 9 is an open source software implementation of the Java
> Servlet, JavaServer Pages, Java Unified Expression Language, Java
> WebSocket and JASPIC technologies.
>
> Apache Tomcat 9.0.35 is a bugfix and feature release. The notable
> changes compared to 9.0.34 include:
>
> - Improve the handling of requests that use an expectation. Do not
>   disable keep-alive where the response has a non-2xx status code
>   but the request body has been fully read.
>
> - Change default value separator for property replacement to ":-"
>   due to possible conflicts. The syntax is now "${name:-default}".
>
> - Update the packaged version of the Tomcat Native Library to 1.2.24
>
> Please refer to the change log for the complete list of changes:
> http://tomcat.apache.org/tomcat-9.0-doc/changelog.html
>
>
> Downloads:
> http://tomcat.apache.org/download-90.cgi
>
> Migration guides from Apache Tomcat 7.x and 8.x:
> http://tomcat.apache.org/migration.html
>
> Enjoy!
>
> - The Apache Tomcat team
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


Re: Tomcat 8.5.x configuration file differences: permission denied

2019-04-04 Thread Maxim Solodovnik
you can use github for this :)

On Thu, 4 Apr 2019 at 16:19, George Angeletos  wrote:
>
> I am getting permission denied when trying to view configuration file
> changes between 8.5.x versions (
> https://tomcat.apache.org/migration-85.html#Upgrading_8.5.x)
>
> https://gitbox.apache.org/repos/asf?p=tomcat.git=blobdiff=conf%2Fcatalina.policy=8.5.37=8.5.39
>
> Cheers,
> George



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Fwd: websocket connections consume too much memory

2019-02-25 Thread Maxim Solodovnik
Hello All,

Maybe this behavior is caused by the fact defaultMaxSessionIdleTimeout
is not set for websockets?

Can be updated as follows

final WsServerContainer sc =
(WsServerContainer)getServletContext().getAttribute(SERVER_CONTAINER_SERVLET_CONTEXT_ATTRIBUTE);
if (sc != null) {
 sc.setDefaultMaxSessionIdleTimeout(60 * 1000L);
}

On Mon, 25 Feb 2019 at 22:04, Иналь Кятов  wrote:
>
> I retest with
>
>
> *8.5.38*
>
> ...
>
> 
> org.apache.tomcat.embed
> tomcat-embed-websocket
> ${tomcat-embedded.version}
> 
> 
> org.apache.tomcat.embed
> tomcat-embed-core
> ${tomcat-embedded.version}
> 
> 
> org.apache.tomcat.embed
> tomcat-embed-el
> ${tomcat-embedded.version}
> 
> 
> org.apache.tomcat
> tomcat-annotations-api
> ${tomcat-embedded.version}
> 
>
>
> The result is the same
>
> I also checked status of the sockets on server with the netstat command.
>
> The number of ESTABLISHED is constantly and rapidly growing.
>
> Note, the problem is reproduced as a result of load testing.
>
>
> ср, 20 февр. 2019 г. в 01:40, Christopher Schultz <
> ch...@christopherschultz.net>:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Иналь,
> >
> > On 2/19/19 12:12, Иналь Кятов wrote:
> > > I encountered a problem with embedded tomcat 8.5.29 (part of spring
> > > boot 1.5).
> >
> > Can you retest with the current version of 8.5.x? Current version is
> > 8.5.38, released 2019-02-11.
> >
> > - -chris
> > -BEGIN PGP SIGNATURE-
> > Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
> >
> > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlxshcsACgkQHPApP6U8
> > pFgaVg//TF4/DVpFjtTLk+d6Z/AOcFX7SEYg/0SEKjpKtxaUr5+19umt5mMi+Zqk
> > UkkCSB19KRpqLUY8o53xlgqL9SqqBF14Wh0T2FYqpXtKSfV/Nv6tvsEV6Bd9LqTz
> > /RSFcAmCTL+SDIwXQ4FzmW55aaPfous9lKgPYdZlYy4UwVvG7PP/EOD7swR470eU
> > DmvjkkOKPJ87mSFra3LJ5MxrvLAw+9PgEACLc4nF6Tkceisn7kTIP/s7SGKb4Few
> > PWXYKy7NfcBASMYfikS/SAdCHNbjD9Za+L6okTuUjjvlNwAQvM7BWnG2CurpX8wQ
> > oEinp/4OsXaD0yZ/pi+dmUOUS/AwSuaxD4YZWembSEvTW658bc+5YgpfcOLivcO+
> > iB4/erdLHW8dLW07Nl2EafTXvKTOXHNlL4HIrTLzoi8SlJ2b+j4U3/9b5LBke2TG
> > HpQSo7MxqVfllhDTiwsYMRIkPupZEqR41x8wG4CpcfpQjXJMmAvaeFpBQA0ZnVyn
> > OkbYDi3IF9C8uAd0sbEx2npZ05ptb8zyHmU0mTawBDSL/e+3xbcFvZ2v0LNujgVB
> > VqJdtXOJKRA66l6dN+nS377guMeL5BQJS4PeRMIapWotJbuCE2nYgcjcie3ipClq
> > SP00v4Vd85g4D5XPAWewoWJXRiOPMp1dc5pTYwviTgG6FNGtoCE=
> > =wHth
> > -END PGP SIGNATURE-
> >



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: [EXTERNAL] Re: tomcat Finding!

2018-12-18 Thread Maxim Solodovnik
You have to add Valve under Server/Service/Engine/Host/
Works for us as expected

On Wed, 19 Dec 2018 at 03:17,  wrote:

> Added following to the Server.xml, still showing in the latest scan.
>
>  showReport=false" showServerInfo="false" />
>
> Thank you,
> Danyaal
>
> -Original Message-
> From: John Palmer [mailto:johnpalm...@gmail.com]
> Sent: Friday, December 14, 2018 6:26 PM
> To: Tomcat Users List
> Subject: [EXTERNAL] Re: tomcat Finding!
>
>  WARNING:This is an external email that originated outside of our email
> system. DO NOT CLICK links or open attachments unless you recognize the
> sender and know that the content is safe!
>
> I found this to be easier to accomplish (and maintain):
>
> add to the Host section of server.xml:
>  showReport=false" showServerInfo="false" />
>
> (this will disable the tomcat version number and the stacktrace  - the
> defaults for these are "true")
>
>
> On Fri, Dec 14, 2018 at 10:18 AM  wrote:
>
> > Good Morning,
> > I'm encountering following scan finding errors and couldn't find way to
> > mitigate this.
> >
> > Tomcat 8.5.32
> > 12085
> > Apache Tomcat Default Files
> > The following default files were found
> > :/nessus-check/default-404-error-page.html
> > Delete the default index page and remove the example JSP and servlets.
> > Follow the Tomcat or OWASP instructions to replace or modify the default
> > error page.
> >
> > Thank you,
> > Danyaal
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>


-- 
WBR
Maxim aka solomax


Re: oracle 12c driver (UNCLASSIFIED)

2018-06-20 Thread Maxim Solodovnik
We are currently using ojdbc6 in production
I would use ojdbc8 for new project (
http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-3110062.html
)

I believe the problem is caused by connection pool settings, not the driver


On Thu, Jun 21, 2018 at 2:38 AM Lueders, Paul T CIV USARMY NGIC (US) <
paul.t.lueders@mail.mil> wrote:

> CLASSIFICATION: UNCLASSIFIED
>
> We have configured an oracle 12c connection using the Oracle jdbc
> connector .  What we are experiencing is that the application is locking up
> and the database requires a restart.  We believe that the issue is that
> application  is not releasing the connections and the database runs out of
> connections.   The question I have is the JDBC driver the best one for
> oracle 12c?  If so what would be some configuration items that  we need to
> set in order to ensure that the application releases the connections
> efficiently.  Lastly is = there a monitor available to watch the database
> connections.
>
> Thanks a lot
> Paul
> CLASSIFICATION: UNCLASSIFIED
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-- 
WBR
Maxim aka solomax


Re: [ANN] Apache Tomcat 9.0.6 available

2018-03-09 Thread Maxim Solodovnik
Maven seems to be updated,
Thanks :)

On Fri, Mar 9, 2018 at 11:18 PM, Mark Thomas <ma...@apache.org> wrote:

>
>
> On 09/03/2018 16:14, Maxim Solodovnik wrote:
>
>> Hello Mark,
>>
>> It seems maven artifacts are not available:
>> https://repo.maven.apache.org/maven2/org/apache/tomcat/embed
>> /tomcat-embed-websocket/
>> https://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat-api/
>>
>
> I might have forgotten to press the right button. I'll do that now. Give
> it a few minutes to take effect.
>
> Mark
>
>
>
>
>> Is it expected?
>>
>> On Fri, Mar 9, 2018 at 7:18 PM, Mark Thomas <ma...@apache.org> wrote:
>>
>> The Apache Tomcat team announces the immediate availability of Apache
>>> Tomcat 9.0.6.
>>>
>>> Apache Tomcat 9 is an open source software implementation of the Java
>>> Servlet, JavaServer Pages, Java Unified Expression Language, Java
>>> WebSocket and JASPIC technologies.
>>>
>>> Apache Tomcat 9.0.6 is a bugfix and feature release. The notable changes
>>> compared to 9.0.5 include:
>>>
>>> - TLS stability improvements.
>>>
>>> - Add the ability to specify static HTML responses for specific error
>>>codes and/or exception types with the ErrorReportValve.
>>>
>>> - Add async HTTP/2 parser for NIO2.
>>>
>>> - Add documentation for the Host Manager web application.
>>>Patch provided by Marek Czernek.
>>>
>>> Please refer to the change log for the complete list of changes:
>>> http://tomcat.apache.org/tomcat-9.0-doc/changelog.html
>>>
>>> Downloads:
>>> http://tomcat.apache.org/download-90.cgi
>>>
>>> Migration guides from Apache Tomcat 7.x and 8.x:
>>> http://tomcat.apache.org/migration.html
>>>
>>> Enjoy!
>>>
>>> - The Apache Tomcat team
>>>
>>>
>>>
>>> For details of the "Tomcat for Administrators" training course being
>>> held in Manchester, UK please see:
>>> https://tomcat.apache.org/conference.html
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>>
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Re: [ANN] Apache Tomcat 9.0.6 available

2018-03-09 Thread Maxim Solodovnik
Hello Mark,

It seems maven artifacts are not available:
https://repo.maven.apache.org/maven2/org/apache/tomcat/embed/tomcat-embed-websocket/
https://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat-api/

Is it expected?

On Fri, Mar 9, 2018 at 7:18 PM, Mark Thomas  wrote:

> The Apache Tomcat team announces the immediate availability of Apache
> Tomcat 9.0.6.
>
> Apache Tomcat 9 is an open source software implementation of the Java
> Servlet, JavaServer Pages, Java Unified Expression Language, Java
> WebSocket and JASPIC technologies.
>
> Apache Tomcat 9.0.6 is a bugfix and feature release. The notable changes
> compared to 9.0.5 include:
>
> - TLS stability improvements.
>
> - Add the ability to specify static HTML responses for specific error
>   codes and/or exception types with the ErrorReportValve.
>
> - Add async HTTP/2 parser for NIO2.
>
> - Add documentation for the Host Manager web application.
>   Patch provided by Marek Czernek.
>
> Please refer to the change log for the complete list of changes:
> http://tomcat.apache.org/tomcat-9.0-doc/changelog.html
>
> Downloads:
> http://tomcat.apache.org/download-90.cgi
>
> Migration guides from Apache Tomcat 7.x and 8.x:
> http://tomcat.apache.org/migration.html
>
> Enjoy!
>
> - The Apache Tomcat team
>
>
>
> For details of the "Tomcat for Administrators" training course being
> held in Manchester, UK please see:
> https://tomcat.apache.org/conference.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-08 Thread Maxim Solodovnik
Thanks a lot for the review Konstantin,
I have correct our tests :)

Will Also contact CXF project
This code was taken from their tests: [1] :))

[1]
https://github.com/apache/cxf/blob/master/systests/cdi/base/src/main/java/org/apache/cxf/systests/cdi/base/tomcat/AbstractTomcatServer.java#L45


On Wed, Nov 8, 2017 at 6:08 PM, Konstantin Kolinko 
wrote:

> I have several comments on
> [1] https://github.com/apache/openmeetings/blob/master/
> openmeetings-web/src/test/java/org/apache/openmeetings/webservice/
> AbstractWebServiceTest.java#L98
>
>
> 2017-11-07 20:07 GMT+03:00 Tobias Soloschenko
> :
> > Hi Maxim,
> >
> > same for me I just created a simple setup like this:
> >
> > String baseDir =".";
> > String webappDirLocation = "src/main/webapp/";
> > String webxmlDirLocation = "src/main/webapp/WEB-INF/web.xml";
> > Tomcat tomcat = new Tomcat();
> > tomcat.setPort(8080);
>
> 1) Maybe you will want to update the test to use a random port number,
> so that several tests could be run in parallel.
>
> Use connector.setPort(0) to enable random port number feature (see
> TomcatBaseTest.setUp())
> followed by connector.getLocalPort(); after startup  (see
> TomcatBaseTest.getPort())
>
> http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/
> catalina/startup/TomcatBaseTest.java?revision=1812119=markup#l146
>
> An example of a simple test case and use of getPort():
> http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/
> catalina/startup/TestTomcat.java?revision=1769263=markup#l189
>
> 2) Tomcat tests use address="localhost" on connector.
> See TomcatBaseTest.setUp()
>
> Running with localhost avoids opening ports on a public interface.
>
> (When running on Windows its Firewall pops up a dialog and asks
> whether to allow network access for this software.
> Using localhost avoid this dialog.)
>
> > tomcat.setBaseDir(baseDir);
> > tomcat.getHost().setAppBase(baseDir);
> > tomcat.getHost().setDeployOnStartup(true);
> > tomcat.getHost().setAutoDeploy(true);
> > tomcat.enableNaming();
> > StandardContext ctx = (StandardContext)
> tomcat.addWebapp("/project", new File(webappDirLocation).
> getAbsolutePath());
> > File additionWebInfClasses = new File("target/classes");
> > WebResourceRoot resources = new StandardRoot(ctx);
> > resources.addPreResources(new DirResourceSet(resources,
> "/WEB-INF/classes",
> > additionWebInfClasses.getAbsolutePath(), "/"));
> > ctx.setResources(resources);
> > ctx.setDefaultWebXml(new File(webxmlDirLocation).
> getAbsolutePath());
> > tomcat.start();
> > tomcat.getServer().await();
> >
>
> 3) In an automated test both "deployOnStartup" and "autoDeploy" flags
> should be set to "false".
>
> Do you want that any random files and directories created in a
> temporary directory (baseDir) to be auto-deployed
> and exposed as web applications in Tomcat?  I guess that you do not
> want that, so set those flags to false.
>
> Tomcat.addWebapp explicitly configures a web application.
> Auto-deployment is not needed.
>
> > I just placed in a Servlet into my classpath and applied the mapping in
> the web.xml - with the dependencies of tomcat-embed-core and
> tomcat-embed-jasper of version 9.0.1 it is not working and with 8.5.23 it
> does.
> >
> > Here is the log of both.
> > [...]
>
> Best regards,
> Konstantin Kolinko
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-07 Thread Maxim Solodovnik
 This is why Tomcat 9.0.1 has no connectors 

sorry for the typo

On Wed, Nov 8, 2017 at 11:30 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> OK :)
> I finally found the difference :)))
>
> Tomcat.java 8.5.23:
> public void start() throws LifecycleException {
> getServer();
> getConnector();
> server.start();
> }
>
> Tomcat.java 9.0.1:
> public void start() throws LifecycleException {
> getServer();
> server.start();
> }
>
> This is why Tomcat 9.0.2 has no connectors 
> Is it bug or feature?
>
>
> On Wed, Nov 8, 2017 at 12:07 AM, Tobias Soloschenko <
> tobiassolosche...@googlemail.com> wrote:
>
>> Hi Maxim,
>>
>> same for me I just created a simple setup like this:
>>
>> String baseDir =".";
>> String webappDirLocation = "src/main/webapp/";
>> String webxmlDirLocation = "src/main/webapp/WEB-INF/web.xml";
>> Tomcat tomcat = new Tomcat();
>> tomcat.setPort(8080);
>> tomcat.setBaseDir(baseDir);
>> tomcat.getHost().setAppBase(baseDir);
>> tomcat.getHost().setDeployOnStartup(true);
>> tomcat.getHost().setAutoDeploy(true);
>> tomcat.enableNaming();
>> StandardContext ctx = (StandardContext)
>> tomcat.addWebapp("/project", new File(webappDirLocation).getAbs
>> olutePath());
>> File additionWebInfClasses = new File("target/classes");
>> WebResourceRoot resources = new StandardRoot(ctx);
>> resources.addPreResources(new DirResourceSet(resources,
>> "/WEB-INF/classes",
>> additionWebInfClasses.getAbsolutePath(), "/"));
>> ctx.setResources(resources);
>> ctx.setDefaultWebXml(new File(webxmlDirLocation).getAbs
>> olutePath());
>> tomcat.start();
>> tomcat.getServer().await();
>>
>> I just placed in a Servlet into my classpath and applied the mapping in
>> the web.xml - with the dependencies of tomcat-embed-core and
>> tomcat-embed-jasper of version 9.0.1 it is not working and with 8.5.23 it
>> does.
>>
>> Here is the log of both.
>>
>> 8.5.23
>>
>> Nov. 07, 2017 6:02:44 NACHM. org.apache.coyote.AbstractProtocol init
>> INFORMATION: Initializing ProtocolHandler ["http-nio-8080"]
>> Nov. 07, 2017 6:02:44 NACHM. org.apache.tomcat.util.net.NioSelectorPool
>> getSharedSelector
>> INFORMATION: Using a shared selector for servlet write/read
>> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardService
>> startInternal
>> INFORMATION: Starting service [Tomcat]
>> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardEngine
>> startInternal
>> INFORMATION: Starting Servlet Engine: Apache Tomcat/8.5.23
>> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.startup.ContextConfig
>> getDefaultWebXmlFragment
>> INFORMATION: No global web.xml found
>> Nov. 07, 2017 6:02:45 NACHM. org.apache.coyote.AbstractProtocol start
>> INFORMATION: Starting ProtocolHandler ["http-nio-8080“]
>>
>> 9.0.1
>>
>> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardService
>> startInternal
>> INFORMATION: Starting service [Tomcat]
>> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardEngine
>> startInternal
>> INFORMATION: Starting Servlet Engine: Apache Tomcat/9.0.1
>> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.startup.ContextConfig
>> getDefaultWebXmlFragment
>> INFORMATION: No global web.xml found
>>
>> kind regards
>>
>> Tobias
>>
>> > Am 07.11.2017 um 15:56 schrieb Maxim Solodovnik <solomax...@gmail.com>:
>> >
>> > Thanks for the hints :)
>> >
>> > I have created sample project: https://github.com/solomax/tom
>> cat-from-java
>> >
>> > I have compared detailed logs.
>> >
>> > Following lines appears in logs while Tomcat8 is used
>> > Nov 07, 2017 9:1 PM org.apache.catalina.util.LifecycleBase
>> > setStateInternal
>> > FINE: Setting state for [Connector[HTTP/1.1-8080]] to
>> > [INITIALIZING]
>> > Nov 07, 2017 9:1 PM org.apache.tomcat.util.modeler.Registry
>> > registerComponent
>> > FINE: Managed= Tomcat:type=Connector,port=8080
>> >
>> > These lines are missing while Tomcat9 is used
>> >
>> > Maybe you can tell me why?
>> >
>> > On Mon, Nov 6, 2017 at 7:5

Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-07 Thread Maxim Solodovnik
Thanks for the clarifications!
I'll update my code

On Wed, Nov 8, 2017 at 1:49 PM, Rémy Maucherat <r...@apache.org> wrote:

> On Wed, Nov 8, 2017 at 5:30 AM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
> > OK :)
> > I finally found the difference :)))
> >
> > Tomcat.java 8.5.23:
> > public void start() throws LifecycleException {
> > getServer();
> > getConnector();
> > server.start();
> > }
> >
> > Tomcat.java 9.0.1:
> > public void start() throws LifecycleException {
> > getServer();
> > server.start();
> > }
> >
> > This is why Tomcat 9.0.2 has no connectors 
> > Is it bug or feature?
> >
>
> The automatic connector creation, among other tings, was conflicting with
> other more sophisticated uses so it was refactored. It was not possible to
> start Tomcat without a connector so that capability was added in Tomcat 9.
> If you want to get a default connector, you have to call getConnector
> yourself.
> BZ60297, BZ60368, then a Tomcat 9 specific change.
>
> Rémy
>
> >
> >
> > On Wed, Nov 8, 2017 at 12:07 AM, Tobias Soloschenko <
> > tobiassolosche...@googlemail.com> wrote:
> >
> > > Hi Maxim,
> > >
> > > same for me I just created a simple setup like this:
> > >
> > > String baseDir =".";
> > > String webappDirLocation = "src/main/webapp/";
> > > String webxmlDirLocation = "src/main/webapp/WEB-INF/web.xml";
> > > Tomcat tomcat = new Tomcat();
> > > tomcat.setPort(8080);
> > > tomcat.setBaseDir(baseDir);
> > > tomcat.getHost().setAppBase(baseDir);
> > > tomcat.getHost().setDeployOnStartup(true);
> > > tomcat.getHost().setAutoDeploy(true);
> > > tomcat.enableNaming();
> > > StandardContext ctx = (StandardContext)
> > > tomcat.addWebapp("/project", new File(webappDirLocation).
> > > getAbsolutePath());
> > > File additionWebInfClasses = new File("target/classes");
> > > WebResourceRoot resources = new StandardRoot(ctx);
> > > resources.addPreResources(new DirResourceSet(resources,
> > > "/WEB-INF/classes",
> > > additionWebInfClasses.getAbsolutePath(), "/"));
> > > ctx.setResources(resources);
> > > ctx.setDefaultWebXml(new File(webxmlDirLocation).
> > > getAbsolutePath());
> > > tomcat.start();
> > > tomcat.getServer().await();
> > >
> > > I just placed in a Servlet into my classpath and applied the mapping in
> > > the web.xml - with the dependencies of tomcat-embed-core and
> > > tomcat-embed-jasper of version 9.0.1 it is not working and with 8.5.23
> it
> > > does.
> > >
> > > Here is the log of both.
> > >
> > > 8.5.23
> > >
> > > Nov. 07, 2017 6:02:44 NACHM. org.apache.coyote.AbstractProtocol init
> > > INFORMATION: Initializing ProtocolHandler ["http-nio-8080"]
> > > Nov. 07, 2017 6:02:44 NACHM. org.apache.tomcat.util.net.
> NioSelectorPool
> > > getSharedSelector
> > > INFORMATION: Using a shared selector for servlet write/read
> > > Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardService
> > > startInternal
> > > INFORMATION: Starting service [Tomcat]
> > > Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardEngine
> > > startInternal
> > > INFORMATION: Starting Servlet Engine: Apache Tomcat/8.5.23
> > > Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.startup.ContextConfig
> > > getDefaultWebXmlFragment
> > > INFORMATION: No global web.xml found
> > > Nov. 07, 2017 6:02:45 NACHM. org.apache.coyote.AbstractProtocol start
> > > INFORMATION: Starting ProtocolHandler ["http-nio-8080“]
> > >
> > > 9.0.1
> > >
> > > Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardService
> > > startInternal
> > > INFORMATION: Starting service [Tomcat]
> > > Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardEngine
> > > startInternal
> > > INFORMATION: Starting Servlet Engine: Apache Tomcat/9.0.1
> > > Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.startup.ContextConfig
> > > getDefaultWebXmlFragment
> > > INFORMATION: No global web.xml found
> > >
> > > kind regards

Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-07 Thread Maxim Solodovnik
OK :)
I finally found the difference :)))

Tomcat.java 8.5.23:
public void start() throws LifecycleException {
getServer();
getConnector();
server.start();
}

Tomcat.java 9.0.1:
public void start() throws LifecycleException {
getServer();
server.start();
}

This is why Tomcat 9.0.2 has no connectors 
Is it bug or feature?


On Wed, Nov 8, 2017 at 12:07 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

> Hi Maxim,
>
> same for me I just created a simple setup like this:
>
> String baseDir =".";
> String webappDirLocation = "src/main/webapp/";
> String webxmlDirLocation = "src/main/webapp/WEB-INF/web.xml";
> Tomcat tomcat = new Tomcat();
> tomcat.setPort(8080);
> tomcat.setBaseDir(baseDir);
> tomcat.getHost().setAppBase(baseDir);
> tomcat.getHost().setDeployOnStartup(true);
> tomcat.getHost().setAutoDeploy(true);
> tomcat.enableNaming();
> StandardContext ctx = (StandardContext)
> tomcat.addWebapp("/project", new File(webappDirLocation).
> getAbsolutePath());
> File additionWebInfClasses = new File("target/classes");
> WebResourceRoot resources = new StandardRoot(ctx);
> resources.addPreResources(new DirResourceSet(resources,
> "/WEB-INF/classes",
> additionWebInfClasses.getAbsolutePath(), "/"));
> ctx.setResources(resources);
> ctx.setDefaultWebXml(new File(webxmlDirLocation).
> getAbsolutePath());
> tomcat.start();
> tomcat.getServer().await();
>
> I just placed in a Servlet into my classpath and applied the mapping in
> the web.xml - with the dependencies of tomcat-embed-core and
> tomcat-embed-jasper of version 9.0.1 it is not working and with 8.5.23 it
> does.
>
> Here is the log of both.
>
> 8.5.23
>
> Nov. 07, 2017 6:02:44 NACHM. org.apache.coyote.AbstractProtocol init
> INFORMATION: Initializing ProtocolHandler ["http-nio-8080"]
> Nov. 07, 2017 6:02:44 NACHM. org.apache.tomcat.util.net.NioSelectorPool
> getSharedSelector
> INFORMATION: Using a shared selector for servlet write/read
> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardService
> startInternal
> INFORMATION: Starting service [Tomcat]
> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.core.StandardEngine
> startInternal
> INFORMATION: Starting Servlet Engine: Apache Tomcat/8.5.23
> Nov. 07, 2017 6:02:44 NACHM. org.apache.catalina.startup.ContextConfig
> getDefaultWebXmlFragment
> INFORMATION: No global web.xml found
> Nov. 07, 2017 6:02:45 NACHM. org.apache.coyote.AbstractProtocol start
> INFORMATION: Starting ProtocolHandler ["http-nio-8080“]
>
> 9.0.1
>
> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardService
> startInternal
> INFORMATION: Starting service [Tomcat]
> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.core.StandardEngine
> startInternal
> INFORMATION: Starting Servlet Engine: Apache Tomcat/9.0.1
> Nov. 07, 2017 6:06:56 NACHM. org.apache.catalina.startup.ContextConfig
> getDefaultWebXmlFragment
> INFORMATION: No global web.xml found
>
> kind regards
>
> Tobias
>
> > Am 07.11.2017 um 15:56 schrieb Maxim Solodovnik <solomax...@gmail.com>:
> >
> > Thanks for the hints :)
> >
> > I have created sample project: https://github.com/solomax/
> tomcat-from-java
> >
> > I have compared detailed logs.
> >
> > Following lines appears in logs while Tomcat8 is used
> > Nov 07, 2017 9:1 PM org.apache.catalina.util.LifecycleBase
> > setStateInternal
> > FINE: Setting state for [Connector[HTTP/1.1-8080]] to
> > [INITIALIZING]
> > Nov 07, 2017 9:1 PM org.apache.tomcat.util.modeler.Registry
> > registerComponent
> > FINE: Managed= Tomcat:type=Connector,port=8080
> >
> > These lines are missing while Tomcat9 is used
> >
> > Maybe you can tell me why?
> >
> > On Mon, Nov 6, 2017 at 7:55 PM, Mark Thomas <ma...@apache.org> wrote:
> >
> >> On 04/11/17 15:25, Maxim Solodovnik wrote:
> >>> Maybe I can set breakpoint somewhere? and check what is wrong?
> >>> Could you point me to the correct class?
> >>
> >> No idea where to look at this point. I'd probably start with the start()
> >> method and go from there.
> >>
> >> Maybe try turning on debug logging?
> >>
> >> Mark
> >>
> >>
> >>>
> >>> On Fri, Nov 3, 2017 at 5:26 PM, Maxim Solodovnik <solomax...@gmail.com
&g

Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-07 Thread Maxim Solodovnik
Thanks for the hints :)

I have created sample project: https://github.com/solomax/tomcat-from-java

I have compared detailed logs.

Following lines appears in logs while Tomcat8 is used
 Nov 07, 2017 9:1 PM org.apache.catalina.util.LifecycleBase
setStateInternal
 FINE: Setting state for [Connector[HTTP/1.1-8080]] to
[INITIALIZING]
 Nov 07, 2017 9:1 PM org.apache.tomcat.util.modeler.Registry
registerComponent
 FINE: Managed= Tomcat:type=Connector,port=8080

These lines are missing while Tomcat9 is used

Maybe you can tell me why?

On Mon, Nov 6, 2017 at 7:55 PM, Mark Thomas <ma...@apache.org> wrote:

> On 04/11/17 15:25, Maxim Solodovnik wrote:
> > Maybe I can set breakpoint somewhere? and check what is wrong?
> > Could you point me to the correct class?
>
> No idea where to look at this point. I'd probably start with the start()
> method and go from there.
>
> Maybe try turning on debug logging?
>
> Mark
>
>
> >
> > On Fri, Nov 3, 2017 at 5:26 PM, Maxim Solodovnik <solomax...@gmail.com>
> > wrote:
> >
> >> I'm OK to add missing code to my tests,
> >> but I'm not sure what need to be added :(
> >>
> >> On Fri, Nov 3, 2017 at 3:24 PM, Maxim Solodovnik <solomax...@gmail.com>
> >> wrote:
> >>
> >>> I see no errors,
> >>> Using debugger I can see tomcat.server.state == STARTED
> >>>
> >>> Everything works as expected if I'm switching back to 8.5.23 without
> any
> >>> other changes
> >>>
> >>> nestat reports:
> >>> *netstat -an |grep 8080*
> >>> tcp6   0  0 :::8080 :::*
> >>>  LISTEN
> >>>
> >>> for 8.5.23
> >>>
> >>>
> >>> On Fri, Nov 3, 2017 at 3:08 PM, Mark Thomas <ma...@apache.org> wrote:
> >>>
> >>>> On 03/11/17 04:51, Maxim Solodovnik wrote:
> >>>>> Hello,
> >>>>>
> >>>>> I recently migrated from Tomcat 8.5.23 to Tomcat 9.0.1
> >>>>> Everything works as expected except tests :(
> >>>>>
> >>>>> I'm using following code to start embedded Tomcat and test CXF web
> >>>> services [1].
> >>>>> With Tomcat 9.0.1 tests failed, netstat -an displays port 8080 is not
> >>>>> being listened
> >>>>> What need to be changed?
> >>>>
> >>>> If Tomcat isn't listening then there should be an exception or error
> >>>> message reported at some point. Do you see anything in the logs?
> >>>>
> >>>> Mark
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>> [1] https://github.com/apache/openmeetings/blob/master/openmeeti
> >>>> ngs-web/src/test/java/org/apache/openmeetings/webservice/
> >>>> AbstractWebServiceTest.java#L98
> >>>>>
> >>>>
> >>>>
> >>>> -
> >>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >>>> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>>
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-04 Thread Maxim Solodovnik
Maybe I can set breakpoint somewhere? and check what is wrong?
Could you point me to the correct class?

On Fri, Nov 3, 2017 at 5:26 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> I'm OK to add missing code to my tests,
> but I'm not sure what need to be added :(
>
> On Fri, Nov 3, 2017 at 3:24 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
>> I see no errors,
>> Using debugger I can see tomcat.server.state == STARTED
>>
>> Everything works as expected if I'm switching back to 8.5.23 without any
>> other changes
>>
>> nestat reports:
>> *netstat -an |grep 8080*
>> tcp6   0  0 :::8080 :::*
>>  LISTEN
>>
>> for 8.5.23
>>
>>
>> On Fri, Nov 3, 2017 at 3:08 PM, Mark Thomas <ma...@apache.org> wrote:
>>
>>> On 03/11/17 04:51, Maxim Solodovnik wrote:
>>> > Hello,
>>> >
>>> > I recently migrated from Tomcat 8.5.23 to Tomcat 9.0.1
>>> > Everything works as expected except tests :(
>>> >
>>> > I'm using following code to start embedded Tomcat and test CXF web
>>> services [1].
>>> > With Tomcat 9.0.1 tests failed, netstat -an displays port 8080 is not
>>> > being listened
>>> > What need to be changed?
>>>
>>> If Tomcat isn't listening then there should be an exception or error
>>> message reported at some point. Do you see anything in the logs?
>>>
>>> Mark
>>>
>>>
>>> >
>>> >
>>> > [1] https://github.com/apache/openmeetings/blob/master/openmeeti
>>> ngs-web/src/test/java/org/apache/openmeetings/webservice/
>>> AbstractWebServiceTest.java#L98
>>> >
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax


Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-03 Thread Maxim Solodovnik
I'm OK to add missing code to my tests,
but I'm not sure what need to be added :(

On Fri, Nov 3, 2017 at 3:24 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> I see no errors,
> Using debugger I can see tomcat.server.state == STARTED
>
> Everything works as expected if I'm switching back to 8.5.23 without any
> other changes
>
> nestat reports:
> *netstat -an |grep 8080*
> tcp6   0  0 :::8080 :::*LISTEN
>
> for 8.5.23
>
>
> On Fri, Nov 3, 2017 at 3:08 PM, Mark Thomas <ma...@apache.org> wrote:
>
>> On 03/11/17 04:51, Maxim Solodovnik wrote:
>> > Hello,
>> >
>> > I recently migrated from Tomcat 8.5.23 to Tomcat 9.0.1
>> > Everything works as expected except tests :(
>> >
>> > I'm using following code to start embedded Tomcat and test CXF web
>> services [1].
>> > With Tomcat 9.0.1 tests failed, netstat -an displays port 8080 is not
>> > being listened
>> > What need to be changed?
>>
>> If Tomcat isn't listening then there should be an exception or error
>> message reported at some point. Do you see anything in the logs?
>>
>> Mark
>>
>>
>> >
>> >
>> > [1] https://github.com/apache/openmeetings/blob/master/openmeeti
>> ngs-web/src/test/java/org/apache/openmeetings/webservice
>> /AbstractWebServiceTest.java#L98
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax


Re: Start embedded Tomcat 9.0.1 server from java code

2017-11-03 Thread Maxim Solodovnik
I see no errors,
Using debugger I can see tomcat.server.state == STARTED

Everything works as expected if I'm switching back to 8.5.23 without any
other changes

nestat reports:
*netstat -an |grep 8080*
tcp6   0  0 :::8080 :::*LISTEN

for 8.5.23


On Fri, Nov 3, 2017 at 3:08 PM, Mark Thomas <ma...@apache.org> wrote:

> On 03/11/17 04:51, Maxim Solodovnik wrote:
> > Hello,
> >
> > I recently migrated from Tomcat 8.5.23 to Tomcat 9.0.1
> > Everything works as expected except tests :(
> >
> > I'm using following code to start embedded Tomcat and test CXF web
> services [1].
> > With Tomcat 9.0.1 tests failed, netstat -an displays port 8080 is not
> > being listened
> > What need to be changed?
>
> If Tomcat isn't listening then there should be an exception or error
> message reported at some point. Do you see anything in the logs?
>
> Mark
>
>
> >
> >
> > [1] https://github.com/apache/openmeetings/blob/master/
> openmeetings-web/src/test/java/org/apache/openmeetings/webservice/
> AbstractWebServiceTest.java#L98
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Start embedded Tomcat 9.0.1 server from java code

2017-11-02 Thread Maxim Solodovnik
Hello,

I recently migrated from Tomcat 8.5.23 to Tomcat 9.0.1
Everything works as expected except tests :(

I'm using following code to start embedded Tomcat and test CXF web services [1].
With Tomcat 9.0.1 tests failed, netstat -an displays port 8080 is not
being listened
What need to be changed?


[1] 
https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/test/java/org/apache/openmeetings/webservice/AbstractWebServiceTest.java#L98

-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Tomcat 8.5.15 Released?

2017-05-15 Thread Maxim Solodovnik
It is in Maven:
http://repo1.maven.org/maven2/org/apache/tomcat/embed/tomcat-embed-core/8.5.15/
So I guess it is released

On Tue, May 16, 2017 at 10:58 AM, Adam Rauch  wrote:

> Is Tomcat 8.5.15 officially released? The home page
> (http://tomcat.apache.org/index.html) seems to indicate that it was
> released
> 2017-05-10. however, the text of the section references the "release of
> version 8.5.14" and "notable changes compared to 8.5.13." And the changelog
> link hits the 8.5.14 anchor. Also, the archives show no 8.5.15 post to the
> tomcat-announce list.
>
>
>
> Perhaps the release is still in progress, but the page has been in this
> state for a few days.
>
>
>
> Thanks,
>
> Adam
>
>


-- 
WBR
Maxim aka solomax


Re: [ANN] New committer: Martin Grigorov

2015-10-26 Thread Maxim Solodovnik
Congrats Martin!

On Mon, Oct 26, 2015 at 8:35 PM, Mark Thomas  wrote:

> On behalf of the Tomcat committers I am pleased to announce that
> Martin Grigorov (mgrigorov) has been voted in as a new Tomcat committer.
>
> Please join me in welcoming him.
>
> Regards,
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
WBR
Maxim aka solomax


Re: Migrating from embedded Tomcat6 to Tomcat8

2015-07-06 Thread Maxim Solodovnik
Thanks Mark and Chris,

I was able to successfully migrate the code :)

On Tue, Jul 7, 2015 at 2:49 AM, Christopher Schultz 
ch...@christopherschultz.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Maxim,

 On 7/3/15 8:28 AM, Mark Thomas wrote:
  On 03/07/2015 12:43, Maxim Solodovnik wrote:
  Hello,
 
  sorry for the newbie question but I was unable to find the answer
  using search :( I'm trying to migrate custom embedded tomcat
  loader from Tomcat6 (works as expected with Tomcat7 with lots of
  deprecations) to Tomcat8.
 
  Previously it was possible to add multiple Engines to Tomcat
  instance, how this can be achieved in Tomcat8?
 
  source file for Tomcat.java  states: // Single engine, service,
  server, connector - few cases need more, they can use server.xml
  unfortunately I need to do it using java (without server.xml)
 
  Thanks in advance for your answers!
 
  Use Tomcat as your starting point.

 Just to clarify, this is the org.apache.catalina.startup.Tomcat class
 that Mark is talking about.

 - -chris
 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - http://gpgtools.org

 iQIcBAEBCAAGBQJVmunxAAoJEBzwKT+lPKRYeoIQAIbyDnbhEJvEN86gHIZmskrD
 r3Reg4ItnSD6fvLz6WZIqxfUkajKRhayz6L8Y2VZKedBfY7acwevNhuauxevKXKu
 hU3O382FjjXRRsr8Uhgo8CmFVd1BaclOeSAvSS9NWlNHFSR9FS/BFHovjfGSxZa4
 P9nzhLuUZgSaGUWm/71tmJPkySD8watndIeBsWBsOYlH9Fx4P3G5ohvaU3GEF+Eo
 RJDcWNhfx2KivvTYFQRwmrqwKDEgRKwNDFlNh9vcjbc70P9UwcmgLbTP4ICwpxQx
 GodD3LlKsdLeiID/EdVjQhsK0NsulJ8NSTpxkTCJeFCRaUUFaqSFI+l+kcRyJypq
 SDIueEayNoLSPBZ+d3/SJ4dozO5g4Dr6zatJpve93bU78bQC0pUxEvKQByhYOjwc
 Z8winJMXRODb1eDNPul1A/QDu4llfy/sqjXtKg464Qw5uV4S3StTQ85biZIiIFRV
 oviOPjq5gKu/FsxZYRDeh26gYWqIahKDzILOiBqCCwiOHZnljLi2HmwScrYLEDML
 2FDjKc5S5qgDb6V7XzywLf9l9szKLyspx4KInztRs0d9cLV6yxcZDX0lBj52i8LB
 Vt8/GvF+rdUH15Lyd55z6s/kC2UY9Olbz0wJCoTxD5RxWon0X7PyWvTK4ql5VsbB
 3rdkykgjns764Wgimwek
 =wov6
 -END PGP SIGNATURE-

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 
WBR
Maxim aka solomax


Migrating from embedded Tomcat6 to Tomcat8

2015-07-03 Thread Maxim Solodovnik
Hello,

sorry for the newbie question but I was unable to find the answer using
search :(
I'm trying to migrate custom embedded tomcat loader from Tomcat6 (works as
expected with Tomcat7 with lots of deprecations) to Tomcat8.

Previously it was possible to add multiple Engines to Tomcat instance, how
this can be achieved in Tomcat8?

source file for Tomcat.java  states: // Single engine, service, server,
connector - few cases need more, they can use server.xml unfortunately I
need to do it using java (without server.xml)

Thanks in advance for your answers!

-- 
WBR
Maxim aka solomax