5 Replies Latest reply on Oct 19, 2013 9:23 AM by julien_viet

"Unexpected callable present in Drone Context" issue with Drone 1.2.0

julien_viet Oct 18, 2013 4:00 PM

Hi all

I'm getting this issue when migrating from Drone 1.2.0.Alpha2 to Drone 1.2.0.Final:

java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment.
  at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57)
  at org.jboss.arquillian.drone.webdriver.augmentation.AugmentingEnhancer.canEnhance(AugmentingEnhancer.java:75)
  at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:112)
  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:601)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
  at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
  at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
  at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83)
  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:601)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
  at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
  at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
  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:601)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
  at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
  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:601)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
  at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87)
  at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204)
  at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
  at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
  at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
  at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
  at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
  at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
  at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
  at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
  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:601)
  at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
  at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
  at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
  at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
  at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)

This happens in the Juzu project, if you want to give a try I pushed the migration attempt in the Juzu GitHub repo in a specific branch.

Julien

1. Re: "Unexpected callable present in Drone Context" issue with Drone 1.2.0

kenfinni Oct 18, 2013 4:17 PM (in response to julien_viet)

Julien,

Are there any messages before that one?

I've usually found that error occurring when the container being tested against has not started correctly

Ken
Actions
2. Re: Re: "Unexpected callable present in Drone Context" issue with Drone 1.2.0

julien_viet Oct 18, 2013 4:34 PM (in response to kenfinni)
Hi Ken,

it does not look like there is one. You can see by yourself by cloning the GitHub project (drone-1.2.0.Final branch) and for instance run the test juzu.impl.bridge.servlet.RouteViewDefaultMappingTestCase from the core module:

> git clone git@github.com:juzu/juzu.git > git checkout drone-1.2.0.Final > mvn test -Dtest=juzu.impl.bridge.servlet.RouteViewDefaultMappingTestCase

By the way this happens at the end of the test that seems to pass.
Actions
3. Re: "Unexpected callable present in Drone Context" issue with Drone 1.2.0

julien_viet Oct 19, 2013 2:56 AM (in response to julien_viet)

So I found the cause of the issue after a night of sleep.

My test classes have twice the @Drone injection, in the test abstract parent class (AbstractRoutePathMappingTestCase) and in the test class itself (RouteViewDefaultMappingTestCase). The code in DroneEnhancer iterates over the injected fields and fire an event in deenhanceDrone method. The event is fine on the first field but fails on the second field with the exception listed above:

1st event : holder is instance of org.openqa.selenium.htmlunit.HtmlUnitDriver
2nd event : holder is instance of org.jboss.arquillian.drone.impl.DroneCallableCreator$1

The issue is resolved if I get only one field injected which is fine for me.

Obviously I believe that there is a bug to fix here :-)
1 of 1 people found this helpful
Actions
4. Re: Re: "Unexpected callable present in Drone Context" issue with Drone 1.2.0

aslak Oct 19, 2013 6:09 AM (in response to julien_viet)

Could you file a jira issue on this one.. ?
Actions
5. Re: "Unexpected callable present in Drone Context" issue with Drone 1.2.0

julien_viet Oct 19, 2013 9:23 AM (in response to aslak)

there you are : [ARQ-1543] Unexpected ISE "Unexpected callable present in Drone Context, should be already instantiated at this moment."…
Actions

Go to original post