Picon
Favicon

[jira] [Closed] (UIMA-2372) On lost connection to a broker UIMA AS Spring JMS listener excessively logs error msgs


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

Jerry Cwiklik closed UIMA-2372.
-------------------------------

    Resolution: Fixed

> On lost connection to a broker UIMA AS Spring JMS listener excessively logs error msgs
> --------------------------------------------------------------------------------------
>
>                 Key: UIMA-2372
>                 URL: https://issues.apache.org/jira/browse/UIMA-2372
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.0AS
>
>
> When UIMA AS service loses a connection to a broker, its JMS listener rapidly fills a log with messages:
> 0 Feb 2012 12:33:33,598  WARN UIMA AS Service.UimaDefaultMessageListenerContainer - Could not refresh
JMS Connection for destination 'queue://<queue name>' - retrying in 5 ms. Cause: Could not connect to
broker URL:
> tcp://<broker url>:61616?wireFormat.maxInactivityDuration=0. Reason:
java.net.ConnectException: Connection refused 
> I've traced the origin of this message to Spring Framework's DefaultMessageListenerContainer.java,
refreshConnectionUntilSuccessful() method. Spring is attempting to auto recover the connection by
(Continue reading)

Picon
Favicon

[jira] [Closed] (UIMA-2377) Modify UIMA AS service to call System.exit(1) when handling java Error


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

Jerry Cwiklik closed UIMA-2377.
-------------------------------

    Resolution: Fixed

> Modify UIMA AS service to call System.exit(1) when handling java Error
> ----------------------------------------------------------------------
>
>                 Key: UIMA-2377
>                 URL: https://issues.apache.org/jira/browse/UIMA-2377
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.4.0AS
>
>
> On OOM, the UIMA AS service is trying to gracefully stop the service via quiesceAndStop. While shutting
down, additional OOMs are thrown possibly due to extra logging that takes place during shutdown. These
errors leave the jvm in a hanging state. When handling java Error, UIMA AS should try to log, and dump a
message to stdout and just exit the jvm.   

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

Picon
Favicon

[jira] [Created] (UIMA-2377) Modify UIMA AS service to call System.exit(1) when handling java Error

Modify UIMA AS service to call System.exit(1) when handling java Error
----------------------------------------------------------------------

                 Key: UIMA-2377
                 URL: https://issues.apache.org/jira/browse/UIMA-2377
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: 2.4.0AS

On OOM, the UIMA AS service is trying to gracefully stop the service via quiesceAndStop. While shutting
down, additional OOMs are thrown possibly due to extra logging that takes place during shutdown. These
errors leave the jvm in a hanging state. When handling java Error, UIMA AS should try to log, and dump a
message to stdout and just exit the jvm.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Apache Jenkins Server | 5 Mar 2012 20:52
Picon

Build failed in Jenkins: UIMA-AS #105

See <https://builds.apache.org/job/UIMA-AS/105/changes>

Changes:

[cwiklik] UIMA-2377 Exit the jvm on java Error

[cwiklik] UIMA-2372 Modified to override Spring's refreshConnectionUntilSuccessful() to control logging

------------------------------------------
[...truncated 5167 lines...]
runTest: Client:::::::::::::: Received:949 Reply
runTest: onBeforeProcessCAS() Notification - CAS:3c6aea8b:135e440b91e:-7bf1 is being processed on
machine:67.195.138.8 by process (PID):3947:159
runTest: Received onBeforeMessageSend() Notification With CAS:3c6aea8b:135e440b91e:-7be9
runTest: Received Reply Containing CAS:3c6aea8b:135e440b91e:-7bf2
runTest: Client:::::::::::::: Received:950 Reply
runTest: onBeforeProcessCAS() Notification - CAS:3c6aea8b:135e440b91e:-7bf0 is being processed on
machine:67.195.138.8 by process (PID):3947:160
runTest: Received onBeforeMessageSend() Notification With CAS:3c6aea8b:135e440b91e:-7be8
runTest: Received Reply Containing CAS:3c6aea8b:135e440b91e:-7bf1
runTest: Client:::::::::::::: Received:951 Reply
runTest: onBeforeProcessCAS() Notification - CAS:3c6aea8b:135e440b91e:-7bef is being processed on
machine:67.195.138.8 by process (PID):3947:158
runTest: Received onBeforeMessageSend() Notification With CAS:3c6aea8b:135e440b91e:-7be7
runTest: Received Reply Containing CAS:3c6aea8b:135e440b91e:-7bf0
runTest: Client:::::::::::::: Received:952 Reply
runTest: onBeforeProcessCAS() Notification - CAS:3c6aea8b:135e440b91e:-7bee is being processed on
machine:67.195.138.8 by process (PID):3947:161
runTest: Received onBeforeMessageSend() Notification With CAS:3c6aea8b:135e440b91e:-7be6
runTest: Received Reply Containing CAS:3c6aea8b:135e440b91e:-7bef
(Continue reading)

Apache Jenkins Server | 5 Mar 2012 21:54
Picon

Build failed in Jenkins: UIMA-AS #106

See <https://builds.apache.org/job/UIMA-AS/106/changes>

Changes:

[cwiklik] UIMA-2377 Forgot to check the type of Throwable before calling System.exit. Only uncaught java
errors should trigger jvm exit

[cwiklik] UIMA-2180 extended support for collecting perf stats to uima-as aggregates

------------------------------------------
[...truncated 5157 lines...]
runTest: Received onBeforeMessageSend() Notification With CAS:-15fb0d80:135e47a8b48:-7beb
runTest: Received onBeforeMessageSend() Notification With CAS:-15fb0d80:135e47a8b48:-7bea
runTest: Received Reply Containing CAS:-15fb0d80:135e47a8b48:-7bf1
runTest: Client:::::::::::::: Received:949 Reply
runTest: Received onBeforeMessageSend() Notification With CAS:-15fb0d80:135e47a8b48:-7be9
runTest: Received Reply Containing CAS:-15fb0d80:135e47a8b48:-7bf4
runTest: Client:::::::::::::: Received:950 Reply
runTest: onBeforeProcessCAS() Notification - CAS:-15fb0d80:135e47a8b48:-7bef is being processed on
machine:67.195.138.8 by process (PID):12549:158
runTest: onBeforeProcessCAS() Notification - CAS:-15fb0d80:135e47a8b48:-7bec is being processed on
machine:67.195.138.8 by process (PID):12549:160
runTest: Received onBeforeMessageSend() Notification With CAS:-15fb0d80:135e47a8b48:-7be8
runTest: Received Reply Containing CAS:-15fb0d80:135e47a8b48:-7bee
runTest: Client:::::::::::::: Received:951 Reply
runTest: Received onBeforeMessageSend() Notification With CAS:-15fb0d80:135e47a8b48:-7be7
runTest: onBeforeProcessCAS() Notification - CAS:-15fb0d80:135e47a8b48:-7bea is being processed on
machine:67.195.138.8 by process (PID):12549:161
runTest: Received Reply Containing CAS:-15fb0d80:135e47a8b48:-7bf0
runTest: Client:::::::::::::: Received:952 Reply
(Continue reading)

Apache Jenkins Server | 5 Mar 2012 22:47
Picon

Jenkins build is back to normal : UIMA-AS #107

See <https://builds.apache.org/job/UIMA-AS/107/changes>

Marshall Schor | 6 Mar 2012 17:25

Quarterly Status report to the Board

It's time for the quarterly status report to the board, covering mid Dec - mid 
March.

We have Peter K. joining the PMC.
We have 4 UIMA CPP release candidates - no release yet...
We have work toward preparing a 2.4.0 release of UIMA-AS.
We have continuing work on several components.

Please reply with additional items for the board report :-)

-Marshall

Picon
Favicon

[jira] [Commented] (UIMA-1169) Specify source directory for JCAsGen


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

Mike Barborak commented on UIMA-1169:
-------------------------------------

For anyone looking for a workaround, when run from the Component Descriptor Editor in Eclipse, JCasGen
uses the project's first folder resource as it output folder. So to change the output folder, open the
project's properties, go to Java Build Path, go to the Order and Export tab, and move the desired output
folder above all other folder resources.

That didn't quite fulfill my needs as I have a project with two type systems: a "real" one for which JCasGen
should output to src and a "test" one for which I'd like JCasGen to output to test. The test type system
imports the real one. 

When I run JCasGen on the test type system, I first move my test source folder to the top of the order list as
described above. Then I run JCasGen. This puts the generated Java classes in the test folder. Yay. But it
also generates the Java classes for the imported type system and puts them in the test folder even though
those classes already exist in the src folder. This creates various compiler issues but they're easily
resolved by deleting the extra Java files.

So I guess a complete fix for me would be to allow specifying an output folder for each type system to JCasGen
or an option to not generate Java classes for imported type systems.

> Specify source directory for JCAsGen
> ------------------------------------
>
>                 Key: UIMA-1169
(Continue reading)

Picon
Favicon

[jira] [Commented] (UIMA-1169) Specify source directory for JCAsGen


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

Jens Grivolla commented on UIMA-1169:
-------------------------------------

An option to not generate Java classes for imported type systems would be interesting for us, too, as we
usually import TSs from jars that include the xml descriptors as well as the generated classes.

> Specify source directory for JCAsGen
> ------------------------------------
>
>                 Key: UIMA-1169
>                 URL: https://issues.apache.org/jira/browse/UIMA-1169
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins
>    Affects Versions: 2.3
>            Reporter: Julien Nioche
>
> By default JCASGen generates java code in the src/ directory (or maybe in the first source directory
available). It would be nice to have the possibility to specify an alternative source directory

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)

Picon
Favicon

[jira] [Commented] (UIMA-1169) Specify source directory for JCAsGen


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

Marshall Schor commented on UIMA-1169:
--------------------------------------

ok, that might not be too hard to do... I'll take a look.

> Specify source directory for JCAsGen
> ------------------------------------
>
>                 Key: UIMA-1169
>                 URL: https://issues.apache.org/jira/browse/UIMA-1169
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins
>    Affects Versions: 2.3
>            Reporter: Julien Nioche
>
> By default JCASGen generates java code in the src/ directory (or maybe in the first source directory
available). It would be nice to have the possibility to specify an alternative source directory

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)


Gmane