Picon
Favicon

[jira] Created: (UIMA-1408) Annotation highlightning does not work with background drawing strategy

Annotation highlightning does not work with background drawing strategy
-----------------------------------------------------------------------

                 Key: UIMA-1408
                 URL: https://issues.apache.org/jira/browse/UIMA-1408
             Project: UIMA
          Issue Type: Bug
          Components: CasEditor
    Affects Versions: 2.3
            Reporter: Jörn Kottmann
            Assignee: Jörn Kottmann
            Priority: Minor

An annotation which is visualized with the background drawing strategy in the cas text edtiro is not
highlighted when selected in the outline view. The annotation appearance should change to give the user a
feedback which annotation is selected.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Frederick R Reiss | 1 Jul 10:01
Picon
Favicon

AUTO: Frederick R Reiss is at SIGMOD (returning 07/03/2009)


I am out of the office until 07/03/2009.

I am at the SIGMOD 2009 conference.  It may take me a day or two to reply
to email.

Note: This is an automated response to your message  "[jira] Closed:
(UIMA-1392) OpenCalaisAnnotator's annotations have truncated 'coveredText'
field" sent on 7/1/09 3:30:47.

This is the only notification you will receive while this person is away.
Picon
Favicon

[jira] Commented: (UIMA-1391) Client of a CAS Multiplier should be able to stop processing of a CAS


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

Jerry Cwiklik commented on UIMA-1391:
-------------------------------------

Modified client code to handle a new message type returned from a remote Cas Multiplier. When a client sends
an input CAS, the Cas Multiplier service immediately returns a ServiceInfo message that contains this
service FreeCas Notification queue. This queue is unique to the service. It is this queue that will
receive notifications from the client. Currently the client can send FreeCas and Stop requests. This
change enables scaleout of remote Cas Multipliers. The client now knows which instance processes each
input CAS. 

> Client of a CAS Multiplier should be able to stop processing of a CAS
> ---------------------------------------------------------------------
>
>                 Key: UIMA-1391
>                 URL: https://issues.apache.org/jira/browse/UIMA-1391
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>             Fix For: 2.3S
>
>
> Normally the number of CASes generated by a Cas Multiplier is determined by the CM itself, but with an
aggregate CM that number may be hard to anticipate or control.  Some applications may not need all of the
generated CASes ... they may be satisfied once an appropriate amount of information has been returned.
(Continue reading)

Burn Lewis (JIRA | 2 Jul 00:16
Picon
Favicon

[jira] Commented: (UIMA-1109) Need ability to quiesce an instance of a service


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

Burn Lewis commented on UIMA-1109:
----------------------------------

Tested using the command-line "q" and also with completeProcessingAndStop via JMX (had to use a Sun JVM for
both the service and jconsole in order to connect) ... both caused a ServiceShutdownException to be sent
to the client which is unexpected.
Also when quiesced via JMX the service did not exit ... perhaps is still waiting for a 'q' or 's'.

When stopped with "s" or the JMX stopNow() the service stopped but did not exit ... required control-C. 
Client also got a ServiceShutdownException but maybe that's to be expected with a hard shutdown.

> Need ability to quiesce an instance of a service
> ------------------------------------------------
>
>                 Key: UIMA-1109
>                 URL: https://issues.apache.org/jira/browse/UIMA-1109
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Assignee: Jerry Cwiklik
>
> We can deploy extra instances of a service seamlessly but also need a mechanism to undeploy without losing
any work, i.e. ask an instance to stop processing messages and shutdown when it finishes its current work.

(Continue reading)

Picon
Favicon

[jira] Created: (UIMA-1409) The implementation of the uimaj-as-camel producer must be thread safe but is not

The implementation of the uimaj-as-camel producer must be thread safe but is not
--------------------------------------------------------------------------------

                 Key: UIMA-1409
                 URL: https://issues.apache.org/jira/browse/UIMA-1409
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.3S
            Reporter: Jörn Kottmann
            Assignee: Jörn Kottmann
             Fix For: 2.3S

The producer implementation is sharing a map between the async CAS sender and the call back listener. This
map is not thread safe but must be.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Picon
Favicon

[jira] Closed: (UIMA-1409) The implementation of the uimaj-as-camel producer must be thread safe but is not


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

Jörn Kottmann closed UIMA-1409.
-------------------------------

    Resolution: Fixed

The issue is solved by using synchronize for accessing the shared map.

> The implementation of the uimaj-as-camel producer must be thread safe but is not
> --------------------------------------------------------------------------------
>
>                 Key: UIMA-1409
>                 URL: https://issues.apache.org/jira/browse/UIMA-1409
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3S
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>             Fix For: 2.3S
>
>
> The producer implementation is sharing a map between the async CAS sender and the call back listener. This
map is not thread safe but must be.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Picon
Favicon

[jira] Updated: (UIMA-1409) The implementation of the uimaj-as-camel producer must be thread safe but is not


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

Jörn Kottmann updated UIMA-1409:
--------------------------------

    Affects Version/s:     (was: 2.3S)
                       2.3AS
        Fix Version/s:     (was: 2.3S)
                       2.3AS

Accidentally picked the wrong version, sorry.

> The implementation of the uimaj-as-camel producer must be thread safe but is not
> --------------------------------------------------------------------------------
>
>                 Key: UIMA-1409
>                 URL: https://issues.apache.org/jira/browse/UIMA-1409
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>             Fix For: 2.3AS
>
>
> The producer implementation is sharing a map between the async CAS sender and the call back listener. This
map is not thread safe but must be.
(Continue reading)

Picon
Favicon

[jira] Created: (UIMA-1410) The uimaj-as-camel producer should report and log all error/exceptions

The uimaj-as-camel producer should report and log all error/exceptions
----------------------------------------------------------------------

                 Key: UIMA-1410
                 URL: https://issues.apache.org/jira/browse/UIMA-1410
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.3AS
            Reporter: Jörn Kottmann
            Assignee: Jörn Kottmann
             Fix For: 2.3AS

There are several TODOs in the implementation which must be replaced with proper error handling and logging.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Thilo Goetz | 2 Jul 10:54
Picon
Picon

Re: Building the eclipse update site

Thilo Goetz wrote:
> All,
> 
> I was trying to follow up on Burn's comments on
> https://issues.apache.org/jira/browse/UIMA-1326
> 
> So I tried to build the eclipse update site to
> be able to (easily) install our eclipse plugins.
> I tried to follow the instructions on our web
> site, but I was unable to find the feature jars
> I'm supposed to copy.  Where are those supposed
> to end up at?  Thanks.
> 
> --Thilo

After some trial and error, I figured this out on
my own.  The instructions are slightly wrong, as
the feature jars do not need to be copied, they
are actually generated during the ant build.  What
also threw me was that the ant build was complaining
I should be setting up and using a *maven* profile
with an eclipse.home property set.  I tried that,
and it didn't do anything for me, while simply
defining an ant property worked fine.  So I'll be
fixing those instructions.

--Thilo

Thilo Goetz (JIRA | 2 Jul 11:02
Picon
Favicon

[jira] Created: (UIMA-1411) Instructions for building eclipse update site are wrong

Instructions for building eclipse update site are wrong
-------------------------------------------------------

                 Key: UIMA-1411
                 URL: https://issues.apache.org/jira/browse/UIMA-1411
             Project: UIMA
          Issue Type: Bug
          Components: Build, Packaging and Test
    Affects Versions: 2.2.2
            Reporter: Thilo Goetz
            Assignee: Thilo Goetz
             Fix For: 2.3

Instructions both on website and ant script need to be fixed.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Gmane