org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
…
Caused by: java.lang.IllegalStateException: StandardEngine[Tomcat].StandardHost[localhost].TomcatEmbeddedContext[] failed to start

Digging a bit deeper I found the real reason:

java.lang.NoClassDefFoundError: javax/annotation/PostConstruct

This can be fixed by also including javax.annotation:javax.annotation-api as a dependency. The new jakarta based library only includes jakarta.annotation.* but not javax.annotation.*. But Spring Boot still requires the old namespace to work. I didn’t dig deeper why including the dependency broke the app though it was working before without both of the dependencies.

Another great sample for how convenient this rename is and further will be.

• @Inject private BeanManager beanManager;
• private BeanManager bm = javax.enterprise.inject.spi.CDI.current().getBeanManager();

Especially the second one can be very handy if you hit a part that doesn’t support CDI already.

Enable JDBC-Spy on Datasource:

/subsystem=datasources/data-source=ExampleDS/:write-attribute(name=spy,value=true)

Or just add spy=”true” as attribute in standalone.xml.

Then you have to enable the spy by adding a loglevel:

/subsystem=logging/logger=jboss.jdbc.spy/:add(level=TRACE)

If this doesn’t output anything your loglevel is above trace. Default is INFO. So nothing is displayed.

Add the following part to your logging configuration to enable TRACE-logging for a single package:

<subsystem xmlns="urn:jboss:domain:logging:2.0">
...
<console-handler name="TRACER">
  <level name="TRACE"/>
  <formatter>
    <named-formatter name="COLOR-PATTERN"/>
  </formatter>
</console-handler>
...
<logger category="jboss.jdbc.spy" use-parent-handlers="false">
  <level name="TRACE"/>
  <handlers>
    <handler name="TRACER"/>
  </handlers>
</logger>
...
</subsystem>

I didn’t use command line for this but of course it would be possible to do so.

<settings>  
  ...  
  <profiles>  
    ...  
    <profile>  
      <id>jboss-public-repository</id>  
      <repositories>  
        <repository>  
          <id>jboss-public-repository-group</id>  
          <name>JBoss Public Maven Repository Group</name>  
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>  
          <layout>default</layout>  
          <releases>  
            <enabled>true</enabled>  
            <updatePolicy>never</updatePolicy>  
          </releases>  
          <snapshots>  
            <enabled>true</enabled>  
            <updatePolicy>never</updatePolicy>  
          </snapshots>  
        </repository>  
      </repositories>  
      <pluginRepositories>  
        <pluginRepository>  
          <id>jboss-public-repository-group</id>  
          <name>JBoss Public Maven Repository Group</name>  
          <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>  
          <layout>default</layout>  
          <releases>  
            <enabled>true</enabled>  
            <updatePolicy>never</updatePolicy>  
          </releases>  
          <snapshots>  
            <enabled>true</enabled>  
            <updatePolicy>never</updatePolicy>  
          </snapshots>  
        </pluginRepository>  
      </pluginRepositories>  
    </profile>  
  
  </profiles>  
  
  <activeProfiles>  
    <activeProfile>jboss-public-repository</activeProfile>  
  </activeProfiles>  
  ...  
</settings>

[copied from https://developer.jboss.org/wiki/MavenGettingStarted-Users, 25.02.2015]

Of course you have to activate it.

First you have to encrypt your password with org.picketbox.datasource.security.SecureIdentityLoginModule. This class includes a main method so you can run it with a single argument which has to be your plaintext password. The result will look like this:

Encoded password: 1ab234cf321cca

The class is included in jboss modules.

Then create a security-domain in your standalone.xml file:

<security-domain name="databaseSecure" cache-type="default">
  <authentication>
    <login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">
      <module-option name="username" value="username"/>
      <module-option name="password" value="1ab234cf321cca"/>
    </login-module>
  </authentication>
</security-domain>

Or with cli:

/subsystem=security/security-domain=databaseSecure:add(cache-type=default)  
/subsystem=security/security-domain=databaseSecure/authentication=classic:add(login-modules=[{"code"=>"org.picketbox.datasource.security.SecureIdentityLoginModule", "flag"=>"required", "module-options"=>[("username"=>"username"), ("password"=>"1ab234cf321cca")]}])

The last step is to replace the username+password part of your datasource with a security-domain element. This would look like this in its simplest way:

<datasource jndi-name="java:jboss/datasources/mypgDS" pool-name="MypgDS" enabled="true" use-java-context="true">
  <connection-url>jdbc:postgresql:db1</connection-url>
  <driver>postgresql</driver>
  <security>
    <security-domain>databaseSecure</security-domain>
  </security>
</datasource>

After theses changes start your application server.

ATTENTION! The passphrase that is used for the Blowfish algorithm is hardcoded in the login module. To make this secure you have to change the password in that component. Change the source and recompile or create an extension and overwrite all necessary parts and add it as a new module.

./jboss-cli.sh --connect --controller=<BindIP>:10099

<configuration>
  <jsp-configuration display-source-fragment="false"/>
</configuration>

Or with cli:

/subsystem=web/configuration=jsp-configuration:write-attribute(name=display-source-fragment, value=false)

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
  <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="-1"/>
</subsystem>

Or with cli:

/subsystem=deployment-scanner/scanner=default:write-attribute(name=scan-interval, value=-1)

<subsystem xmlns="urn:jboss:domain:web:1.5" default-virtual-server="default-host" native="false">
  <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
  <virtual-server name="default-host" enable-welcome-root="false">
    <alias name="localhost"/>
  </virtual-server>
  <configuration>
    <jsp-configuration x-powered-by="false"/>
  </configuration>
</subsystem>

Or with cli:

/subsystem=web/configuration=jsp-configuration:write-attribute(name=x-powered-by,value=false)

In a JSF application you have to add the following context param:

<context-param>
    <param-name>com.sun.faces.sendPoweredByHeader</param-name>
    <param-value>false</param-value>
</context-param>

Then start your server and the header should be gone.

<subsystem xmlns="urn:jboss:domain:logging:2.0">
  ...
  <!-- add begin -->
  <console-handler name="DEBUGCONSOLE">
    <level name="DEBUG" />
    <formatter>
      <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%F:%L)  %s%E%n" />
    </formatter>
  </console-handler>
  <logger category="pm.mbo" use-parent-handlers="false">
    <level name="DEBUG" />
    <handlers>
      <handler name="DEBUGCONSOLE" />
    </handlers>
  </logger>
  <!-- add end -->
  ...
</subsystem>

Of course you have to change the category (your package name) in the logger. The snippet is from Wildfly 8.1. But it is the same approach for JBoss AS 7+.