Re: UIMA DUCC java.lang.SecurityException

2016-10-07 Thread Jaroslaw Cwiklik
Looks like a bug in  Ducc. Just rebuilt Ducc from trunk and am seeing this
in the sm.log:

07 Oct 2016 11:47:59,477  INFO SM.PingDriver - 0 run  Starting INTERNAL
ping.
07 Oct 2016 11:47:59,655 ERROR SM.PingDriver - 0 handleStatistics
 Missed_pings  1 endpoint UIMA-AS:FixedSleepAE_1:tcp://bluejws65:61617
Alive[false] Healthy[false] + Inf\
o: QDEPTH[0] AveNQ[0] Consum[0] Prod[0] minNQ[0] maxNQ[0] expCnt[0]
inFlt[0] DQ[0] NQ[0] NDisp[0] MetaNode[N/A] MetaPid[N/A]: Cannot issue
getMeta to: FixedSleepAE_1:tcp:\
//bluejws65:61617: java.lang.SecurityException: User name [null] or
password is invalid.

Will check the code this afternoon. Looks like a regression.

Jerry

On Fri, Oct 7, 2016 at 9:30 AM, Wahed Hemati 
wrote:

> Hi,
>
> I am trying to register a service to ducc. It's failing with the exception
> java.lang.SecurityException: User name [null] or password is invalid. The
> exception is in sm.log file
>
> ERROR SM.PingDriver - 0 handleStatistics  Missed_pings  13 endpoint
> UIMA-AS:FixedSleepAE_0:tcp://wahed-pc:61617 Alive[false] Healthy[false] +
> Info: JMX Failure[Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: wahed-pc; nested
> exception is:
> java.net.ConnectException: Connection refused]]] MetaNode[N/A]
> MetaPid[N/A: Cannot issue getMeta to: FixedSleepAE_0:tcp://wahed-pc:61617:
> java.lang.SecurityException: User name [null] or password is inval
> id.
>
> Thanks in advance
>
> -Wahed
>
>


UIMA DUCC java.lang.SecurityException

2016-10-07 Thread Wahed Hemati

Hi,

I am trying to register a service to ducc. It's failing with the 
exception java.lang.SecurityException: User name [null] or password is 
invalid. The exception is in sm.log file


ERROR SM.PingDriver - 0 handleStatistics  Missed_pings  13 endpoint 
UIMA-AS:FixedSleepAE_0:tcp://wahed-pc:61617 Alive[false] Healthy[false] 
+ Info: JMX Failure[Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: wahed-pc; nested 
exception is:
java.net.ConnectException: Connection refused]]] MetaNode[N/A] 
MetaPid[N/A: Cannot issue getMeta to: 
FixedSleepAE_0:tcp://wahed-pc:61617: java.lang.SecurityException: User 
name [null] or password is inval

id.

Thanks in advance

-Wahed



Re: Removed Mbeans

2016-10-07 Thread Jaroslaw Cwiklik
Matthias, I will take a look at this soon.  The undeploy should only remove
MBeans related to a pipeline being undeployed. Not sure how involved a fix
for this will be yet. Just created JIRA for this:
https://issues.apache.org/jira/browse/UIMA-5136

Jerry

On Fri, Oct 7, 2016 at 3:28 AM, Matthias Koch 
wrote:

> Hi,
>
> We are currently using Uima-AS 2.8.1.
> We are deploying several Pipelines on the same tomcat with the
> baseUimaAsynchronousEngine. Then we can see their statistics via JConsole
> and everything seems fine.
> But if we are undeploying on of the pipelines, every jmxMbean is removed.
> We investigated the 'bug' and it seems that the undeploy call calls a
> terminate() method and 5 methods later it leads to a
> JMXManager.destroy call
>
> Line 138 -140 in org.apache.uima.aae.jmx.JmxManager
>
> public void destroy() throws Exception {
> unregisterDomainObjects("org.apache.uima:type=ee.jms.services,*");
>
> }
>
>
> Can we prevent this from happening?
>
> Every time we undeploy a pipeline we lose all statistic of all pipelines.
>
>
> Sincerely,
>
> Matthias
>
>


Removed Mbeans

2016-10-07 Thread Matthias Koch

Hi,

We are currently using Uima-AS 2.8.1.
We are deploying several Pipelines on the same tomcat with the 
baseUimaAsynchronousEngine. Then we can see their statistics via 
JConsole and everything seems fine.
But if we are undeploying on of the pipelines, every jmxMbean is 
removed. We investigated the 'bug' and it seems that the undeploy call 
calls a terminate() method and 5 methods later it leads to a

JMXManager.destroy call

Line 138 -140 in org.apache.uima.aae.jmx.JmxManager

public void destroy() throws Exception {
unregisterDomainObjects("org.apache.uima:type=ee.jms.services,*");

}


Can we prevent this from happening?

Every time we undeploy a pipeline we lose all statistic of all pipelines.


Sincerely,

Matthias