[jira] Created: (UIMA-1672) BaseAnalysisEngineController.stopCasMultiplier should log stopping also to log file
BaseAnalysisEngineController.stopCasMultiplier should log stopping also to log file --- Key: UIMA-1672 URL: https://issues.apache.org/jira/browse/UIMA-1672 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial Fix For: 2.3AS The mentioned method should log in line 2045 also to the logger: System.out.println( Instance Hashcode: + hashCode() + Controller: + getComponentName() + Stopping Collocated Delegate Cas Multiplier: + casMultiplier.getKey()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1673) uimaee_messages.properties contains key UIMAEE_stopping_collocated_cm_INFO twice
uimaee_messages.properties contains key UIMAEE_stopping_collocated_cm_INFO twice
Key: UIMA-1673
URL: https://issues.apache.org/jira/browse/UIMA-1673
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jörn Kottmann
Priority: Trivial
Fix For: 2.3AS
The file contains the key twice:
UIMAEE_stopping_collocated_cm_INFO = Controller: {0} Stopping Collocated
Delegate Cas Multiplier: {1}
UIMAEE_stopping_collocated_cm_INFO = Controller: {0} Stopping Remote Delegate
Cas Multiplier: {1}
Maybe the second one should be UIMAEE_stopping_remote_cm_INFO, can someone
please confirm that?
At least UIMAEE_stopping_remote_cm_INFO is used at BaseAnalysisEngineController
line 2040, but does
not occur in uimaee_messages.properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1674) Exception thrown from CasMultiplier.process should be reported to client as failure
Exception thrown from CasMultiplier.process should be reported to client as failure --- Key: UIMA-1674 URL: https://issues.apache.org/jira/browse/UIMA-1674 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Fix For: 2.3AS The first Analysis Engine in our uima-as setup is a CasMultiplier, we implement the process method and from this method our implementation throws a RuntimeException, not nice but it can happen. In the client interface we get the CAS back, but EntityProcessStatus.isException returns false, but it should return true and provide the exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1675) UIMA AS client does not log time out error correctly
UIMA AS client does not log time out error correctly
Key: UIMA-1675
URL: https://issues.apache.org/jira/browse/UIMA-1675
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jörn Kottmann
Priority: Trivial
Fix For: 2.3AS
This is the log from the client (written to console):
INFO: Timeout While Waiting For Reply From Delegate:SearchQueueUima Process CAS
Request Timed Out. Configured Reply Window Of 120,000. Cas Reference
Id:5679462b:12511e6d9cf:-7fcc
Nov 20, 2009 3:05:38 PM
org.apache.uima.adapter.jms.client.ClientServiceDelegate handleError
INFO: Process Timeout. Uima AS Client Didnt Receive Process Reply Within
Configured Window Of: {0}
But should be: ... Configured Window Of: 120,000
And it should be logged with unit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1673) uimaee_messages.properties contains key UIMAEE_stopping_collocated_cm_INFO twice
[
https://issues.apache.org/jira/browse/UIMA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann resolved UIMA-1673.
-
Resolution: Fixed
Assignee: Jerry Cwiklik
Please review and close issue.
uimaee_messages.properties contains key UIMAEE_stopping_collocated_cm_INFO
twice
Key: UIMA-1673
URL: https://issues.apache.org/jira/browse/UIMA-1673
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jörn Kottmann
Assignee: Jerry Cwiklik
Priority: Trivial
Fix For: 2.3AS
The file contains the key twice:
UIMAEE_stopping_collocated_cm_INFO = Controller: {0} Stopping Collocated
Delegate Cas Multiplier: {1}
UIMAEE_stopping_collocated_cm_INFO = Controller: {0} Stopping Remote
Delegate Cas Multiplier: {1}
Maybe the second one should be UIMAEE_stopping_remote_cm_INFO, can someone
please confirm that?
At least UIMAEE_stopping_remote_cm_INFO is used at
BaseAnalysisEngineController line 2040, but does
not occur in uimaee_messages.properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1672) BaseAnalysisEngineController.stopCasMultiplier should log stopping also to log file
[ https://issues.apache.org/jira/browse/UIMA-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann resolved UIMA-1672. - Resolution: Fixed Assignee: Jerry Cwiklik Please review and close. BaseAnalysisEngineController.stopCasMultiplier should log stopping also to log file --- Key: UIMA-1672 URL: https://issues.apache.org/jira/browse/UIMA-1672 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Assignee: Jerry Cwiklik Priority: Trivial Fix For: 2.3AS The mentioned method should log in line 2045 also to the logger: System.out.println( Instance Hashcode: + hashCode() + Controller: + getComponentName() + Stopping Collocated Delegate Cas Multiplier: + casMultiplier.getKey()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780572#action_12780572 ] Jörn Kottmann commented on UIMA-1649: - Thanks, seems to work now :-) deployAsyncService.sh log4j warnings - Key: UIMA-1649 URL: https://issues.apache.org/jira/browse/UIMA-1649 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial Fix For: 2.3AS When starting with deployAsyncService.sh there is log4j warning: log4j:WARN No appenders could be found for logger (org.springframework.context.support.FileSystemXmlApplicationContext). log4j:WARN Please initialize the log4j system properly. Maybe I am doing something wrong ? Otherwise I think a default log4j.properties should be provided ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
UIMA AS extended tests just hang
Hi, I tried to add a test to the extended tests, but when I execute them they just hang. Jörn Console output: ... UIMA AS Client - Shared JMS Connection Not Closed. Current Client Instance Count1 UIMA AS Client Undeployed All Containers Nov 20, 2009 4:29:42 PM org.apache.uima.adapter.jms.activemq.JmsOutputChannel stop INFO: Controller: NoOpAnnotatorQueue Output Channel Shutdown Completed Nov 20, 2009 4:29:42 PM org.apache.uima.aae.controller.AnalysisEngineInstancePoolWithThreadAffinity abort INFO: NoOpAnnotator Calling Destroy On AE instance # 0 Nov 20, 2009 4:29:42 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection destroy INFO: UIMA AS Client Terminated. Shared Connection Still Open. Current Client Count:1 getMeta Timeout on delegate:NoOpAnnotatorQueue runTest: Initialization Received Reply Containing Exception: Stopping Uima AS Client API. Service Not Responding To a Ping. Nov 20, 2009 4:29:57 PM org.apache.uima.aae.delegate.Delegate$1 Delegate.TimerTask.run INFO: Timeout While Waiting For Reply From Delegate:NoOpAnnotatorQueue GetMeta Request Timed Out. Configured Reply Window Of 60,000. Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl notifyOnTimout INFO: Request For Metadata Has Timed-out. Service Queue:NoOpAnnotatorQueue org.apache.uima.aae.error.UimaASMetaRequestTimeout at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyOnTimout(BaseUIMAAsynchronousEngineCommon_impl.java:1872) at org.apache.uima.adapter.jms.client.ClientServiceDelegate.handleError(ClientServiceDelegate.java:152) at org.apache.uima.aae.delegate.Delegate$1.run(Delegate.java:624) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.ClientServiceDelegate handleError INFO: Request For Metadata Has Timed-out. Service Queue:NoOpAnnotatorQueue Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl stop INFO: Stopping Asynchronous Client. Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl stop INFO: Asynchronous Client Has Stopped. Nov 20, 2009 4:29:57 PM org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl terminate INFO: Controller: NoOpAnnotator Received Terminate Event Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsInputChannel stop INFO: Stopping Service JMS Transport. Service: NoOpAnnotatorQueue Service:NoOpAnnotator Message Channel:queue://NoOpAnnotatorQueue Selector:Command=2000 OR Command=2002 Stopped Service:NoOpAnnotator Message Channel:queue://NoOpAnnotatorQueue Selector:Command=2001 Stopped Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsInputChannel stop INFO: Stopping Service JMS Transport. Service: NoOpAnnotatorQueue Nov 20, 2009 4:29:57 PM org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl stop INFO: Stopping Controller: NoOpAnnotator Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsOutputChannel stop INFO: Controller: NoOpAnnotatorQueue Aborted Connection To Endpoint: ID:karkand-54505-1258730845595-3:3664:4 and Broker Uri: tcp://localhost:8200 Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsOutputChannel stop INFO: Controller: NoOpAnnotatorQueue Aborted Connection To Endpoint: ID:karkand-54505-1258730845595-3:3664:1 and Broker Uri: tcp://localhost:8200 Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsOutputChannel stop INFO: Controller: NoOpAnnotatorQueue Aborted Connection To Endpoint: ID:karkand-54505-1258730845595-3:3664:2 and Broker Uri: tcp://localhost:8200 Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl initialize WARNING: Aborting Asynchronous Client Due to: Metadata Timeout Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl notifyOnInitializationFailure WARNING: Top Level Controller Initialization Exception. Cause: org.apache.uima.resource.ResourceInitializationException org.apache.uima.resource.ResourceInitializationException at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.initialize(BaseUIMAAsynchronousEngine_impl.java:668) at org.apache.uima.ee.test.utils.BaseTestSupport.initialize(BaseTestSupport.java:169) at org.apache.uima.ee.test.TestUimaASExtended.access$3(TestUimaASExtended.java:1) at org.apache.uima.ee.test.TestUimaASExtended$1.run(TestUimaASExtended.java:438) Caused by: org.apache.uima.aae.error.UimaASMetaRequestTimeout ... 4 more JMS Connection to Broker: tcp://localhost:8200 Closed Service:NoOpAnnotator Stopped UIMA AS Client - Shared JMS Connection Closed UIMA AS Client Undeployed All Containers Nov 20, 2009 4:29:57 PM org.apache.uima.adapter.jms.activemq.JmsOutputChannel stop INFO:
UIMA AS console input
Press 'q'+'Enter' to quiesce and stop the service or 's'+'Enter' to stop it now. Note: selected option is not echoed on the console. On Ubuntu Linux it is echoed to the console (connected via ssh to the machine). Jörn
Re: UIMA AS console input
Jörn Kottmann wrote: Press 'q'+'Enter' to quiesce and stop the service or 's'+'Enter' to stop it now. Note: selected option is not echoed on the console. On Ubuntu Linux it is echoed to the console (connected via ssh to the machine). How nice :-)... I guess we need to say Note: selection option *may not* be echoed -Marshall Jörn
[jira] Closed: (UIMA-1675) UIMA AS client does not log time out error correctly
[
https://issues.apache.org/jira/browse/UIMA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1675.
---
Resolution: Fixed
A message that was being logged had an apostrophe that has to be escaped to
work correctly. There were multiple instances where this had to be done both in
uima-as-jms and uima-as-core property files.
UIMA AS client does not log time out error correctly
Key: UIMA-1675
URL: https://issues.apache.org/jira/browse/UIMA-1675
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jörn Kottmann
Priority: Trivial
Fix For: 2.3AS
This is the log from the client (written to console):
INFO: Timeout While Waiting For Reply From Delegate:SearchQueueUima Process
CAS Request Timed Out. Configured Reply Window Of 120,000. Cas Reference
Id:5679462b:12511e6d9cf:-7fcc
Nov 20, 2009 3:05:38 PM
org.apache.uima.adapter.jms.client.ClientServiceDelegate handleError
INFO: Process Timeout. Uima AS Client Didnt Receive Process Reply Within
Configured Window Of: {0}
But should be: ... Configured Window Of: 120,000
And it should be logged with unit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1649) deployAsyncService.sh log4j warnings
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1649. --- Resolution: Fixed Modified to define LOG4J_CONFIG_FILE in case the UIMA AS is not installed. It is being set to a NO OP. It is only done to satisfy java command line parser. The change is shown below: @rem Check if Uima AS is installed, and if so set the default log4j configuration file @if EXIST %UIMA_HOME%\as_config (set LOG4J_CONFIG_FILE=-Dlog4j.configuration=file:%UIMA_HOME%\as_config\log4j.properties) else (set LOG4J_CONFIG_FILE=-DNoOp) deployAsyncService.sh log4j warnings - Key: UIMA-1649 URL: https://issues.apache.org/jira/browse/UIMA-1649 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial Fix For: 2.3AS When starting with deployAsyncService.sh there is log4j warning: log4j:WARN No appenders could be found for logger (org.springframework.context.support.FileSystemXmlApplicationContext). log4j:WARN Please initialize the log4j system properly. Maybe I am doing something wrong ? Otherwise I think a default log4j.properties should be provided ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1674) Exception thrown from CasMultiplier.process should be reported to client as failure
[ https://issues.apache.org/jira/browse/UIMA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780770#action_12780770 ] Jerry Cwiklik commented on UIMA-1674: - Jorn, can you describe your setup in more detail. As I understand it, your client is connecting to a remote UIMA AS aggregate that has a CM and possibly other delegate services. Is the CM in the same jvm as the aggregate or remote? In the client, do you use sendAndReceive() or sendCAS(). Is there any indication in the Uima AS service log that there was a problem processing a CAS? The ResourceProcessException should be thrown from the AE (CM or not), if there is a problem processing a CAS. There should also be an entry in the uima log made by a client if it receives an exception instead of a CAS in the process reply. Thanks, Jerry Exception thrown from CasMultiplier.process should be reported to client as failure --- Key: UIMA-1674 URL: https://issues.apache.org/jira/browse/UIMA-1674 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Fix For: 2.3AS The first Analysis Engine in our uima-as setup is a CasMultiplier, we implement the process method and from this method our implementation throws a RuntimeException, not nice but it can happen. In the client interface we get the CAS back, but EntityProcessStatus.isException returns false, but it should return true and provide the exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
