[jira] [Created] (UIMA-5477) javax.jms.IllegalStateException: The Session is closed after establish connections between uima-as client and ActiveMQ

[Nelson RIvera (JIRA)]

Nelson RIvera created UIMA-5477:
---

 Summary: javax.jms.IllegalStateException: The Session is closed 
after establish connections between uima-as client and ActiveMQ
 Key: UIMA-5477
 URL: https://issues.apache.org/jira/browse/UIMA-5477
 Project: UIMA
  Issue Type: Access
  Components: Async Scaleout
Affects Versions: 2.9.0AS
 Environment: ubuntu xenial, openjdk-8-jdk
Reporter: Nelson RIvera


In my program main, i initialize a uimas-as client only once and I use
this client to consume all requests to a displayed service uima-as.

Before process a request i ask to uima-as client with:
BaseUIMAAsynchronousEngine_impl.connectionOpen()
and if the result es "false", i stop the uima-as client and initialize it again.

With some steps, still undefined, but basically when restart the UIMA-AS Broker
without restart service uima-as.
The instruccion to uima-as client
BaseUIMAAsynchronousEngine_impl.connectionOpen() return "true", but
them i get a "javax.jms.IllegalStateException: The Session is closed"
when proces the request.

One peculiarity is that, is a primitive annotator implented in c++,
but is deployed with de deployAsyncService.sh de uima-as directly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [jira] [Created] (UIMA-5477) javax.jms.IllegalStateException: The Session is closed after establish connections between uima-as client and ActiveMQ

[Jaroslaw Cwiklik]

Hi, looks like a Connection has been recovered but the code has a stale
Session created with a previous connection. I will try to reproduce. The
remote C++ service is not an issue here.

Once you restart the broker (not the uima-as client), can you send more
than one CAS?

Jerry

On Wed, Jul 5, 2017 at 8:24 AM, Nelson RIvera (JIRA) 
wrote:

> Nelson RIvera created UIMA-5477:
> ---
>
>  Summary: javax.jms.IllegalStateException: The Session is
> closed after establish connections between uima-as client and ActiveMQ
>  Key: UIMA-5477
>  URL: https://issues.apache.org/jira/browse/UIMA-5477
>  Project: UIMA
>   Issue Type: Access
>   Components: Async Scaleout
> Affects Versions: 2.9.0AS
>  Environment: ubuntu xenial, openjdk-8-jdk
> Reporter: Nelson RIvera
>
>
> In my program main, i initialize a uimas-as client only once and I use
> this client to consume all requests to a displayed service uima-as.
>
> Before process a request i ask to uima-as client with:
> BaseUIMAAsynchronousEngine_impl.connectionOpen()
> and if the result es "false", i stop the uima-as client and initialize it
> again.
>
> With some steps, still undefined, but basically when restart the UIMA-AS
> Broker
> without restart service uima-as.
> The instruccion to uima-as client
> BaseUIMAAsynchronousEngine_impl.connectionOpen() return "true", but
> them i get a "javax.jms.IllegalStateException: The Session is closed"
> when proces the request.
>
> One peculiarity is that, is a primitive annotator implented in c++,
> but is deployed with de deployAsyncService.sh de uima-as directly.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Re: [jira] [Created] (UIMA-5477) javax.jms.IllegalStateException: The Session is closed after establish connections between uima-as client and ActiveMQ

[Jaroslaw Cwiklik]

Also, please provide a complete stack trace

Jerry

On Wed, Jul 5, 2017 at 9:29 AM, Jaroslaw Cwiklik  wrote:

> Hi, looks like a Connection has been recovered but the code has a stale
> Session created with a previous connection. I will try to reproduce. The
> remote C++ service is not an issue here.
>
> Once you restart the broker (not the uima-as client), can you send more
> than one CAS?
>
> Jerry
>
> On Wed, Jul 5, 2017 at 8:24 AM, Nelson RIvera (JIRA) 
> wrote:
>
>> Nelson RIvera created UIMA-5477:
>> ---
>>
>>  Summary: javax.jms.IllegalStateException: The Session is
>> closed after establish connections between uima-as client and ActiveMQ
>>  Key: UIMA-5477
>>  URL: https://issues.apache.org/jira/browse/UIMA-5477
>>  Project: UIMA
>>   Issue Type: Access
>>   Components: Async Scaleout
>> Affects Versions: 2.9.0AS
>>  Environment: ubuntu xenial, openjdk-8-jdk
>> Reporter: Nelson RIvera
>>
>>
>> In my program main, i initialize a uimas-as client only once and I use
>> this client to consume all requests to a displayed service uima-as.
>>
>> Before process a request i ask to uima-as client with:
>> BaseUIMAAsynchronousEngine_impl.connectionOpen()
>> and if the result es "false", i stop the uima-as client and initialize it
>> again.
>>
>> With some steps, still undefined, but basically when restart the UIMA-AS
>> Broker
>> without restart service uima-as.
>> The instruccion to uima-as client
>> BaseUIMAAsynchronousEngine_impl.connectionOpen() return "true", but
>> them i get a "javax.jms.IllegalStateException: The Session is closed"
>> when proces the request.
>>
>> One peculiarity is that, is a primitive annotator implented in c++,
>> but is deployed with de deployAsyncService.sh de uima-as directly.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.4.14#64029)
>>
>
>

[jira] [Commented] (UIMA-5477) javax.jms.IllegalStateException: The Session is closed after establish connections between uima-as client and ActiveMQ

[Nelson RIvera (JIRA)]

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

Nelson RIvera commented on UIMA-5477:
-

This behavior is random, not occurs always. In the most of the simple programs 
and simple test case tested, after restart the UIMA-AS Broker without restart 
service uima-as, the instruccion to uima-as client
"BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and correctly 
i initialize the client again.

The incorrect behavior is most frequently with many uima-as client instances. 
Is the case of my general application in which i have many service uima-as, and 
for each one creates one instace of uima-as client 
(BaseUIMAAsynchronousEngine_impl) and keep it alive to process all requests of 
the service uima-as.

Is in this scenario with many instancies of uima-as client 
(BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic application 
web in tomcat) where after restart the UIMA-AS Broker without restart any 
service uima-as, many uima-as client returns "true" to the instruccion 
"BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw 
"javax.jms.IllegalStateException: The Session is closed"
when proces the request.

> javax.jms.IllegalStateException: The Session is closed after establish 
> connections between uima-as client and ActiveMQ
> --
>
> Key: UIMA-5477
> URL: https://issues.apache.org/jira/browse/UIMA-5477
> Project: UIMA
>  Issue Type: Access
>  Components: Async Scaleout
>Affects Versions: 2.9.0AS
> Environment: ubuntu xenial, openjdk-8-jdk
>Reporter: Nelson RIvera
>
> In my program main, i initialize a uimas-as client only once and I use
> this client to consume all requests to a displayed service uima-as.
> Before process a request i ask to uima-as client with:
> BaseUIMAAsynchronousEngine_impl.connectionOpen()
> and if the result es "false", i stop the uima-as client and initialize it 
> again.
> With some steps, still undefined, but basically when restart the UIMA-AS 
> Broker
> without restart service uima-as.
> The instruccion to uima-as client
> BaseUIMAAsynchronousEngine_impl.connectionOpen() return "true", but
> them i get a "javax.jms.IllegalStateException: The Session is closed"
> when proces the request.
> One peculiarity is that, is a primitive annotator implented in c++,
> but is deployed with de deployAsyncService.sh de uima-as directly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (UIMA-5478) OrderedFsSet_array has several infrequent problems

[Marshall Schor (JIRA)]

Marshall Schor created UIMA-5478:


 Summary: OrderedFsSet_array has several infrequent problems
 Key: UIMA-5478
 URL: https://issues.apache.org/jira/browse/UIMA-5478
 Project: UIMA
  Issue Type: Bug
  Components: Core Java Framework
Affects Versions: 3.0.0SDK-alpha02
Reporter: Marshall Schor
Assignee: Marshall Schor
 Fix For: 3.0.0SDK-beta


More extensive testing in a larger user application reveals some problems with 
the main data structure used to implement sorted FS indexes in UV3.  Build a 
much more comprehensive test case that tests all kinds of adds and removes, to 
uncover these, and fix them.  Also,add IllegalArgumentException for passing a 
null to add or remove.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (UIMA-5478) OrderedFsSet_array has several infrequent problems

[Marshall Schor (JIRA)]

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

Marshall Schor resolved UIMA-5478.
--
Resolution: Fixed

> OrderedFsSet_array has several infrequent problems
> --
>
> Key: UIMA-5478
> URL: https://issues.apache.org/jira/browse/UIMA-5478
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Affects Versions: 3.0.0SDK-alpha02
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDK-beta
>
>
> More extensive testing in a larger user application reveals some problems 
> with the main data structure used to implement sorted FS indexes in UV3.  
> Build a much more comprehensive test case that tests all kinds of adds and 
> removes, to uncover these, and fix them.  Also,add IllegalArgumentException 
> for passing a null to add or remove.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (UIMA-5405) DUCC should allow the "ducc" user to be other than exactly "ducc"

[Burn Lewis (JIRA)]

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

Burn Lewis reassigned UIMA-5405:


Assignee: Eddie Epstein  (was: Lou DeGenaro)

Please review security changes to ducc_ling since revision 1786348

> DUCC should allow the "ducc" user to be other than exactly "ducc"
> -
>
> Key: UIMA-5405
> URL: https://issues.apache.org/jira/browse/UIMA-5405
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Eddie Epstein
> Fix For: 2.2.1-Ducc
>
>
> There is no guarantee that user "ducc" will be available as the DUCC userid.
> Allow for specification of ducc.uid in the site.ducc.properties file and use 
> same for:
> - ducc_ling
> - CgroupsManager & CgroupsTest
> - DbManager & DbCreate
> - ducc_util.py & db_util.py 
> - jconsole.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (UIMA-5479) uv3 performance bug - FsIterator_subtypes_ordered not using custom comparator

[Marshall Schor (JIRA)]

Marshall Schor created UIMA-5479:


 Summary: uv3 performance bug - FsIterator_subtypes_ordered not 
using custom comparator
 Key: UIMA-5479
 URL: https://issues.apache.org/jira/browse/UIMA-5479
 Project: UIMA
  Issue Type: Improvement
  Components: Core Java Framework
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Minor
 Fix For: 3.0.0SDK-beta


Most uses of Sorted UIMA indexes for comparing FSs make use of custom 
comparators for Annotation indexes (versus using the general purpose 
comparator).  But the implementation of FsIterator_subtypes_ordered fails to 
use this one.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Build failed in Jenkins: UIMA-AS #495

[Apache Jenkins Server]

See 

Changes:

[cwiklik] UIMA-5477 Modified to catch a stale session and create a new one 
along with a new JMS producer

--
[...truncated 1007.04 KB...]
at 
org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.process(PrimitiveAnalysisEngineController_impl.java:1244)
at 
org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:121)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient(ProcessRequestHandler_impl.java:572)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1090)
at 
org.apache.uima.aae.handler.input.MetadataRequestHandler_impl.handle(MetadataRequestHandler_impl.java:78)
at 
org.apache.uima.adapter.jms.activemq.JmsInputChannel.onMessage(JmsInputChannel.java:735)
at 
org.apache.uima.adapter.jms.activemq.JmsInputChannel.onMessage(JmsInputChannel.java:563)
at 
org.apache.uima.aae.UimaAsPriorityBasedThreadFactory$1.run(UimaAsPriorityBasedThreadFactory.java:165)
... 1 more
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop() - 
Stopping UIMA-AS Client
BaseMessageSender.doStop() called
BaseMessageSender.run() - Exiting Dispatch Thread
BaseMessageSender.doStop() added empty message to force stop 

javax.jms.JMSException: java.io.EOFException
at 
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at 
org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1949)
at 
org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1968)
at 
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at 
org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
at 
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at 
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at 
org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
at 
org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344)
at 
org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at 
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at 
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 moreTests run: 128, Failures: 0, Errors: 0, Skipped: 0, Time 
elapsed: 1,537.524 sec

org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop() - 
Stopping UIMA-AS Client
BaseMessageSender.doStop() called
BaseMessageSender.run() - Exiting Dispatch Thread
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop() - 
Stopping UIMA-AS Client
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop() - 
Stopping UIMA-AS Client
BaseMessageSender.doStop() called
BaseMessageSender.run() - Exiting Dispatch Thread
BaseMessageSender.doStop() added empty message to force stop 

BaseMessageSender.doStop() added empty message to force stop 


Results :

Tests run: 128, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (surefire-integration) @ 
uimaj-as-activemq ---
[INFO] Skipping execution of surefire because it has already been run for this 
configuration
[JENKINS] Recording test results
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) < [cobertura]test 
@ uimaj-as-activemq <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.7:cobertura (default-cli) @ 
uimaj-as-activemq ---
[INFO] Cobertura 2.1.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
[INFO] Cobertura: Loaded information on 42 classes.
Report time: 2005ms

[INFO] Cobertura Report generation was successful.
[INFO] 
[INFO] >>> maven-javadoc-plugin:2.9.1:javadoc (default-cli) > generate-sources 
@ uimaj-as-activemq >>>
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-versions) @ 
uimaj-as-activemq ---
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:parse-versio