RE: ecj-4.6.3 no longer required?
User error. Not sure how I thought it was removed. Thanks Dave -Original Message- From: Jason Wee Sent: Tuesday, March 26, 2019 3:35 PM To: Tomcat Users List Subject: Re: ecj-4.6.3 no longer required? which 8.5.x u were referring? i just checked 8.5.39 has ecj in lib directory. On Wed, Mar 27, 2019 at 1:58 AM David Cleary wrote: > > I'm current updating our server that is based on Tomcat 8.5.x and found that > ecj-4.6.3.jar is no longer in the distribution. The changelog does not note > that it has been removed. I just want to confirm that I should remove this > library as part of the Tomcat update. > > Thanks > Dave
Re: Tomcat 9 - Web Application deployment fails: OperationNotSupportedException: Context is read only
On 27/03/2019 17:12, Ted Spradley wrote: > My web application deploys/starts normally locally on MacOS with the same > TomEE and JVM 1.8.0_202-b08 and other JMS (embedded ActiveMQ) Websocket > application, but on the remote Linux (CentOS) it fails with the “Context is > read only” error below. > > Any suggestion of where to begin looking? Seems like I’ve looked everywhere > the past two days. This looks like a question for the TomEE lists. Mark > Thank you, > > Ted S. > > > > Server & OS: > > 27-Mar-2019 11:17:25.189 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke Server version:Apache > Tomcat (TomEE)/9.0.12 (8.0.0-M1) > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke Server built: Sep 4 2018 > 22:13:41 UTC > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke Server number: 9.0.12.0 > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke OS Name: Linux > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke OS Version: > 3.10.0-957.5.1.el7.x86_64 > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke Architecture: amd64 > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke Java Home: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64/jre > > 27-Mar-2019 11:17:25.190 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke JVM Version: > 1.8.0_201-b09 > > 27-Mar-2019 11:17:25.191 INFO [main] > sun.reflect.NativeMethodAccessorImpl.invoke JVM Vendor:Oracle > Corporation > > > > Stack Trace: > > 27-Mar-2019 12:01:04.804 INFO [http-nio-9086-exec-4] > org.apache.openejb.util.JarExtractor.extract Extracting jar: > /usr/share/apache-tomee-plus-8.0.0-M1/webapps/o-test.war > > 27-Mar-2019 12:01:05.483 INFO [http-nio-9086-exec-4] > org.apache.openejb.util.JarExtractor.extract Extracted path: > /usr/share/apache-tomee-plus-8.0.0-M1/webapps/o-test > > 27-Mar-2019 12:01:05.539 SEVERE [http-nio-9086-exec-4] > sun.reflect.NativeMethodAccessorImpl.invoke Creation of the naming context > failed: [javax.naming.OperationNotSupportedException: Context is read only] > > 27-Mar-2019 12:01:05.540 SEVERE [http-nio-9086-exec-4] > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal Error merging > Java EE JNDI entries in to war /o-test: Exception: null > > java.lang.NullPointerException > > at > org.apache.catalina.core.NamingContextListener.createSubcontexts(NamingContextListener.java:1253) > > at > org.apache.catalina.core.NamingContextListener.addEnvironment(NamingContextListener.java:785) > > at > org.apache.catalina.core.NamingContextListener.processGlobalResourcesChange(NamingContextListener.java:432) > > at > org.apache.catalina.core.NamingContextListener.propertyChange(NamingContextListener.java:382) > > at > java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) > > at > java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327) > > at > java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) > > at > org.apache.catalina.deploy.NamingResourcesImpl.addEnvironment(NamingResourcesImpl.java:303) > > at > org.apache.tomee.catalina.OpenEJBNamingResource.addEnvironment(OpenEJBNamingResource.java:78) > > at > org.apache.tomee.catalina.TomcatJndiBuilder.mergeRef(TomcatJndiBuilder.java:403) > > at > org.apache.tomee.catalina.TomcatJndiBuilder.mergeJndi(TomcatJndiBuilder.java:125) > > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1394) > > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1130) > > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133) > > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) > > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5007) > > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743) > > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719) > > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:703) > > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) > > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) > > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1651) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Na
Tomcat 9 - Web Application deployment fails: OperationNotSupportedException: Context is read only
My web application deploys/starts normally locally on MacOS with the same TomEE and JVM 1.8.0_202-b08 and other JMS (embedded ActiveMQ) Websocket application, but on the remote Linux (CentOS) it fails with the “Context is read only” error below. Any suggestion of where to begin looking? Seems like I’ve looked everywhere the past two days. Thank you, Ted S. Server & OS: 27-Mar-2019 11:17:25.189 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke Server version:Apache Tomcat (TomEE)/9.0.12 (8.0.0-M1) 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke Server built: Sep 4 2018 22:13:41 UTC 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke Server number: 9.0.12.0 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke OS Name: Linux 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke OS Version: 3.10.0-957.5.1.el7.x86_64 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke Architecture: amd64 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke Java Home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64/jre 27-Mar-2019 11:17:25.190 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke JVM Version: 1.8.0_201-b09 27-Mar-2019 11:17:25.191 INFO [main] sun.reflect.NativeMethodAccessorImpl.invoke JVM Vendor:Oracle Corporation Stack Trace: 27-Mar-2019 12:01:04.804 INFO [http-nio-9086-exec-4] org.apache.openejb.util.JarExtractor.extract Extracting jar: /usr/share/apache-tomee-plus-8.0.0-M1/webapps/o-test.war 27-Mar-2019 12:01:05.483 INFO [http-nio-9086-exec-4] org.apache.openejb.util.JarExtractor.extract Extracted path: /usr/share/apache-tomee-plus-8.0.0-M1/webapps/o-test 27-Mar-2019 12:01:05.539 SEVERE [http-nio-9086-exec-4] sun.reflect.NativeMethodAccessorImpl.invoke Creation of the naming context failed: [javax.naming.OperationNotSupportedException: Context is read only] 27-Mar-2019 12:01:05.540 SEVERE [http-nio-9086-exec-4] org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal Error merging Java EE JNDI entries in to war /o-test: Exception: null java.lang.NullPointerException at org.apache.catalina.core.NamingContextListener.createSubcontexts(NamingContextListener.java:1253) at org.apache.catalina.core.NamingContextListener.addEnvironment(NamingContextListener.java:785) at org.apache.catalina.core.NamingContextListener.processGlobalResourcesChange(NamingContextListener.java:432) at org.apache.catalina.core.NamingContextListener.propertyChange(NamingContextListener.java:382) at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) at org.apache.catalina.deploy.NamingResourcesImpl.addEnvironment(NamingResourcesImpl.java:303) at org.apache.tomee.catalina.OpenEJBNamingResource.addEnvironment(OpenEJBNamingResource.java:78) at org.apache.tomee.catalina.TomcatJndiBuilder.mergeRef(TomcatJndiBuilder.java:403) at org.apache.tomee.catalina.TomcatJndiBuilder.mergeJndi(TomcatJndiBuilder.java:125) at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1394) at org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1130) at org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5007) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:703) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1651) 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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:287) at com.su
Re: HTTP/1.x broken with Tomcat 9, Java 11 and Http11NioProtocol
On Wed, Mar 27, 2019 at 4:21 PM Mark Thomas wrote:
> On 27/03/2019 15:13, Mark Thomas wrote:
> > On 27/03/2019 04:23, Jason Rivard wrote:
> >> I'm trying to get the following configuration working:
> >>
> >> - Tomcat 9.0.17 (also tested with 9.0.16)
> >> - AdoptOpenJDK Java 11.0.2 on Linux (also tested on Windows)
> >> - Http11NioProtocol Connector
> >> - Http2Protocol ProtocolUpgrade
> >>
> >> I'm using the following connector config:
> >>
> >> protocol="org.apache.coyote.http11.Http11NioProtocol"
> >>
> sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"
> >> SSLEnabled="true" scheme="https" secure="true"
> >> keystoreFile="/appData/jks-keystore" keystorePass="password">
> >>
> >>
> >>
> >> With the UpgradeProtocol in place, HTTP/2.0 works fine, but when I
> >> attempt a pure HTTP/1.0 or HTTP/1.1 request the server closes the
> >> connection before responding. This breaks any non-HTTP2.0 client.
> >>
> >> My first question is: Should this configuration work?
> >
> > Yes.
> >
> >> My second is: Why is it broken? :)
> >
> > Don't know yet. Just started looking.
>
> That didn't take long.
>
> When ALPN is available but no protocol is negotiated, OpenSSL returns
> null whereas JSSE returns "".
>
> Tomcat was doing:
> if (negotiatedProtocol != null) { ...
>
> rather than
>
> if (negotiatedProtocol != null && negotiatedProtocol.length() > 0) {
>
> and trying to create a Processor object for the "" protocol, failing and
> then closing the connection.
>
> The fix will be in the next set of releases (expected towards the end of
> next week).
>
This is a rather serious bug IMO, so that release cannot be delayed.
Rémy
Re: HTTP/1.x broken with Tomcat 9, Java 11 and Http11NioProtocol
On Wed, Mar 27, 2019 at 11:21 AM Mark Thomas wrote: > > Don't know yet. Just started looking. [snip] > That didn't take long. > The fix will be in the next set of releases (expected towards the end of > next week). [snip] Wow, that was fast! Thanks for the quick response! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: HTTP/1.x broken with Tomcat 9, Java 11 and Http11NioProtocol
On 27/03/2019 15:13, Mark Thomas wrote:
> On 27/03/2019 04:23, Jason Rivard wrote:
>> I'm trying to get the following configuration working:
>>
>> - Tomcat 9.0.17 (also tested with 9.0.16)
>> - AdoptOpenJDK Java 11.0.2 on Linux (also tested on Windows)
>> - Http11NioProtocol Connector
>> - Http2Protocol ProtocolUpgrade
>>
>> I'm using the following connector config:
>>
>> >
>> sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"
>> SSLEnabled="true" scheme="https" secure="true"
>> keystoreFile="/appData/jks-keystore" keystorePass="password">
>>
>>
>>
>> With the UpgradeProtocol in place, HTTP/2.0 works fine, but when I
>> attempt a pure HTTP/1.0 or HTTP/1.1 request the server closes the
>> connection before responding. This breaks any non-HTTP2.0 client.
>>
>> My first question is: Should this configuration work?
>
> Yes.
>
>> My second is: Why is it broken? :)
>
> Don't know yet. Just started looking.
That didn't take long.
When ALPN is available but no protocol is negotiated, OpenSSL returns
null whereas JSSE returns "".
Tomcat was doing:
if (negotiatedProtocol != null) { ...
rather than
if (negotiatedProtocol != null && negotiatedProtocol.length() > 0) {
and trying to create a Processor object for the "" protocol, failing and
then closing the connection.
The fix will be in the next set of releases (expected towards the end of
next week).
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: HTTP/1.x broken with Tomcat 9, Java 11 and Http11NioProtocol
On 27/03/2019 04:23, Jason Rivard wrote: > I'm trying to get the following configuration working: > > - Tomcat 9.0.17 (also tested with 9.0.16) > - AdoptOpenJDK Java 11.0.2 on Linux (also tested on Windows) > - Http11NioProtocol Connector > - Http2Protocol ProtocolUpgrade > > I'm using the following connector config: > > > sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation" > SSLEnabled="true" scheme="https" secure="true" > keystoreFile="/appData/jks-keystore" keystorePass="password"> > > > > With the UpgradeProtocol in place, HTTP/2.0 works fine, but when I > attempt a pure HTTP/1.0 or HTTP/1.1 request the server closes the > connection before responding. This breaks any non-HTTP2.0 client. > > My first question is: Should this configuration work? Yes. > My second is: Why is it broken? :) Don't know yet. Just started looking. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Windows Event Log
On 27/03/2019 13:24, GERALD EICHELBERGER wrote: > Greetings, I am looking for assistance in determining if Apache Tomcat has > the ability to have its events/logs to output to the Windows Event Log. Out of the box? No. Configure logging to use log4j and then add Log4JNA and it looks to be doable. > This is now a requirement for my organization. If this is not available where > can I go to get documentation so that I can create a BRJ for this requirement? BRJ? > I am currently working with Tomcat version 7.0.93 in a Test and Production > environment on Windows Server 2012. With Tomcat 7 you'll probably want to use log4j rather than log4j2 but still with log4JNA. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Windows Event Log
Greetings, I am looking for assistance in determining if Apache Tomcat has the ability to have its events/logs to output to the Windows Event Log. This is now a requirement for my organization. If this is not available where can I go to get documentation so that I can create a BRJ for this requirement? I am currently working with Tomcat version 7.0.93 in a Test and Production environment on Windows Server 2012. Gerald
