Spring Boot Gradle Project Multi module weird bug NoSuchMethodError

I have a problem, something strange and sure someone has happened this, the case is this: I have three modules that are web services within a project Springboot with Gradle.
Modules: Commons Hr and Collab
Hr and Collab depend on Commons

Collab: http: // localhost: 8080 /collab-api/ auth / commons / motivation / category / 91ea125f-a17d-40b6-adb3-6f0de414bf36

HR: http: // localhost: 8081 /hr-api/ auth / commons / motivation / category / 91ea125f-a17d-40b6-adb3-6f0de414bf36

/ auth / commons / motivation / category / 91ea125f-a17d-40b6-adb3-6f0de414bf36

As you can see, the service in collab and in hr is just the same one they access from different modules and go through the same common service when it is run from

collab-api

But I have no problems when I turn it off

hr-api

I get an exception: java.lang.NoSuchMethodError: xxx.WsMotivationCategory. (Ljava / lang / String; Ljava / lang / String; Ljava / util / ArrayList;) V

The error only occurs when the LinkedHashSet variable attempts to add a new item to the stack.

Enter the description of the image here

Any help or suggestion will be well received, thanks Capos!

The server does not boot after editing fstab

I've added a few things fstab for my XFS partition, and I think I may have copied the entire line instead of adding it (I know I should have typed and double-checked it).

I did a reboot after editing and now I do not boot anymore. I do not have access to an issue to say why. It is currently in rescue mode with the GRML rescue system.

I have very little experience with rescue mode, so I'm not sure what to do.

Any help would be appreciated.

boot – windows does not add grub

I have Linux Mint and Windows 10 on my laptop and replace my hard drive with an SSD hard drive
Before replacing, I created an image of 3 partitions: 1- Reserved Windows partition 2- Installed Windows partition 3- Installed Linux partition. and then I restore this image partition in Linux Live on SSD and then I do with Repair Boot recommended steps, but I have only Linux in the startup phase in the Grub OS selection menu, then I execute the following command, but I have a problem:

sudo update-grub

sudo os-prober
sudo: os-prober: command not found

blkid -o list

/ dev / sda1 ntfs System Reserved (not mounted) 10CE91E6CE91C3FE
/ dev / sda2 ext4 / 96c436a1-3a18-4d1e-b774-75e681accd2d
/ dev / sda3 ntfs C / media / mohsen / C1 FCEA94CEEA948714
/ dev / sda4 ntfs / media / mohsen / 0AE389FE4A849CE3 0AE389FE4A849CE3

How can you fix this?
Thank you for your kindness

Windows – MacPro, APFS, bootcamp boot disk

Has anyone used Brigadier to get the bootcamp installer on a newer Mac and extract the bits that can be used to display APFS volumes in the boot floppy selection in the bootcamp control panel on Windows? If so, what exactly did you have to do?

Details:

End of 2012, a MacPro. It boots Mac OS X Mojave and Windows 10 twice. To run Mojave, the graphics card had to be updated. The Sapphire RX580 Pulse is recognized by Apple as a working "metal" card and seemed to be very popular, so I decided to do it. The problem is that it does not support boot screens. Not a big problem until you want to restart Windows in Mac OS X on Mojave. Since Mojave automatically converts the installation target to APFS, there is currently no way to zap the PRAM or start the recovery and change the boot disk in this way. The absence of boot screens means that no startup menu is supported when the Option key is held down.

I've been digging a lot and I understand that newer Macs using bootcamp with APFS correctly display the OS X hard drive as a boot disk in Bootcamp Control Panel on Windows. So I came to the question of whether anyone took the time to find out which drivers or what specific components in Bootcamp ESD were changed for these Macs and had APFS work properly with respect to "Restart in OS X" Bootcamp Option under Windows.

Ubuntu: How to Repair the UEFI Secure Boot – Change Pass

After running sudo dpkg --configure -a (The system prompts you to run this command.) Configuring Secure Boot reported:

UEFI Secure Boot is enabled on your system.

│ UEFI Secure Boot requires additional configuration
│ Third-party drivers.

│ The system supports you in configuring UEFI Secure Boot. Allow
│ When using third-party drivers, a new machine owner key (MOK) has been created
│ generated. This key must now be registered in the firmware of your system.

│ To make sure that this change is made by you as an authorized user,
│ and not by an attacker, you must now choose a password and then confirm
│ the change after restarting with the same password, in the two "Register
│ The MOK and Change Secure Boot State menus that you see
│ when this system restarts.
The system supports you in configuring UEFI Secure Boot. Allow
│ When using third-party drivers, a new machine owner key (MOK) has been created
│ generated. This key must now be registered in the firmware of your system.

│ To make sure that this change is made by you as an authorized user,
│ and not by an attacker, you must now choose a password and then confirm
│ the change after restarting with the same password, in the two "Register
│ The MOK and Change Secure Boot State menus that you see
│ when this system restarts.

│ If you continue but do not confirm the password on reboot, Ubuntu will do so
│ You can still boot on your system, but with the required hardware
│ Third-party drivers that work properly may not work.

I have no stitch where I can change the password. How can I fix this problem with pass? I do not have to change it with command after this message
sudo -i. passwd

Enter image description here

usb – Ubuntu 18.04.02 does not wake up after sleep (boot to usb3.0 SSD)

I start Ubuntu 18.04.02 on a USB3.0 SSD drive and have problems waking up after the suspend. After experimenting, I came to the conclusion that Ubuntu is not properly stopped on battery power, which prevents waking up (only ext4 and variable errors are read, yes, they vary each time).

At first (shortly after installation) it never woke up, then I added "usbcore.autosuspend = -1" in / etc / default / grub under "GRUB_CMDLINE_LINUX_DEFAULT" and got the following:

  • When power is turned on, Ubuntu will power up properly even if I unplug the power cord before waking up.
  • In battery mode, Ubuntu will not wake up in 90% of the time (even if I turn on the power before waking up).

I use Ubuntu 18.04.02 with kernel 4.15.48-51.

bootcamp – Installing Windows on MBP 2015 (Mojave) with boot camp, error: Not enough space!

I have a MacBook Pro 2015 with macOS Mojave.

I downloaded the Windows 10×64 update for October (and April) and tried to install both with the Boot Camp Assistant.

I have a 500 GB hard drive with 300 GB of free space. So I set the size of the Windows partition to 150 GB.

In this version of macOS there are no task steps in the bootcamp. And Boot Camp says, "Please remove any external storage devices connected to this system before proceeding."

The problem is that after these steps an error appears with this message:

The Windows support software could not be saved to the selected drive.
There was an error saving the Windows support software.

Or:

There is not enough space on the hard disk.

I tried so many solutions that I found them on forums, but I could not install Windows yet!

Thank you for your help! 🙂

spring boot – @Scheduled requires @EnableScheduling at the class level

@ Planned is used to perform tasks automatically and periodically. This label uses a support called scheduling,

Enable this support and use the annotation @ Planned We also have to add the label @EnableScheduling in our class.

Therefore, both complement each other, as one allows the support of the other

boot – Mac Blue Screen of Death

So I tried to get the bootcamp running and followed some instructions that said I should hit Alt + R at startup. This happened after I played with Bootcamp so I could try to load a Windows image onto a USB flash drive. I was able to fix the bluescreen of my PC. For some reason, when I tried to boot it, just let me boot a blue shielded version of Windows. I have not even installed Windows, but even if I hold down the Alt key while booting Mac, it will not show up as a boot option. Control alt p r does not seem to have helped either.