Adds a JFR event for socket connect operations.
Existing tests TestSocketEvents and TestSocketChannelEvents modified to also
check for connect events.
-
Commit messages:
- fix default settings
- fix merge
- Merge branch 'master' into JDK-8310996
- added tests and support for soc
.FileForceEvent to be a mirror event.
>
> Updated FileChannelImpl to use the jdk internal event static methods, and
> removed the force() method from FileChannelImplInstrumentor.
>
> Uses the existing tests.
Tim Prinzing has updated the pull request incrementally with one
On Fri, 29 Mar 2024 00:52:46 GMT, Tim Prinzing wrote:
> Currently the JFR event FileForceEvent is generated by instrumenting the
> sun.nio.ch.FileChannelImpl class. This needs to be changed to use the newer
> mirror events with static methods.
>
> Add
Currently the JFR event FileForceEvent is generated by instrumenting the
sun.nio.ch.FileChannelImpl class. This needs to be changed to use the newer
mirror events with static methods.
Added the event at jdk.internal.event.FileForceEvent, and changed
jdk.jfr.events.FileForceEvent to be a mirror
On Tue, 6 Jun 2023 19:39:31 GMT, Tim Prinzing wrote:
> The socket read/write JFR events currently use instrumentation of java.base
> code using templates in the jdk.jfr modules. This results in some java.base
> code residing in the jdk.jfr module which is undesirable.
>
> JDK
On Tue, 19 Sep 2023 15:35:11 GMT, Tim Prinzing wrote:
>> The socket read/write JFR events currently use instrumentation of java.base
>> code using templates in the jdk.jfr modules. This results in some java.base
>> code residing in the jdk.jfr module which is undesirable.
e at runtime with
> annotations that add the extra arguments.
> At compile time the build arguments had to be augmented in
> make/test/BuildMicrobenchmark.gmk
Tim Prinzing has updated the pull request with a new target base due to a merge
or a rebase. The pull request now contains 12 co
On Tue, 22 Aug 2023 07:18:21 GMT, Alan Bateman wrote:
>> src/java.base/share/classes/java/net/Socket.java line 1133:
>>
>>> 1131: return parent.getSoTimeout();
>>> 1132: } catch (Throwable t) {
>>> 1133: // ignored - avoiding exceptions in jfr event da
e at runtime with
> annotations that add the extra arguments.
> At compile time the build arguments had to be augmented in
> make/test/BuildMicrobenchmark.gmk
Tim Prinzing has updated the pull request incrementally with one additional
commit since the last revision:
More changes
On Tue, 22 Aug 2023 07:31:36 GMT, Alan Bateman wrote:
> > https://bugs.openjdk.org/browse/JDK-8310979 - better exception handling
> > https://bugs.openjdk.org/browse/JDK-8310978 - missing code paths for event
> > generation https://bugs.openjdk.org/browse/JDK-8310994 - non-blocking,
> > event
On Wed, 28 Jun 2023 18:53:12 GMT, Tim Prinzing wrote:
>> The socket read/write JFR events currently use instrumentation of java.base
>> code using templates in the jdk.jfr modules. This results in some java.base
>> code residing in the jdk.jfr module which is undesirable.
e at runtime with
> annotations that add the extra arguments.
> At compile time the build arguments had to be augmented in
> make/test/BuildMicrobenchmark.gmk
Tim Prinzing has updated the pull request incrementally with one additional
commit since the last revision:
less exception fi
e at runtime with
> annotations that add the extra arguments.
> At compile time the build arguments had to be augmented in
> make/test/BuildMicrobenchmark.gmk
Tim Prinzing has updated the pull request with a new target base due to a merge
or a rebase. The pull request now contains ten co
e at runtime with
> annotations that add the extra arguments.
> At compile time the build arguments had to be augmented in
> make/test/BuildMicrobenchmark.gmk
Tim Prinzing has updated the pull request incrementally with one additional
commit since the last revision:
Avoid excepti
On Thu, 22 Jun 2023 13:39:51 GMT, Erik Gahlin wrote:
> In cases where the implRead/implWrite call throws an exception, shouldn't the
> event contain that exception, or at least exception message? If it doesn't
> should it be emitted at all, or should another event be emitted instead?
Added iss
On Thu, 22 Jun 2023 10:21:46 GMT, Alan Bateman wrote:
>> The socket read/write JFR events currently use instrumentation of java.base
>> code using templates in the jdk.jfr modules. This results in some java.base
>> code residing in the jdk.jfr module which is undesirable.
>>
>> JDK19 added sta
The socket read/write JFR events currently use instrumentation of java.base
code using templates in the jdk.jfr modules. This results in some java.base
code residing in the jdk.jfr module which is undesirable.
JDK19 added static support for event classes. The old instrumentor classes
should be
17 matches
Mail list logo
