[jira] Updated: (UIMA-1658) UIMA AS worker does not respond to client initialize after failover
[ https://issues.apache.org/jira/browse/UIMA-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-1658: Affects Version/s: 2.3AS defer past 2.3.0 UIMA AS worker does not respond to client initialize after failover --- Key: UIMA-1658 URL: https://issues.apache.org/jira/browse/UIMA-1658 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu 8.10 Server, Java 1.6 and ActiveMQ 5.3.0 Reporter: Jörn Kottmann Fix For: 2.3AS A Pure Master Slave Broker is used to increase availability of the broker. More information about it can be found in the activemq documentation: http://activemq.apache.org/pure-master-slave.html In a test we simulated Master failure through killing the process with kill -9. Here is the log output from the worker node: INFO FailoverTransport - Successfully connected to tcp://XXX1:61616 Here I stopped the master broker process with kill -9 WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 Afterwards the client was restarted but got a time out error during initialize. During initializes it sends a message to the worker nodes input queue, but this message if never retrieved. I used the activemq web interface to get some information about the message: Command 2001 MessageFrom ID:-51032-1257865414664-0:1:1 ServerURI failover:(tcp://XXX1:61616,tcp://XXX2:61616)?randomize=false MessageType 3000 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1663) All directories in UIMA distribution should be 755
[ https://issues.apache.org/jira/browse/UIMA-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778784#action_12778784 ] Jörn Kottmann commented on UIMA-1663: - Thanks for fixing that Marshall. All directories in UIMA distribution should be 755 -- Key: UIMA-1663 URL: https://issues.apache.org/jira/browse/UIMA-1663 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Affects Versions: 2.3, 2.3AS Reporter: Jörn Kottmann Assignee: Marshall Schor Fix For: 2.3S, 2.3, 2.3AS The uima-as-2.3.0-incubating-bin.tar.gz and uimaj-2.3.0-incubating-bin.tar.gz contain directories which also have write permissions for group and other set. That permissions for directories should be 755 (no write for group and other). Here is a list of the directories: apache-uima bin config apache-activemq.4.1.1 as_config examples (only uima-as) saxon I did not check uimacpp and the sandbox. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1667) UIMA AS should also log the ActiveMQ version on startup
UIMA AS should also log the ActiveMQ version on startup --- Key: UIMA-1667 URL: https://issues.apache.org/jira/browse/UIMA-1667 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial UIMA AS should also log the ActiveMQ version on startup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1667) UIMA AS should also log the ActiveMQ version on startup
[ https://issues.apache.org/jira/browse/UIMA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778790#action_12778790 ] Jörn Kottmann commented on UIMA-1667: - defer past 2.3.0 UIMA AS should also log the ActiveMQ version on startup --- Key: UIMA-1667 URL: https://issues.apache.org/jira/browse/UIMA-1667 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Trivial UIMA AS should also log the ActiveMQ version on startup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1658) UIMA AS worker does not respond to client initialize after failover
[ https://issues.apache.org/jira/browse/UIMA-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-1658: Fix Version/s: (was: 2.3AS) UIMA AS worker does not respond to client initialize after failover --- Key: UIMA-1658 URL: https://issues.apache.org/jira/browse/UIMA-1658 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu 8.10 Server, Java 1.6 and ActiveMQ 5.3.0 Reporter: Jörn Kottmann A Pure Master Slave Broker is used to increase availability of the broker. More information about it can be found in the activemq documentation: http://activemq.apache.org/pure-master-slave.html In a test we simulated Master failure through killing the process with kill -9. Here is the log output from the worker node: INFO FailoverTransport - Successfully connected to tcp://XXX1:61616 Here I stopped the master broker process with kill -9 WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616 Afterwards the client was restarted but got a time out error during initialize. During initializes it sends a message to the worker nodes input queue, but this message if never retrieved. I used the activemq web interface to get some information about the message: Command 2001 MessageFrom ID:-51032-1257865414664-0:1:1 ServerURI failover:(tcp://XXX1:61616,tcp://XXX2:61616)?randomize=false MessageType 3000 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1668) Update sample descriptor for cas editor test UI_009
Update sample descriptor for cas editor test UI_009 --- Key: UIMA-1668 URL: https://issues.apache.org/jira/browse/UIMA-1668 Project: UIMA Issue Type: Bug Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3 The UI_009 test depends on an AE descriptor which uses the Regex annotator from the examples project, tough this dependencies was removed from the uima eclipse runtime project. The test should be updated to use a dummy AE which is already part of the cas editor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1669) Add Cas Editor sample project to distribution
Add Cas Editor sample project to distribution - Key: UIMA-1669 URL: https://issues.apache.org/jira/browse/UIMA-1669 Project: UIMA Issue Type: Improvement Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann The Cas Editor sample project should be added to the distribution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1668) Update sample descriptor for cas editor test UI_009
[ https://issues.apache.org/jira/browse/UIMA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778897#action_12778897 ] Jörn Kottmann commented on UIMA-1668: - Do we have a Dummy Annotator in the core uima which can be used for the test ? The Cas Editor contains one but it cannot be loaded because the Cas Editor does not declare Eclipse-RegisterBuddy in its MANIFEST.MF file. Update sample descriptor for cas editor test UI_009 --- Key: UIMA-1668 URL: https://issues.apache.org/jira/browse/UIMA-1668 Project: UIMA Issue Type: Bug Components: CasEditor Affects Versions: 2.3 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3 The UI_009 test depends on an AE descriptor which uses the Regex annotator from the examples project, tough this dependencies was removed from the uima eclipse runtime project. The test should be updated to use a dummy AE which is already part of the cas editor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
UIMA AS error handling of exception thrown from CasMultiplier.process
Hi, 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, how can it be detected that the CAS was not processed successfully ? Thanks, Jörn
testing rc-2
We invite all who are following this list to download and test release candidate 2. Please visit the wiki page http://cwiki.apache.org/confluence/display/UIMA/TestPlan2.3.0 and edit it as needed. A good practice: if you decide to test something (say, for instance, the install on a MAC platform), edit the bottom part of the page and add a line describing what you plan to do, with an empty box for Status / comments. This will let others know you are planning to test this area, and may avoid some duplicate work :-). When the test is done, add that in the status, something like 100% done or whatever. I hope to get the essential testing and reviews done this week. -Marshall
How to avoid message localization failed ?
Hello, on our sever message localization always fails with this error message: MESSAGE LOCALIZATION FAILED: Can't find bundle for base name jms_adapter_messages, locale en_DK This is a little annoying because even in case it fails it should just use english error messages, and if that fails the key of the error message is better than nothing. Should I open a jira ? Jörn
Re: How to avoid message localization failed ?
Jörn Kottmann wrote: Hello, on our sever message localization always fails with this error message: MESSAGE LOCALIZATION FAILED: Can't find bundle for base name jms_adapter_messages, locale en_DK This is a little annoying because even in case it fails it should just use english error messages, and if that fails the key of the error message is better than nothing. Should I open a jira ? The localization code already is trying various variations, down to the base name by itself. It's the Java standard getBundle in the standard Java class ResourceBundle. The base name here is jms_adapter_messages, and there is supposed to be a jms_adapter_messages.properties file on the classpath (it's in uimaj-as-jms project, in src/main/resources). Can you find out why this is not on the classpath? -Marshall Jörn
