Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?

[nelson rivera]

Hi, i retest my general application, now without call connectionOpen()
to test the connection in uima-as cliente's source code.
And now this is the behavior:

-After restart the broker, the first uima-as client that is consumed
(no matter which) is fail and the client's log show this lines

.. Client running 
jul 20, 2017 3:10:21 PM
org.rp.platform.charset.uima.CharsetDetectorRemoteUIMAProcessing
process
INFORMACIÓN: Inicio de procesamiento en detección de charset.
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.ActiveMQMessageSender reject
INFORMACIÓN: UIMA AS Client Message Dispatcher Rejecting Process
Request - the Broker Is Not Available.
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
handleException
INFORMACIÓN: Received Exception In Message From Service on
Queue:UimaASClient Broker: tcp://172.24.10.193:61616 Cas
Identifier:1c2940e4:15d6161f9a6:-7ff4
Exception:org.apache.uima.jms.error.handler.BrokerConnectionException:
Unable To Deliver Message To Destination. Connection To Broker
tcp://172.24.10.193:61616 Has Been Lost
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection
retryConnectionUntilSuccessfull
ADVERTENCIA: UIMA AS Client Has Lost Connection To
Broker:tcp://172.24.10.193:61616 Retrying Connection every 5secs until
successful. Is Client Stopped:
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
sendAndReceiveCAS
INFORMACIÓN: UIMA AS Handling Exception in sendAndReceive(). CAS
hashcode:436494949. ThreadMonitor Released Semaphore For Thread ID:71
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
INFORMACIÓN: Initializing JMS Message Consumer. Broker:
tcp://172.24.10.193:61616 Queue Name:
ID:nelson-XPS-8700-42632-1500577397286-1:2:1
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
INFORMACIÓN: Initializing JMS Message Consumer. Broker:
tcp://172.24.10.193:61616 Queue Name:
ID:nelson-XPS-8700-42632-1500577397286-1:2:2
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
INFORMACIÓN: Initializing JMS Message Consumer. Broker:
tcp://172.24.10.193:61616 Queue Name:
ID:nelson-XPS-8700-42632-1500577397286-1:2:3
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
INFORMACIÓN: Initializing JMS Message Consumer. Broker:
tcp://172.24.10.193:61616 Queue Name:
ID:nelson-XPS-8700-42632-1500577397286-1:2:4
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection
retryConnectionUntilSuccessfull
INFORMACIÓN: UIMA AS Client Recovered Connection to Broker:
tcp://172.24.10.193:61616
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.ActiveMQMessageSender run
INFORMACIÓN: UIMA AS Client Message Dispatcher Sending GetMeta Ping To
the Service
Uima-AS Client Recovered Broker Connection - Sending GetMeta Ping
 Client Received GetMeta Ping Reply
jul 20, 2017 3:10:21 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
handleMetadataReply
INFORMACIÓN: UIMA AS Client Received GetMeta Ping Reply from
Service:XCharsetDetector on host: 127.0.1.1


Next uima-as clients to consume seem to have recovered and included
correct temp queue for reply and the processing is success.

Except the uima-as client of the service aggregate that have one
delegate remote. The behavior of this client is similar at the
beginning,shows the following lines and keep waiting.

INFORMACIÓN: Inicio de procesamiento en clustering de de
/opt/datys/xinetica/uima/share/data/cluster/collection5142806964189631238
jul 20, 2017 3:12:08 PM
cu.datys.xinetica.uima.listener.StatusCalbackListenerPerformance
onBeforeProcessCAS
INFORMACIÓN: null
jul 20, 2017 3:12:09 PM
org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
INFORMACIÓN: UIMA AS Client Failed Creating Session To Destination:
XClusterAnalyzerAggregate Managed By Broker:
tcp://nelson-XPS-8700:61616
jul 20, 2017 3:12:09 PM
org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
INFORMACIÓN: UIMA AS Client Connection To Destination:
XClusterAnalyzerAggregate Managed By Broker:
tcp://nelson-XPS-8700:61616 Is Closed
jul 20, 2017 3:12:09 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$2
onMessage
ADVERTENCIA:
org.apache.activemq.ConnectionClosedException: The connection is already closed
at 
org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQConnection.java:1459)
at 
org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1446)
at 
org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:328)
at 

RE: DUCC Web Server Service Visibility and Default Reservations

[Osborne, John David (Campus)]

Thanks Burn - I'm going to try with a secondary broker and see how it goes.

 -John


-Original Message-
From: Burn Lewis [mailto:burnle...@gmail.com] 
Sent: Thursday, July 20, 2017 6:58 AM
To: user@uima.apache.org
Subject: Re: DUCC Web Server Service Visibility and Default Reservations

I think this is one of the reasons we don't encourage use of the DUCC broker 
... it uses non-standard ports (to avoid conflicts with a user-created broker) 
and your error message probably means that the default pinger cannot access the 
default JMX port of 1099.  There is a way to specify the JMX port for the 
pinger but I think the simple and more general approach is for you to use a 
separate broker.  The DUCC installation includes UIMA-AS so from some shell set 
UIMA_HOME and start a broker, e.g.
export UIMA_HOME=$DUCC_HOME/apache-uima
$UIMA_HOME/bin/startBroker.sh

~Burn

On Wed, Jul 19, 2017 at 4:25 PM, Osborne, John David (Campus) < ozb...@uab.edu> 
wrote:

> Thanks Burn, looks like it is deployed but not healthy due to a 
> refused RMI connection. The web services page is refreshed, in 
> addition to displaying no services it does not display values for some 
> other fields (Updated, Utilization) that are displayed on other web server 
> pages.
>
> Any info appreciated, I'm not seeing anything more in sm.log than I am 
> seeing here from the ducc_services --query I ran. Both of the lines 
> end at the number 38 for the MetaPid.
>
>  -John
>
>
> [X]
>
>
> Service: UIMA-AS:MRN_Document_Pull_Queue:tcp://localhost:61617
>Service Class : Registered as ID 33 Owner[ducc] instances[1]
> linger[30]
>Implementors  : 31.0
>References: None
>Dependencies  : none
>Service State : Available
>Ping Active   : true
>Start Mode: manual, Enabled
>Last Use  : N/A
>Last Ping : Wed Jul 19 15:02:54 CDT 2017
>Last Runnable : Wed Jul 19 15:03:18 CDT 2017
>Registration Date : Tue Jul 18 14:55:18 CDT 2017
>Service Statistics:
>Alive[true] Healthy[false] + Info: JMX Failure[Failed to 
> retrieve RMIServer stub: javax.naming.ServiceUnavailableException 
> [Root exception is java.rmi.ConnectException: Connection refused to 
> host: localhost; nested exception is:
> java.net.ConnectException: Connection refused (Connection 
> refused)]]] MetaNode[10.23.142.165] MetaPid[1988:38
>
>
> 
> From: Burn Lewis 
> Sent: Wednesday, July 19, 2017 2:50:18 PM
> To: user@uima.apache.org
> Subject: Re: DUCC Web Server Service Visibility and Default 
> Reservations
>
> Did you refresh the Services page?  Ensure that the Users field is 
> empty (except for the hint)?  Also try $DUCC_HOME/bin/ducc_services 
> --query
>
> Reservations made by the "System" user are for internal use.
>
> ~Burn
>
> On Wed, Jul 19, 2017 at 3:21 PM, Lou DeGenaro 
> wrote:
>
> > It should always be the case that if you successfully "ducc_services 
> > --register..." a service it should appear on the ducc-mon Services page.
> > When you click on the Id for a Service you should see zero of more 
> > deployments, each Running instance corresponding to an O/S process.
> >
> > If you ever want to run DUCC Jobs you need to have the JobDriver 
> > Reservation.
> >
> > Lou.
> >
> > On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) < 
> > ozb...@uab.edu> wrote:
> >
> > > I have (according the log files in $HOME/ducc/logs) started as
> registered
> > > service successfully via ducc_services. I can see the process 
> > > running
> via
> > > the ps command, but it does not appear in the webserver under the
> > services
> > > section. Is this because I am running ducc anonymously using 
> > > active-ducc-unsecure.xml? I did not implement a pinger for this
> service,
> > > but I assume that since it is an AS service a default pinger will 
> > > be provided for me. I'm guessing only services with pingers appear 
> > > in the service page on the ducc webserver...?
> > >
> > > I also noticed a reservation in DUCC, dating back to when I first 
> > > installed DUCC with an ID of 0. It is of class JobDriver, from the
> system
> > > user, is in the state Assigned with 0 user processes and does not 
> > > have
> > the
> > > option for termination. Is this some reservation I created 
> > > errorenously
> > or
> > > is this standard on all ducc systems? I would like to cancel it if 
> > > I
> > don't
> > > need it, it taking up 2 GBS of memory.
> > >
> > > Thanks for any help,
> > >
> > > -John
> > >
> >
>

Re: DUCC Web Server Service Visibility and Default Reservations

[Burn Lewis]

I think this is one of the reasons we don't encourage use of the DUCC
broker ... it uses non-standard ports (to avoid conflicts with a
user-created broker) and your error message probably means that the default
pinger cannot access the default JMX port of 1099.  There is a way to
specify the JMX port for the pinger but I think the simple and more general
approach is for you to use a separate broker.  The DUCC installation
includes UIMA-AS so from some shell set UIMA_HOME and start a broker, e.g.
export UIMA_HOME=$DUCC_HOME/apache-uima
$UIMA_HOME/bin/startBroker.sh

~Burn

On Wed, Jul 19, 2017 at 4:25 PM, Osborne, John David (Campus) <
ozb...@uab.edu> wrote:

> Thanks Burn, looks like it is deployed but not healthy due to a refused
> RMI connection. The web services page is refreshed, in addition to
> displaying no services it does not display values for some other fields
> (Updated, Utilization) that are displayed on other web server pages.
>
> Any info appreciated, I'm not seeing anything more in sm.log than I am
> seeing here from the ducc_services --query I ran. Both of the lines end at
> the number 38 for the MetaPid.
>
>  -John
>
>
> [X]
>
>
> Service: UIMA-AS:MRN_Document_Pull_Queue:tcp://localhost:61617
>Service Class : Registered as ID 33 Owner[ducc] instances[1]
> linger[30]
>Implementors  : 31.0
>References: None
>Dependencies  : none
>Service State : Available
>Ping Active   : true
>Start Mode: manual, Enabled
>Last Use  : N/A
>Last Ping : Wed Jul 19 15:02:54 CDT 2017
>Last Runnable : Wed Jul 19 15:03:18 CDT 2017
>Registration Date : Tue Jul 18 14:55:18 CDT 2017
>Service Statistics:
>Alive[true] Healthy[false] + Info: JMX Failure[Failed to retrieve
> RMIServer stub: javax.naming.ServiceUnavailableException [Root exception
> is java.rmi.ConnectException: Connection refused to host: localhost; nested
> exception is:
> java.net.ConnectException: Connection refused (Connection
> refused)]]] MetaNode[10.23.142.165] MetaPid[1988:38
>
>
> 
> From: Burn Lewis 
> Sent: Wednesday, July 19, 2017 2:50:18 PM
> To: user@uima.apache.org
> Subject: Re: DUCC Web Server Service Visibility and Default Reservations
>
> Did you refresh the Services page?  Ensure that the Users field is empty
> (except for the hint)?  Also try $DUCC_HOME/bin/ducc_services --query
>
> Reservations made by the "System" user are for internal use.
>
> ~Burn
>
> On Wed, Jul 19, 2017 at 3:21 PM, Lou DeGenaro 
> wrote:
>
> > It should always be the case that if you successfully "ducc_services
> > --register..." a service it should appear on the ducc-mon Services page.
> > When you click on the Id for a Service you should see zero of more
> > deployments, each Running instance corresponding to an O/S process.
> >
> > If you ever want to run DUCC Jobs you need to have the JobDriver
> > Reservation.
> >
> > Lou.
> >
> > On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) <
> > ozb...@uab.edu> wrote:
> >
> > > I have (according the log files in $HOME/ducc/logs) started as
> registered
> > > service successfully via ducc_services. I can see the process running
> via
> > > the ps command, but it does not appear in the webserver under the
> > services
> > > section. Is this because I am running ducc anonymously using
> > > active-ducc-unsecure.xml? I did not implement a pinger for this
> service,
> > > but I assume that since it is an AS service a default pinger will be
> > > provided for me. I'm guessing only services with pingers appear in the
> > > service page on the ducc webserver...?
> > >
> > > I also noticed a reservation in DUCC, dating back to when I first
> > > installed DUCC with an ID of 0. It is of class JobDriver, from the
> system
> > > user, is in the state Assigned with 0 user processes and does not have
> > the
> > > option for termination. Is this some reservation I created errorenously
> > or
> > > is this standard on all ducc systems? I would like to cancel it if I
> > don't
> > > need it, it taking up 2 GBS of memory.
> > >
> > > Thanks for any help,
> > >
> > > -John
> > >
> >
>