# Subscription issues in python client

**URL:** <https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914>\
**Category:** General Discussion\
**Created:** [December 14, 2015, 4:34pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914 "2015-12-14T16:34:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [December 14, 2015, 4:34pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/1 "2015-12-14T16:34:55Z")

</div>

Hello all,

I’ve just run into a peculiar problem subscribing to nodes from an external python client :

```auto
PublishService	Returning ServiceFault for request: [PublishRequest requestHandle=9]. StatusCode=StatusCode[Severity=Bad, Subcode=Bad_InternalError]
 	
java.lang.IllegalArgumentException: fromIndex(0) > toIndex(-1)
at java.util.ArrayList.subListRangeCheck(ArrayList.java:1006)
at java.util.ArrayList.subList(ArrayList.java:996)
at com.inductiveautomation.xopc.server.subscriptions.NotificationMessageFactory.createMessageForItems(NotificationMessageFactory.java:118)
at com.inductiveautomation.xopc.server.subscriptions.BaseSubscription.returnNotifications(BaseSubscription.java:583)
at com.inductiveautomation.xopc.server.subscriptions.BaseSubscription.requestReceivedNormal(BaseSubscription.java:453)
at com.inductiveautomation.xopc.server.subscriptions.BaseSubscription.consume(BaseSubscription.java:409)
at com.inductiveautomation.xopc.server.sessions.UaSession.publishRequestReceived(UaSession.java:313)
at com.inductiveautomation.xopc.server.core.services.subscription.PublishService.executeInternal(PublishService.java:38)
at com.inductiveautomation.xopc.server.core.services.subscription.PublishService.executeInternal(PublishService.java:18)
at com.inductiveautomation.xopc.server.core.services.AbstractService.execute(AbstractService.java:51)
at com.inductiveautomation.xopc.server.stack.AbstractUAServer$RequestServer.serveRequest(AbstractUAServer.java:77)
at com.inductiveautomation.xopc.server.stack.AbstractUAServer$RequestServer.run(AbstractUAServer.java:66)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

```

Has anyone ever run into this? I’ve tested the client with other OPC servers, with no problems.

Thanks for your help.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 14, 2015, 5:03pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/2 "2015-12-14T17:03:36Z")

</div>

Do you know what MaxNotificationsPerPublish parameter your client is creating the subscription with?

---

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [December 14, 2015, 5:11pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/3 "2015-12-14T17:11:19Z")

</div>

The default MaxNotificationsPerPublish is 4294967295

---

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [December 14, 2015, 5:13pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/4 "2015-12-14T17:13:05Z")

</div>

Here are all the parameters:

RequestedPublishingInterval = period  
RequestedLifetimeCount = 3000  
RequestedMaxKeepAliveCount = 10000  
MaxNotificationsPerPublish = 4294967295  
PublishingEnabled = True  
Priority = 0

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 14, 2015, 5:50pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/5 "2015-12-14T17:50:09Z")

</div>

Looks like a bug in the server dealing with a value over a certain size. As a workaround you could probably change that value to 0, which let’s the server choose, or use a value \<= 2147483647.

---

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [December 15, 2015, 8:50am UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/6 "2015-12-15T08:50:01Z")

</div>

Ok, I’ll give it a go.

Thanks for looking into this.

---

<div class="post-metadata">

**Author:** ![nifemi](https://avatars.discourse-cdn.com/v4/letter/n/a5b964/32.png) [@nifemi](https://forum.inductiveautomation.com/u/nifemi)\
**Post date:** [December 15, 2015, 1:24pm UTC](https://forum.inductiveautomation.com/t/subscription-issues-in-python-client/10914/7 "2015-12-15T13:24:03Z")

</div>

Brilliant, that did the trick.