No service named urn:PegaRULES:SOAP:PegaAES:Events is available
Hello,
We can see many time on AES log the error message :
No service named urn:PegaRULES:SOAP:PegaAES:Events is available
No service named urn:PegaRULES:SOAP:PegaAES:Events#logAlert is available
Something can tell me how, and where we can configure this, to prevent this error.
Hello, and tahnks you for this response ;
AES version : 03.04
we don't find any log on monitored node or on AES node.
I join some screen of dynatrace tool (supervision tool on jboss node) that show this error.
We can see the error and the related jboss monitored instance
Thanks you
Hi Yoann,
Even we are observing similar error in Dynatrace. Were you able to solve this problem ?
Message: No service named urn:PegaRULES:SOAP:PegaAES:Events is available
Message: No service named urn:PegaRULES:SOAP:PegaAES:Events#logAlert is available
Exception Details
Type: ConfigurationException: No service named urn:PegaRULES:SOAP:PegaAES:Events is available
Exception Class: com.pega.apache.axis.ConfigurationException
Message: No service named urn:PegaRULES:SOAP:PegaAES:Events is available
Thread Name: Dispatcher-Thread-116 <431036849>
Exception StackTrace
Method Class Line File Name
getService com.pega.apache.axis.configuration.FileProvider 234 <unknown>
getService com.pega.apache.axis.AxisEngine 311 <unknown>
setTargetService com.pega.apache.axis.MessageContext 756 <unknown>
invoke com.pega.apache.axis.client.Call 2733 <unknown>
invoke com.pega.apache.axis.client.Call 2437 <unknown>
invoke com.pega.apache.axis.client.Call 2360 <unknown>
invoke com.pega.apache.axis.client.Call 1804 <unknown>
sendEvent com.pega.pegarules.priv.util.SOAPAppenderPega 310 <unknown>
_append com.pega.pegarules.priv.util.SOAPAppenderPega 278 <unknown>
append com.pega.pegarules.priv.util.SOAPAppenderPega 155 <unknown>
doAppend com.pega.pegarules.priv.util.SOAPAppenderPega 902 <unknown>
appendLoopOnAppenders com.pega.apache.log4j.helpers.AppenderAttachableImpl 66 <unknown>
run com.pega.apache.log4j.AsyncAppender$Dispatcher 578 <unknown>
run java.lang.Thread 767 <unknown>
Exception Details
Type: ConfigurationException: No service named urn:PegaRULES:SOAP:PegaAES:Events#logAlert is available
Exception Class: com.pega.apache.axis.ConfigurationException
Message: No service named urn:PegaRULES:SOAP:PegaAES:Events#logAlert is available
Thread Name: Dispatcher-Thread-116 <431036849>
Exception StackTrace
Method Class Line File Name
getService com.pega.apache.axis.configuration.FileProvider 234 <unknown>
getService com.pega.apache.axis.AxisEngine 311 <unknown>
setTargetService com.pega.apache.axis.MessageContext 756 <unknown>
setupMessageContextImpl com.pega.apache.axis.transport.http.HTTPTransport 89 <unknown>
setupMessageContext com.pega.apache.axis.client.Transport 46 <unknown>
invoke com.pega.apache.axis.client.Call 2763 <unknown>
invoke com.pega.apache.axis.client.Call 2437 <unknown>
invoke com.pega.apache.axis.client.Call 2360 <unknown>
invoke com.pega.apache.axis.client.Call 1804 <unknown>
sendEvent com.pega.pegarules.priv.util.SOAPAppenderPega 310 <unknown>
_append com.pega.pegarules.priv.util.SOAPAppenderPega 278 <unknown>
append com.pega.pegarules.priv.util.SOAPAppenderPega 155 <unknown>
doAppend com.pega.pegarules.priv.util.SOAPAppenderPega 902 <unknown>
appendLoopOnAppenders com.pega.apache.log4j.helpers.AppenderAttachableImpl 66 <unknown>
run com.pega.apache.log4j.AsyncAppender$Dispatcher 578 <unknown>
run java.lang.Thread 767 <unknown>
Hello,
We've opened the SR-A77131 and we got from Pega the following answer:
«We have checked with our product development team and we came to know that there will not be any impact with this exception.
The reason for this exception is, there is an exception scenario in the normal code flow(which is part of a standard third party tool i.e : apache AXIS) and it is executing the alternate solution/code flow once exception is raised. Because of that we are not writing that error/exception anywhere in the pega related log files.
DynaTrace is great for examining garbage collection because of that it is capturing that exception and showing it. As there is no performance or functional issue with this we can ignore it.»
Regards,
Duarte
what is your AES version? Is this happening in AES server log or on the monitored node? If you can attach the actual log file, it would help.