-
Bug
-
Resolution: Done
-
Blocker
-
7.2.0.GA
-
None
-
5
-
CR1
-
-
-
-
-
-
CR2
-
https://github.com/jboss-integration/bpms-installer/pull/50, https://github.com/jboss-integration/installer-commons/pull/60, https://github.com/jboss-integration/bpms-installer/pull/51, https://github.com/jboss-integration/bpms-installer/pull/53, https://github.com/jboss-integration/installer-commons/pull/61, https://github.com/jboss-integration/bpms-installer/pull/54
-
-
2018 Week 48-50
Checking the default path with CR1 installer for JWS, I found an error message in server log:
Error when initializing server extension of type jBPM KIE Server extension
java.lang.RuntimeException: Unable to create EntityManagerFactory due to Unable to find jta data source under name java:jboss/datasources/ExampleDS
Looking at the configuration, please make following changes:
- please don't add jboss-logging as a part of the installation process. I mistakenly advised putting it there, as for community Tomcat it's needed, but JWS already contains it.
- only the "sharedDataSource" was created in the context.xml. The additional data source bringing pooling capabilities is missing
- by default, KIE Server expects the "java:jboss/datasources/ExampleDS" to exist. This JNDI won't work for JWS even if the second data source was created. I can see that in BXMSPROD-160 you proposed a name "jdbc/processServerDS". Please make it just "processServerDS" and point KIE Server to it via a system property "-Dorg.kie.server.persistence.ds=java:comp/env/processServerDS". The reason I am asking you to remove the "jdbc/" prefix is that I ran into an issue with JWS restricting the JNDI lookup to the same subtree. As a result, this data source could not look up some of its dependencies, e.g. the TransactionManager