[Red Hat JIRA] (WFLY-13691) Ajax call causes exception: Target Unreachable, 'null' returned null
by erick leal (Jira)
[ https://issues.redhat.com/browse/WFLY-13691?page=com.atlassian.jira.plugi... ]
erick leal updated WFLY-13691:
------------------------------
Affects Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
(was: 22.0.0.Alpha1)
> Ajax call causes exception: Target Unreachable, 'null' returned null
> --------------------------------------------------------------------
>
> Key: WFLY-13691
> URL: https://issues.redhat.com/browse/WFLY-13691
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 22.0.0.Beta1
> Reporter: erick leal
> Priority: Major
> Attachments: project.zip
>
>
> I still have a problem with JSF 2.3 related to ViewParam, I tested it with WildFly 21 and the bug is still there.
> Note that Wildfly already incorporated all the fixes recently done by [@soul2zimate|https://github.com/soul2zimate]
> When you click on button the second time a exception happens, this is not the case when using mojarra 2.2, myfaces 2.2 or myfaces 2.3
> url to test: http://localhost/project-0.0.1-SNAPSHOT/test.xhtml
> XHTML:
>
> {code:java}
> <f:metadata> <f:viewParam id="id" name="id" value="#{testView.testClass.id}" /> </f:metadata> <h:form> <p:commandButton update="@form" /> <p:dataTable var="m" selectionMode="single" selection="#{testView.testClass}" rowKey="#{m.id}" value="#{testView.testClasses}"> </p:dataTable> </h:form>{code}
> beans
> {code:java}
> import java.io.Serializable; import java.util.List; import javax.annotation.PostConstruct; import javax.faces.view.ViewScoped; import javax.inject.Named; @Named @ViewScoped public class TestView implements Serializable { private TestClass testClass; private List<TestClass> testClasses; @PostConstruct public void init() { testClass = new TestClass(); } public TestClass getTestClass() { return testClass; } public void setTestClass(TestClass testClass) { this.testClass = testClass; } public List<TestClass> getTestClasses() { return testClasses; } public void setTestClasses(List<TestClass> testClasses) { this.testClasses = testClasses; } }{code}
> model
> {code:java}
> public class TestClass { Integer id; public Integer getId() { return id; } public void setId(Integer id) { this.id = id; } }{code}
> You also need to set in web.xml the following param
> {code:java}
> <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param>{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14244) Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
by Ricardo Martin Camarero (Jira)
[ https://issues.redhat.com/browse/WFLY-14244?page=com.atlassian.jira.plugi... ]
Ricardo Martin Camarero updated WFLY-14244:
-------------------------------------------
Description:
If you have defined a local repository in your maven {{settings.xml}} like the following:
{code:xml}
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<localRepository>/path/to/repository</localRepository>
...
</settings>
{code}
The folder {{ee-9/feature-path}} fails with the following error:
{noformat}
...
[INFO] --------------< org.wildfly:wildfly-preview-feature-pack >--------------
[INFO] Building WildFly: EE 9 Preview Galleon Feature Pack 22.0.0.Final-SNAPSHOT [146/162]
[INFO] --------------------------------[ pom ]---------------------------------
...
[INFO] --- wildfly-galleon-maven-plugin:5.0.0.Final:build-feature-pack (feature-pack-build) @ wildfly-preview-feature-pack ---
[INFO] EE9: transformed infinispan-hibernate-cache-v53-11.0.8.Final.jar
...
[INFO] EE9: transformed jakarta.json-api-1.1.6.jar
[INFO] EE9: transformed jakarta.json-1.1.6.jar
Forked embedded process has failed with the following error:
java.lang.IllegalStateException: WFLYEMB0022: Cannot invoke 'start' on embedded process
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:119)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:305)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
at org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
at org.jboss.as.server.ServerService.boot(ServerService.java:426)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
{noformat}
If you use the -X option the initial exception is the following:
{noformat}
ERROR: WFLYSRV0055: Caught exception during boot
org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.mail
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100)
at org.jboss.as.server.parsing.StandaloneXml_6.readServerElement(StandaloneXml_6.java:221)
at org.jboss.as.server.parsing.StandaloneXml_6.readElement(StandaloneXml_6.java:121)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:114)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
... 3 more
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/mail/Session
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:92)
... 10 more
Caused by: java.lang.NoClassDefFoundError: javax/mail/Session
at org.jboss.as.mail.extension.MailSessionDefinition.<clinit>(MailSessionDefinition.java:49)
at org.jboss.as.mail.extension.MailSubsystemParser4_0.getParserDescription(MailSubsystemParser4_0.java:39)
at org.jboss.as.controller.PersistentResourceXMLParser.cacheXMLDescription(PersistentResourceXMLParser.java:45)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.preCacheParserDescription(ExtensionRegistry.java:522)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.attemptCurrentParserInitialization(ExtensionRegistry.java:508)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.access$200(ExtensionRegistry.java:434)
at org.jboss.as.controller.extension.ExtensionRegistry.initializeParsers(ExtensionRegistry.java:249)
at org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:116)
at org.jboss.as.controller.parsing.DeferredExtensionContext.access$000(DeferredExtensionContext.java:44)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:74)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.lang.ClassNotFoundException: javax.mail.Session from [Module "org.jboss.as.mail" version 22.0.0.Final-SNAPSHOT from local module loader @3cb1ffe6 (finder: local module finder @3dfc5fb8 (roots: /home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules,/home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules/system/layers/base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
... 18 more
{noformat}
The feature spec generator fails because the server prefers the local repository in your settings than the one in the system property (jboss-modules does it). The artifact was located from the local repo in the settings, and it was not the ee9 jar. The ee9 folder is forced by the galleon plugin using a system prop but it was not used because of my {{settings.xml}}.
was:
If you have defined a local repository in your maven {{settings.xml}} like the following:
{code:xml}
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<localRepository>/path/to/repository</localRepository>
...
</settings>
{code}
The folder {{ee-9/feature-path}} fails with the following error:
{noformat}
...
[INFO] --------------< org.wildfly:wildfly-preview-feature-pack >--------------
[INFO] Building WildFly: EE 9 Preview Galleon Feature Pack 22.0.0.Final-SNAPSHOT [146/162]
[INFO] --------------------------------[ pom ]---------------------------------
...
[INFO] --- wildfly-galleon-maven-plugin:5.0.0.Final:build-feature-pack (feature-pack-build) @ wildfly-preview-feature-pack ---
[INFO] EE9: transformed infinispan-hibernate-cache-v53-11.0.8.Final.jar
...
[INFO] EE9: transformed jakarta.json-api-1.1.6.jar
[INFO] EE9: transformed jakarta.json-1.1.6.jar
Forked embedded process has failed with the following error:
java.lang.IllegalStateException: WFLYEMB0022: Cannot invoke 'start' on embedded process
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:119)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:305)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
at org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
at org.jboss.as.server.ServerService.boot(ServerService.java:426)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
{noformat}
If you use the -X option the initial exception is the following:
{noformat}
ERROR: WFLYSRV0055: Caught exception during boot
org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.mail
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100)
at org.jboss.as.server.parsing.StandaloneXml_6.readServerElement(StandaloneXml_6.java:221)
at org.jboss.as.server.parsing.StandaloneXml_6.readElement(StandaloneXml_6.java:121)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:114)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
... 3 more
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/mail/Session
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:92)
... 10 more
Caused by: java.lang.NoClassDefFoundError: javax/mail/Session
at org.jboss.as.mail.extension.MailSessionDefinition.<clinit>(MailSessionDefinition.java:49)
at org.jboss.as.mail.extension.MailSubsystemParser4_0.getParserDescription(MailSubsystemParser4_0.java:39)
at org.jboss.as.controller.PersistentResourceXMLParser.cacheXMLDescription(PersistentResourceXMLParser.java:45)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.preCacheParserDescription(ExtensionRegistry.java:522)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.attemptCurrentParserInitialization(ExtensionRegistry.java:508)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.access$200(ExtensionRegistry.java:434)
at org.jboss.as.controller.extension.ExtensionRegistry.initializeParsers(ExtensionRegistry.java:249)
at org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:116)
at org.jboss.as.controller.parsing.DeferredExtensionContext.access$000(DeferredExtensionContext.java:44)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:74)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.lang.ClassNotFoundException: javax.mail.Session from [Module "org.jboss.as.mail" version 22.0.0.Final-SNAPSHOT from local module loader @3cb1ffe6 (finder: local module finder @3dfc5fb8 (roots: /home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules,/home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules/system/layers/base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
... 18 more
{noformat}
The feature spec generator fails because the server prefers the local repository in your settings than the one in the system property (jboss-modules does it). The artifact was located from the local repo in the settings, and it was not the ee9 jar. The ee9 folder is forced by the galleon plugin using a system prop but it was not used vecause of my {{settings.xml}}.
> Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
> ------------------------------------------------------------------------------------
>
> Key: WFLY-14244
> URL: https://issues.redhat.com/browse/WFLY-14244
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Ricardo Martin Camarero
> Priority: Major
>
> If you have defined a local repository in your maven {{settings.xml}} like the following:
> {code:xml}
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
> <localRepository>/path/to/repository</localRepository>
> ...
> </settings>
> {code}
> The folder {{ee-9/feature-path}} fails with the following error:
> {noformat}
> ...
> [INFO] --------------< org.wildfly:wildfly-preview-feature-pack >--------------
> [INFO] Building WildFly: EE 9 Preview Galleon Feature Pack 22.0.0.Final-SNAPSHOT [146/162]
> [INFO] --------------------------------[ pom ]---------------------------------
> ...
> [INFO] --- wildfly-galleon-maven-plugin:5.0.0.Final:build-feature-pack (feature-pack-build) @ wildfly-preview-feature-pack ---
> [INFO] EE9: transformed infinispan-hibernate-cache-v53-11.0.8.Final.jar
> ...
> [INFO] EE9: transformed jakarta.json-api-1.1.6.jar
> [INFO] EE9: transformed jakarta.json-1.1.6.jar
> Forked embedded process has failed with the following error:
> java.lang.IllegalStateException: WFLYEMB0022: Cannot invoke 'start' on embedded process
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:119)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
> at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
> at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:305)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> at org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
> at org.jboss.as.server.ServerService.boot(ServerService.java:426)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> If you use the -X option the initial exception is the following:
> {noformat}
> ERROR: WFLYSRV0055: Caught exception during boot
> org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:395)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.mail
> at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100)
> at org.jboss.as.server.parsing.StandaloneXml_6.readServerElement(StandaloneXml_6.java:221)
> at org.jboss.as.server.parsing.StandaloneXml_6.readElement(StandaloneXml_6.java:121)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:114)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
> ... 3 more
> Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/mail/Session
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:92)
> ... 10 more
> Caused by: java.lang.NoClassDefFoundError: javax/mail/Session
> at org.jboss.as.mail.extension.MailSessionDefinition.<clinit>(MailSessionDefinition.java:49)
> at org.jboss.as.mail.extension.MailSubsystemParser4_0.getParserDescription(MailSubsystemParser4_0.java:39)
> at org.jboss.as.controller.PersistentResourceXMLParser.cacheXMLDescription(PersistentResourceXMLParser.java:45)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.preCacheParserDescription(ExtensionRegistry.java:522)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.attemptCurrentParserInitialization(ExtensionRegistry.java:508)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.access$200(ExtensionRegistry.java:434)
> at org.jboss.as.controller.extension.ExtensionRegistry.initializeParsers(ExtensionRegistry.java:249)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:116)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.access$000(DeferredExtensionContext.java:44)
> at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:74)
> at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:71)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> Caused by: java.lang.ClassNotFoundException: javax.mail.Session from [Module "org.jboss.as.mail" version 22.0.0.Final-SNAPSHOT from local module loader @3cb1ffe6 (finder: local module finder @3dfc5fb8 (roots: /home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules,/home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> ... 18 more
> {noformat}
> The feature spec generator fails because the server prefers the local repository in your settings than the one in the system property (jboss-modules does it). The artifact was located from the local repo in the settings, and it was not the ee9 jar. The ee9 folder is forced by the galleon plugin using a system prop but it was not used because of my {{settings.xml}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14244) Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFLY-14244:
----------------------------------------------
Summary: Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
Key: WFLY-14244
URL: https://issues.redhat.com/browse/WFLY-14244
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Ricardo Martin Camarero
If you have defined a local repository in your maven {{settings.xml}} like the following:
{code:xml}
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<localRepository>/path/to/repository</localRepository>
...
</settings>
{code}
The folder {{ee-9/feature-path}} fails with the following error:
{noformat}
...
[INFO] --------------< org.wildfly:wildfly-preview-feature-pack >--------------
[INFO] Building WildFly: EE 9 Preview Galleon Feature Pack 22.0.0.Final-SNAPSHOT [146/162]
[INFO] --------------------------------[ pom ]---------------------------------
...
[INFO] --- wildfly-galleon-maven-plugin:5.0.0.Final:build-feature-pack (feature-pack-build) @ wildfly-preview-feature-pack ---
[INFO] EE9: transformed infinispan-hibernate-cache-v53-11.0.8.Final.jar
...
[INFO] EE9: transformed jakarta.json-api-1.1.6.jar
[INFO] EE9: transformed jakarta.json-1.1.6.jar
Forked embedded process has failed with the following error:
java.lang.IllegalStateException: WFLYEMB0022: Cannot invoke 'start' on embedded process
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:119)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:305)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
at org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
at org.jboss.as.server.ServerService.boot(ServerService.java:426)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
{noformat}
If you use the -X option the initial exception is the following:
{noformat}
ERROR: WFLYSRV0055: Caught exception during boot
org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.mail
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100)
at org.jboss.as.server.parsing.StandaloneXml_6.readServerElement(StandaloneXml_6.java:221)
at org.jboss.as.server.parsing.StandaloneXml_6.readElement(StandaloneXml_6.java:121)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:114)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
... 3 more
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/mail/Session
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:92)
... 10 more
Caused by: java.lang.NoClassDefFoundError: javax/mail/Session
at org.jboss.as.mail.extension.MailSessionDefinition.<clinit>(MailSessionDefinition.java:49)
at org.jboss.as.mail.extension.MailSubsystemParser4_0.getParserDescription(MailSubsystemParser4_0.java:39)
at org.jboss.as.controller.PersistentResourceXMLParser.cacheXMLDescription(PersistentResourceXMLParser.java:45)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.preCacheParserDescription(ExtensionRegistry.java:522)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.attemptCurrentParserInitialization(ExtensionRegistry.java:508)
at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.access$200(ExtensionRegistry.java:434)
at org.jboss.as.controller.extension.ExtensionRegistry.initializeParsers(ExtensionRegistry.java:249)
at org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:116)
at org.jboss.as.controller.parsing.DeferredExtensionContext.access$000(DeferredExtensionContext.java:44)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:74)
at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.lang.ClassNotFoundException: javax.mail.Session from [Module "org.jboss.as.mail" version 22.0.0.Final-SNAPSHOT from local module loader @3cb1ffe6 (finder: local module finder @3dfc5fb8 (roots: /home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules,/home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules/system/layers/base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
... 18 more
{noformat}
The feature spec generator fails because the server prefers the local repository in your settings than the one in the system property (jboss-modules does it). The artifact was located from the local repo in the settings, and it was not the ee9 jar. The ee9 folder is forced by the galleon plugin using a system prop but it was not used vecause of my {{settings.xml}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14233) Undertow xnio direct memory buffer leaking
by Mike Zhary (Jira)
[ https://issues.redhat.com/browse/WFLY-14233?page=com.atlassian.jira.plugi... ]
Mike Zhary commented on WFLY-14233:
-----------------------------------
[~flavia.rainone] Well, I can't provide an application for this now due to commercials.
Yep, I got that there must be some reallocation, but as you can see at first parts of graphs it didn't happen at all. but apllying the patch makes good changes to us. I'll ask our programmers to provide some code that can reproduce it. After that I'll attach it here
> Undertow xnio direct memory buffer leaking
> ------------------------------------------
>
> Key: WFLY-14233
> URL: https://issues.redhat.com/browse/WFLY-14233
> Project: WildFly
> Issue Type: Bug
> Components: IO, Web (Undertow)
> Affects Versions: 19.0.0.Final
> Reporter: Mike Zhary
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: 2020-11-10-112753_563x276_scrot.png, api_src_main_java_org_xnio_ByteBufferSlicePool.java, image_2020_10_30T09_55_47_082Z.png, Снимок экрана 2020-12-16 в 15.33.53.png, Снимок экрана 2020-12-16 в 15.34.20.png
>
>
> Wildfly.19.0.1.Final standalone
> We'd found an issue with direct memory buffer leaking on one from our servers.
> There is rest api application allocated there.
> it provides hugh data on some requests.
> As per graphics we noticed that there is corrielation between sessions on server and using of direct memory buffer.
> !Снимок экрана 2020-12-16 в 15.33.53.png|width=1199,height=400!!Снимок экрана 2020-12-16 в 15.34.20.png|width=1170,height=392!
> Our suggestion was that direct memory buffer is reallocatable with new web requests, that's we tried change session lifetime to minimum we prefer.
> You can see it on graphs with memory. Red line means direct memory buffer.
> At first time it takes as much as it can, but after changing session lifetime we faced the same problem.
> There are some drops of redline to zero, but there were restarts of wildfly.
> As per our investigations there is the problem in that GC free some part of memory, but it can't get DMB and that's why it increases.
> Something allocates ByteBufferSlicePool (but it marked as depricated, so I think it'll disappared in sometime, but our bug still reproduceable on WF21)
> {code:java}
> 2020-10-15 18:24:59,569 ERROR (default I/O-4) [listener] [SOMEAPP] XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: Direct buffer memory
> at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
> at java.base/java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:118)
> at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:317)
> at org.jboss.xnio@3.7.3.Final//org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57)
> at org.jboss.xnio@3.7.3.Final//org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55)
> at org.jboss.xnio@3.7.3.Final//org.xnio.ByteBufferSlicePool.allocateSlices(ByteBufferSlicePool.java:162)
> at org.jboss.xnio@3.7.3.Final//org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:149)
> at io.undertow.core@2.0.27.Final//io.undertow.server.XnioByteBufferPool.allocate(XnioByteBufferPool.java:53)
> at io.undertow.core@2.0.27.Final//io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:147)
> at io.undertow.core@2.0.27.Final//io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.core@2.0.27.Final//io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
> at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> {code}
> !2020-11-10-112753_563x276_scrot.png|thumbnail!
> When something needs memory it allocates and save this memory to directBuffers(that was removed)
> Seems there is a point of leaking in that some code allocates direct memory when client doesn't need it
> Another point is at method of cleaning of direct memory. When it called directBuffers saves in static variable of class as null-buffers and it can be reusable for ByteBufferSlicePool, that is potential leak point, because of this variable never clean just accumulate.
> So, after removing variable directBuffers we'd found a "method".
> We'd disable some cache mechanism of allocated memory areas and now clients of this lib gets DMB directly and when it free GC clean it.
> You can see it on graphics. first part of it shows that DMB grows before maxim get OOM and another part is when there is no problem with OOM.
> Some nearest issue WFCORE-4600
> that is our patched library:
> [^api_src_main_java_org_xnio_ByteBufferSlicePool.java]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14243) New JAXB tests in WFLY-13968 fails on ee9 profile
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFLY-14243:
----------------------------------------------
Summary: New JAXB tests in WFLY-13968 fails on ee9 profile
Key: WFLY-14243
URL: https://issues.redhat.com/browse/WFLY-14243
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Ricardo Martin Camarero
Assignee: Ricardo Martin Camarero
The new JAXB tests introduced in WFLY-13968 fails when using the ee9 profile:
* org.jboss.as.test.integration.jaxb.unit.JAXBContextSystemPropCustomTestCase
* org.jboss.as.test.integration.jaxb.unit.JAXBContextUsingPropertiesTestCase
The reason is that in ee9 the system property and the keys inside the {{jaxb.properties}} file needs to be prefixed by {{jakarta}} instead of {{javax}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking
by Mike Zhary (Jira)
[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ]
Mike Zhary commented on WFLY-14234:
-----------------------------------
I hope it'll help with investigations from your side.
> EJB bean method direct memory buffer leaking
> --------------------------------------------
>
> Key: WFLY-14234
> URL: https://issues.redhat.com/browse/WFLY-14234
> Project: WildFly
> Issue Type: Bug
> Components: EJB, IO
> Affects Versions: 19.0.0.Final
> Reporter: Mike Zhary
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java
>
>
> Wildfly.19.0.1.Final standalone
> We're using haproxy to balance ejb calls between wildfly servers.
> That's very useful model, but there are problems with it.
> All connections are declared as remote-outbound-connection and it works.
> {code}
> <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> {code}
> But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response.
> Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
> But everything is clear, when port closed or server don't response for a calls.
> Haproxy doesn't have feature to don't listen port if backed is offline.
> At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
> At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
> Take a look:
> !2020-11-10-112753_563x276_scrot.png|thumbnail!
> Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
> The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
> We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
> As per investigations DMB used for an SSL connection, but we don't it.
> So we were to patch jboss-remoting class RemoteConnectionProvider.
> after that we'd solved issue with leaking of DMB.
> Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
> Please take look how this bug can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months
[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking
by Mike Zhary (Jira)
[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ]
Mike Zhary commented on WFLY-14234:
-----------------------------------
Hi.
there are to be 2 servers and haproxy between them.
[wildfly-server1] <-> [haproxy] <-> [wildfly-server2]
there are to be defined remote connections to haproxy server
like this:
{code}
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
<outbound-connections>
<remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" protocol="http-remoting" security-realm="ejb-security-realm" username="ejb">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
</outbound-connections>
{code}
{code}
<outbound-socket-binding name="remote-ejb">
<remote-destination host="test-ejb-balance01" port="30001"/>
</outbound-socket-binding>
{code}
haproxy.cfg
{code}
### start config for haproxy_host.name balance
frontend balance_test-wf01
bind 192.168.230.13:30000
mode tcp
default_backend test-wf01_servers
option tcplog
log global
capture request header X-Forwarded-For len 15
backend test-wf01_servers
balance roundrobin
server server-test-wf01 test-wf01:8080 check
### stop config for haproxy_host.name balance
### start config for haproxy_host.name balance
frontend balance_test-wf02
bind 192.168.230.13:30001
mode tcp
default_backend test-wf02_servers
option tcplog
log global
capture request header X-Forwarded-For len 15
backend test-wf02_servers
balance roundrobin
server server-test-wf02 test-wf02:8080 check
### stop config for haproxy_host.name balance
{code}
You can see tcp mode in *haproxy.cfg*, but I'd tried even http mode.
In order to reproduce this scheme I deployed application which calls remote-ejb on wildfly-server2.
When wildfly-server2 is online there are no problems.
But if I'll shutdown wildfly there I'll have situation I described before.
> EJB bean method direct memory buffer leaking
> --------------------------------------------
>
> Key: WFLY-14234
> URL: https://issues.redhat.com/browse/WFLY-14234
> Project: WildFly
> Issue Type: Bug
> Components: EJB, IO
> Affects Versions: 19.0.0.Final
> Reporter: Mike Zhary
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java
>
>
> Wildfly.19.0.1.Final standalone
> We're using haproxy to balance ejb calls between wildfly servers.
> That's very useful model, but there are problems with it.
> All connections are declared as remote-outbound-connection and it works.
> {code}
> <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> {code}
> But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response.
> Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
> But everything is clear, when port closed or server don't response for a calls.
> Haproxy doesn't have feature to don't listen port if backed is offline.
> At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
> At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
> Take a look:
> !2020-11-10-112753_563x276_scrot.png|thumbnail!
> Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
> The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
> We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
> As per investigations DMB used for an SSL connection, but we don't it.
> So we were to patch jboss-remoting class RemoteConnectionProvider.
> after that we'd solved issue with leaking of DMB.
> Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
> Please take look how this bug can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 5 months