Azure / Azure/Azure-Spring-Apps
Starting application fails during initialization of boot layer with java.nio.file.AccessDeniedException: /jca/lib
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 9
- Forks
- 11
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
**Describe the bug**
We can no longer start our Spring Boot applications deployed to Azure Spring Apps. The apps fail to start with 'Exit code 1'. The console output from the application has:
_Error occurred during initialization of boot layer
java.lang.module.FindException: java.nio.file.AccessDeniedException: /jca/lib_
What I noticed is if we disable loading a Certificate into the trust store (attached screenshot), the application will start. However, we need the Certificate loaded into the trust store so our applications can access resources utilizing the Certificate so this option isn't a viable solution.
We first ran into the error on 11/8/2023 around 2pm EST. We have multiple applications running in Azure Spring. However, we're very afraid that if we restart them, they will fail with this error because we load the same Certificate into the trust store of each application. It appears that something has changed within Azure (Azure Spring or Azure Key Vault) as we haven't changed anything with our applications for a few weeks.
**To Reproduce**
Steps to reproduce the behavior:
1. Create a Spring Boot application deployment in Azure Spring which relies on a Certificate in the trust store
2. Add the Certificate to the application and check 'Load into trust store'
3. Start the Spring Boot application deployment
4. Start should fail with exit code 1
**Expected behavior**
Application starts successfully
**Screenshots**

**Can we contact you for additional details?** Y/N
Y
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Aucun fichier du dépôt ni aucun test n’est mentionné. Commencez par reproduire le déploiement dans Azure Spring Apps avec un certificat configuré pour être chargé dans le magasin de confiance, puis examinez la sortie de la console d’initialisation à la recherche de l’AccessDeniedException sur /jca/lib. C’est terminé lorsque l’application démarre correctement tandis que le certificat reste chargé dans le magasin de confiance.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- azure, java, spring-boot
- Domaine
- cloud, security
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100