2025-04-08
2025-04-02
"Fixed" (workaround) - Cannot sign into Minecraft -“Too many requests”
Instead of login by using "Login" button.
I able to login, by click on the "Profile" button
2025-03-27
SVN with eclipse Version: 2025-03 (4.35.0) Build id: 20250306-0812
With reference:
2025-01-22
Eclipse version 2023 working with maven jdk 21 project
Googled: eclipse version 2023 maven jdk 21
Search Labs | AI Overview
Key points:
- Eclipse version: 2023-12
- Java version (JDK): 21
- Maven integration: Eclipse comes pre-loaded with the "M2E" plugin for Maven integration.
2024-12-09
SoupUi save file from API POST call
soupui post api download file
https://www.soapui.org/getting-started/working-with-soapui/saving-responses/
https://community.smartbear.com/discussions/readyapi-questions/resdump-file-option-for-request-properties-is-not-editable/39116
2024-11-20
haproxy-3.0.6 failed to chroot, explained by Gemini Code Assist
haproxy-2.6.6 was able to run with user root
but haproxy-3.0.6 hit error:
haproxy[384105]: [ALERT] (384105) : [/usr/local/sbin/haproxy.main()] Cannot chroot(/opt/haproxy/chroot).
The fact that HAProxy 2.6.6 ran as root while HAProxy 3.0.6 fails with a chroot error when run as root indicates a key difference: HAProxy 2.6.6 was not actually using chroot, even if the directive was present in the configuration file. Running as root bypasses the chroot setup because root has access to the entire filesystem. The chroot directive was effectively being ignored.
With HAProxy 3.0.6, the chroot is being correctly enforced. Since the chroot environment (/opt/haproxy/chroot) is likely missing the necessary files for HAProxy to run (its binary, libraries, configuration, etc.), it fails to start.
Here's what to do:
Confirm
chrootnecessity: Do you actually needchroot? If not, remove thechroot /opt/haproxy/chrootline from your/etc/haproxy/haproxy.cfg. This is often the simplest and best solution.If
chrootis required:- Populate the
chrootenvironment: Copy the necessary files into/opt/haproxy/chroot. This includes the HAProxy binary, required libraries (useldd /usr/local/sbin/haproxyto find them), yourhaproxy.cfgfile, and any other files HAProxy needs (e.g., certificates). Remember, the paths inside thechrootmust match the paths HAProxy expects. So, if a library is normally in/lib64/, it needs to be in/opt/haproxy/chroot/lib64/. - Permissions: Even as root, ensure the files within
/opt/haproxy/chroothave the correct permissions for the user HAProxy runs as within thechroot.
- Populate the
Alternatives: Consider alternatives to
chroot, such as Docker or systemd's isolation features, which are easier to manage and often provide better security.
The key takeaway: your HAProxy 2.6.6 was likely not using chroot at all, even if the directive was present in the configuration. The root user bypassed the chroot restriction. Now, with 3.0.6, the chroot is being enforced, hence the error. Either populate the chroot or, better yet, remove the chroot directive if it's not essential.
2024-10-29
Spring Boot 2 to 3
JPA
with @MappedSuperclass
Fixed by
by package:
2024-10-18
Maven build script JDK version error
Issue:
Resolved by configured to Execution Environment.
Maven structure - year '22
https://stackoverflow.com/questions/73652655/microservices-and-maven-structure
2024-10-15
Eclipse Version: 2024-09 (4.33.0) - Downloading external resources is disabled
Downloading external resources is disabled. pom.xml /your-project line 3 Language Servers
2024-10-09
Backup WiFi
Processes/Files that locking USB external HDD to be ejected and safely removed from laptop.
2024-10-04
Eclipse Java Maven Project doesn't download Maven Dependencies
Run As > Maven Install
2024-07-29
2024-07-25
Java - Error: Unable to access jarfile
Error: Unable to access jarfile
2024-07-24
Spring Boot build install failed with error: Unable to find a single main class from the following candidates.
Caused by: java.lang.IllegalStateException: Unable to find a single main class from the following candidates
For my case, resolved by Maven clean goal.
2024-07-22
2024-07-03
Logrotate failed because parent directory has insecure permissions (It's world writable or writable by group which is not "root")
Error:
error: skipping "output.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Googled: Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
/var/log/tomcat5/base/*.txt {
su tomcat tomcat
notifempty
copytruncate
weekly
rotate 52
compress
missingok
}
/var/log/tomcat5/base/catalina.out {
su tomcat tomcat
notifempty
copytruncate
weekly
rotate 52
compress
missingok
}
2024-07-02
jaxb2-maven-plugin 2.5.0 package javax.xml.bind.annotation does not exist
Not working
<!--
[ERROR]
.../generated/AcademicTitleCode.java:[11,33]
package javax.xml.bind.annotation does not exist
-->
<dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<!--
<version>4.0.0</version>
-->
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<!--
<version>4.0.0</version>
<scope>runtime</scope>
-->
</dependency>
<!--
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>4.0.0</version>
</dependency>
-->
Resolved by:
<!--
https://github.com/FasterXML/jackson-modules-base/discussions/239
-->
<!-- https://mvnrepository.com/artifact/javax.xml.bind/jaxb-api -->
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.1</version>
</dependency>
2024-06-21
Java Adoptium - JDK & JRE
https://github.com/microsoft/winget-pkgs/issues/67708
The EclipseAdoptium.Temurin packages are currently split as two separate packages: EclipseAdoptium.Temurin and EclipseAdoptium.TemurinJRE. I feel like it would be beneficial if, for clarity, the packages matched more like the ojdkbuild packages on here. (Shown below)