Misconfigured device causes ProviderOutOfServiceEvent

[derrickgunter]

Hi Everyone,

We have a customer that mistakenly associated a logout profile with a device with no lines configured.  As shown in the attached jtapi log this resulted in an DeviceLineInfoEvent error followed by a NullPointerException. It appears that this one device problem then causes the entire provider to go out of service.

Cisco Jtapi version 8.6(2.10000)-2 Release.

1. Does this diagnosis appear correct?  If so...
2. Is this a normal behavior - provider going out of service from just one bad device/profile?
3. Is there a fix in a more recent JTAPI version?

Thank you,

Derrick

Here is the the problem:

11217: Apr 08 03:58:36.932 EST %JTAPI-PROTOCOL-7-UNK:(P1-58.162.162.112)Error with DeviceLineInfoEvent received for device: SEP500604732F73 with error: -1932787712

11218: Apr 08 03:58:36.932 EST %JTAPI-MISC-7-UNK:(P1-58.162.162.112) EventThread: queuing com.cisco.cti.protocol.ProviderGetSingleDeviceAndLinesCompletedEvent

11219: Apr 08 03:58:36.936 EST %JTAPI-CTIIMPL-7-UNK:(P1-58.162.162.112) caught java.lang.NullPointerException

java.lang.NullPointerException

  at com.cisco.cti.client.implementation.Provider.handleEvent(Provider.java:2900)

  at com.cisco.cti.client.implementation.Provider$EventThread.messageReceived(Provider.java:610)

  at com.cisco.cti.util.MessageThread.deliver(MessageThread.java:358)

  at com.cisco.cti.util.MessageThread.deliverAll(MessageThread.java:327)

  at com.cisco.cti.util.MessageThread.run(MessageThread.java:282)

11220: Apr 08 03:58:36.936 EST %JTAPI-CTIIMPL-7-UNK:(P1-58.162.162.112) EventThread handling event com.cisco.cti.protocol.ProviderGetSingleDeviceAndLinesCompletedEvent[969]

11221: Apr 08 03:58:36.936 EST %JTAPI-PROTOCOL-7-UNK:(P1-58.162.162.112) Received ProviderGetSingleDeviceAndLinesCompletedEvent

11222: Apr 08 03:58:36.936 EST %JTAPI-PROTOCOL-7-UNK:(P1-58.162.162.112) received Event: com.cisco.cti.protocol.ProviderOutOfServiceEvent {

  eventSequence                 = 970

  PROVIDER_OUT_OF_SERVICE_EVENT = 200

  }

11223: Apr 08 03:58:36.937 EST %JTAPI-MISC-7-UNK:(P1-58.162.162.112) EventThread: queuing com.cisco.cti.protocol.ProviderOutOfServiceEvent

[derrickgunter]

Any ideas?  Thanks!

[mpotluri · Accepted solution]

Attached log ends at Apr 08 03:58:35.690 EST just before the snippet mentioned in this thread. During the initialization if JTAPI is unable to create a Terminal correctly it would bail and restart the initialization process. The initialization process is changed/optimized in CUCM 9.0 and we should not see this issue.

[derrickgunter]

Thanks Mohan.  That answers my question.  I attached the correct jtapi log as jtapi.zip.