Constantly freezes the Spring Tool Suite (STS) - ide

I recently started using the Spring Tool Suite (STS) for development under Spring Boot.
After not continuing the work after starting STS hangs tightly.
Used OS Linux Mint.
Tell me how to diagnose the problem of suspense?

If STS hangs, I would strongly recommend to:
capture a thread dump while STS hangs (using jps and jstack)
file an issue at https://github.com/spring-projects/spring-ide/issues and attach the full thread dump
continue to capture thread dumps and attach them to the issue, sometimes slightly different thread dumps reveal interesting details
The thread dump usually reveals whether there is a thread deadlock under the hood, a network issue, or some other very long running process doing some work.

Faced similar issue in windows. Encountered when extracted by jar -xvf spring-tool-***.jar.
It has been resolved the way by which the jar is extracted by executing it rather extract directly.
java -jar spring-tool-***.jar

Related

Failed to open connection to "session" message bus: /usr/bin/dbus-launch terminated abnormally without any error message [duplicate]

I am using a very complex setup to test various non-public webpages. I use jenkins to run the python-selenium tests within a dockerimage. That way, I am completely independent of the jenkins environment and can create my own environment. In this environment I have the following software installed:
Ubuntu 16.04.3
Firefox: Mozilla Firefox 57.0.1
geckodriver: 0.18.0
nosetests: 1.3.7
selenium: 3.8.0
When running the tests, which mostly succeed, I see in the geckodriver.log output messages like
(firefox:55): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
My questions:
What does this message mean?
Could that be an indication of the reason why sometimes the tests are failing?
If so, how to fix it?
The error you are seeing is :
(firefox:55): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
So it is clear Firefox attempts to connect to D-BUS daemon and fails as dbus-launch gets terminated abnormally.
dbus-launch
dbus-launch is basically the utility to start a message bus by firefox through a shell script. It would normally be called from a user's login scripts. dbus-launch launches a session bus instance and print the address and pid of that instance to standard output.
You can read more about dbus-launch from the Linux man page
Root Cause
This error can arise if you use su (root), sudo, suedit, gksu. The main reason is DBUS_SESSION_BUS_ADDRESS retains its value when you su instead of picking up the value in /root/.dbus/session-bus.
Here you will find a detailed discussion on GConf Error: No D-BUS daemon running?! How to reinstall or fix?.
Another possible reason may be the base Firefox Browser version may be an older version on which updates were taken to reach the current version.
Solution :
There are a couple of solutions available to address this ubuntu related issue as follows :
Before you start Firefox you have to type export $(dbus-launch)
However this may result into another error with NSS_USE_SHARED_DB. So you have to use export NSS_USE_SHARED_DB=ENABLED as well.
The most convenient way would be to put all the configuration with in .bashrc file :
export $(dbus-launch)
export NSS_USE_SHARED_DB=ENABLED
firefox &
This discussion speaks about the solution in details.
If dbus-launch is not installed on your system you have to install dbus-x11 package which contains the dbus-launch program.
An effective solution would be to uninstall the older base version of Firefox Browser and install a recent released GA version of Firefox Browser.
Best Approach
The issue with dbus-launch was addressed properly by both Ubuntu and Mozila. To overcome this error you need to follow the below mentioned steps :
Keep your Ubuntu os updated with the Latest Patch Releases and updates.
Always use the latest released version of Selenium-Python client, WebDriver variant e.g. GeckoDriver and Web Browser, e.g. Firefox Browser.
Clean and Build the Project Workspace afresh through your IDE before and after executing your Test Suite.
Clear the Browser Cache before and after the execution of your Tests.
If you have to uninstall any of the Web Client variants (e.g. Mozilla Firefox) you can use Revo Uninstallar with Moderate Memory Scan so that the stale registry settings are discarded.
Use CCleaner tool regularly to wipe away the OS chores including the stale rust_mozprofile directories.
What does this message mean?
DBus is a message bus system for interprocess commutation. There is an open geckodriver issue on a similar if not the same subject:
request to geckodriver fails with no meaningful log entry when there is no access to $HOME/.mozilla or $HOME/.cache
Could that be an indication of the reason why sometimes the tests are failing?
The warning should not really affect the tests but it's difficult to speculate about your intermittent test failures without seeing what is actually happening in your tests.
If so, how to fix it?
Here are some things to try:
upgrade geckodriver to the latest stable version (currently 0.19.1)
update Firefox to the latest nightly version (currently 58)
try this answer
try this answer
For me the solution was to install dbus-x11
apt install dbus-x11

ADF pipelines not able to run on self hosted integration runtime

We have Azure Data Factory V2 pipeline, consuming data from on-prem SQL Server, Pipelines was running perfectly fine until 2 weeks. 2 weeks back it started running very slow (15min vs 2h:15min).
So today we tried to restart the machine which installed IR. After that pipeline started giving an error:
Unable to load DLL 'jvm.dll': The specified module could not be found.
We have verify everything mentioned in post.
Then we have reinstalled the Integration Runtime on the machine and now pipelines keep running without transferring data. All the pipelines lies in the queue. There is no activity we can see on IR Monitor. Pipelines are not sending any request to IR.
Sharing the answer as per the comment by the original poster:
Able to resolve the issue by reinstalling JRE and integration runtime.
Try a clean install. Uninstall the IR and the JRE, then install JRE, then IR.

Apache, catalina keeps saying stackoverflow

Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2104)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2048)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1994)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1964)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1917)
...
I am new to the Spring framework.
Here is the error message. Sometimes it can run while after stopping the project and re-run it, these messages are shown (but if I leave the IDE along for 5-10 mins, it can be run without errors).
What exactly is happening here? I am using the newest IDEA and Tomcat 8.
Solved. The reason is I was using a different version of Tomcat, version 8, while somehow the code is using version 7.
I am using macOS Mojave. On Windows, the code can be run via different versions, however, it seems that on macOS the version matters.

Managing selenium grids/nodes

Currently we are running the selenium grid on a Windows 7 vm and we have about 10 other win 7 vms for the nodes. We periodically run into some problems where the node stops working and just needs to be restarted. We also would like a periodic restart. I am curious how others are managing/ monitoring the nodes to see when something fails. Not sure if there is a way to monitor with something like Nagios?
I thought for restarting that I could try to build the node jar as a reservice and just have a schedule to reboot it once a month. Thoughts? Do I need to elaborate some more? Thanks
You can try selenium-grid-extras. Its been open sourced by groupon, I believe. From their git hub page:
This project is designed to help you manage your Selenium Grid installation by giving you control over the Grid Hub machine and Grid Node machine. This is very useful in cases when Internet Explorer Driver crashes, and you need to kill the iedriver.exe so that next test can start and not fail.
Link to the page - https://github.com/groupon/Selenium-Grid-Extras

Error while using jprofiler for profiling remote weblogic server

Hi I am new to jprofiler . My task is to profile a remote weblogic server for which i have followed the steps for remote profiling and came till sh file creation which the jprofiler creates itself. As i have read I need to start my weblogic server with this sh file .
But i am stuck up with the following error.
:Error occured during initialisation of VM could not find agent library in the absolute path ......./linuxX64/libjprofilerti.so
I can see the file in path mentioned in the error. Help needed quickly .
Thanks in advance,
Raghu dev
Likely, you're profiling a 32-bit JVM, not a 64-bit JVM. Repeat the integration wizard and deselect the "64-bit JVM" check box on the "Profiled JVM" step. Then it should work.
uncheck the 64-bit vm option in jprofiler while creating the profiling settings. this should solve the issue