You can no longer deploy a WAR which contains Vaadin 7.2 to JBoss EAP-6.0.0

[vaadin-bot]

Originally by nelsond6

---

When deploying a WAR that contains Vaadin 7.2 to JBoss, JBoss chokes on the deploy complaining about a logging.properties file being invalid in one of the Vaadin jar files. The logging.properties file which is causing the hang up is in the vaadin-sass-compiler-0.9.2.jar file.

A workaround to this problem is to configure the JBoss system property "org.jboss.as.logging.per-deployment" to false. But this might not be an option for everyone.

I am attaching my JBoss deployment logs.

---

Imported from https://dev.vaadin.com/ issue #14000

[vaadin-bot]

Originally by nelsond6

---

Attachment added: jboss-log.txt (4.5 KiB)

[vaadin-bot]

Originally by proaccountapp

---

Updated prioritization date.

[vaadin-bot]

Originally by mgrankvi

---

Could check your logging.properties file and look compare it with the problem that is discussed on the thread https://community.jboss.org/thread/221915

If this doesn't work could you verify that the problem exists also on JBoss EAP 6.1.0 or 6.2.0[[BR]] If it does could you add a small sample project that recreates the problem.

[vaadin-bot]

Originally by nelsond6

---

I tested again with these default installations of Jboss: EAP 6.0.0, 6.1.0, 6.2.0 and Wildfly 8.1.0. The deploy only fails on Jboss EAP 6.0.0. It is successful on the rest. I compared the Jboss logging.properties between 6.0 and 6.1 and they are different, but I am not sure what fixes the issue in the later releases. I looked at the link that you posted and in EAP 6.0, the default logging.properties file is using the recommended PatternMatcher class and not the SimpleFormatter.

For now, I am fine with the workaround that I suggested in the ticket as that works for us and we do plan on updating to a more recent Jboss EAP release in the near future. But you guys might want to keep in mind that peeps using the default EAP 6.0 installation will not be able to deploy a Vaadin application.

[vaadin-bot]

Originally by proaccountapp

---

Removed prioritization date.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[stale[bot]]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!