[JBoss JIRA] (WFLY-3702) RetryInvoker needs to be aware of transaction status
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-3702?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-3702:
-------------------------------
Summary: RetryInvoker needs to be aware of transaction status (was: RetryInvoker is useless within the context of a transaction.)
> RetryInvoker needs to be aware of transaction status
> ----------------------------------------------------
>
> Key: WFLY-3702
> URL: https://issues.jboss.org/browse/WFLY-3702
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.2.0.CR1, 9.0.0.Beta1
>
>
> RetryInvoker should not retry if a given operation is transactional. If the operation fails - the status of the current transaction will be rollback-only, which will fail due to invalid transaction status if retried.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBASMP-66) Could not execute goal add-resource / wildfly-maven-plugin
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-66?page=com.atlassian.jira.plugin.... ]
James Perkins updated JBASMP-66:
--------------------------------
Description:
My pom: http://pastebin.com/BJ9zcXrg
felix@felix-DQ77PRO:~/workspaces/java/workspaceGastos/yyy-project$ mvn clean install -X
The debug output:
http://pastebin.com/cM8LbR62
The problem is here:
{code}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null: IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal add-resource. Reason: null
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:118)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asList(ModelValue.java:132)
at org.jboss.dmr.ModelNode.asList(ModelNode.java:1302)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.resourceExists(AddResourceMojo.java:258)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.addCompositeResource(AddResourceMojo.java:180)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.processResources(AddResourceMojo.java:148)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:112)
... 21 more
{code}
Same problem:
http://stackoverflow.com/questions/22533311/wildfly-maven-plugin-not-depl...
Other:
http://stackoverflow.com/questions/21020926/add-an-xa-datasource-fails-wi...
was:
My pom: http://pastebin.com/BJ9zcXrg
felix@felix-DQ77PRO:~/workspaces/java/workspaceGastos/yyy-project$ mvn clean install -X
The debug output:
http://pastebin.com/cM8LbR62
The problem is here:
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null: IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal add-resource. Reason: null
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:118)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asList(ModelValue.java:132)
at org.jboss.dmr.ModelNode.asList(ModelNode.java:1302)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.resourceExists(AddResourceMojo.java:258)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.addCompositeResource(AddResourceMojo.java:180)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.processResources(AddResourceMojo.java:148)
at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:112)
... 21 more
Same problem:
http://stackoverflow.com/questions/22533311/wildfly-maven-plugin-not-depl...
Other:
http://stackoverflow.com/questions/21020926/add-an-xa-datasource-fails-wi...
> Could not execute goal add-resource / wildfly-maven-plugin
> ----------------------------------------------------------
>
> Key: JBASMP-66
> URL: https://issues.jboss.org/browse/JBASMP-66
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: deploy, wildfly
> Affects Versions: 7.5.Final
> Environment: Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T14:37:52-03:00)
> Maven home: /home/felix/Downloads/apache-maven-3.2.1
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-oracle/jre
> Default locale: pt_BR, platform encoding: UTF-8
> OS name: "linux", version: "3.8.0-35-generic", arch: "amd64", family: "unix"
> Reporter: Felix Coutinho
> Assignee: James Perkins
> Priority: Blocker
> Labels: maven, wildfly
>
> My pom: http://pastebin.com/BJ9zcXrg
> felix@felix-DQ77PRO:~/workspaces/java/workspaceGastos/yyy-project$ mvn clean install -X
> The debug output:
> http://pastebin.com/cM8LbR62
> The problem is here:
> {code}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null: IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:add-resource (add-datasource) on project logr: Could not execute goal add-resource. Reason: null
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal add-resource. Reason: null
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:118)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asList(ModelValue.java:132)
> at org.jboss.dmr.ModelNode.asList(ModelNode.java:1302)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.resourceExists(AddResourceMojo.java:258)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.addCompositeResource(AddResourceMojo.java:180)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.processResources(AddResourceMojo.java:148)
> at org.wildfly.plugin.deployment.resource.AddResourceMojo.execute(AddResourceMojo.java:112)
> ... 21 more
> {code}
> Same problem:
> http://stackoverflow.com/questions/22533311/wildfly-maven-plugin-not-depl...
> Other:
> http://stackoverflow.com/questions/21020926/add-an-xa-datasource-fails-wi...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3708) Websocket Error in Deployed War File (WildFly)
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3708?page=com.atlassian.jira.plugin.... ]
David Lloyd moved XNIO-233 to WFLY-3708:
----------------------------------------
Project: WildFly (was: XNIO)
Key: WFLY-3708 (was: XNIO-233)
> Websocket Error in Deployed War File (WildFly)
> ----------------------------------------------
>
> Key: WFLY-3708
> URL: https://issues.jboss.org/browse/WFLY-3708
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Tom Goldsmith
>
> In Immutant incremental 195, I am seeing the following error when I deploy a .war file to WildFly and try to connect to a websocket:
> 12:30:22,273 WARN [org.jboss.modules] (XNIO-2 I/O-1) Failed to define class org.xnio.ChannelListener$Setter in Module "deployment.websocket-wildfly-test-0.1.0-SNAPSHOT-standalone.war:main" from Service Module Loader: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/xnio/ChannelListener$Setter"
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0_05]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760) [rt.jar:1.8.0_05]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]
> at org.projectodd.wunderboss.websocket.UndertowWebsocket$1.onConnect(UndertowWebsocket.java:43) [wunderboss-web-1.x.incremental.98.jar:]
> at io.undertow.websockets.WebSocketProtocolHandshakeHandler$1.handleUpgrade(WebSocketProtocolHandshakeHandler.java:190) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.exchangeComplete(HttpReadListener.java:271) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpServerConnection.exchangeComplete(HttpServerConnection.java:221) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.invokeExchangeCompleteListeners(HttpServerExchange.java:1131) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.terminateResponse(HttpServerExchange.java:1351) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.Connectors.terminateResponse(Connectors.java:78) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.ServerFixedLengthStreamSinkConduit.channelFinished(ServerFixedLengthStreamSinkConduit.java:33) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.conduits.AbstractFixedLengthStreamSinkConduit.exitFlush(AbstractFixedLengthStreamSinkConduit.java:273) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.conduits.AbstractFixedLengthStreamSinkConduit.flush(AbstractFixedLengthStreamSinkConduit.java:207) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at org.xnio.conduits.ConduitStreamSinkChannel.flush(ConduitStreamSinkChannel.java:162) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at io.undertow.channels.DetachableStreamSinkChannel.flush(DetachableStreamSinkChannel.java:100) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.closeAndFlushResponse(HttpServerExchange.java:1489) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.endExchange(HttpServerExchange.java:1470) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.spi.AsyncWebSocketHttpServerExchange.endExchange(AsyncWebSocketHttpServerExchange.java:187) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.upgradeChannel(Handshake.java:121) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.performUpgrade(Handshake.java:114) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.performUpgrade(Handshake.java:142) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.version13.Hybi13Handshake.handshakeInternal(Hybi13Handshake.java:61) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.handshake(Handshake.java:92) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.WebSocketProtocolHandshakeHandler.handleRequest(WebSocketProtocolHandshakeHandler.java:196) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:56) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:57) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.SetHeaderHandler.handleRequest(SetHeaderHandler.java:49) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:156) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:91) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:45) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.2.0.Final.jar:3.2.0.Final]
> 12:30:22,282 ERROR [io.undertow.request] (XNIO-2 I/O-1) Blocking request failed HttpServerExchange{ GET /}: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/xnio/ChannelListener$Setter"
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0_05]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760) [rt.jar:1.8.0_05]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]
> at org.projectodd.wunderboss.websocket.UndertowWebsocket$1.onConnect(UndertowWebsocket.java:43) [wunderboss-web-1.x.incremental.98.jar:]
> at io.undertow.websockets.WebSocketProtocolHandshakeHandler$1.handleUpgrade(WebSocketProtocolHandshakeHandler.java:190) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.exchangeComplete(HttpReadListener.java:271) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpServerConnection.exchangeComplete(HttpServerConnection.java:221) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.invokeExchangeCompleteListeners(HttpServerExchange.java:1131) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.terminateResponse(HttpServerExchange.java:1351) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.Connectors.terminateResponse(Connectors.java:78) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.ServerFixedLengthStreamSinkConduit.channelFinished(ServerFixedLengthStreamSinkConduit.java:33) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.conduits.AbstractFixedLengthStreamSinkConduit.exitFlush(AbstractFixedLengthStreamSinkConduit.java:273) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.conduits.AbstractFixedLengthStreamSinkConduit.flush(AbstractFixedLengthStreamSinkConduit.java:207) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at org.xnio.conduits.ConduitStreamSinkChannel.flush(ConduitStreamSinkChannel.java:162) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at io.undertow.channels.DetachableStreamSinkChannel.flush(DetachableStreamSinkChannel.java:100) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.closeAndFlushResponse(HttpServerExchange.java:1489) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.HttpServerExchange.endExchange(HttpServerExchange.java:1470) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.spi.AsyncWebSocketHttpServerExchange.endExchange(AsyncWebSocketHttpServerExchange.java:187) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.upgradeChannel(Handshake.java:121) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.performUpgrade(Handshake.java:114) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.performUpgrade(Handshake.java:142) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.version13.Hybi13Handshake.handshakeInternal(Hybi13Handshake.java:61) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.core.protocol.Handshake.handshake(Handshake.java:92) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.websockets.WebSocketProtocolHandshakeHandler.handleRequest(WebSocketProtocolHandshakeHandler.java:196) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:56) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:57) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.handlers.SetHeaderHandler.handleRequest(SetHeaderHandler.java:49) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:156) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:91) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:45) [undertow-core-1.0.15.Final.jar:1.0.15.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.2.0.Final.jar:3.2.0.Final]
> (that is the whole stacktrace).
> A sample app that reproduces this scenario for me can be found at the following link: https://dl.dropboxusercontent.com/u/37542498/websocket-wildfly-test.zip
> I am creating my .war file with lein-ring. The following command is used in terminal: lein ring uberwar
> I am then deploying to WildFly standalone by running the following commands from the WildFly bin:
> Terminal Tab #1:
> ./standalone
> Terminal Tab #2:
> ./jboss-cli.sh
> connect
> deploy <path-to-war-file>/websocket-wildfly-test-0.1.0-SNAPSHOT-standalone.war
> I am then using http://www.websocket.org/echo.html to connect to the websocket on port 5000. When I click the "connect" button, the aforementioned stacktrace is seen in the standalone WildFly terminal tab.
> I have cleared my maven cache and done everything I can think of to make sure it is a completely fresh install.
> Thanks,
> Tom
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3706) Inconsistent DMR response structure
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3706?page=com.atlassian.jira.plugin.... ]
Brian Stansberry edited comment on WFLY-3706 at 8/4/14 11:22 AM:
-----------------------------------------------------------------
Do you have any more info on what the conditions were when this happened? Testing against master, the EAP 6.x branch and an EAP 6.2.2 build I have I get this:
{code}
[domain@localhost:9999 /] /profile=full/subsystem=ejb3/service=*:read-resource-description
{
"outcome" => "failed",
"failure-description" => "JBAS014883: No resource definition is registered for address [
(\"profile\" => \"full\"),
(\"subsystem\" => \"ejb3\"),
(\"service\" => \"*\")
]",
"rolled-back" => true
}
{code}
Was the 'rbac' provider enabled? Maybe that matters.
My EAP 6.x branch may be a a week or so out of date; I'll update and rebuild in case that matters.
was (Author: brian.stansberry):
Do you have any more info on what the conditions were when this happened? Testing against master, the EAP 6.x branch and an EAP 6.2.2 build I have I get this:
```
[domain@localhost:9999 /] /profile=full/subsystem=ejb3/service=*:read-resource-description
{
"outcome" => "failed",
"failure-description" => "JBAS014883: No resource definition is registered for address [
(\"profile\" => \"full\"),
(\"subsystem\" => \"ejb3\"),
(\"service\" => \"*\")
]",
"rolled-back" => true
}
```
Was the 'rbac' provider enabled? Maybe that matters.
My EAP 6.x branch may be a a week or so out of date; I'll update and rebuild in case that matters.
> Inconsistent DMR response structure
> -----------------------------------
>
> Key: WFLY-3706
> URL: https://issues.jboss.org/browse/WFLY-3706
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
>
> {noformat}
> {
> "address" => [
> ("profile" => "full"),
> ("subsystem" => "ejb3"),
> ("service" => "*")
> ],
> "operation" => "read-resource-description"
> }
> {
> "outcome" => "success",
> "result" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014883: No resource definition is registered for address [
> (\"profile\" => \"full\"),
> (\"subsystem\" => \"ejb3\"),
> (\"service\" => \"*\")
> ]",
> "rolled-back" => true
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3706) Inconsistent DMR response structure
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3706?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3706:
----------------------------------------
Do you have any more info on what the conditions were when this happened? Testing against master, the EAP 6.x branch and an EAP 6.2.2 build I have I get this:
```
[domain@localhost:9999 /] /profile=full/subsystem=ejb3/service=*:read-resource-description
{
"outcome" => "failed",
"failure-description" => "JBAS014883: No resource definition is registered for address [
(\"profile\" => \"full\"),
(\"subsystem\" => \"ejb3\"),
(\"service\" => \"*\")
]",
"rolled-back" => true
}
```
Was the 'rbac' provider enabled? Maybe that matters.
My EAP 6.x branch may be a a week or so out of date; I'll update and rebuild in case that matters.
> Inconsistent DMR response structure
> -----------------------------------
>
> Key: WFLY-3706
> URL: https://issues.jboss.org/browse/WFLY-3706
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
>
> {noformat}
> {
> "address" => [
> ("profile" => "full"),
> ("subsystem" => "ejb3"),
> ("service" => "*")
> ],
> "operation" => "read-resource-description"
> }
> {
> "outcome" => "success",
> "result" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014883: No resource definition is registered for address [
> (\"profile\" => \"full\"),
> (\"subsystem\" => \"ejb3\"),
> (\"service\" => \"*\")
> ]",
> "rolled-back" => true
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3707) ":read-log-file" op throws OutOfMemoryError for big values of parameter "lines"
by Harald Pehl (JIRA)
Harald Pehl created WFLY-3707:
---------------------------------
Summary: ":read-log-file" op throws OutOfMemoryError for big values of parameter "lines"
Key: WFLY-3707
URL: https://issues.jboss.org/browse/WFLY-3707
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Reporter: Harald Pehl
Assignee: James Perkins
When passing big values for parameter "line" of the ":read-log-file" operation the servers throws an OutOfMemoryError.
Maybe the parameter should be limited to a reasonable max-value.
If #lines(log-file) < parameter(lines) no OOME should happen at all.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBBUILD-738) Wrong link in the web
by David Hladky (JIRA)
David Hladky created JBBUILD-738:
------------------------------------
Summary: Wrong link in the web
Key: JBBUILD-738
URL: https://issues.jboss.org/browse/JBBUILD-738
Project: JBoss Build System
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: David Hladky
Assignee: Paul Gier
I checked the links mentioned in ORG-2187. I browsed the web page and it is wrong there as well. It is not clear what are the proper links so I am opening a ticket here.
For more details see ORG-2187
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-2524) logging-profile works for a servlet, but doesn't for a JSP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2524?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2524:
-----------------------------------------------
Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1031448|https://bugzilla.redhat.com/show_bug.cgi?id=1031448] from NEW to ASSIGNED
> logging-profile works for a servlet, but doesn't for a JSP
> ----------------------------------------------------------
>
> Key: WFLY-2524
> URL: https://issues.jboss.org/browse/WFLY-2524
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: 8.0.0.Beta1
> Reporter: Osamu Nagano
> Assignee: James Perkins
> Attachments: logone.zip
>
>
> Suppose the following logging-profile has been set in logging subsystem, and a web app has a proper entry in its MANIFEST.MF ({{Logging-Profile: logone}}). Then all messages via "com.example.logone" logger should go into a file, logone.log. It does so with a logger got in a servlet, but it doesn't work a logger got in a JSP.
> {code}
> <logging-profiles>
> <logging-profile name="logone">
> <file-handler name="logone">
> <level name="INFO"/>
> <file relative-to="jboss.server.log.dir" path="logone.log"/>
> </file-handler>
> <logger category="com.example.logone">
> <level name="INFO"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="logone"/>
> </handlers>
> </root-logger>
> </logging-profile>
> </logging-profiles>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months