You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <ui...@incubator.apache.org> on 2008/04/05 00:50:24 UTC
[jira] Created: (UIMA-959) Scaleout doc wrongly implies Vinci and
AS services can be in same aggregate
Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
---------------------------------------------------------------------------
Key: UIMA-959
URL: https://issues.apache.org/jira/browse/UIMA-959
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.2.2AS
Reporter: Burn Lewis
Priority: Minor
Fix For: 2.2.2AS
In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
be used as a primitive analysis engine in a deployment descriptor
We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
If not in an aggregate we get:
org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-959) Scaleout doc wrongly implies Vinci and
AS services can be in same aggregate
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein updated UIMA-959:
-------------------------------
Fix Version/s: (was: 2.2.2AS)
Added to known issues in the README file for UIMA-AS.
> Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
> ---------------------------------------------------------------------------
>
> Key: UIMA-959
> URL: https://issues.apache.org/jira/browse/UIMA-959
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2AS
> Reporter: Burn Lewis
> Priority: Minor
> Attachments: UIMA-959.patch
>
>
> In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
> A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
> be used as a primitive analysis engine in a deployment descriptor
> We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
> If not in an aggregate we get:
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-959) Scaleout doc wrongly implies Vinci and
AS services can be in same aggregate
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein resolved UIMA-959.
--------------------------------
Resolution: Fixed
Assignee: Eddie Epstein
Documentation changed to clarify that a Vinci service should not be called from within a UIMA AS service.
> Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
> ---------------------------------------------------------------------------
>
> Key: UIMA-959
> URL: https://issues.apache.org/jira/browse/UIMA-959
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2AS
> Reporter: Burn Lewis
> Assignee: Eddie Epstein
> Priority: Minor
> Attachments: UIMA-959.patch
>
>
> In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
> A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
> be used as a primitive analysis engine in a deployment descriptor
> We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
> If not in an aggregate we get:
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-959) Scaleout doc wrongly implies Vinci and
AS services can be in same aggregate
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis updated UIMA-959:
----------------------------
Attachment: UIMA-959.patch
FWIW here's a JUnit test that verifies that a JMS client service descriptor when wrapped in an aggregate deployed as an AS primitive WILL work with regular AS delegates. I've verified that the more useful case with a Vinci service descriptor also works but that's not tested here. If we want to remove the wrapping requirement this test can be easily modified.
> Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
> ---------------------------------------------------------------------------
>
> Key: UIMA-959
> URL: https://issues.apache.org/jira/browse/UIMA-959
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2AS
> Reporter: Burn Lewis
> Priority: Minor
> Fix For: 2.2.2AS
>
> Attachments: UIMA-959.patch
>
>
> In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
> A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
> be used as a primitive analysis engine in a deployment descriptor
> We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
> If not in an aggregate we get:
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-959) Scaleout doc wrongly implies Vinci and
AS services can be in same aggregate
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589114#action_12589114 ]
Burn Lewis commented on UIMA-959:
---------------------------------
Correction: the original error message occurred when trying to use a JMS service descriptor ... here's the one for Vinci:
java.lang.ClassCastException: org.apache.uima.resource.impl.URISpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
Get the same error if deploying a Vinci service descriptor as an async primitive.
Full stack trace is:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'primitive_ctlr_NoOp_1.2' defined in URL [file:C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/UIMAdd2springOutput64014.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.URISpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.URISpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
Caused by: java.lang.ClassCastException: org.apache.uima.resource.impl.URISpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
at org.apache.uima.aae.controller.BaseAnalysisEngineController.getComponentName(BaseAnalysisEngineController.java:536)
at org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.registerChildController(AggregateAnalysisEngineController_impl.java:176)
at org.apache.uima.aae.controller.BaseAnalysisEngineController.<init>(BaseAnalysisEngineController.java:264)
at org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.<init>(PrimitiveAnalysisEngineController_impl.java:117)
at org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.<init>(PrimitiveAnalysisEngineController_impl.java:113)
at org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.<init>(PrimitiveAnalysisEngineController_impl.java:103)
at org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.<init>(PrimitiveAnalysisEngineController_impl.java:98)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:85)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:186)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:799)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:717)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:384)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:93)
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:77)
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:67)
at org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.deploy(SpringContainerDeployer.java:200)
at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.deploy(BaseUIMAAsynchronousEngine_impl.java:487)
at org.apache.uima.ee.test.utils.BaseTestSupport.deployService(BaseTestSupport.java:76)
at org.apache.uima.ee.test.TestUimaASExtended.testDeployAggregateWithJmsService(TestUimaASExtended.java:456)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
> ---------------------------------------------------------------------------
>
> Key: UIMA-959
> URL: https://issues.apache.org/jira/browse/UIMA-959
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2AS
> Reporter: Burn Lewis
> Priority: Minor
> Attachments: UIMA-959.patch
>
>
> In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
> A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
> be used as a primitive analysis engine in a deployment descriptor
> We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
> If not in an aggregate we get:
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.