gpars (Groovy Parallel Systems)

caling stop() within a DynamicDispatchActor inMessage() when there is an afterStop() causes exception when called from Java

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 0.12
  • Fix Version/s: 1.0.0
  • Component/s: Actors
  • Labels:
    None
  • Environment:
    Linux, Java 6
  • Number of attachments :
    2

Description

Take the StatelessActorTest.java, and add a stop() to the onMessage(), add an afterStop() handler as well.

The following exception is seen...

An exception occurred in the Actor thread Actor Thread 2
java.lang.ArrayIndexOutOfBoundsException: 0
at org.codehaus.groovy.reflection.ParameterTypes.coerceArgumentsToClasses(ParameterTypes.java:138)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:231)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1058)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:886)
at org.codehaus.groovy.runtime.InvokerHelper.invokePojoMethod(InvokerHelper.java:781)
at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:772)
at groovyx.gpars.actor.Actor.callDynamic(Actor.java:345)
at groovyx.gpars.actor.Actor.handleTermination(Actor.java:301)
at groovyx.gpars.actor.AbstractLoopingActor$1.handleMessage(AbstractLoopingActor.java:86)
at groovyx.gpars.util.AsyncMessagingCore.run(AsyncMessagingCore.java:132)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

  1. File
    gparsbug.groovy
    15/Nov/11 2:38 AM
    1.0 kB
    Jim Morris
  2. Java Source File
    StatelessActorTest.java
    15/Nov/11 2:27 AM
    2 kB
    Jim Morris

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jim Morris added a comment -

This also happens in 1.0.0-snapshot

Show
Jim Morris added a comment - This also happens in 1.0.0-snapshot
Hide
Permalink
Jim Morris added a comment -

Attached is the junit test modified version that demonstrates the issue

Show
Jim Morris added a comment - Attached is the junit test modified version that demonstrates the issue
Hide
Permalink
Jim Morris added a comment -

Also happens in groovy, see attached example.

Show
Jim Morris added a comment - Also happens in groovy, see attached example.
Hide
Permalink
Vaclav Pech added a comment -

The afterStop() method needs to take an argument - a list of unconsumed messages.
I'm thinking that the API should allow for parameter-less afterStop() methods as well.

Show
Vaclav Pech added a comment - The afterStop() method needs to take an argument - a list of unconsumed messages. I'm thinking that the API should allow for parameter-less afterStop() methods as well.
Hide
Permalink
Jim Morris added a comment -

ok that does not appear to be documented yet. in java what would I pass in as an argument? an Object[] if so how big?

Show
Jim Morris added a comment - ok that does not appear to be documented yet. in java what would I pass in as an argument? an Object[] if so how big?
Hide
Permalink
Jim Morris added a comment -

adding

public void afterStop(List undeliveredMessages)

{ System.out.println("afterStop()"); }

seems to work, thanks

Show
Jim Morris added a comment - adding public void afterStop(List undeliveredMessages) { System.out.println("afterStop()"); } seems to work, thanks
Hide
Permalink
Vaclav Pech added a comment -

Right, List is the expected type.

Show
Vaclav Pech added a comment - Right, List is the expected type.

People

  • Assignee:
    Vaclav Pech
    Reporter:
    Jim Morris
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: