Re: [VOTE] 8.0.x EOL - 30 June 2018
Am 22.06.2017 um 17:18 schrieb Mark Thomas: We had a couple of threads discussing this. I think it is time for a vote. [X] +1 We should announce 8.0.x EOL for 30 June 2018 [ ] -1 We should announce 8.0.x EOL for [insert date here] [ ] -1 We should not announce 8.0.x EOL at this time +1 Thanks and regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 9.0.0.M22
Am 21.06.2017 um 16:18 schrieb Mark Thomas:
The proposed 9.0.0.M22 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 9.0.0.M22
+1 to release as alpha.
Details
===
- SHA1 and MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src consistent with svn tag
- except bin shell scripts are not executable in src tarball
(not critical)
- builds fine
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- JMX MBean Comparison with 9.0.0.M21 (same as M20):
- Filter MBeans for SetCharacterEncodingFilter are gone
(webapps manager, host-manager and examples)
This is due to r1798121 and r1798125
- New Servlet MBean "responsetrailer" in examples webapp
This is due to r1796186
- Manager MBean attribute sessionAttributeValueClassNameFilter added
for webapp manager and host-manager with value
java\.lang\.(?:Boolean|Integer|Long|Number|String)|org\.apache\.catalina\.filters\.CsrfPreventionFilter\$LruCache(?:\$1)?|java\.util\.(?:Linked)?HashMap
This is due to BZ61150, r1798384
- one more thread is started
- MBean java.util.logging:type=Logging has three items removed
from the LoggerNames array: org.apache.catalina.session,
org.apache.catalina.session.ManagerBase and
org.apache.catalina.session.StandardManager
- Unit tests: No failures, below comparisons are against M20 and M21.
Numbers are given for M20 / M21 / M22.
- Exceptions:
- new java.lang.IllegalStateExceptions:
- M21 (both once):
java.lang.IllegalStateException: Calling [asyncComplete()] is
not valid for a request with Async state [MUST_COMPLETE]
java.lang.IllegalStateException: Unexpected read state [CLOSING]
- M22 (twice):
Exception in thread "testBug54928"
java.lang.IllegalStateException: Calling [asyncComplete()] is not valid
for a request with Async state [MUST_ERROR]
- changed in M22 (was 2 / 1):
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
instead now once
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service()
for servlet [simple] in context with path [] threw exception
and the exception is
[junit] java.io.IOException: Stream reset
[junit] at
org.apache.coyote.http2.Stream$StreamInputBuffer.doRead(Stream.java:866)
[junit] at org.apache.coyote.Request.doRead(Request.java:526)
...
- 20 / 26 / 22 java.lang.NullPointerException
- java.io.IOException
- new in M22 (once)
java.security.cert.CertificateException: Could not parse certificate:
java.io.IOException: Incomplete data
Caused by: java.io.IOException: Incomplete data
- 4 / 3 / 3
java.io.IOException: The socket [NUMBER] associated with this connection
has been closed.
- 6 / 5 / 6
java.io.IOException: java.io.IOException: Unexpected error [NUMBER]
writing data to the APR/native socket [NUMBER] with wrapper
[org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper@HEX:NUM].
- 12 / 12 / 11
java.io.IOException: java.io.IOException: Broken pipe
- 2 / 2 / 3
Caused by: java.io.IOException: Connection reset by peer
- 2 / 1 / 2 java.io.EOFException
- only in M21 (once)
java.util.concurrent.RejectedExecutionException: Executor not running,
can't force a command into the queue
- only in M21 (once)
java.lang.Exception.(Exception.java:LINE)
java.lang.InterruptedException.(InterruptedException.java:LINE)
- only in M21 (once apr) and M22 (once nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 2 / 1 / 3
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run
IOException in replication worker, unable to drain channel. Probable
cause: Keep alive socket closed[null].
- 5 / 4 / 5
java.nio.channels.ClosedChannelException
- 7 / 5 / 4
org.apache.catalina.tribes.ChannelException: Sender not connected.; No
faulty members identified.
- 3 / 3 / 2
org.apache.catalina.tribes.ChannelException: Operation has timed
out([NUMBER] ms.).; Faulty members:tcp://{IP}:PORT;
but instead in M22 one new
org.apache.catalina.tribes.ChannelException: Send failed, and sender is
disconnected. Not retrying.; Faulty members:tcp://{IP}:PORT;
- SEVERE messages
- new in M22
org.apache.catalina.valves.SSLValve.invoke The SSL provider specified on
the connector associated with this request of [wontBeFound] is invalid.
The certificate data could not be processed.
together with
java.security.NoSuchProviderException: no such provider: wontBeFound
- 1 / 0 / 1 for apr
org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error
handling configured for
[org.apache.tomcat.websocket.TesterEchoServer$Async] and the following
error occurred
- 1 / 0 / 0 for nio
org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error
handling configured for
Re: [VOTE] Release Apache Tomcat 8.5.16
Am 21.06.2017 um 23:37 schrieb Mark Thomas:
The proposed 8.5.16 release is: [ ] Broken - do not release [X]
Stable - go ahead and release as 8.5.16
+1 to release.
Details
===
- SHA1 and MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src consistent with svn tag
- except bin shell scripts are not executable in src tarball
(not critical)
- builds fine
- warning about unchecked calls or conversions in:
- org/apache/catalina/tribes/tipis/AbstractReplicatedMap.java
- org/apache/tomcat/jdbc/pool/PoolProperties.java
Not a regression
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- JMX MBean Comparison with 8.5.15 (same as 8.5.14):
- Manager MBean attribute sessionAttributeValueClassNameFilter added
for webapp manager and host-manager with value
java\.lang\.(?:Boolean|Integer|Long|Number|String)|org\.apache\.catalina\.filters\.CsrfPreventionFilter\$LruCache(?:\$1)?|java\.util\.(?:Linked)?HashMap
This is due to BZ61150, r1798385
- MBean java.util.logging:type=Logging has three items removed
from the LoggerNames array: org.apache.catalina.session,
org.apache.catalina.session.ManagerBase and
org.apache.catalina.session.StandardManager
- ThreadPool MBean new attributes acceptCount, connectionLinger
and connectionTimeout
- ProtocolHandler MBean new attributes acceptCount and
connectionLinger
- Unit tests: No failures, below comparisons are against 8.5.14 and 8.5.15
Numbers are given for 14 / 15 / 16.
- Exceptions:
- new java.lang.IllegalStateExceptions:
- 15 (once):
java.lang.IllegalStateException: Calling [asyncComplete()] is not valid
for a request with Async state [MUST_COMPLETE]
- 15 (once)
java.lang.IllegalStateException: Cannot call sendError() after the
response has been committed
- 16 (once):
Exception in thread "testBug54928" java.lang.IllegalStateException:
Calling [asyncComplete()] is not valid for a request with Async state
[DISPATCHED]
- 16 (once)
java.lang.IllegalStateException: Unexpected read state [CLOSING]
- 1 / 0 / 1
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
- new in 16
Exception in thread "http-apr-127.0.0.1-auto-I-exec-P"
java.lang.NullPointerException
- 9 / 7 / 10
java.lang.NullPointerException
- java.io.IOException
- new in M22 (3 times)
java.security.cert.CertificateException: Unable to initialize,
java.io.IOException: extra data given to DerValue constructor
java.io.IOException: extra data given to DerValue constructor
maybe related to the error following next:
java.security.NoSuchProviderException: no such provider: wontBeFound
- 5 / 5 / 6
java.io.IOException: Unexpected error [NUMBER] writing data to the
APR/native socket [NUMBER] with wrapper
[org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper@HEX:NUM].
- 11 / 11 / 12
java.io.IOException: java.io.IOException: Broken pipe
- 1 / 2 / 2
java.io.EOFException
- only in 8.5.15 (once)
java.util.concurrent.RejectedExecutionException: Executor not running,
can't force a command into the queue
- in 8.5.14 (once apr) 8.5.15 (once apr and nio each)
and 8.5.16 (once nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 6 / 3 / 0
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run
IOException in replication worker, unable to drain channel. Probable
cause: Keep alive socket closed[null].
- 5 / 4 / 5
java.nio.channels.ClosedChannelException
- 9 / 7 / 6
org.apache.catalina.tribes.ChannelException: Sender not connected.; No
faulty members identified.
- 2 / 4 / 2
org.apache.catalina.tribes.ChannelException: Operation has timed
out([NUMBER] ms.).; Faulty members:tcp://{IP}:PORT;
- 5 / 1 / 0
org.apache.catalina.tribes.ChannelException: java.net.ConnectException:
Connection refused; Faulty members:tcp://{IP}:PORT;
Caused by: java.net.ConnectException: Connection refused
- SEVERE messages
- new in 16 (3 times)
org.apache.catalina.valves.SSLValve.invoke The SSL provider specified on
the connector associated with this request of [wontBeFound] is invalid.
The certificate data could not be processed.
- 1 / 0 / 1 (nio)
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
- 1 / 0 / 1 (nio2 / nio)
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service()
for servlet [simple] in context with path [] threw exception
- 1(apr) / 1xapr+2xnio / 1(nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 4(apr) / 4(apr) / 5(apr)+1(jsse-nio)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
reading request, ignored
- 2xapr+2xnio / 1xnio+2xnio2 / 2xapr+2xnio2
org.apache.coyote.http11.Http11Processor.endRequest Error finish
Re: [VOTE] 8.0.x EOL - 30 June 2018
On 23/06/17 23:17, Emmanuel Bourg wrote: > Le 23/06/2017 à 21:15, Christopher Schultz a écrit : > >> The idea was to encourage package repository maintainers to migrate to >> Tomcat 8.5. If we never sundown Tomcat 8.0, they'll never move (witness >> the presence of Tomcat 6.0 still lurking around half the Internet). > > As far as Debian is concerned, the migration to Tomcat 8.5 did happen in > Debian 9. But Debian 8 users are stuck with Tomcat 8.0.x until June > 2020. Tomcat 8.5 isn't a drop-in replacement for Tomcat 8.0 > unfortunately, so it's a bit difficult to push this upgrade in a stable > distribution. If 8.5.x was a drop-in replacement would that make a difference? And as a follow-up, what would need to change so 8.5.x was viewed a drop-in replacement? The only thing I can think of is lack of support for the BIO connectors. I have an easy fix for that if there is interest. Anything else? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 9.0.0.M22
Am 21. Juni 2017 16:18:39 MESZ schrieb Mark Thomas : >The proposed Apache Tomcat 9.0.0.M22 release is now available for >voting. > >This is a milestone release for the 9.0.x branch. It should be >noted that, as a milestone release: >- Servlet 4.0 is not finalised >- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0 > >The major changes compared to the 9.0.0.M21 release are: > >- Add a new JULI FileHandler configuration for specifying the maximum > number of days to keep the log files. By default the log files will be > kept 90 days. > >- Update the Servlet 4.0 implementation to add support for setting > trailer fields for HTTP responses. > >- When pre-compiling with JspC, report all compilation errors rather > than stopping after the first error. > >Along with lots of other bug fixes and improvements > >For full details, see the changelog: >http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml > >It can be obtained from: >https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M22/ >The Maven staging repo is: >https://repository.apache.org/content/repositories/orgapachetomcat-1137/ >The svn tag is: >http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M22/ > >The proposed 9.0.0.M22 release is: >[ ] Broken - do not release >[x] Alpha - go ahead and release as 9.0.0.M22 Felix > >- >To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 8.5.16
Am 21. Juni 2017 23:37:31 MESZ schrieb Mark Thomas : >The proposed Apache Tomcat 8.5.16 release is now available for voting. > >The major changes compared to the 8.5.16 release are: > >- Add a new JULI FileHandler configuration for specifying the maximum > number of days to keep the log files. By default the log files will be > kept 90 days. > >- Improvements to enable the Manager and HostManager to work in the > default configuration when working under a security manager > >- Introduce new API o.a.tomcat.websocket.WsSession#suspend/ > o.a.tomcat.websocket.WsSession#resume that can be used to > suspend/resume reading of the incoming messages. > > >It can be obtained from: >https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.16/ >The Maven staging repo is: >https://repository.apache.org/content/repositories/orgapachetomcat-1138/ >The svn tag is: >http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_16/ > >The proposed 8.5.16 release is: >[ ] Broken - do not release >[x] Stable - go ahead and release as 8.5.16 Felix > >- >To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61214] New: NoSuchMethodException in JMX Proxy when accessing to Context MBeans
https://bz.apache.org/bugzilla/show_bug.cgi?id=61214 Bug ID: 61214 Summary: NoSuchMethodException in JMX Proxy when accessing to Context MBeans Product: Tomcat 9 Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Manager Assignee: dev@tomcat.apache.org Reporter: alexis.hass...@sewatech.fr Target Milestone: - The servlets attribute is still in the StandardContext mbean but is no longer in the org.apache.catalina.core.StandardContext class. Here is the stacktrace : 24-Jun-2017 23:41:41.058 SEVERE [http-nio-8080-exec-1] org.apache.catalina.mbeans.MBeanDumper.dumpBeans Error getting attribute Catalina:j2eeType=WebModule,name=//localhost/host-manager,J2EEApplication=none,J2EEServer=none servlets javax.management.ReflectionException: Cannot find getter method getServlets at org.apache.tomcat.util.modeler.ManagedBean.getGetter(ManagedBean.java:458) at org.apache.tomcat.util.modeler.BaseModelMBean.getAttribute(BaseModelMBean.java:180) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647) at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) at org.apache.catalina.mbeans.MBeanDumper.dumpBeans(MBeanDumper.java:81) at org.apache.catalina.manager.JMXProxyServlet.listBeans(JMXProxyServlet.java:185) at org.apache.catalina.manager.JMXProxyServlet.doGet(JMXProxyServlet.java:121) at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:592) at org.apache.catalina.valves.RequestFilterValve.process(RequestFilterValve.java:319) at org.apache.catalina.valves.RemoteAddrValve.invoke(RemoteAddrValve.java:88) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:625) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:498) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:796) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1372) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodException: org.apache.catalina.core.StandardContext.getServlets() at java.lang.Class.getMethod(Class.java:1786) at org.apache.tomcat.util.modeler.ManagedBean.getGetter(ManagedBean.java:451) ... 32 more -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] tomcat pull request #65: Fix bug #61214 : NoSuchMethodException in JMX Proxy...
GitHub user hasalex opened a pull request: https://github.com/apache/tomcat/pull/65 Fix bug #61214 : NoSuchMethodException in JMX Proxy (Context MBeans) Remove servlets attribute in the ServletContext mbean description You can merge this pull request into a Git repository by running: $ git pull https://github.com/hasalex/tomcat getServlets Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tomcat/pull/65.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #65 commit 328c2bdbcd5c8d3b25a9ecdff46a60ba9ab70b0b Author: Alexis Hassler Date: 2017-06-24T21:51:49Z Fix bug #61214 : NoSuchMethodException in JMX Proxy when accessing to Context MBeans Remove servlets attribute in the ServletContext mbean description --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61214] NoSuchMethodException in JMX Proxy when accessing to Context MBeans
https://bz.apache.org/bugzilla/show_bug.cgi?id=61214 --- Comment #1 from Alexis Hassler --- PR sent -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61215] New: NoSuchMethodException in JMX Proxy when accessing to RemoteAddrValve MBeans
https://bz.apache.org/bugzilla/show_bug.cgi?id=61215 Bug ID: 61215 Summary: NoSuchMethodException in JMX Proxy when accessing to RemoteAddrValve MBeans Product: Tomcat 9 Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Manager Assignee: dev@tomcat.apache.org Reporter: alexis.hass...@sewatech.fr Target Milestone: - The RemoteAddrValve class has some new boolean attributes (addConnectorPort, invalidAuthenticationWhenDeny, addConnectorPort, invalidAuthenticationWhenDeny) but the accessors are not mbean-friendly. 'is' should be used instead of 'get'. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] tomcat pull request #66: Fix bug #61215 : Bug 61215 - NoSuchMethodException ...
GitHub user hasalex opened a pull request: https://github.com/apache/tomcat/pull/66 Fix bug #61215 : Bug 61215 - NoSuchMethodException in JMX Proxy (RemoteAddrValve) You can merge this pull request into a Git repository by running: $ git pull https://github.com/hasalex/tomcat RemoteAddrValve Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tomcat/pull/66.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #66 commit 1abd336b3bb0e5122e2824651a17fdaf7c8e1d59 Author: Alexis Hassler Date: 2017-06-24T22:24:56Z Fix bug #61215 : Bug 61215 - NoSuchMethodException in JMX Proxy when accessing to RemoteAddrValve MBeans Replace getXxx accessors with isXXX --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61215] NoSuchMethodException in JMX Proxy when accessing to RemoteAddrValve MBeans
https://bz.apache.org/bugzilla/show_bug.cgi?id=61215 --- Comment #1 from Alexis Hassler --- PR sent (#66) : - replace the getInvalidAuthenticationWhenDeny with isInvalidAuthenticationWhenDeny in RequestFilterValve - replace getAddConnectorPort with isAddConnectorPort in RemoteAddrValve -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61216] New: Enhanced output format of CompositeData and TabularData in JMXProxy
https://bz.apache.org/bugzilla/show_bug.cgi?id=61216
Bug ID: 61216
Summary: Enhanced output format of CompositeData and
TabularData in JMXProxy
Product: Tomcat 9
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: Manager
Assignee: dev@tomcat.apache.org
Reporter: alexis.hass...@sewatech.fr
Target Milestone: -
CompositeData and TabularData are printed with toString in the Manager
JMXProxy. It makes the result hard to read (for a human) and to grep.
CompositeData could be represented as {key1=value1, key2=value2,...}.
TabularData could be printed like arrays.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] tomcat pull request #67: Fix #61216 - Enhanced output format of CompositeDat...
GitHub user hasalex opened a pull request:
https://github.com/apache/tomcat/pull/67
Fix #61216 - Enhanced output format of CompositeData and TabularData
CompositeData are represented as {key1=value1, key2=value2,...}.
Ex. java.lang:type=Runtime.
TabularData could be printed like arrays.
Ex. java.lang:type=Memory or com.sun.management:type=HotSpotDiagnostic
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hasalex/tomcat MBeanDumper
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tomcat/pull/67.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #67
commit 39b1a2704b30396bb1961f753641bd6d6c7f9e23
Author: Alexis Hassler
Date: 2017-06-24T23:28:49Z
Fix #61216 - Enhanced output format of CompositeData and TabularData in
JMXProxy
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 61216] Enhanced output format of CompositeData and TabularData in JMXProxy
https://bz.apache.org/bugzilla/show_bug.cgi?id=61216 --- Comment #1 from Alexis Hassler --- PR sent (#67) -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Need a help to begin.
I am a Beginner. I have searched for bugs marks for Beginners. But i couldn't find them. Can anyone help me to find them or Can anyone show me a bug which can work on. Thank u On Fri, Jun 23, 2017 at 4:03 PM, Mark Thomas wrote: > On 22/06/17 13:43, Kasun Prabath Amarasinghe wrote: > > I'm a computer Engineering undergraduate student. I would like to > > contribute to open source projects. But I don't know where to start and > how > > to start.Can anyone guide me to start. > > > > Welcome to the Apache Tomcat community. > > There is some useful information available at http://tomcat.apache.org/ > Have a look at the links under "Get Involved" in the menu on the left > hand side. > > We have recently started to mark some bugs as "Beginner" if we think > they are suitable for someone new to the project. There aren't many of > them yet. > > The most important thing is to do something that you find interesting. > > If you have any questions, or suggestions for how we can improve the > experience for people new to the project, do let us know. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
