[JBoss JIRA] (WFLY-6003) Minor typos and in CLI description texts
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-6003?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky reassigned WFLY-6003:
---------------------------------------
Component/s: Web (Undertow)
(was: CLI)
Assignee: Stuart Douglas (was: Alexey Loubyansky)
> Minor typos and in CLI description texts
> -----------------------------------------
>
> Key: WFLY-6003
> URL: https://issues.jboss.org/browse/WFLY-6003
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Priority: Trivial
>
> - there are few typos in CLI description text for
> - missing size units for some of attributes for better UX
> - add more info to {{undertow.listener.max-connections}} so user can more easily understand how to configure it properly
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-6003) Minor typos and in CLI description texts
by Jan Stourac (JIRA)
Jan Stourac created WFLY-6003:
---------------------------------
Summary: Minor typos and in CLI description texts
Key: WFLY-6003
URL: https://issues.jboss.org/browse/WFLY-6003
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 10.0.0.CR5
Reporter: Jan Stourac
Assignee: Alexey Loubyansky
Priority: Trivial
- there are few typos in CLI description text for
- missing size units for some of attributes for better UX
- add more info to {{undertow.listener.max-connections}} so user can more easily understand how to configure it properly
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-6002) Listener secure attribute doesn't work as expected
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6002?page=com.atlassian.jira.plugin.... ]
Radim Hatlapatka updated WFLY-6002:
-----------------------------------
Attachment: confidential.war
> Listener secure attribute doesn't work as expected
> --------------------------------------------------
>
> Key: WFLY-6002
> URL: https://issues.jboss.org/browse/WFLY-6002
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Attachments: confidential.war
>
>
> When setting {{secure}} attributed on {{http-listener}} and deploying web application which requires secured connection ({{<transport-guarantee>CONFIDENTIAL</transport-guarantee>}}. The web application should be accessible even from the {{http}} as the listener is defined as secured, but instead it results to redirect to https (when having redirect-socket defined) or to internal server error (when no redirect-socket).
> Steps to reproduce:
> # start eap and deploy attached confidential.war
> # configure http-listener default as secured => /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=secure, value=true)
> # reload the server
> # go to http://127.0.0.1:8080/confidential/index.jsp
> # you should get 200 response code, still you get 302, which is not correct as the listener is defined as secured
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-6002) Listener secure attribute doesn't work as expected
by Radim Hatlapatka (JIRA)
Radim Hatlapatka created WFLY-6002:
--------------------------------------
Summary: Listener secure attribute doesn't work as expected
Key: WFLY-6002
URL: https://issues.jboss.org/browse/WFLY-6002
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Reporter: Radim Hatlapatka
Assignee: Stuart Douglas
When setting {{secure}} attributed on {{http-listener}} and deploying web application which requires secured connection ({{<transport-guarantee>CONFIDENTIAL</transport-guarantee>}}. The web application should be accessible even from the {{http}} as the listener is defined as secured, but instead it results to redirect to https (when having redirect-socket defined) or to internal server error (when no redirect-socket).
Steps to reproduce:
# start eap and deploy attached confidential.war
# configure http-listener default as secured => /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=secure, value=true)
# reload the server
# go to http://127.0.0.1:8080/confidential/index.jsp
# you should get 200 response code, still you get 302, which is not correct as the listener is defined as secured
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-6002) Listener secure attribute doesn't work as expected
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6002?page=com.atlassian.jira.plugin.... ]
Radim Hatlapatka updated WFLY-6002:
-----------------------------------
Affects Version/s: 10.0.0.CR5
> Listener secure attribute doesn't work as expected
> --------------------------------------------------
>
> Key: WFLY-6002
> URL: https://issues.jboss.org/browse/WFLY-6002
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
>
> When setting {{secure}} attributed on {{http-listener}} and deploying web application which requires secured connection ({{<transport-guarantee>CONFIDENTIAL</transport-guarantee>}}. The web application should be accessible even from the {{http}} as the listener is defined as secured, but instead it results to redirect to https (when having redirect-socket defined) or to internal server error (when no redirect-socket).
> Steps to reproduce:
> # start eap and deploy attached confidential.war
> # configure http-listener default as secured => /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=secure, value=true)
> # reload the server
> # go to http://127.0.0.1:8080/confidential/index.jsp
> # you should get 200 response code, still you get 302, which is not correct as the listener is defined as secured
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBAS-9465) NPE during deployment in org.jboss.weld.util.ApiAbstraction.annotationTypeForName
by Alexey Pakseykin (JIRA)
[ https://issues.jboss.org/browse/JBAS-9465?page=com.atlassian.jira.plugin.... ]
Alexey Pakseykin commented on JBAS-9465:
----------------------------------------
I've just found a workaround for similar issue.
h3. Issue
We use JBoss `6.1.0.Final` for our Maven cargo integration tests in Linux environment.
JBoss is extracted into (my home dir):
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
Environment variable `JBOSS_HOME` pointed to this location.
File `boot.log` contained no significant/related issues (no ERRORs at all).
On the other hand, file `server.log` started with exactly the same stacktrace:
{{
2016-01-15 15:45:07,635 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (Thread-2) Error installing to Create: name=vfs:///home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final/server/foundation-test/deploy/FMKArchive-3.1.1.0-SNAPSHOT.ear_WeldBootstrapBean state=Configured: java.lang.NullPointerException
at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
...
}}
Then log continues with absolutely sick (unexplainable) long list of deployment issues.
What I realized that the issue was not reproducible anywhere else (continuous integration platform and all other machines for other developers).
I checked side by side everything between my hosts and the other working one:
- Environment variables
- Working directory (clean up ignored files)
- JBoss distribution binaries
- Checksums for all files and made sure no corruption..
*Nothing helped until...*
h3. Workaround
The only thing which was different is that path to my home directory contained a symlink:
{{
ls -ld /home
lrwxrwxrwx. 1 root root 16 Aug 16 2014 /home -> /mnt/backup/home
}}
When I changed `JBOSS_HOME` from this
{{
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
to this
{{
/mnt/backup/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
problem disappeared!
In other words, JBoss didn't tolerate symlinks within the path specified by `JBOSS_HOME`.
> NPE during deployment in org.jboss.weld.util.ApiAbstraction.annotationTypeForName
> ---------------------------------------------------------------------------------
>
> Key: JBAS-9465
> URL: https://issues.jboss.org/browse/JBAS-9465
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Components: Weld/CDI
> Affects Versions: 6.0.0.Final, 6.1.0
> Environment: Windows 7 64bit
> Java 1.6.0_29 64bit
> Maven Cargo Plugin 1.4 or command line
> Reporter: Dirk Mahler
> Assignee: Marius Bogoevici
>
> We are using maven cargo plugin for our integration tests to start/stop JBoss AS 6.1.0.Final and deploying artifacts. The cargo plugin is configured with a installation directory (e.g. C:/development/work/cargo) which is used by cargo to construct a command line to start the AS. On some of our Windows 7 systems we faced the following exception while starting and deploying EAR artifacts containing CDI enabled bean archives with the default JBOSS server configuration:
> 11:11:46,637 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Create: name=vfs:///C:/development/work/cargo/default/deploy/application.ear-2.3.7.3-SNAPSHOT.ear_WeldBootstrapBean state=Configured: java.lang.NullPointerException
> at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
> at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:156) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:293) [:6.1.0.Final]
> at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:106) [:6.1.0.Final]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29]
> at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29]
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-ker
> nel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:
> 2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.SP
> 2]
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.
> 2.0.SP2]
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.2.GA]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.2.GA]
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.2.GA]
> at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.1.0.Final]
> at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.
> 2.0.SP2]
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2]
> at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2]
> at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2]
> at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]
> at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.1.0.Final]
> at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.1.0.Final]
> at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
> at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
> The reason could be tracked down to the fact that the specified directory must be specified using the correct case as reported by the file system (e.g. C:/development/work/cargo vs. C:/Development/work/cargo).
> The problem also exists if running the AS from the command line (without maven cargo plugin involved):
> C:\development\Java\jdk_1.6.0_29\jre\bin\java.exe -Xmx1200M -XX:MaxPermSize=768M -Xms128m -XX:PermSize=48m -Djboss.bind.address=127.0.0.1 -Dlogging.configuration=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/bin/logging.properties -Djboss.common.lib.url=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/common/lib/ -Djava.endorsed.dirs=C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\lib\endorsed -Djboss.home.dir=C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final -Djboss.server.home.dir=C:\development\work/cargo/default -Djboss.server.home.url=file:/C:/development/work/cargo/default/ -Djboss.server.name=default -Djboss.server.lib.url=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/server/default/lib/ -Djboss.server.log.threshold=INFO -classpath C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar;C:\development\Java\jdk_1.6.0_29\lib\tools.jar org.jboss.Main --host=localhost --configuration=default
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBAS-9465) NPE during deployment in org.jboss.weld.util.ApiAbstraction.annotationTypeForName
by Alexey Pakseykin (JIRA)
[ https://issues.jboss.org/browse/JBAS-9465?page=com.atlassian.jira.plugin.... ]
Alexey Pakseykin edited comment on JBAS-9465 at 1/15/16 3:01 AM:
-----------------------------------------------------------------
I've just found a workaround for similar issue.
h2. Issue
We use JBoss `6.1.0.Final` for our Maven cargo integration tests in Linux environment.
JBoss is extracted into (my home dir):
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
Environment variable `JBOSS_HOME` pointed to this location.
File `boot.log` contained no significant/related issues (no ERRORs at all).
On the other hand, file `server.log` started with exactly the same stacktrace:
{{
2016-01-15 15:45:07,635 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (Thread-2) Error installing to Create: name=vfs:///home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final/server/foundation-test/deploy/FMKArchive-3.1.1.0-SNAPSHOT.ear_WeldBootstrapBean state=Configured: java.lang.NullPointerException
at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
...
}}
Then log continues with absolutely sick (unexplainable) long list of deployment issues.
What I realized that the issue was not reproducible anywhere else (continuous integration platform and all other machines for other developers).
I checked side by side everything between my hosts and the other working one:
- Environment variables
- Working directory (clean up ignored files)
- JBoss distribution binaries
- Checksums for all files and made sure no corruption..
*Nothing helped until...*
h2. Workaround
The only thing which was different is that path to my home directory contained a symlink:
{{
ls -ld /home
lrwxrwxrwx. 1 root root 16 Aug 16 2014 /home -> /mnt/backup/home
}}
When I changed `JBOSS_HOME` from this
{{
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
to this
{{
/mnt/backup/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
problem disappeared!
In other words, JBoss didn't tolerate symlinks within the path specified by `JBOSS_HOME`.
was (Author: uvsmtid):
I've just found a workaround for similar issue.
h3. Issue
We use JBoss `6.1.0.Final` for our Maven cargo integration tests in Linux environment.
JBoss is extracted into (my home dir):
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
Environment variable `JBOSS_HOME` pointed to this location.
File `boot.log` contained no significant/related issues (no ERRORs at all).
On the other hand, file `server.log` started with exactly the same stacktrace:
{{
2016-01-15 15:45:07,635 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (Thread-2) Error installing to Create: name=vfs:///home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final/server/foundation-test/deploy/FMKArchive-3.1.1.0-SNAPSHOT.ear_WeldBootstrapBean state=Configured: java.lang.NullPointerException
at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
...
}}
Then log continues with absolutely sick (unexplainable) long list of deployment issues.
What I realized that the issue was not reproducible anywhere else (continuous integration platform and all other machines for other developers).
I checked side by side everything between my hosts and the other working one:
- Environment variables
- Working directory (clean up ignored files)
- JBoss distribution binaries
- Checksums for all files and made sure no corruption..
*Nothing helped until...*
h3. Workaround
The only thing which was different is that path to my home directory contained a symlink:
{{
ls -ld /home
lrwxrwxrwx. 1 root root 16 Aug 16 2014 /home -> /mnt/backup/home
}}
When I changed `JBOSS_HOME` from this
{{
/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
to this
{{
/mnt/backup/home/uvsmtid/Apps/maven.test.jboss/jboss-6.1.0.Final
}}
problem disappeared!
In other words, JBoss didn't tolerate symlinks within the path specified by `JBOSS_HOME`.
> NPE during deployment in org.jboss.weld.util.ApiAbstraction.annotationTypeForName
> ---------------------------------------------------------------------------------
>
> Key: JBAS-9465
> URL: https://issues.jboss.org/browse/JBAS-9465
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Components: Weld/CDI
> Affects Versions: 6.0.0.Final, 6.1.0
> Environment: Windows 7 64bit
> Java 1.6.0_29 64bit
> Maven Cargo Plugin 1.4 or command line
> Reporter: Dirk Mahler
> Assignee: Marius Bogoevici
>
> We are using maven cargo plugin for our integration tests to start/stop JBoss AS 6.1.0.Final and deploying artifacts. The cargo plugin is configured with a installation directory (e.g. C:/development/work/cargo) which is used by cargo to construct a command line to start the AS. On some of our Windows 7 systems we faced the following exception while starting and deploying EAR artifacts containing CDI enabled bean archives with the default JBOSS server configuration:
> 11:11:46,637 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Create: name=vfs:///C:/development/work/cargo/default/deploy/application.ear-2.3.7.3-SNAPSHOT.ear_WeldBootstrapBean state=Configured: java.lang.NullPointerException
> at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
> at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:156) [:6.1.0.Final]
> at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:293) [:6.1.0.Final]
> at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:106) [:6.1.0.Final]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29]
> at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29]
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.1.SP1]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-ker
> nel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:
> 2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.SP
> 2]
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.
> 2.0.SP2]
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.2.GA]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.2.GA]
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.2.GA]
> at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.1.0.Final]
> at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.
> 2.0.SP2]
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP2]
> at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2]
> at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2]
> at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2]
> at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2]
> at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]
> at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.1.0.Final]
> at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.1.0.Final]
> at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
> at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
> The reason could be tracked down to the fact that the specified directory must be specified using the correct case as reported by the file system (e.g. C:/development/work/cargo vs. C:/Development/work/cargo).
> The problem also exists if running the AS from the command line (without maven cargo plugin involved):
> C:\development\Java\jdk_1.6.0_29\jre\bin\java.exe -Xmx1200M -XX:MaxPermSize=768M -Xms128m -XX:PermSize=48m -Djboss.bind.address=127.0.0.1 -Dlogging.configuration=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/bin/logging.properties -Djboss.common.lib.url=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/common/lib/ -Djava.endorsed.dirs=C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\lib\endorsed -Djboss.home.dir=C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final -Djboss.server.home.dir=C:\development\work/cargo/default -Djboss.server.home.url=file:/C:/development/work/cargo/default/ -Djboss.server.name=default -Djboss.server.lib.url=file:/C:/development/work/cargo/jboss-as-distribution-6.1.0.Final/jboss-6.1.0.Final/server/default/lib/ -Djboss.server.log.threshold=INFO -classpath C:\development\work\cargo\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar;C:\development\Java\jdk_1.6.0_29\lib\tools.jar org.jboss.Main --host=localhost --configuration=default
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5480) SPEC JMS 2007 benchmark fails with AMQ214013: Failed to decode packet
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5480?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5480:
-------------------------------
Comment: was deleted
(was: [~flavia.rainone] try updating to latest wildfly, we are currently using wildly-010 which required changes in our integration to be compatible with. I would wager a good guess that latest 1.1.x is probably drop-in able on wf master (unless something else changed).)
> SPEC JMS 2007 benchmark fails with AMQ214013: Failed to decode packet
> ---------------------------------------------------------------------
>
> Key: WFLY-5480
> URL: https://issues.jboss.org/browse/WFLY-5480
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Ondřej Kalman
> Assignee: Flavia Rainone
> Priority: Blocker
>
> But I have another problem, when I removed trace logs from config I'm not able to run benchmark on localhost to the end, because clients starts getting :
> AMQ214013: Failed to decode packet
> java.lang.IndexOutOfBoundsException: readerIndex: 2130706436 (expected: 0 <= readerIndex <= writerIndex(2943))
> at io.netty.buffer.AbstractByteBuf.readerIndex(AbstractByteBuf.java:73)
> at io.netty.buffer.WrappedByteBuf.readerIndex(WrappedByteBuf.java:99)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readerIndex(ChannelBufferWrapper.java:405)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.decode(MessageImpl.java:1052)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.decodeFromBuffer(MessageImpl.java:459)
> at org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionReceiveMessage.decode(SessionReceiveMessage.java:94)
> at org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.decode(ClientPacketDecoder.java:42)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:371)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1374)
> at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:242)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:847)
> at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteCha
> nnel.java:131)
> at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
> at java.lang.Thread.run(Thread.java:745)
> and
> Thread-9 (ActiveMQ-client-global-threads-1266561810): Uncaught exception.
> java.lang.NumberFormatException: null
> at java.lang.Integer.parseInt(Integer.java:542)
> at java.lang.Integer.valueOf(Integer.java:766)
> at org.apache.activemq.artemis.utils.TypedProperties.getIntProperty(TypedProperties.java:280)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.getIntProperty(MessageImpl.java:811)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getIntProperty(ActiveMQMessage.java:578)
> at org.spec.jms.agents.SPECWorkerThread.receivedMessage(SPECWorkerThread.java:849)
> at org.spec.jms.agents.SPECWorkerThread.onMessage(SPECWorkerThread.java:820)
> at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:100)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1089)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1224)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Thread-3 (ActiveMQ-client-global-threads-1266561810): Uncaught exception.
> javax.jms.IllegalStateException: AMQ119027: Could not find reference on consumer ID=0, messageId = 104,833 queue = 127\.0\.0\.1_VM1_SPAgent7_0.SP_CallForOffersEH_7_EHID_1PF0
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:410)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.sendACK(ActiveMQSessionContext.java:461)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.acknowledge(ClientSessionImpl.java:765)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.doAck(ClientConsumerImpl.java:1212)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.flushAcks(ClientConsumerImpl.java:830)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.flushAcks(ClientSessionImpl.java:1852)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:501)
> at org.apache.activemq.artemis.core.client.impl.DelegatingSession.commit(DelegatingSession.java:159)
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.commit(ActiveMQSession.java:218)
> at org.spec.jms.eventhandler.sp.SP_CallForOffersEH.handleMessage(SP_CallForOffersEH.java:306)
> at org.spec.jms.agents.SPECWorkerThread.onMessage(SPECWorkerThread.java:821)
> at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:100)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1089)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1224)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecut
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1201) Could not upload new deployment
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ]
Jason Greene updated WFCORE-1201:
---------------------------------
Fix Version/s: 2.0.8.Final
(was: 2.0.7.Final)
> Could not upload new deployment
> -------------------------------
>
> Key: WFCORE-1201
> URL: https://issues.jboss.org/browse/WFCORE-1201
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.2.Final
> Environment: 2 different machines
> Linux Debian Squeeze & Jessie
> Oracle Java SE 8
> Reporter: Claudio Weiler
> Assignee: Harald Pehl
> Fix For: 2.0.8.Final
>
>
> WildFly stop to accept deployments via interface upload with following stacktrace:
> ERROR [io.undertow.request] (XNIO-1 task-2) Undertow request failed HttpServerExchange{ POST /management-upload}: java.io.IOException: UT000036: Connection terminated parsing multipart data
> at io.undertow.server.handlers.form.MultiPartParserDefinition$MultiPartUploadHandler.parseBlocking(MultiPartParserDefinition.java:203)
> at org.jboss.as.domain.http.server.DomainApiGenericOperationHandler.handleRequest(DomainApiGenericOperationHandler.java:104)
> at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63)
> at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56)
> at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87)
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Same artifact was used before with success, nothing changed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months