Author Message
RenatoPinheiro
Joined: Nov 16, 2011
Messages: 9
Location: São Paulo - SP - Brazil
Offline
Hi,

We have an application already in production that uses JTAPI tp listen to events in a set of extensions and when there is active call on them, it adds a new party to the call with service observation. The application works well, but we had a problem reported by the customer that the application stopped working.

The log file indicate that the application had the JTAPI provider shutdown and then it stopped receiving events. It got the following error:


ERROR 2013-06-29 11:59:08,568 [DistributeCSTAEvent] (TSEventHandler.java:3026) - Event Distributor Exception - shutting down provider TSProvider[#1]@1c44a6d

Is there any reason for that to happen? How can I avoid this problem to happen again?
The AES version is 5.2.

thanks,
Renato
RenatoPinheiro
Joined: Nov 16, 2011
Messages: 9
Location: São Paulo - SP - Brazil
Offline
additional info: the application also uses dmcc to register to the extensions that will be added to the call (with service observation)

regards,
Renato
ShantanuJoshi
Joined: Dec 12, 2013
Messages: 21
Offline
Hi Renato,

Do you have a complete stacktrace? The line in the error message below is in a function which is called from multiple places in JTAPI. We need to determine exactly where the error occurred. You might need to increase the JTAPI debugLevel in the TSAPI.PRO file to get more information.

Shantanu
RenatoPinheiro
Joined: Nov 16, 2011
Messages: 9
Location: São Paulo - SP - Brazil
Offline
Hi Joshi,

Thanks for the answer.
There are more exceptions that follows after that, which I think may be because of that first exception I posted.
I hope it helps, this the trace I have:

[DistributeCSTAEvent] (TSEventHandler.java:3026) - Event Distributor Exception - shutting down provider TSProvider[#1]@1c44a6d
EERROR 2013-06-29 11:59:08,568RROR 2013-06-29 11:59:08,568 [DistributeCSTAEvent] (TSEventHandler.java:3027) - com.avaya.jtapi.tsapi.impl.core.TSCall cannot be cast to com.avaya.jtapi.tsapi.impl.core.TSDevice
java.lang.ClassCastException: com.avaya.jtapi.tsapi.impl.core.TSCall cannot be cast to com.avaya.jtapi.tsapi.impl.core.TSDevice
   at com.avaya.jtapi.tsapi.impl.core.TSEventHandler.doConnEvents(TSEventHandler.java:1347)
   at com.avaya.jtapi.tsapi.impl.core.TSEventHandler.cstaUnsolicited(TSEventHandler.java:303)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventDistributor.handleEvent(TsapiEventDistributor.java:113)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventQueue.run(TsapiEventQueue.java:104)
ERROR 2013-06-29 11:59:10,048 [Thread-14849] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88774
com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:556)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:471)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.makeCall(Tsapi.java:1199)
   at com.avaya.jtapi.tsapi.impl.core.TSCall.fastConnect(TSCall.java:5233)
   at com.avaya.jtapi.tsapi.impl.TsapiCall.fastConnect(TsapiCall.java:2086)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:86)
   at java.lang.Thread.run(Thread.java:662)
ERROR 2013-06-29 11:59:10,049 [Thread-14850] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88929
com.avaya.jtapi.tsapi.TsapiPlatformException: no conf event
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:556)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:471)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.makeCall(Tsapi.java:1199)
   at com.avaya.jtapi.tsapi.impl.core.TSCall.fastConnect(TSCall.java:5233)
   at com.avaya.jtapi.tsapi.impl.TsapiCall.fastConnect(TsapiCall.java:2086)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:86)
   at java.lang.Thread.run(Thread.java:662)
ERROR 2013-06-29 11:59:10,551 [Thread-14849] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88774
com.avaya.jtapi.tsapi.TsapiUnableToSendException: client not in service
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:527)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.sendAsync(TsapiSession.java:478)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDeviceInfoAsync(Tsapi.java:1076)
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.<init>(TSDevice.java:2455)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:2520)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1685)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1659)
   at com.avaya.jtapi.tsapi.impl.TsapiProvider.getAddress(TsapiProvider.java:279)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:77)
   at java.lang.Thread.run(Thread.java:662)
ERROR 2013-06-29 11:59:10,551 [Thread-14850] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88929
com.avaya.jtapi.tsapi.TsapiUnableToSendException: client not in service
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:527)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.sendAsync(TsapiSession.java:478)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDeviceInfoAsync(Tsapi.java:1076)
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.<init>(TSDevice.java:2455)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:2520)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1685)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1659)
   at com.avaya.jtapi.tsapi.impl.TsapiProvider.getAddress(TsapiProvider.java:279)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:77)
   at java.lang.Thread.run(Thread.java:662)
ERROR 2013-06-29 11:59:11,053 [Thread-14849] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88774
com.avaya.jtapi.tsapi.TsapiUnableToSendException: client not in service
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:527)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.sendAsync(TsapiSession.java:478)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDeviceInfoAsync(Tsapi.java:1076)
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.<init>(TSDevice.java:2455)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:2520)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1685)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1659)
   at com.avaya.jtapi.tsapi.impl.TsapiProvider.getAddress(TsapiProvider.java:279)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:77)
   at java.lang.Thread.run(Thread.java:662)
ERROR 2013-06-29 11:59:11,054 [Thread-14850] (CallSOConnectionCreatorThread.java:91) - Error when trying to call:(fac+host):18885922 from 88929
com.avaya.jtapi.tsapi.TsapiUnableToSendException: client not in service
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:527)
   at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.sendAsync(TsapiSession.java:478)
   at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDeviceInfoAsync(Tsapi.java:1076)
   at com.avaya.jtapi.tsapi.impl.core.TSDevice.<init>(TSDevice.java:2455)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:2520)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1685)
   at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.createDevice(TSProviderImpl.java:1659)
   at com.avaya.jtapi.tsapi.impl.TsapiProvider.getAddress(TsapiProvider.java:279)
   at com.avaya.ept.bbhbeeptone.server.callmanagement.CallSOConnectionCreatorThread.run(CallSOConnectionCreatorThread.java:77)
   at java.lang.Thread.run(Thread.java:662)
DEBUG 2013-06-29 11:59:11,555 [Thread-14849] (CallSOConnectionCreatorThread.java:104) - END SO CREATION!
DEBUG 2013-06-29 11:59:11,556 [Thread-14850] (CallSOConnectionCreatorThread.java:104) - END SO CREATION!
Jul 7, 2013 3:23:52 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 32814
Jul 7, 2013 3:24:12 AM org.apache.jk.common.ChannelSocket receive
WARNING: can't read body, waited #256
Jul 7, 2013 3:24:12 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: Closing ajp connection -1
Jul 7, 2013 3:24:12 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 5635
Jul 7, 2013 3:24:12 AM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 70
Jul 7, 2013 3:24:12 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 5120
Jul 7, 2013 3:24:32 AM org.apache.jk.common.ChannelSocket receive
WARNING: can't read body, waited #5376
Jul 7, 2013 3:24:32 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: Closing ajp connection -1
Jul 7, 2013 3:24:32 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 5635
Jul 7, 2013 3:24:32 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: Closing ajp connection 0
Jul 7, 2013 3:24:32 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 18245
Jul 7, 2013 3:24:32 AM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.lang.IndexOutOfBoundsException
   at java.io.BufferedInputStream.read(BufferedInputStream.java:310)
   at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:628)
   at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:585)
   at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:693)
   at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898)
   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
   at java.lang.Thread.run(Thread.java:662)
Jul 7, 2013 3:24:32 AM org.apache.jk.common.MsgAjp processHeader
SEVERE: BAD packet signature 18245
Jul 7, 2013 3:24:32 AM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
ShantanuJoshi
Joined: Dec 12, 2013
Messages: 21
Offline
Hi,

java.lang.ClassCastException: com.avaya.jtapi.tsapi.impl.core.TSCall cannot be cast to com.avaya.jtapi.tsapi.impl.core.TSDevice

This is a known issue which was fixed recently, and the fix will be in the next release of AES (6.3.1).

Shantanu
RenatoPinheiro
Joined: Nov 16, 2011
Messages: 9
Location: São Paulo - SP - Brazil
Offline
Hi Joshi,


Do you know if an AES upgrade will be required? (The customer currently uses AES 5.2)
Or, if I just upgrade the jtapi library will fix the issue?

Also, do you know when this version will be released?

thank you!
Renato
ShantanuJoshi
Joined: Dec 12, 2013
Messages: 21
Offline
Hi,
Just the JTAPI library will need to be updated, and it will be backward compatible. AES 6.3.1 will be available in October 2013.

Shantanu
RenatoPinheiro
Joined: Nov 16, 2011
Messages: 9
Location: São Paulo - SP - Brazil
Offline
Hi,

I am thinking in adding a listener to the provider to check its health and if it is detected that the provider is out of service, the application will then try to reconnect the provider and so make it back to work again.
Do you know if in this case it is possible to recover jtapi connection?

thanks,
Renato
ShantanuJoshi
Joined: Dec 12, 2013
Messages: 21
Offline
It's not possible to reconnect an existing provider which has shutdown. Instead, when the provider shuts down, the listener will be receive an event, and you can create a new provider. Any call listeners created using the old provider will no longer be valid, and will need to be added again using the new provider. Any Call objects using the old provider will also no longer be valid.
Go to:   
Mobile view