If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Infrequent error when executing trigger

Started by richard@AA, 24 Feb 2017 09:45:38 AM

Previous topic - Next topic

richard@AA



We have a distributed system (4 servers) and we have about 20 triggers that are executed every day, by an application called skybot. basically sends commands, but just like manually executing a trigger. Every couple of days or so we have a (non the same each time) trigger that fails, it happens on different triggers on different servers. below is the error we are receiving from the skybot logs, there is nothing in the Cognos logs. Again, this is happening on different servers (that are executing the trigger) and different triggers, they all work most of the time.


E:\Temp>%CognosScripts%\runTrigger rsp_j2_d
"D:\Program Files (x86)\Skybot\Skybot Scheduler Agent\bin\Win32\eecho" COMPLETED_CMDID_20170224.054207.787: %Errorlevel%
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Connection reset
faultActor:
faultNode:
faultDetail:
   {http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Connection reset
   at java.net.SocketInputStream.read(SocketInputStream.java:208)
   at java.net.SocketInputStream.read(SocketInputStream.java:134)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:247)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:266)
   at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:593)
   at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
   at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
   at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
   at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
   at org.apache.axis.client.Call.invoke(Call.java:2767)
   at org.apache.axis.client.Call.invoke(Call.java:2443)
   at org.apache.axis.client.Call.invoke(Call.java:2366)
   at org.apache.axis.client.Call.invoke(Call.java:1812)
   at com.cognos.developer.schemas.bibus._3.EventManagementServiceStub.trigger(EventManagementServiceStub.java:7925)
   at Trigger.fireTrigger(Trigger.java:190)
   at Trigger.main(Trigger.java:287)

   {http://xml.apache.org/axis/}hostname:CTCOGNOSPAS02

java.net.SocketException: Connection reset
   at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
   at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
   at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
   at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
   at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
   at org.apache.axis.client.Call.invoke(Call.java:2767)
   at org.apache.axis.client.Call.invoke(Call.java:2443)
   at org.apache.axis.client.Call.invoke(Call.java:2366)
   at org.apache.axis.client.Call.invoke(Call.java:1812)
   at com.cognos.developer.schemas.bibus._3.EventManagementServiceStub.trigger(EventManagementServiceStub.java:7925)
   at Trigger.fireTrigger(Trigger.java:190)
   at Trigger.main(Trigger.java:287)
Caused by: java.net.SocketException: Connection reset
   at java.net.SocketInputStream.read(SocketInputStream.java:208)
   at java.net.SocketInputStream.read(SocketInputStream.java:134)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:247)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:266)
   at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:593)
   at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
   ... 12 more

Failed to fire trigger rsp_j2_d.

Note that if a schedule was not triggered, it may be
because the current user does not have sufficient permissions
to access the schedule. For more information, see the
Administration and Security Guide.