jboss-as | Please use this location for all purposes | Continuous Deployment library

It should not be created in modules/system/lasers/base. That is for components provided by the container. Having the module off the root $JBOSS_HOME/modules directory is correct.

I found that the element that was messing with the setup was the tag in the . It should either have the P6Spy driver

hadoop-azure pulls in hadoop-common, which pulls in Jersey. In the version of hadoop-azure you're using, hadoop-common is in compile . In new version, it is in provided scope. So you can just upgrade the hadoop-azure dependency to the latest one. If you need hadoop-common to compile, then you can redeclare hadoop-common and put it in provided scope.

Your code looks correct. But as the error shows "nested exception is java.lang.IllegalStateException: Client id must not be empty.", you need to check the application.properties again and make sure it's correct.

And the sample needs three dependencies(spring-boot-starter-oauth2-client, spring-boot-starter-web, azure-spring-boot-starter-active-directory), you could try to update your pom with the newer version.

There is my code following the tutorial.

Main:

The issue here was the conflict between the Hibernate jars in JBoss modules and my project. When I use the JBoss latest one(WildFly 20), the issue went away. Note that I had to copy the MySQL connector jar into WildFly deployments dir and add the following datasource to my project.

I assume that you don't have an Application class:

HornetQ 2.4.0.Final is not compatible with Java 13. You need to use Java 8.

The copyright for Pro Spring 5 is 2017 which probably means most of the book was written in 2016. Java 9 wasn't released until September 2017 and HornetQ 2.4.0.Final was released in December 2013. My point here is that if you're going to use an old book and old software you need to use a comparably old version of Java.

It's also worth noting that the HornetQ code-base was donated to the Apache ActiveMQ community in 2014 and the broker has carried on as ActiveMQ Artemis. There hasn't been a release of HornetQ in the last 7 years or so because of this. However, there are regular releases of ActiveMQ Artemis (2.13.0 was released just a few weeks ago).

The problem was due to dependency conflict, which I could exclude using the following jboss-deployment-structure.xml

I suspect you may try to set the content length in the header. IE, the size of of your request using Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. I would guess that if you correctly identified the size of the request the server might not choke on it. Worth a try.

Content-Length: SIZE OF REQUIRED DATA IN BYTES \n\n

It may require accessing some lower level portions of your request framework. References: https://tools.ietf.org/html/rfc7230#section-3.3.2 https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Length