[JBoss JIRA] (WFLY-4480) Websocket exception using async remote
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4480?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4480:
--------------------------------------
This should be fixed in Undertow upstream, although I can't reproduce it so it is hard to be sure.
> Websocket exception using async remote
> --------------------------------------
>
> Key: WFLY-4480
> URL: https://issues.jboss.org/browse/WFLY-4480
> Project: WildFly
> Issue Type: Bug
> Components: Web Sockets
> Affects Versions: 9.0.0.Beta2
> Reporter: nicolas desmaziers
> Assignee: Stuart Douglas
>
> Sending binary messages on the AsyncRemote endpoint throws an error in the log:
> 21:11:28,747 ERROR [org.xnio.listener] (default I/O-6) XNIO001007: A channel event listener threw an exception: java.lang.IllegalStateException: XNIO000017: Buffer was already freed
> at org.xnio.ByteBufferSlicePool$PooledByteBuffer.getResource(ByteBufferSlicePool.java:206)
> at org.xnio.ByteBufferSlicePool$PooledByteBuffer.getResource(ByteBufferSlicePool.java:176)
> at io.undertow.server.protocol.framed.AbstractFramedChannel.flushSenders(AbstractFramedChannel.java:490)
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameWriteListener.handleEvent(AbstractFramedChannel.java:793)
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameWriteListener.handleEvent(AbstractFramedChannel.java:790)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:93)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
> This happens after a few minutes and generally the number of errors increase rapidly and we can easily have a 2Go log after a few hours.
> Code is:
> session.getAsyncRemote.sendBinary(event.asReadOnlyBuffer(), new SendHandler(){
> override def onResult(result:SendResult) {
> }
> })
> It worked well with wildly 9.0 alpha 1 but bug appeared with beta 2.
> I generally receive a close event on the web socket session after the error logging.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4374) java.lang.IllegalAccessError and other classloader issues
by Anindhya Sharma (JIRA)
[ https://issues.jboss.org/browse/WFLY-4374?page=com.atlassian.jira.plugin.... ]
Anindhya Sharma commented on WFLY-4374:
---------------------------------------
Thanks for your response.
The Java EE 6 specification, section 8.2 Library Support and in it sub section 8.2.1 Bundled Libraries clearly states a JAR file may reference another JAR file using the Class-Path header in the manifest.
The above is what we have done in previous versions too of JBoss and other vendor products and it works as noted.
Here is an excerpt from the Wildfly documentation from the Developer's Guide, section on "Class Loading in Wildfly",
"If the ear-subdeployments-isolated is set to true then no automatic module dependencies between the sub-deployments are set up. User must manually setup the dependency with Class-Path entries, or by setting up explicit module dependencies."
Further it goes on to state
"
Portability
The Java EE specification says that portable applications should not rely on sub deployments having access to other sub deployments unless an explicit Class-Path entry is set in the MANIFEST.MF. So portable applications should always use Class-Path entry to explicitly state their dependencies.
"
So I am not sure how for Wildfly it can be stated that it meets EE specs (and your own documentation).
> java.lang.IllegalAccessError and other classloader issues
> ---------------------------------------------------------
>
> Key: WFLY-4374
> URL: https://issues.jboss.org/browse/WFLY-4374
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.2.0.Final, 9.0.0.Beta2
> Environment: Windows 7/Java 7 update 67
> Reporter: John Sipher
> Assignee: David Lloyd
> Attachments: problem-demo.zip
>
>
> Update 4/1/2015: I have verified that 9.0.0.Beta2 fixes the IllegalAccessError and the war file in problem-demo.zip/hello-world6/target now duplicates the original problem. The order of the jar files in the classpath should be
> WEB-INF/lib/patch/patch2.jar
> WEB-INF/lib/patch/patch1.jar
> WEB-INF/lib/base/helloworld-sans-cdi.jar
> org.jboss.as.quickstarts.helloworld.HelloService exists in both patch2.jar and helloworld-sans-cdi.jar. The version from patch2.jar should be used because it is first in the classpath, but the classloader is picking up the original class from helloworld-sans-cdi.jar instead.
> Original problem description follows:
> We use manifest-only jar files in our WAR and EAR files to control the order that jar files are searched for classes. When we issue patches, we put the modified class(es) in a separate jar file, add that jar file to the affected EAR or WAR file, and update the classpath in our manifest-only jar file to put the new patch at the beginning of the class path so that it will be used in place of the original class (which is still in the original jar file).
>
> For example, WEB-INF/lib will contain a single jar file named manifest.jar and sub-folders named 3rdparty, base, patch, and custom. The Class-Path entry in WEB-INF/lib/manifest.jar|META-INF/MANIFEST.MF looks like this:
> Class-Path: 3rdparty/manifest.jar patch/manifest.jar base/manifest.jar custom/manifest.jar
>
> When we publish a patch, the patch jar file is added to WEB-INF/lib/patch and to the front of the classpath in WEB-INF/lib/patch/manifest.jar's MANIFEST.MF.
>
> This worked fine for us for years with JBoss 4.2.3.GA, 5.1.0.GA, 7.1.2.Final, and 7.2.0.Final, but it's broken in WildFly 8.2.0.Final.
> When I run it in debug I can see where the problem shows up in this section of org.jboss.modules.Module (lines 562 - 573).
> final String path = pathOfClass(className);
> final Map<String, List<LocalLoader>> paths = getPathsUnchecked();
> final List<LocalLoader> loaders = paths.get(path);
> if (loaders != null) {
> Class<?> clazz;
> for (LocalLoader loader : loaders) {
> clazz = loader.loadClassLocal(className, resolve);
> if (clazz != null) {
> return clazz;
> }
> }
> }
> The modules in the loaders list at line 565 are
> * deployment.service.ear.lib/base/shared.jar:main
> * deployment.service.ear.lib/base/deployment.jar:main
> * deployment.service.ear.lib/patch/patch.jar:main
> The last one should actually be the first in the list. I haven't been able to track down the actual source of the error yet.
> I've been trying to create a simple example based on the helloworld quickstart to reproduce the problem, but I haven't been successful yet because of other classloader errors that I've run into. I decided to go ahead and open this issue and document the things I am able to reproduce. Those are:
> 1. CDI injection doesn't work when the annotated classes are in jar files under WEB-INF/lib instead of unpacked in WEB-INF/classes.
> 2. WildFly doesn't process the javax.servlet.annotation.WebServlet annotation if the jar file containing the annotated class is in a sub-folder of WEB-INF/lib.
> 3. WildFly throws a java.lang.IllegalAccessError trying to load a "patched" class.
> The first problem exists in both 7.2.0.Final and 8.2.0.Final. The other two problems are new in 8.2.0.Final.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-630) jboss-cli.xml should include timeout of 30 seconds
by Travis Rogers (JIRA)
[ https://issues.jboss.org/browse/WFCORE-630?page=com.atlassian.jira.plugin... ]
Travis Rogers moved WFLY-4367 to WFCORE-630:
--------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-630 (was: WFLY-4367)
Affects Version/s: (was: 8.2.0.Final)
Component/s: CLI
(was: CLI)
> jboss-cli.xml should include timeout of 30 seconds
> ---------------------------------------------------
>
> Key: WFCORE-630
> URL: https://issues.jboss.org/browse/WFCORE-630
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Travis Rogers
> Assignee: Alexey Loubyansky
> Attachments: loop-cli-cmd.sh
>
>
> Description of problem:
> CLI commands use a default timeout of 5 seconds. Testing has shown that connection timeouts will occur with a timeout value this low. Recommended value is 30 seconds.
> The following default setting should be added to $JBOSS_HOME/bin/jboss-cli.xml:
> <connection-timeout>30000</connection-timeout>
> Version-Release number of selected component (if applicable):
> How to reproduce:
> Loop calling the CLI executing a command.
> Example command:
> jboss-cli.sh -c --command=":read-attribute(name=server-state)"
> Actual results:
> Connection timeout error will eventually be thrown.
> Expected results:
> No errors due to connection timeout.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4297) [PATCH] fix 2 bugs in bin/standalone.sh
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4297?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4297:
--------------------------------------
Assignee: Tomaz Cerar (was: Jason Greene)
Component/s: Scripts
Tomaz, please move to WFCORE if this is still valid, else please resolve as Out of Date.
> [PATCH] fix 2 bugs in bin/standalone.sh
> ---------------------------------------
>
> Key: WFLY-4297
> URL: https://issues.jboss.org/browse/WFLY-4297
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Martin Petricek
> Assignee: Tomaz Cerar
> Attachments: bin-fix.patch
>
>
> bin/standalone.sh does not use "shift" correctly when parsing commandline option, failing with "bin/standalone.sh: 34: shift: can't shift that many" if "--debug" without a parameter is used on dash (default shell in debian)
> Second issue is that the script does not handle correctly situation when CDPATH environment variable is set, failing completely.
> Attaching patch that fixes both these issues.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4315) Allow Individual servers in a server group to be restarted
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4315?page=com.atlassian.jira.plugin.... ]
Brian Stansberry closed WFLY-4315.
----------------------------------
Resolution: Out of Date
You can start/stop any server by accessing the /host=<hostname>/server=<servername> resource or the /host=<hostname>/server-config=<servername> resource.
> Allow Individual servers in a server group to be restarted
> ----------------------------------------------------------
>
> Key: WFLY-4315
> URL: https://issues.jboss.org/browse/WFLY-4315
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Carlton Zachary
> Assignee: Jason Greene
>
> Currently, in domain mode you can only do a restart on a server group. Could the feature be added to have the option to do a restart on an individual server in the server group. Seems to only be there when a configuration change has been made and requires a restart.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4367) jboss-cli.xml should include timeout of 30 seconds
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4367?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-4367:
----------------------------------------
This should be moved to WFCORE, as that is where this file is currently maintained.
> jboss-cli.xml should include timeout of 30 seconds
> ---------------------------------------------------
>
> Key: WFLY-4367
> URL: https://issues.jboss.org/browse/WFLY-4367
> Project: WildFly
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 8.2.0.Final
> Reporter: Travis Rogers
> Assignee: Alexey Loubyansky
> Attachments: loop-cli-cmd.sh
>
>
> Description of problem:
> CLI commands use a default timeout of 5 seconds. Testing has shown that connection timeouts will occur with a timeout value this low. Recommended value is 30 seconds.
> The following default setting should be added to $JBOSS_HOME/bin/jboss-cli.xml:
> <connection-timeout>30000</connection-timeout>
> Version-Release number of selected component (if applicable):
> How to reproduce:
> Loop calling the CLI executing a command.
> Example command:
> jboss-cli.sh -c --command=":read-attribute(name=server-state)"
> Actual results:
> Connection timeout error will eventually be thrown.
> Expected results:
> No errors due to connection timeout.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4373) WildFly CLI API ModelControllerClient memory leak?
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4373?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-4373:
----------------------------------------
Does this happen with WildFly 9.0.0.Beta2?
If so, please attach a thread dump of both the client process and the server process, taken while close() is hanging.
Also, why does the title refer to a memory leak?
Finally, the "Environment" field references some xnio versions. Are those the standard versions in WildFly 8.2.0.Final? If not, does the problem occur when the standard versions are used?
> WildFly CLI API ModelControllerClient memory leak?
> --------------------------------------------------
>
> Key: WFLY-4373
> URL: https://issues.jboss.org/browse/WFLY-4373
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, IO
> Affects Versions: 8.2.0.Final
> Environment: Ubuntu 14.04 LTS, Java 1.8, xnio-api and xnio-nio are 3.3.0.Final
> Reporter: Georgy Go
> Assignee: Tomaz Cerar
> Labels: cli, dmr
>
> The following snippet of code to redeploy an application:
> ModelControllerClient cl = ModelControllerClient.Factory.create("localhost", 9999);
> ModelNode operation = new ModelNode();
> operation.get("operation").set("redeploy");
> operation.get("address").add("deployment", "server.war");
> cl.execute(operation);
> cl.close();
> - works fine, but .close() freezes forever.
> This issue depends to not only redeploy, but also for any other operations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4373) WildFly CLI API ModelControllerClient memory leak?
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4373?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4373:
-----------------------------------
Component/s: Domain Management
(was: CLI)
> WildFly CLI API ModelControllerClient memory leak?
> --------------------------------------------------
>
> Key: WFLY-4373
> URL: https://issues.jboss.org/browse/WFLY-4373
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, IO
> Affects Versions: 8.2.0.Final
> Environment: Ubuntu 14.04 LTS, Java 1.8, xnio-api and xnio-nio are 3.3.0.Final
> Reporter: Georgy Go
> Assignee: Alexey Loubyansky
> Labels: cli, dmr
>
> The following snippet of code to redeploy an application:
> ModelControllerClient cl = ModelControllerClient.Factory.create("localhost", 9999);
> ModelNode operation = new ModelNode();
> operation.get("operation").set("redeploy");
> operation.get("address").add("deployment", "server.war");
> cl.execute(operation);
> cl.close();
> - works fine, but .close() freezes forever.
> This issue depends to not only redeploy, but also for any other operations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4373) WildFly CLI API ModelControllerClient memory leak?
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4373?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4373:
--------------------------------------
Assignee: Brian Stansberry (was: Alexey Loubyansky)
> WildFly CLI API ModelControllerClient memory leak?
> --------------------------------------------------
>
> Key: WFLY-4373
> URL: https://issues.jboss.org/browse/WFLY-4373
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, IO
> Affects Versions: 8.2.0.Final
> Environment: Ubuntu 14.04 LTS, Java 1.8, xnio-api and xnio-nio are 3.3.0.Final
> Reporter: Georgy Go
> Assignee: Brian Stansberry
> Labels: cli, dmr
>
> The following snippet of code to redeploy an application:
> ModelControllerClient cl = ModelControllerClient.Factory.create("localhost", 9999);
> ModelNode operation = new ModelNode();
> operation.get("operation").set("redeploy");
> operation.get("address").add("deployment", "server.war");
> cl.execute(operation);
> cl.close();
> - works fine, but .close() freezes forever.
> This issue depends to not only redeploy, but also for any other operations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months