headers
Jörn Kottmann (JIRA | 1 Feb 13:39
Picon
Favicon

[jira] Commented: (UIMA-1728) UIMA AS Service logs falsely Stopping Collocated Delegate Cas Multiplier message


    [
https://issues.apache.org/jira/browse/UIMA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828078#action_12828078
] 

Jörn Kottmann commented on UIMA-1728:
-------------------------------------

Jerry:

"What is happening in your scenario
is the following:

1) CM receives input CAS C1
2) The CM generates a new CAS C2
3) C2 is sent to Delegate Service D1
4) D1 throws exception on C2
5) Aggregate receives exception from D1 and sends STOP message to CM asking
it to stop producing
    new CASes from C1. This message is not sent to stop the CM!
6) CM returns C1 to the Aggregate
7) Aggregate determines that C1 has been marked as failed ( because of C2
failure)
8) Aggregate returns C1 marked as failed to the client

The confusion is the message that the aggregate logs: Stopping Collocated
Delegate Cas Multiplier:
It should say something like, Sending Request to CM to Stop Generating New
CASes from CAS id: xxx
"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 1 Feb 13:43
Picon
Favicon

[jira] Commented: (UIMA-1728) UIMA AS Service logs falsely Stopping Collocated Delegate Cas Multiplier message


    [
https://issues.apache.org/jira/browse/UIMA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828090#action_12828090
] 

Jörn Kottmann commented on UIMA-1728:
-------------------------------------

The message is also logged to the console, but the exception from the process method is not logged to the
console.  
The message should not be logged to the console, or together with the exception.

> UIMA AS Service logs falsely Stopping Collocated Delegate Cas Multiplier message
> --------------------------------------------------------------------------------
>
>                 Key: UIMA-1728
>                 URL: https://issues.apache.org/jira/browse/UIMA-1728
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jörn Kottmann
>            Priority: Minor
>         Attachments: test.zip
>
>
> The service has one CM which creates for every CAS one new CAS and a dummy AE which throws an exception on
every second CAS.
> It looks like that for each exception thrown from the AE.process method the stopping collocated delegate
CM message is printed
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tommaso Teofili | 1 Feb 15:25
Picon
Gravatar

Re: [Discuss] graduation

After reading that page I also think UIMA is ready to graduate.
Cheers,
Tommaso

2010/1/30 Eddie Epstein <eaepstein@...>

> Reading through the main link (use .html not htm) there are a lot of
> things to do as part of the graduation process, and UIMA looks ready
> to start.
>
> I'm +1 for helping.
>
> Eddie
>
> On Fri, Jan 29, 2010 at 5:00 PM, Marshall Schor <msa@...> wrote:
> > After reading the parts of the ASF website related to graduation from
> > the incubator to a top-level project (for instance I think this is the
> > main link: http://incubator.apache.org/guides/graduation.htm), do you
> > think we're ready for graduation?  Is there more we need to do first?
> >
> > -Marshall
> >
>
Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Feb 16:01

Re: [PROPOSAL] AlchemyAPI Annotator

30% * 19K lines = ~ 5.7Klocs, written by 2 people (mostly Tommaso). 

This seems to me to fit the criteria of needing a software grant (see
http://apache.org/licenses/#grants), where it says:

When an individual or corporation decides to donate a body of existing
software or documentation to one of the Apache projects, they need to
execute a formal Software Grant Agreement
<http://apache.org/licenses/software-grant.txt> (SGA) with the ASF.

I don't think it is very difficult to do - the main issue in the past
has been getting confirmation that it was "recorded".

See bottom of page http://incubator.apache.org/ip-clearance/index.html
for instructions re: having multiple people sign. 

See this page
http://incubator.apache.org/ip-clearance/ip-clearance-template.html for
instructions on where to send (under Process, step 3).

-Marshall

Tommaso Teofili wrote:
> 2010/1/29 Jörn Kottmann <kottmann@...>
>
>   
>> How many of these 19K lines are generated ?
>>     
>
>
(Continue reading)

Permalink | Reply | 7 comments |
headers
Marshall Schor | 1 Feb 18:50

[Discuss] Apache UIMA top level project charter - scope

Part of any proposal for a vote to graduate is the Charter (see
http://incubator.apache.org/guides/graduation.html ).

The original project description on our Status page (
http://incubator.apache.org/projects/uima ) was recently broadened from
the original to include scale-out capability, annotators, and "other
components that can be used with the framework", such as the Simple
Server, and the Maven / Ant packaging tools to package things as Pears. 
I feel that having these additions is important to helping UIMA succeed,
but that level of detail may be best omitted in the Charter.

Here's a first try at the project-scope part of Charter, please discuss:

...
RESOLVED, that the Apache UIMA Project be and hereby is responsible for
the creation and maintenance of software related to components and
component frameworks for the analysis of unstructured data, guided by
the UIMA Oasis Standard (http://www.oasis-open.org) ...

Please suggest improvements :-)

-Marshall
Permalink | Reply | 1 comment |
headers
Jerry Cwiklik (JIRA | 1 Feb 19:48
Picon
Favicon

[jira] Commented: (UIMA-1731) ResourceInitializationExceptions thrown by a deployed aggregate are only partially logged


    [
https://issues.apache.org/jira/browse/UIMA-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828217#action_12828217
] 

Jerry Cwiklik commented on UIMA-1731:
-------------------------------------

I checked the code and discovered that the problem described here is due to a wrong style of logging. In many
places, while logging WARNING messages using these keys: 

UIMAEE_exception__WARNING
UIMAJMS_exception__WARNING

the UIMA AS code uses something like this:

UIMAFramework.getLogger(CLASS_NAME).logrb(Level.WARNING, getClass().getName(),
                "takeAction", UIMAEE_Constants.JMS_LOG_RESOURCE_BUNDLE,
                "UIMAEE_exception__WARNING", new Object[] { e });

The above does not log the whole stack trace hiding a real cause. Change code to use this instead:

UIMAFramework.getLogger(CLASS_NAME).logrb(Level.WARNING, getClass().getName(),
                "takeAction", UIMAEE_Constants.JMS_LOG_RESOURCE_BUNDLE,
                "UIMAEE_exception__WARNING", e);

The above is better than just using 

log(Level level, String aMessage, Throwable thrown);
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Feb 19:51

how to use maven-remote-resources-plugin to handle our Notice / License etc. in our Jar builds

This plugin
(http://maven.apache.org/plugins/maven-remote-resources-plugin ) is
configured as a standard part of the apache maven superpom (version 6) (
http://repo1.maven.org/maven2/org/apache/apache/6/apache-6.pom ), which
references a "standard" object for this (
org.apache:apache-jar-resource-bundle:1.4 , located here:
http://repo2.maven.org/maven2/org/apache/apache-jar-resource-bundle/1.4/apache-jar-resource-bundle-1.4.jar
)
This jar has "velocity macros" (same as we use for our xdocs->docs
website building).

It appears to be part of standard apache build process to automagically
include the license / notice / and some kind of dependency information
in generated Jars.  This would correspond, I think, to our use of
uimaj-distr things in our Jar setup (where we have ant tasks that copy
things).

After reading the documentation, I still couldn't quite figure out how
we could use this.  Any pointers or explanations by those who've already
climbed the learning curve would be appreciated :-).

-Marshall
Permalink | Reply | 0 comments |
headers
Jerry Cwiklik (JIRA | 1 Feb 19:58
Picon
Favicon

[jira] Closed: (UIMA-1731) ResourceInitializationExceptions thrown by a deployed aggregate are only partially logged


     [
https://issues.apache.org/jira/browse/UIMA-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1731.
-------------------------------

    Resolution: Fixed
      Assignee: Jerry Cwiklik

Modified UIMA AS code to log the entire stack trace when logging exceptions. Also, added additional
messages identifying service name in which an exception occurs.

> ResourceInitializationExceptions thrown by a deployed aggregate are only partially logged
> -----------------------------------------------------------------------------------------
>
>                 Key: UIMA-1731
>                 URL: https://issues.apache.org/jira/browse/UIMA-1731
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.3AS
>
>
> When the XcasCollectionReader fails to init because its input directory is missing it reports the cause
when run in core UIMA, i.e.
> Caused by: org.apache.uima.resource.ResourceInitializationException: Initialization of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jerry Cwiklik (JIRA | 1 Feb 20:32
Picon
Favicon

[jira] Closed: (UIMA-1728) UIMA AS Service logs falsely Stopping Collocated Delegate Cas Multiplier message


     [
https://issues.apache.org/jira/browse/UIMA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1728.
-------------------------------

    Resolution: Fixed
      Assignee: Jerry Cwiklik

Modified log message when sending a request to CM to stop producing CASes from an input CAS. Removed logging
to stdout.

> UIMA AS Service logs falsely Stopping Collocated Delegate Cas Multiplier message
> --------------------------------------------------------------------------------
>
>                 Key: UIMA-1728
>                 URL: https://issues.apache.org/jira/browse/UIMA-1728
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jörn Kottmann
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>         Attachments: test.zip
>
>
> The service has one CM which creates for every CAS one new CAS and a dummy AE which throws an exception on
every second CAS.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jerry Cwiklik (JIRA | 1 Feb 21:16
Picon
Favicon

[jira] Closed: (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:all-tabpanel ]

Jerry Cwiklik closed UIMA-1667.
-------------------------------

    Resolution: Fixed
      Assignee: Jerry Cwiklik

The best thing I can log is the value of environment variable ACTIVEMQ_HOME. This is set in runUIMAClass
scripts when launching a UIMA AS service. Below is an example of what is now logged upon UIMA AS service startup:
+------------------------------------------------------------------
                   Starting UIMA AS Service - PID:6708
+------------------------------------------------------------------
+ Service Name:Room Number Annotator
+ Service Queue Name:RoomNumberAnnotatorQueue
+ Service Start Time:01 Feb 2010 15:06:37
+ UIMA AS Version:2.3.0
+ UIMA Core Version:2.3.0
<b>+ JMS Provider Home:c:\uima\releases\2.3.0\apache-uima\apache-activemq-4.1.1</b>
+ OS Name:Windows XP
+ OS Version:5.1
+ OS Architecture:x86
+ OS CPU Count:2
+ JVM Vendor:Sun Microsystems Inc.
+ JVM Name:Java HotSpot(TM) Client VM
+ JMS Provider Home:c:\uima\releases\2.3.0-09\apache-uima\apache-activemq-4.1.1
+ JVM Version:1.6.0_02-b05
+ JVM Input Args:[-DVNS_HOST=localhost, -DVNS_PORT=9000, -Duima.home=c:\uima\rel
(Continue reading)

Permalink | Reply | 0 comments |

Gmane