[JBoss JIRA] (WFLY-937) ServletContext.getResource() doesn't work correctly for files containing hash characters
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-937?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas resolved WFLY-937.
---------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
> ServletContext.getResource() doesn't work correctly for files containing hash characters
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-937
> URL: https://issues.jboss.org/browse/WFLY-937
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.CR1
> Environment: Linux 3.2.0-30-generic Ubuntu SMP x86_64 GNU/Linux
> Reporter: Christian Kaltepoth
> Assignee: Stuart Douglas
> Fix For: 8.0.1.Final
>
> Attachments: as7-url-bug.zip
>
>
> {{ServletContext.getResource()}} returns an invalid URL if the file name contains {{#}} characters.
> Example:
> {code:java}
> URL url = servletContext.getResource("/file#1.txt");
> {code}
> The resulting URL object will be spitted at the {{#}} character like this:
> {code}
> url.toString(): jndi:/default-host/tomcat-url-bug/file#1.txt
> url.getPath(): /default-host/tomcat-url-bug/file
> url.getRef(): 1.txt
> {code}
> Calling {{url.openStream()}} will throw a {{FileNotFoundException}}.
> This is a known Tomcat issue fixed in 7.0.28.
> References:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=53257
> https://issues.apache.org/bugzilla/show_bug.cgi?id=51584
> According to the discussion on the Tomcat issue tracker, there are also problems for other characters which have special meaning in URLs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3087) Websocket NullPointerException on io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler.handleBinaryMessage(AnnotatedEndpoint.java:373)
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3087?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-3087.
----------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
> Websocket NullPointerException on io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler.handleBinaryMessage(AnnotatedEndpoint.java:373)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3087
> URL: https://issues.jboss.org/browse/WFLY-3087
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Environment: windows server 2008
> Reporter: Admin FlirtyMob
> Assignee: Stuart Douglas
> Fix For: 8.0.1.Final
>
>
> 2014-03-07 17:10:49,208 ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception: java.lang.NullPointerException
> at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler.handleBinaryMessage(AnnotatedEndpoint.java:373)
> at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler.access$1100(AnnotatedEndpoint.java:126)
> at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler$6.complete(AnnotatedEndpoint.java:332)
> at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler$6.complete(AnnotatedEndpoint.java:329)
> at io.undertow.websockets.core.BufferedBinaryMessage.read(BufferedBinaryMessage.java:76)
> at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$AnnotatedEndpointFrameHandler.onBinary(AnnotatedEndpoint.java:329)
> at io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:24)
> at io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:15)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:615)
> at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:601)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:531) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3113) Websocket connection fails when connecting to protected URL (basic login)
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3113?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-3113.
----------------------------------
Resolution: Rejected
As far as I can tell Undertow is behaving as it should.
> Websocket connection fails when connecting to protected URL (basic login)
> -------------------------------------------------------------------------
>
> Key: WFLY-3113
> URL: https://issues.jboss.org/browse/WFLY-3113
> Project: WildFly
> Issue Type: Clarification
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: WildFly 8.0.0.Final, Windows 8, RedHat Linux
> Chrome, Firefox
> Reporter: Alexandre Nikolov
> Assignee: Stuart Douglas
> Labels: jsr356,, login
>
> In a sample application for JSR356 support, added security constraints with basic log-in. The websocket endpoint is protect with basic log-in.
> When a websocket connection is attempted to the protected URL, there is inconsistent behavior in different browsers:
> 1. Chrome fails with 401 error code and the log-in screen is not displayed at all.
> 2. Firefox displays the log-in screen and the websocket is created and opened after the log-in succeeds.
> But in a different application, using Atmosphere - both connections fails:
> 1. Chrome fails with the same error and the log-in screen is displayed after that. Most probably the log-in screen is triggered by Atmosphere when it falls back to long-polling
> 2. Firefox - The login screen is displayed and if the log-in suceeds, the socket is created, but Atmosphere fails to process it.
> For example if the context root is "jsr356test" and the protected path is /pubsub/protected, Atmosphere tries to map /jsr356test/pubsub/protected (which in JSR356 is Session#getRequestURI()) but has mapping set-up for /pubsub/protected (which for a Http request would be the path info)
> Here is the related discussion on the Atmosphere users group:
> https://groups.google.com/forum/#!topic/atmosphere-framework/ntIHOohlYIc
> There is test WAR and source in the Atmosphere forum to reproduce the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3093) Undertow doesn't show the correct error page (401)
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3093?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-3093.
----------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
> Undertow doesn't show the correct error page (401)
> --------------------------------------------------
>
> Key: WFLY-3093
> URL: https://issues.jboss.org/browse/WFLY-3093
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Juergen Zimmermann
> Assignee: Stuart Douglas
> Fix For: 8.0.1.Final
>
>
> I'm using the WildFly snapshot from last Thursday with Undertow 1.0.1.
> When I try to invoke a protected web page, I'm getting an almost blank web page with just the contents "401 - Unauthorized".
> However, in WEB-INF/web.xml I'm having this declaration:
> {code}
> <error-page>
> <error-code>401</error-code>
> <location>/rf/error/accessDenied.jsf</location>
> </error-page>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3146) Undertow Memory Leak for JAX-RS requests
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3146?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-3146.
-------------------------------
Assignee: Stuart Douglas (was: Tomaz Cerar)
Resolution: Done
Both component upgrades ware merged.
> Undertow Memory Leak for JAX-RS requests
> ----------------------------------------
>
> Key: WFLY-3146
> URL: https://issues.jboss.org/browse/WFLY-3146
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: Windows 7 Professional
> JDK 1.7.0_21
> WildFly 8.0.0.Final
> Reporter: Darren Jones
> Assignee: Stuart Douglas
> Priority: Critical
> Labels: MemoryLeak
> Fix For: 8.0.1.Final
>
> Attachments: hello-client.zip, hello-service-0.1-SNAPSHOT.war, hello-service.zip, JProfiler GC Root.png, server.keystore, standalone.xml, VisualVM Memory.png
>
>
> After half an hour or so of running the automated test suite for our application, the server hangs due to GC and many OutOfMemoryErrors appear in the WildFly server log.
> I've attached VisualVM and JProfiler, both of which demonstrate that many of the objects that are not being garbage collected are Undertow objects. Both tools show that the path to the GC root is via a Java nio SelectionKey, which is held by sun.nio.ch.WindowsSelectorImpl.
> I'll attach a screenshot of a JProfiler window to demonstrate, but VisualVM shows the same result (albeit presented differently).
> I have also found similar behaviour with a small, trivial example, as described in the Steps to Reproduce. It makes repeated calls to a simple RESTful call to a JAX-RS service. The example doesn't cause as fast a leak as our test suite, but it does demonstrate the problem.
> The example uses https for the call because it seems to leak memory faster than http - but http does also exhibit the problem.
> I have also tried patching WildFly 8.0.0.Final up to Undertow.1.0.2-SNAPSHOT and XNIO.3.3.0-SNAPSHOT (as of this morning), but the problem still occurs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3153) Testing legacy subsystem transformers between different versions of Wildlfy
by Emmanuel Hugonnet (JIRA)
Emmanuel Hugonnet created WFLY-3153:
---------------------------------------
Summary: Testing legacy subsystem transformers between different versions of Wildlfy
Key: WFLY-3153
URL: https://issues.jboss.org/browse/WFLY-3153
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 8.0.0.Final
Reporter: Emmanuel Hugonnet
Assignee: Brian Stansberry
The legacy web subsystem is still evolving. Thus we need to make the legacy web subsystem in WildFly evolve and test the transformers.
But testing the transformation between WildFly 8.0.0.Final and the next version of WildFly fails with the following exception :
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
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.jboss.as.subsystem.bridge.local.ScopedKernelServicesBootstrap.createChildClassLoaderKernelServices(ScopedKernelServicesBootstrap.java:85)
at org.jboss.as.subsystem.bridge.local.ScopedKernelServicesBootstrap.createKernelServices(ScopedKernelServicesBootstrap.java:53)
at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.install(SubsystemTestDelegate.java:771)
at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.access$700(SubsystemTestDelegate.java:644)
at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.build(SubsystemTestDelegate.java:616)
at org.jboss.as.web.test.WebSubsystemTestCase.testTransformation_2_0(WebSubsystemTestCase.java:443)
at org.jboss.as.web.test.WebSubsystemTestCase.testTransformationWildFly8(WebSubsystemTestCase.java:427)
Caused by: java.lang.IllegalArgumentException: JBAS014880: No operation entry called 'add' registered at '[("subsystem" => "web")]'
at org.jboss.as.controller.operations.validation.OperationValidator.throwOrWarnAboutDescriptorProblem(OperationValidator.java:549)
at org.jboss.as.controller.operations.validation.OperationValidator.validateOperation(OperationValidator.java:123)
at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:199)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:289)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256)
at java.lang.Thread.run(Thread.java:744)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3152) Failed initializing module org.jboss.as.logging
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3152?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-3152.
-------------------------------
Resolution: Rejected
This is not a bug. The error message explains the exact problem. If you need help, please use the user forums.
> Failed initializing module org.jboss.as.logging
> ------------------------------------------------
>
> Key: WFLY-3152
> URL: https://issues.jboss.org/browse/WFLY-3152
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Huu Loi Lai
> Priority: Blocker
>
> I try to run integration test with arquillian and wildfly and I get following erros:
> ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:314)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:294)
> at org.jboss.as.server.ServerService.boot(ServerService.java:356)
> at org.jboss.as.server.ServerService.boot(ServerService.java:331)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91)
> ... 10 more
> Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:98)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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:744)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3152) Failed initializing module org.jboss.as.logging
by Huu Loi Lai (JIRA)
Huu Loi Lai created WFLY-3152:
---------------------------------
Summary: Failed initializing module org.jboss.as.logging
Key: WFLY-3152
URL: https://issues.jboss.org/browse/WFLY-3152
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Huu Loi Lai
Priority: Blocker
I try to run integration test with arquillian and wildfly and I get following erros:
ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469)
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268)
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:314)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:294)
at org.jboss.as.server.ServerService.boot(ServerService.java:356)
at org.jboss.as.server.ServerService.boot(ServerService.java:331)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91)
... 10 more
Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103)
at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:98)
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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:744)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1811) Arithmetic Exception in MPerf when sending less than 10 messages
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1811?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1811:
---------------------------
Fix Version/s: 3.5
> Arithmetic Exception in MPerf when sending less than 10 messages
> ----------------------------------------------------------------
>
> Key: JGRP-1811
> URL: https://issues.jboss.org/browse/JGRP-1811
> Project: JGroups
> Issue Type: Bug
> Reporter: Andrei Palade
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> Not sure if this is intended to be like this, but in MPerf when the user tries to set the num_msg to 1 and start sending the messages, MPerf throws
> Mar 22, 2014 4:02:25 PM org.jgroups.logging.JDKLogImpl error
> SEVERE: failure unmarshalling buffer
> java.lang.ArithmeticException: / by zero
> at org.jgroups.tests.perf.MPerf.handleData(MPerf.java:418)
> at org.jgroups.tests.perf.MPerf.receive(MPerf.java:280)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:890)
> at org.jgroups.JChannel.up(JChannel.java:746)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:146)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.SEQUENCER.deliver(SEQUENCER.java:606)
> at org.jgroups.protocols.SEQUENCER.unwrapAndDeliver(SEQUENCER.java:573)
> at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:279)
> at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:308)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
> at org.jgroups.stack.Protocol.up(Protocol.java:409)
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:520)
> at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:927)
> at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:857)
> at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:792)
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:573)
> at org.jgroups.protocols.BARRIER.up(BARRIER.java:152)
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
> at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:199)
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:296)
> at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
> at org.jgroups.protocols.Discovery.up(Discovery.java:379)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1532)
> at org.jgroups.protocols.TP$3.run(TP.java:1466)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1811) Arithmetic Exception in MPerf when sending less than 10 messages
by Andrei Palade (JIRA)
Andrei Palade created JGRP-1811:
-----------------------------------
Summary: Arithmetic Exception in MPerf when sending less than 10 messages
Key: JGRP-1811
URL: https://issues.jboss.org/browse/JGRP-1811
Project: JGroups
Issue Type: Bug
Reporter: Andrei Palade
Assignee: Bela Ban
Priority: Minor
Not sure if this is intended to be like this, but in MPerf when the user tries to set the num_msg to 1 and start sending the messages, MPerf throws
Mar 22, 2014 4:02:25 PM org.jgroups.logging.JDKLogImpl error
SEVERE: failure unmarshalling buffer
java.lang.ArithmeticException: / by zero
at org.jgroups.tests.perf.MPerf.handleData(MPerf.java:418)
at org.jgroups.tests.perf.MPerf.receive(MPerf.java:280)
at org.jgroups.JChannel.invokeCallback(JChannel.java:890)
at org.jgroups.JChannel.up(JChannel.java:746)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:146)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
at org.jgroups.protocols.SEQUENCER.deliver(SEQUENCER.java:606)
at org.jgroups.protocols.SEQUENCER.unwrapAndDeliver(SEQUENCER.java:573)
at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:279)
at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:308)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
at org.jgroups.stack.Protocol.up(Protocol.java:409)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294)
at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:520)
at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:927)
at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:857)
at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:792)
at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:573)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:152)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:199)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:296)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
at org.jgroups.protocols.Discovery.up(Discovery.java:379)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1532)
at org.jgroups.protocols.TP$3.run(TP.java:1466)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months