date:20150922

RE: Warning from users@tomcat.apache.org

2015-09-22 Thread Shree, Shubha

Hi,

Please do not remove my name  from the list of recipients .

Regards,
Shubha Shree
Important : The information transmitted is intended for the person or entity to 
which it is addressed and may contain confidential, privileged or copyrighted 
material or attorney work product. If you receive this in error, please contact 
the sender and delete the material from any computer. Any comments or 
statements made are not necessarily those of FIL India Business Services 
Private Limited or any other Fidelity entity. All e-mails may be monitored or 
recorded.


-Original Message-
From: users-h...@tomcat.apache.org [mailto:users-h...@tomcat.apache.org] 
Sent: 22 September 2015 11:25
To: Shree, Shubha
Subject: Warning from users@tomcat.apache.org

Hi! This is the ezmlm program. I'm managing the users@tomcat.apache.org mailing 
list.

I'm working for my owner, who can be reached at users-ow...@tomcat.apache.org.


Messages to you from the users mailing list seem to have been bouncing. I've 
attached a copy of the first bounce message I received.

If this message bounces too, I will send you a probe. If the probe bounces, I 
will remove your address from the users mailing list, without further notice.


I've kept a list of which messages from the users mailing list have bounced 
from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request), send a 
short message to:
   

To receive a subject and author list for the last 100 or so messages, send a 
short message to:
   

Here are the message numbers:

   254672
   254673
   254674
   254675
   254676
   254677
   254678
   254679
   254680
   254681
   254682
   254683
   254684
   254685
   254687
   254688
   254689
   254686
   254691
   254692
   254693
   254694
   254695
   254690
   254697
   254698
   254699
   254696
   254700
   254701
   254702
   254705
   254706
   254707
   254708
   254703
   254704
   254709
   254710
   254711
   254712
   254713
   254714
   254715
   254716
   254717
   254718
   254719
   254720
   254721
   254722
   254723
   254725
   254724
   254726
   254727
   254728
   254730
   254731
   254732
   254729
   254734
   254733
   254735
   254736
   254737
   254738
   254739
   254740
   254741
   254742
   254743
   254744
   254745
   254746
   254747
   254748

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 35992 invoked for bounce); 12 Sep 2015 00:41:51 -
Date: 12 Sep 2015 00:41:51 -
From: mailer-dae...@apache.org
To: users-return-2546...@tomcat.apache.org
Subject: failure notice


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

Re: Tomcat 7 and APR connector parameters

2015-09-22 Thread Mark Thomas

On 22/09/2015 01:31, Igor Cicimov wrote:
> On 21/09/2015 7:47 PM, "Mark Thomas"  wrote:
>>
>> On 21/09/2015 10:45, Igor Cicimov wrote:
>>> On Mon, Sep 21, 2015 at 6:21 PM, Mark Thomas  wrote:
>>>
 On 21/09/2015 08:37, Igor Cicimov wrote:
> Hi all,
>
> After enabling the APR/Native connector I can see the following
> warning
> messages upon tomcat restart:
>
> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
 property
> 'SSLDisableCompression' to 'true' did not find a matching property.
> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
 property
> 'SSLHonorCipherOrder' to 'true' did not find a matching property.
>
> although I can see those options available in the documentation:
>

> https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_APR/Native

 You are looking at the docs for 7.0.64 but running 7.0.26.

 You need to use a more recent Tomcat 7.0.x release if you want to use
 those features.

 Mark

>>>
>>> Thanks Mark for confirming. Is it possible to specify this in the
>>> documentation like which feature is available since which release?
>>
>> That is (usually) in the change log.
>>
>> Each release ships with docs appropriate to that release. The website
>> always has the docs for the latest release.
>>
>> Mark
>>
> True but that means if I was interested in finding when was a feature
> introduced in tomcat 7 lets say I need to read dozens (depends on how lucky
> I am and when and where I start reading from) of change logs right?

Nope. The changelog contains everything from 7.0.0 to the latest. If you
are lucky the attribute name will be mentioned in the change log. If it
isn't a sensible search should led you to the right entry.

http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

SSLDisableCompression -> compression -> 7.0.?
SSLHonorCipherOrder   -> 7.0.?

I shouldn't take you more than a few seconds to fill in the blanks.

> It would be helpful if the latest tomcat docs include something like:
> 
> 'SSLHonorCipherOrder' | some description (available since tomcat 7.0.x)
> 
> I see this on many other web sites for various products and I personally
> find this very useful and user friendly.

Patches welcome.

Mark


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

is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

2015-09-22 Thread Johan Compagner

Hi,

when we have a webfragment in our war  to enable i think that absolute
ordering
we get this exception?:

21-Sep-2015 14:15:11.355 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.ContextConfig.processServletContainerInitializers
Failed to process JAR found at URL [/post_install_test] for
ServletContainerInitializers for context with name [{1}]
 java.net.MalformedURLException: no !/ in spec
at java.net.URL.(Unknown Source)
at java.net.URL.(Unknown Source)
at java.net.URL.(Unknown Source)
at java.net.JarURLConnection.parseSpecs(Unknown Source)
at java.net.JarURLConnection.(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.(Unknown Source)
at sun.net.www.protocol.jar.Handler.openConnection(Unknown Source)
at java.net.URL.openConnection(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at 
org.apache.catalina.startup.WebappServiceLoader.parseConfigFile(WebappServiceLoader.java:156)
at 
org.apache.catalina.startup.WebappServiceLoader.load(WebappServiceLoader.java:113)
at 
org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1597)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1125)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:768)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5069)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:919)
at 
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1704)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException: no !/ in spec
at sun.net.www.protocol.jar.Handler.parseAbsoluteSpec(Unknown Source)
at sun.net.www.protocol.jar.Handler.parseURL(Unknown Source)
... 29 more


if we say to tomcat8 to not extract the war (unpack=false)


This is completely outside of the application itself because it is
trying to start it. when unpack is default (true) then it works fine.


so in our WEB-INF/web.xml we have:


  
servoy_ngclient
  



and then in the WEB-INF/lib/ngclient.jar/META-INF/web-fragement.xml


http://java.sun.com/xml/ns/javaee;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd; version="3.0">
servoy_ngclient



If we remove that ordering and/or the web-fragement.xml then it starts
working again


-- 
Johan Compagner
Servoy

Reply from Hitesh Raghava

2015-09-22 Thread Raghav, Hitesh

Hi ,

Please do not remove my name from the list of recipients .



The information transmitted is intended for the person or entity to which it is 
addressed and may contain confidential, privileged or copyrighted material or 
attorney work product. If you receive this in error, please contact the sender 
and delete the material from any computer. Any comments or statements made are 
not necessarily those of FIL India Business Services Private Limited or any 
other Fidelity entity. All e-mails may be monitored or recorded

Re: is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

2015-09-22 Thread Johan Compagner

just quickly tested it and 8.0.26 so the latest has this problem

On 22 September 2015 at 11:37, Mark Thomas  wrote:

> On 22/09/2015 10:25, Johan Compagner wrote:
> > Hi,
> >
> > when we have a webfragment in our war  to enable i think that absolute
> > ordering
> > we get this exception?:
>
> Tomcat version?
>
> Mark
>
>
> >
> > 21-Sep-2015 14:15:11.355 SEVERE [localhost-startStop-1]
> >
> org.apache.catalina.startup.ContextConfig.processServletContainerInitializers
> > Failed to process JAR found at URL [/post_install_test] for
> > ServletContainerInitializers for context with name [{1}]
> >  java.net.MalformedURLException: no !/ in spec
> >   at java.net.URL.(Unknown Source)
> >   at java.net.URL.(Unknown Source)
> >   at java.net.URL.(Unknown Source)
> >   at java.net.JarURLConnection.parseSpecs(Unknown Source)
> >   at java.net.JarURLConnection.(Unknown Source)
> >   at sun.net.www.protocol.jar.JarURLConnection.(Unknown Source)
> >   at sun.net.www.protocol.jar.Handler.openConnection(Unknown Source)
> >   at java.net.URL.openConnection(Unknown Source)
> >   at java.net.URL.openStream(Unknown Source)
> >   at
> org.apache.catalina.startup.WebappServiceLoader.parseConfigFile(WebappServiceLoader.java:156)
> >   at
> org.apache.catalina.startup.WebappServiceLoader.load(WebappServiceLoader.java:113)
> >   at
> org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1597)
> >   at
> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1125)
> >   at
> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:768)
> >   at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
> >   at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> >   at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> >   at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5069)
> >   at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >   at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
> >   at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
> >   at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
> >   at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:919)
> >   at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1704)
> >   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
> Source)
> >   at java.util.concurrent.FutureTask.run(Unknown Source)
> >   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)
> >   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> >   at java.lang.Thread.run(Unknown Source)
> > Caused by: java.lang.NullPointerException: no !/ in spec
> >   at sun.net.www.protocol.jar.Handler.parseAbsoluteSpec(Unknown
> Source)
> >   at sun.net.www.protocol.jar.Handler.parseURL(Unknown Source)
> >   ... 29 more
> >
> >
> > if we say to tomcat8 to not extract the war (unpack=false)
> >
> >
> > This is completely outside of the application itself because it is
> > trying to start it. when unpack is default (true) then it works fine.
> >
> >
> > so in our WEB-INF/web.xml we have:
> >
> >
> >   
> > servoy_ngclient
> >   
> >
> >
> >
> > and then in the WEB-INF/lib/ngclient.jar/META-INF/web-fragement.xml
> >
> >
> > http://java.sun.com/xml/ns/javaee;
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> > http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd; version="3.0">
> >   servoy_ngclient
> > 
> >
> >
> > If we remove that ordering and/or the web-fragement.xml then it starts
> > working again
> >
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
Johan Compagner
Servoy

Re: is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

2015-09-22 Thread Mark Thomas

On 22/09/2015 10:25, Johan Compagner wrote:
> Hi,
> 
> when we have a webfragment in our war  to enable i think that absolute
> ordering
> we get this exception?:

Tomcat version?

Mark


> 
> 21-Sep-2015 14:15:11.355 SEVERE [localhost-startStop-1]
> org.apache.catalina.startup.ContextConfig.processServletContainerInitializers
> Failed to process JAR found at URL [/post_install_test] for
> ServletContainerInitializers for context with name [{1}]
>  java.net.MalformedURLException: no !/ in spec
>   at java.net.URL.(Unknown Source)
>   at java.net.URL.(Unknown Source)
>   at java.net.URL.(Unknown Source)
>   at java.net.JarURLConnection.parseSpecs(Unknown Source)
>   at java.net.JarURLConnection.(Unknown Source)
>   at sun.net.www.protocol.jar.JarURLConnection.(Unknown Source)
>   at sun.net.www.protocol.jar.Handler.openConnection(Unknown Source)
>   at java.net.URL.openConnection(Unknown Source)
>   at java.net.URL.openStream(Unknown Source)
>   at 
> org.apache.catalina.startup.WebappServiceLoader.parseConfigFile(WebappServiceLoader.java:156)
>   at 
> org.apache.catalina.startup.WebappServiceLoader.load(WebappServiceLoader.java:113)
>   at 
> org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1597)
>   at 
> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1125)
>   at 
> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:768)
>   at 
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
>   at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>   at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>   at 
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5069)
>   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>   at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
>   at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
>   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
>   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:919)
>   at 
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1704)
>   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>   at java.util.concurrent.FutureTask.run(Unknown Source)
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>   at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException: no !/ in spec
>   at sun.net.www.protocol.jar.Handler.parseAbsoluteSpec(Unknown Source)
>   at sun.net.www.protocol.jar.Handler.parseURL(Unknown Source)
>   ... 29 more
> 
> 
> if we say to tomcat8 to not extract the war (unpack=false)
> 
> 
> This is completely outside of the application itself because it is
> trying to start it. when unpack is default (true) then it works fine.
> 
> 
> so in our WEB-INF/web.xml we have:
> 
> 
>   
> servoy_ngclient
>   
> 
> 
> 
> and then in the WEB-INF/lib/ngclient.jar/META-INF/web-fragement.xml
> 
> 
> http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd; version="3.0">
>   servoy_ngclient
> 
> 
> 
> If we remove that ordering and/or the web-fragement.xml then it starts
> working again
> 
> 


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

RE: Warning from users@tomcat.apache.org

Re: Tomcat 7 and APR connector parameters

is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

Reply from Hitesh Raghava

Re: is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

Re: is there already a case for web-fragment.xml in the war and then unpack=false option to not extract the war?

6 matches

Site Navigation

Mail list logo

Footer information