It can be run successfully in idea, but cannot be debugged
Related
When I was debugging the startup process of my SpringBoot application, sometimes it will show up the following warning log:
WARN 3781 --- [on(4)-127.0.0.1] javax.management.remote.misc : The server has decided to close this client connection.
After some searching, I found out the package javax.management.remote has something to do with RMI, but still can't figure out the reason, Can someone explain why this warning is shown?
I am using IntelliJ IDEA, OpenJDK17, spring boot of version 2.6, and JPA, p6spy as dependencies.
I am creating a demo application for Groovy using Spring boot with Kafka and elastic.
I used #EmbeddedKafka annotation in my Spock tests and they are working really nice locally; both on Windows and Ubuntu. They work from within Intellij by just running or debuggin, no issue. It's the same when trying in my shell "./gradlew test". Everything is good.
As soon as I pushed it to github.com, my github action fails. But it's calling the same command.
the action definition: https://github.com/besessener/GroovySpringBootKafkaElasticsearchDemo/blob/main/.github/workflows/test.yml
remote failing test case:
https://github.com/besessener/GroovySpringBootKafkaElasticsearchDemo/blob/main/src/test/groovy/me/spring/GroovyDemo/stream/KafkaSendAndReceiveTest.groovy
action: https://github.com/besessener/GroovySpringBootKafkaElasticsearchDemo/runs/3019862203?check_suite_focus=true
The only thing that looks like an error to me from the actions output, is this:
2021-07-08 14:05:35.896 WARN 2693 --- [ntainer#0-0-C-1] org.apache.kafka.clients.NetworkClient : [Consumer clientId=consumer-UserGroup-1, groupId=UserGroup] Error while fetching metadata with correlation id 4 : {topic-user=LEADER_NOT_AVAILABLE}
I read many things about not using static ports for the kafka tests. but this is my only kafka test, so I don't really understand how there should be a conflict. Furthermore LEADER_NOT_AVAILABLE could be a problem with a non-existing topic or maybe the consumer is simply not able to properly conenct to the broker. But I don't see any of this.
I still have the feeling it is more related to "localhost:9092" as brokerProperties. Is there an issue in regards to that when using Github actions? Or anything else I am missing?
I am running Jmeter to do some load testing on my app. When I run it with a single thread, I get all 200 codes in my test. Great. But when I run 2 threads, I start getting 302 redirect errors on my second thread. BUT that's not what I'm asking about.
How can I enable debug in my Spring Boot app in order to tell WHY I am getting these 302s? In my application.properties I have tried:
debug=true
logging.level.org.apache.tomcat.* = debug
logging.level.org.springframework.web.*=debug
.. but those don't get me the info I'm looking for. What else can I try to get more debug?
I can see the 302s in the Tomcat localhost_accersss_log.txt file, but no other info is there (as expected)
I am deploying an ear file in Websphere WAS7 console. The application is built on JDK1.6. The deployment is successful with no errors. But when I try to test the process by pushing a file, I am getting the below error during runtime.
E CWPST0164E: /opt/IBM/WebSphere/AppServer/profiles/AppSrv1/config/cells/lvqma942Cell/applications/null.ear/deployments/deployment.xml composition unit is not found.
Has anyone came across this? I can post more info as needed. Any help is appreciated!
I am currently having an issue where when I try to start my app I get the error:
ERROR context.GrailsContextLoader - Error initializing the application: Cannot execute
null+null
Message: Cannot execute null+null
This only happens when I tell the program to compile the Spring Security CAS plugin. This only started happening when I turned off forking, since it was making it hard to set up a JNDI. Is there a way to fix this problem without turning back on forking?
It turns out that the reason it wasn't working was because I hadn't finished configuring it. This doesn't make much sense to me, given that I was able to run the app just fine before without configuring it, seeing as how I never used that plugin within the implementation, it was just downloaded.