transaction-manager | Angular 2 Maven Spring WebApp | Build Tool library

I am assuming you are using Tomcat server. In your applicationContext.xml, it is trying to lookup a JNDI DataSource provided by the container.

You need to declare the JNDI resource in tomcat's server.xml something like below. Provide db related configuration like url, username, password, driver class etc.

In spring-security.xml you have the following lines:

I suggest a read of the schema that defines the tx namespace. It states explicitly what is possible and what it does.

From said spring-tx.xsd

Creates a default JtaTransactionManager bean with name "transactionManager", matching the default bean name expected by the "annotation-driven" tag. Automatically detects WebLogic and WebSphere: creating a WebLogicJtaTransactionManager or WebSphereUowTransactionManager, respectively.

As expected the name will be transactionManager and there is no way to change that as there are no attributes or further configuration on that element.

I suppose problem may be with the namespaces starting with https vs http. Try to use following namespace declarations in root element:

The throttle-limit="3" that you've set on the step is for the threads that will run your step. For your use case, you should be looking for a way to configure the TaskExecutor that is used by the JobLauncher to limit the number of concurrent jobs.

You can for example configure the JobLauncher with a ThreadPoolTaskExecutor on which you set the queueCapacity to 3. With this configuration, if you submit more than 3 jobs at a time, the 4th submitted job will fail and you can show the error in your UI.

For the monitoring part, you can inspect the executor's queue size as described in Spring framework monitoring ThreadPoolTaskExecutor queue size

I found a similar problem described here

Please try to run under Java 8. The problem comes that you use Java 11.

Most of the frameworks are not compatible and are not fully tested on Java 11.

Without knowing anything about the version of your MySQL installation, i think it is a version 8 installation. The one DB that is working is probably an older installation, where a different authentication mechanism is used.

The issue has been discussed before here: How to resolve Unable to load authentication plugin 'caching_sha2_password' issue

Best thing should be to update your connector i think: https://dev.mysql.com/downloads/connector/j/

Otherwise you could check the manual on how to alter the identification to allow mysql_native_password: https://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html

What helped me in the end was the following post: https://medium.com/@james.tran/how-to-deploy-spring-boot-2-x-apps-on-websphere-8-5-5-d0b2e257f606

Specifically, the following step:

In the administrative console, click Applications > Application Types > WebSphere enterprise applications > application_name > Manage modules > webmodule_name.

Select Classes loaded with local class loader first (parent last) from the drop down list.

I had already done this elsewhere in the console, but not here.

Additionally, I tried the following:

https://www.ibm.com/support/pages/apar/PM26361

1. Open the administrative console.
2. Select Servers -> Server Types -> WebSphere application servers.
3. Select the server you want to configure.
4. In the Server Infrastructure area, select Java and Process Management -> Process definition.
5. In the Server Infrastructure area, select Process Definition.
6. In the Additional Properties area, select Java Virtual Machine.
7. In the Additional Properties area, select Custom Properties.
8. Select the New box.
9. In the Name entry field, type: com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProcess ing
10. In the Value entry field, type the names of the applications to be excluded from JPA processing. If there are multiple appli[c]ations separate each with the ":" character. If you wish to specify all applications simply type the "*" character.
11. Select OK.
12. Restart the server.

I don't know which steps helped - I'll try and narrow it down and report back if I get a chance.

First of all, the dynamic project is created in a wrong way.

I have used tomcat 8.5.57 version for my testing with JDK 8.

I was facing this issue while deploying the project on tomcat :