Aspects on Webflux acting funky
0
I am developing code for both MVC and Webflux endpoints. I have written AspectJ code for Autologging, pretty standard.
But, whenever I apply this Autologging code for Webflux endpoints, there seems to be a memory leak and when I stop the server, it closes with a warning.
2018-11-21 17:49:25.456 INFO [webflux-async_logback,,,] 6174 --- [on(2)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/Users/ahallim/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.12/tomcat-embed-core-9.0.12.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Is writing Aspects for Webflux/Reactive code a bad idea? If yes, why? Is there anyway to address this and mitigate?
Thanks in advance
spring aop aspectj spring-webflux reactive
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
add a comment |
0
I am developing code for both MVC and Webflux endpoints. I have written AspectJ code for Autologging, pretty standard.
But, whenever I apply this Autologging code for Webflux endpoints, there seems to be a memory leak and when I stop the server, it closes with a warning.
2018-11-21 17:49:25.456 INFO [webflux-async_logback,,,] 6174 --- [on(2)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/Users/ahallim/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.12/tomcat-embed-core-9.0.12.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Is writing Aspects for Webflux/Reactive code a bad idea? If yes, why? Is there anyway to address this and mitigate?
Thanks in advance
spring aop aspectj spring-webflux reactive
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
2
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49
add a comment |
0
0
0
I am developing code for both MVC and Webflux endpoints. I have written AspectJ code for Autologging, pretty standard.
But, whenever I apply this Autologging code for Webflux endpoints, there seems to be a memory leak and when I stop the server, it closes with a warning.
2018-11-21 17:49:25.456 INFO [webflux-async_logback,,,] 6174 --- [on(2)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/Users/ahallim/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.12/tomcat-embed-core-9.0.12.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Is writing Aspects for Webflux/Reactive code a bad idea? If yes, why? Is there anyway to address this and mitigate?
Thanks in advance
spring aop aspectj spring-webflux reactive
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
I am developing code for both MVC and Webflux endpoints. I have written AspectJ code for Autologging, pretty standard.
But, whenever I apply this Autologging code for Webflux endpoints, there seems to be a memory leak and when I stop the server, it closes with a warning.
2018-11-21 17:49:25.456 INFO [webflux-async_logback,,,] 6174 --- [on(2)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/Users/ahallim/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.12/tomcat-embed-core-9.0.12.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Is writing Aspects for Webflux/Reactive code a bad idea? If yes, why? Is there anyway to address this and mitigate?
Thanks in advance
spring aop aspectj spring-webflux reactive
spring aop aspectj spring-webflux reactive
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
asked Nov 21 '18 at 13:06
Anoop HallimalaAnoop Hallimala
117112
117112
2
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49
add a comment |
2
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49
2
2
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49
add a comment |
1 Answer
1
active
oldest
votes
0
This was not a memory leak. Webflux and AOP work together just fine.
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412731%2faspects-on-webflux-acting-funky%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
This was not a memory leak. Webflux and AOP work together just fine.
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
add a comment |
0
This was not a memory leak. Webflux and AOP work together just fine.
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
add a comment |
0
0
0
This was not a memory leak. Webflux and AOP work together just fine.
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
This was not a memory leak. Webflux and AOP work together just fine.
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
answered Nov 27 '18 at 8:31
Anoop HallimalaAnoop Hallimala
117112
117112
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412731%2faspects-on-webflux-acting-funky%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
why does that warning indicate a memory leak? There is no such mention... Even without aspects this message occurs (at least it did with me). It has to do with tomcat doing some reflected calls that are deprecated in Java 10+.
– M. Deinum
Nov 21 '18 at 15:55
I thought there could be memory leak as the system slowed down drastically. But, seeing your comment I couldn't reproduce the issue. Aspects on Webflux is running fine as of now. Thank you.
– Anoop Hallimala
Nov 23 '18 at 6:49