[Red Hat JIRA] (WFLY-14434) Heap usage continuously growing and exhausting available heap memory in production
by Manas Panda (Jira)
[ https://issues.redhat.com/browse/WFLY-14434?page=com.atlassian.jira.plugi... ]
Manas Panda commented on WFLY-14434:
------------------------------------
We have not tried with 22.0.1 though our product release is done with 18.0.1. Again if we are going to upgrade wildfly then we need to wait for a new mass release which will take another couple of months and customer will be in trouble for their production dead line.
So requesting you if any work around patch available then we can test on that and will plan for 22.0.1 in later.
> Heap usage continuously growing and exhausting available heap memory in production
> ----------------------------------------------------------------------------------
>
> Key: WFLY-14434
> URL: https://issues.redhat.com/browse/WFLY-14434
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Manas Panda
> Assignee: Paul Ferraro
> Priority: Major
> Attachments: Heap_Size_keeps_increasing.jpg, Heap_dump_analysis_1.jpg
>
>
> # Problem description:
> Critical issue of heap usage continuously growing and exhausting available heap memory in production. As you can see in below heap dump org.infinispan.container.impl.DefaultDataContainer is growing as the time passes and not garbage collected by GC. This increase in heap happening after upgrading from Wildfly 10.1 to Wildfly 18.0.1. There is no change in JDK in both cases ( Wildfly 10.1 and Wildfly 18.0.1).
> 2. Web application environment
> * OS: RHEL 7.5
> * Wildfly 18.0.1
> * JDK 1.8
> * Wildfly is being run in cluster mode
> * Integrated with Keycloak 3.4.3 for SSO ( SAML)
> * Enabled Wildfly clustering mode
> * G1GC garbage collector used. And 20gigs of heap allocated ( -Xmx)
> * Environment of Web App on Wildfly 10.1 is same ( except Wildfly 18) with same hardware
> * Web application uses Spring web framework and security
> 3. Heap dump analysis
> * We have few web users logging in and every second and external application consuming few API’s exposed by same application.
> * As you can see infinispan.container.impl.DefaultDataContainer Has already grown 14gigs.
> * Please note that web application does not use infinispan directly.
> * The heap does not grow in wildfly 10.1 and its normal ( garbage gets collected and size gets reduced after GC)
> Please find the snapshot as attached.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6032) Class name conflict by class "D" in exec-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6032?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-6032:
--------------------------------------
Description:
If you use a fact class named "D", you will hit errors during executable-model code generation.
{code:java}
@Test
public void testClassNameConflict() {
String str =
"import " + D.class.getCanonicalName() + ";" +
"rule R when\n" +
" D(name == \"John\")\n" +
"then\n" +
"end";
KieSession ksession = getKieSession( str );
D fact = new D("John");
ksession.insert( fact );
assertEquals(1, ksession.fireAllRules());
}
public static class D {
private String name;
public D(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
{code}
{noformat}
[ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
package defaultpkg;
import org.drools.modelcompiler.dsl.pattern.D;
import org.drools.model.Index.ConstraintType;
import org.drools.modelcompiler.CompilerTest.D;
...
{noformat}
was:
If you use a fact class named "D", you will hit errors while executable-model code generation.
{code:java}
@Test
public void testClassNameConflict() {
String str =
"import " + D.class.getCanonicalName() + ";" +
"rule R when\n" +
" D(name == \"John\")\n" +
"then\n" +
"end";
KieSession ksession = getKieSession( str );
D fact = new D("John");
ksession.insert( fact );
assertEquals(1, ksession.fireAllRules());
}
public static class D {
private String name;
public D(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
{code}
{noformat}
[ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
package defaultpkg;
import org.drools.modelcompiler.dsl.pattern.D;
import org.drools.model.Index.ConstraintType;
import org.drools.modelcompiler.CompilerTest.D;
...
{noformat}
> Class name conflict by class "D" in exec-model
> ----------------------------------------------
>
> Key: DROOLS-6032
> URL: https://issues.redhat.com/browse/DROOLS-6032
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.50.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> If you use a fact class named "D", you will hit errors during executable-model code generation.
> {code:java}
> @Test
> public void testClassNameConflict() {
> String str =
> "import " + D.class.getCanonicalName() + ";" +
> "rule R when\n" +
> " D(name == \"John\")\n" +
> "then\n" +
> "end";
> KieSession ksession = getKieSession( str );
> D fact = new D("John");
> ksession.insert( fact );
> assertEquals(1, ksession.fireAllRules());
> }
> public static class D {
> private String name;
> public D(String name) {
> this.name = name;
> }
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> }
> {code}
> {noformat}
> [ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
> text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
> text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
> package defaultpkg;
> import org.drools.modelcompiler.dsl.pattern.D;
> import org.drools.model.Index.ConstraintType;
> import org.drools.modelcompiler.CompilerTest.D;
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6032) Class name conflict by class "D" in exec-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6032?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi edited comment on DROOLS-6032 at 2/15/21 11:56 PM:
---------------------------------------------------------------------
Possible approaches to fix:
* Use FQCN for all org.drools.modelcompiler.dsl.pattern.D / org.drools.modelcompiler.CompilerTest.D occurrences instead of using import. Note: Currently generated codes switches the PATTERN/FLOW "D" class by the import.
Or
* Use FQCN for all fact Classes instead of using import
was (Author: tkobayashi):
Possible approaches to fix:
* Use FQCN for all org.drools.modelcompiler.dsl.pattern.D / org.drools.modelcompiler.CompilerTest.D occurrences instead of using import
* Note: Currently generated codes switches the PATTERN/FLOW "D" class by the import.
Or
* Use FQCN for all fact Classes instead of using import
> Class name conflict by class "D" in exec-model
> ----------------------------------------------
>
> Key: DROOLS-6032
> URL: https://issues.redhat.com/browse/DROOLS-6032
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.50.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> If you use a fact class named "D", you will hit errors while executable-model code generation.
> {code:java}
> @Test
> public void testClassNameConflict() {
> String str =
> "import " + D.class.getCanonicalName() + ";" +
> "rule R when\n" +
> " D(name == \"John\")\n" +
> "then\n" +
> "end";
> KieSession ksession = getKieSession( str );
> D fact = new D("John");
> ksession.insert( fact );
> assertEquals(1, ksession.fireAllRules());
> }
> public static class D {
> private String name;
> public D(String name) {
> this.name = name;
> }
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> }
> {code}
> {noformat}
> [ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
> text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
> text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
> package defaultpkg;
> import org.drools.modelcompiler.dsl.pattern.D;
> import org.drools.model.Index.ConstraintType;
> import org.drools.modelcompiler.CompilerTest.D;
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6032) Class name conflict by class "D" in exec-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6032?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi commented on DROOLS-6032:
-------------------------------------------
Possible approaches to fix:
* Use FQCN for all org.drools.modelcompiler.dsl.pattern.D / org.drools.modelcompiler.CompilerTest.D occurrences instead of using import
* Note: Currently generated codes switches the PATTERN/FLOW "D" class by the import.
Or
* Use FQCN for all fact Classes instead of using import
> Class name conflict by class "D" in exec-model
> ----------------------------------------------
>
> Key: DROOLS-6032
> URL: https://issues.redhat.com/browse/DROOLS-6032
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.50.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> If you use a fact class named "D", you will hit errors while executable-model code generation.
> {code:java}
> @Test
> public void testClassNameConflict() {
> String str =
> "import " + D.class.getCanonicalName() + ";" +
> "rule R when\n" +
> " D(name == \"John\")\n" +
> "then\n" +
> "end";
> KieSession ksession = getKieSession( str );
> D fact = new D("John");
> ksession.insert( fact );
> assertEquals(1, ksession.fireAllRules());
> }
> public static class D {
> private String name;
> public D(String name) {
> this.name = name;
> }
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> }
> {code}
> {noformat}
> [ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
> text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
> text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
> package defaultpkg;
> import org.drools.modelcompiler.dsl.pattern.D;
> import org.drools.model.Index.ConstraintType;
> import org.drools.modelcompiler.CompilerTest.D;
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6032) Class name conflict by class "D" in exec-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6032?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-6032:
--------------------------------------
Description:
If you use a fact class named "D", you will hit errors while executable-model code generation.
{code:java}
@Test
public void testClassNameConflict() {
String str =
"import " + D.class.getCanonicalName() + ";" +
"rule R when\n" +
" D(name == \"John\")\n" +
"then\n" +
"end";
KieSession ksession = getKieSession( str );
D fact = new D("John");
ksession.insert( fact );
assertEquals(1, ksession.fireAllRules());
}
public static class D {
private String name;
public D(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
{code}
{noformat}
[ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
package defaultpkg;
import org.drools.modelcompiler.dsl.pattern.D;
import org.drools.model.Index.ConstraintType;
import org.drools.modelcompiler.CompilerTest.D;
...
{noformat}
was:
If you use a fact class named "D", you will hit errors while executable-model code generation.
{code:java}
@Test
public void testClassNameConflict() {
String str =
"import " + D.class.getCanonicalName() + ";" +
"rule R when\n" +
" D(name == \"John\")\n" +
"then\n" +
"end";
KieSession ksession = getKieSession( str );
D fact = new D("John");
ksession.insert( fact );
assertEquals(1, ksession.fireAllRules());
}
public static class D {
private String name;
public D(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
{code}
> Class name conflict by class "D" in exec-model
> ----------------------------------------------
>
> Key: DROOLS-6032
> URL: https://issues.redhat.com/browse/DROOLS-6032
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.50.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> If you use a fact class named "D", you will hit errors while executable-model code generation.
> {code:java}
> @Test
> public void testClassNameConflict() {
> String str =
> "import " + D.class.getCanonicalName() + ";" +
> "rule R when\n" +
> " D(name == \"John\")\n" +
> "then\n" +
> "end";
> KieSession ksession = getKieSession( str );
> D fact = new D("John");
> ksession.insert( fact );
> assertEquals(1, ksession.fireAllRules());
> }
> public static class D {
> private String name;
> public D(String name) {
> this.name = name;
> }
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> }
> {code}
> {noformat}
> [ERROR] CompilerTest.testClassNameConflict:2573->BaseModelTest.getKieSession:111->BaseModelTest.getKieSession:115->BaseModelTest.getKieContainer:119->BaseModelTest.getKieContainer:126->BaseModelTest.createKieBuilder:137->BaseModelTest.createKieBuilder:164 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=5, column=1
> text=a type with the same simple name is already defined by the single-type-import of org.drools.modelcompiler.dsl.pattern.D], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java, line=0, column=0
> text=Java source of src/main/java/defaultpkg/RulesF625E96E2F948CA04652DBAC4C6DBB79.java in error:
> package defaultpkg;
> import org.drools.modelcompiler.dsl.pattern.D;
> import org.drools.model.Index.ConstraintType;
> import org.drools.modelcompiler.CompilerTest.D;
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6032) Class name conflict by class "D" in exec-model
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-6032:
-----------------------------------------
Summary: Class name conflict by class "D" in exec-model
Key: DROOLS-6032
URL: https://issues.redhat.com/browse/DROOLS-6032
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.50.0.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
If you use a fact class named "D", you will hit errors while executable-model code generation.
{code:java}
@Test
public void testClassNameConflict() {
String str =
"import " + D.class.getCanonicalName() + ";" +
"rule R when\n" +
" D(name == \"John\")\n" +
"then\n" +
"end";
KieSession ksession = getKieSession( str );
D fact = new D("John");
ksession.insert( fact );
assertEquals(1, ksession.fireAllRules());
}
public static class D {
private String name;
public D(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14301) jandex exception when using @DataSourceDefinition and Pg driver
by hantsy bai (Jira)
[ https://issues.redhat.com/browse/WFLY-14301?page=com.atlassian.jira.plugi... ]
hantsy bai commented on WFLY-14301:
-----------------------------------
Decrease the pg driver to an early version to overcome this issue. Not sure there is an incompatible issue with jandex .
> jandex exception when using @DataSourceDefinition and Pg driver
> ---------------------------------------------------------------
>
> Key: WFLY-14301
> URL: https://issues.redhat.com/browse/WFLY-14301
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 22.0.0.Final
> Reporter: hantsy bai
> Assignee: Brian Stansberry
> Priority: Major
>
> I used `@DataSourceDeifnition` and included a postgres driver in the project dependencies, and it works well in Payara, but I encountered the deployment issue when running it on WildFly.
> The original description is posted on Stackoverflow.
> [https://stackoverflow.com/questions/65746765/datasourcedefinition-usage-o...]
>
> The full exception when deploying to WildFly.
>
> {code:java}
> 14:01:20,667 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "cargo-tracker.war" (runtime-name: "cargo-tracker.war")
> 14:01:22,027 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /D:/appsvr/wildfly-22.0.0.Final/bin/content/cargo-tracker.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:932)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:792)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:711)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:619)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.index(Indexer.java:1613)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)14:01:22,090 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/util/LruCache.class at /D:/appsvr/wildfly-22.0.0.Final/bin/content/cargo-tracker.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.updateTypeTarget(Indexer.java:847)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.updateTypeTargets(Indexer.java:630)
> at org.jboss.jandex@2.1.4.Final//org.jboss.jandex.Indexer.index(Indexer.java:1614)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)14:01:22,593 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."cargo-tracker.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."cargo-tracker.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "cargo-tracker.war"
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.msc.service.ServiceNotFoundException: service jboss.ejb.default-resource-adapter-name-service not found
> at org.jboss.msc@1.4.12.Final//org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
> at org.jboss.as.ejb3@22.0.0.Final//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:257)
> at org.jboss.as.ejb3@22.0.0.Final//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
> at org.jboss.as.ejb3@22.0.0.Final//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
> at org.jboss.as.ejb3@22.0.0.Final//org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:150)
> at org.jboss.as.ejb3@22.0.0.Final//org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.deploy(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:82)
> at org.jboss.as.server@14.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
> ... 8 more14:01:22,593 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "cargo-tracker.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cargo-tracker.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"cargo-tracker.war\"
> Caused by: org.jboss.msc.service.ServiceNotFoundException: service jboss.ejb.default-resource-adapter-name-service not found"}}
> 14:01:22,593 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "cargo-tracker.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cargo-tracker.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"cargo-tracker.war\"
> Caused by: org.jboss.msc.service.ServiceNotFoundException: service jboss.ejb.default-resource-adapter-name-service not found"}}
> 14:01:22,718 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment cargo-tracker.war (runtime-name: cargo-tracker.war) in 118ms
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14440) Add tests to ejb3 subsystem for attributes that allow expression
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-14440?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-14440:
------------------------------
Description:
Need to add tests to verify all ejb3 subsystem attributes that allow expression.
See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
The following attributes allow expression in its value:
statistics-enabled
enable-statistics (deprecated)
log-system-exceptions
in-vm-remote-interface-invocation-pass-by-value
enable-graceful-txn-shutdown
disable-default-ejb-permissions (deprecated)
default-stateful-bean-session-timeout
default-stateful-bean-access-timeout
default-slsb-instance-pool
default-singleton-bean-access-timeout
default-sfsb-passivation-disabled-cache
default-sfsb-cache
default-security-domain
default-resource-adapter-name
default-missing-method-permissions-deny-access
default-mdb-instance-pool
default-entity-bean-optimistic-locking
default-entity-bean-instance-pool
default-distinct-name
default-clustered-sfsb-cache (deprecated)
allow-ejb-name-regex
cache/passivation-store
mdb-delivery-group/active
passivation-store/bean-cache
passivation-store/cache-container
passivation-store/max-size
remoting-profile/exclude-local-receiver
remoting-profile/local-receiver-pass-by-value
remoting-profile/remote-http-connection/uri
remoting-profile/remoting-ejb-receiver/connect-timeout
remoting-profile/remoting-ejb-receiver/outbound-connection-ref
remoting-profile/remoting-ejb-receiver/channel-creation-options/value
service/async/thread-pool-name
service/iiop/enable-by-default
service/iiop/use-qualified-name
service/remote/cluster
service/remote/execute-in-worker
service/remote/thread-pool-name
service/remote/channel-creation-options/value
service/timer-service/database-data-store/allow-execution
service/timer-service/database-data-store/database
service/timer-service/database-data-store/datasource-jndi-name
service/timer-service/database-data-store/partition
service/timer-service/database-data-store/refresh-interval
service/timer-service/file-data-store/path
strict-max-bean-instance-pool/derive-size
strict-max-bean-instance-pool/max-pool-size
strict-max-bean-instance-pool/timeout
strict-max-bean-instance-pool/timeout-unit
thread-pool/core-threads
thread-pool/max-threads
was:
Need to add tests to verify all ejb3 subsystem attributes that allow expression.
See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
statistics-enabled
enable-statistics (deprecated)
log-system-exceptions
in-vm-remote-interface-invocation-pass-by-value
enable-graceful-txn-shutdown
disable-default-ejb-permissions (deprecated)
default-stateful-bean-session-timeout
default-stateful-bean-access-timeout
default-slsb-instance-pool
default-singleton-bean-access-timeout
default-sfsb-passivation-disabled-cache
default-sfsb-cache
default-security-domain
default-resource-adapter-name
default-missing-method-permissions-deny-access
default-mdb-instance-pool
default-entity-bean-optimistic-locking
default-entity-bean-instance-pool
default-distinct-name
default-clustered-sfsb-cache (deprecated)
allow-ejb-name-regex
cache/passivation-store
mdb-delivery-group/active
passivation-store/bean-cache
passivation-store/cache-container
passivation-store/max-size
remoting-profile/exclude-local-receiver
remoting-profile/local-receiver-pass-by-value
remoting-profile/remote-http-connection/uri
remoting-profile/remoting-ejb-receiver/connect-timeout
remoting-profile/remoting-ejb-receiver/outbound-connection-ref
remoting-profile/remoting-ejb-receiver/channel-creation-options/value
service/async/thread-pool-name
service/iiop/enable-by-default
service/iiop/use-qualified-name
service/remote/cluster
service/remote/execute-in-worker
service/remote/thread-pool-name
service/remote/channel-creation-options/value
service/timer-service/database-data-store/allow-execution
service/timer-service/database-data-store/database
service/timer-service/database-data-store/datasource-jndi-name
service/timer-service/database-data-store/partition
service/timer-service/database-data-store/refresh-interval
service/timer-service/file-data-store/path
strict-max-bean-instance-pool/derive-size
strict-max-bean-instance-pool/max-pool-size
strict-max-bean-instance-pool/timeout
strict-max-bean-instance-pool/timeout-unit
thread-pool/core-threads
thread-pool/max-threads
> Add tests to ejb3 subsystem for attributes that allow expression
> ----------------------------------------------------------------
>
> Key: WFLY-14440
> URL: https://issues.redhat.com/browse/WFLY-14440
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Need to add tests to verify all ejb3 subsystem attributes that allow expression.
> See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
> The following attributes allow expression in its value:
> statistics-enabled
> enable-statistics (deprecated)
> log-system-exceptions
> in-vm-remote-interface-invocation-pass-by-value
> enable-graceful-txn-shutdown
> disable-default-ejb-permissions (deprecated)
> default-stateful-bean-session-timeout
> default-stateful-bean-access-timeout
> default-slsb-instance-pool
> default-singleton-bean-access-timeout
> default-sfsb-passivation-disabled-cache
> default-sfsb-cache
> default-security-domain
> default-resource-adapter-name
> default-missing-method-permissions-deny-access
> default-mdb-instance-pool
> default-entity-bean-optimistic-locking
> default-entity-bean-instance-pool
> default-distinct-name
> default-clustered-sfsb-cache (deprecated)
> allow-ejb-name-regex
> cache/passivation-store
> mdb-delivery-group/active
> passivation-store/bean-cache
> passivation-store/cache-container
> passivation-store/max-size
> remoting-profile/exclude-local-receiver
> remoting-profile/local-receiver-pass-by-value
> remoting-profile/remote-http-connection/uri
> remoting-profile/remoting-ejb-receiver/connect-timeout
> remoting-profile/remoting-ejb-receiver/outbound-connection-ref
> remoting-profile/remoting-ejb-receiver/channel-creation-options/value
> service/async/thread-pool-name
> service/iiop/enable-by-default
> service/iiop/use-qualified-name
> service/remote/cluster
> service/remote/execute-in-worker
> service/remote/thread-pool-name
> service/remote/channel-creation-options/value
> service/timer-service/database-data-store/allow-execution
> service/timer-service/database-data-store/database
> service/timer-service/database-data-store/datasource-jndi-name
> service/timer-service/database-data-store/partition
> service/timer-service/database-data-store/refresh-interval
> service/timer-service/file-data-store/path
> strict-max-bean-instance-pool/derive-size
> strict-max-bean-instance-pool/max-pool-size
> strict-max-bean-instance-pool/timeout
> strict-max-bean-instance-pool/timeout-unit
> thread-pool/core-threads
> thread-pool/max-threads
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14440) Add tests to ejb3 subsystem for attributes that allow expression
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-14440?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-14440:
------------------------------
Description:
Need to add tests to verify all ejb3 subsystem attributes that allow expression.
See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
statistics-enabled
enable-statistics (deprecated)
log-system-exceptions
in-vm-remote-interface-invocation-pass-by-value
enable-graceful-txn-shutdown
disable-default-ejb-permissions (deprecated)
default-stateful-bean-session-timeout
default-stateful-bean-access-timeout
default-slsb-instance-pool
default-singleton-bean-access-timeout
default-sfsb-passivation-disabled-cache
default-sfsb-cache
default-security-domain
default-resource-adapter-name
default-missing-method-permissions-deny-access
default-mdb-instance-pool
default-entity-bean-optimistic-locking
default-entity-bean-instance-pool
default-distinct-name
default-clustered-sfsb-cache (deprecated)
allow-ejb-name-regex
cache/passivation-store
mdb-delivery-group/active
passivation-store/bean-cache
passivation-store/cache-container
passivation-store/max-size
remoting-profile/exclude-local-receiver
remoting-profile/local-receiver-pass-by-value
remoting-profile/remote-http-connection/uri
remoting-profile/remoting-ejb-receiver/connect-timeout
remoting-profile/remoting-ejb-receiver/outbound-connection-ref
remoting-profile/remoting-ejb-receiver/channel-creation-options/value
service/async/thread-pool-name
service/iiop/enable-by-default
service/iiop/use-qualified-name
service/remote/cluster
service/remote/execute-in-worker
service/remote/thread-pool-name
service/remote/channel-creation-options/value
service/timer-service/database-data-store/allow-execution
service/timer-service/database-data-store/database
service/timer-service/database-data-store/datasource-jndi-name
service/timer-service/database-data-store/partition
service/timer-service/database-data-store/refresh-interval
service/timer-service/file-data-store/path
strict-max-bean-instance-pool/derive-size
strict-max-bean-instance-pool/max-pool-size
strict-max-bean-instance-pool/timeout
strict-max-bean-instance-pool/timeout-unit
thread-pool/core-threads
thread-pool/max-threads
was:
Need to add tests to verify all ejb3 subsystem attributes that allow expression.
See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
> Add tests to ejb3 subsystem for attributes that allow expression
> ----------------------------------------------------------------
>
> Key: WFLY-14440
> URL: https://issues.redhat.com/browse/WFLY-14440
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Need to add tests to verify all ejb3 subsystem attributes that allow expression.
> See [WildFly Full 22 Model Reference|https://docs.wildfly.org/22/wildscribe/subsystem/ejb3/index.html] for details.
> statistics-enabled
> enable-statistics (deprecated)
> log-system-exceptions
> in-vm-remote-interface-invocation-pass-by-value
> enable-graceful-txn-shutdown
> disable-default-ejb-permissions (deprecated)
> default-stateful-bean-session-timeout
> default-stateful-bean-access-timeout
> default-slsb-instance-pool
> default-singleton-bean-access-timeout
> default-sfsb-passivation-disabled-cache
> default-sfsb-cache
> default-security-domain
> default-resource-adapter-name
> default-missing-method-permissions-deny-access
> default-mdb-instance-pool
> default-entity-bean-optimistic-locking
> default-entity-bean-instance-pool
> default-distinct-name
> default-clustered-sfsb-cache (deprecated)
> allow-ejb-name-regex
> cache/passivation-store
> mdb-delivery-group/active
> passivation-store/bean-cache
> passivation-store/cache-container
> passivation-store/max-size
> remoting-profile/exclude-local-receiver
> remoting-profile/local-receiver-pass-by-value
> remoting-profile/remote-http-connection/uri
> remoting-profile/remoting-ejb-receiver/connect-timeout
> remoting-profile/remoting-ejb-receiver/outbound-connection-ref
> remoting-profile/remoting-ejb-receiver/channel-creation-options/value
> service/async/thread-pool-name
> service/iiop/enable-by-default
> service/iiop/use-qualified-name
> service/remote/cluster
> service/remote/execute-in-worker
> service/remote/thread-pool-name
> service/remote/channel-creation-options/value
> service/timer-service/database-data-store/allow-execution
> service/timer-service/database-data-store/database
> service/timer-service/database-data-store/datasource-jndi-name
> service/timer-service/database-data-store/partition
> service/timer-service/database-data-store/refresh-interval
> service/timer-service/file-data-store/path
> strict-max-bean-instance-pool/derive-size
> strict-max-bean-instance-pool/max-pool-size
> strict-max-bean-instance-pool/timeout
> strict-max-bean-instance-pool/timeout-unit
> thread-pool/core-threads
> thread-pool/max-threads
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months