Latest Contributions by VladimirStrinski

Just my 2c - Although I understand the reasoning behind I think the specific solution is causing more trouble than helping. If possible I'd like to have an option or a switch in the API whether I want this extra behavior, or I'd rather see the mixed content warning messages in the console. There are valid business scenarios when serving and accessing pages and layers via localhost is needed. In such cases HTTP is a good solution. By adding a fake certificate to fake security we are merely masking the issue, and not necessarily adding any security. It is rather the opposite - adding and trusting an insecure certificate that shouldn't be trusted. Imagine the case where a department with hundreds of computers will need to have a fake certificate generated and be made trusted on each of those machines. Separately from all that, the "isSecureContext" is still an experimental technology (as per the MDN page), and that behavior may change by the time it becomes an official standard. ... View more

Hello RJ, Thanks for the update. We're looking to test the solution in 10.6.1. Unfortunately the suggestion "As a work around please consider manually creating a GeoEvent Definition which is flat (e.g. no Group elements)." does not work for us - the data comes from a third party and we have no control over its structure. We don't have an option to use "no Group elements". As of 10.6 this issue has been confirmed to still be present. Regards, Vladimir ... View more

Chris and RJ - Thanks for the prompt updates! And yes - I am interested in being able to extract that XML and give this option a shot. If that procedure is documented somewhere can you please point me in the right direction? Feel free to PM me the link if you prefer. If not we can follow up with Tech Support. Regards, Vladimir ... View more

Some more details and observations - Using latest Chrome I hit the issue almost all the time and can't edit definitions with sub-attributes. Using IE11 it works fine until I hit 15 sub-attributes. Using latest FireFox it failed me today at the 12th attribute. This has become a major pain, exaggerated by an upcoming conference where we need to show GeoEvent Server and do demos and teach customers. Any help would be greatly appreciated! ... View more

Confirmed: Up until 14 sub-attributes it works fine. As soon as I add the 15th sub-attribute it starts misbehaving. I've been able to reproduce this 4 times so far (the first two accidentally) Is there a separate process for submitting bugs? Or will this thread suffice? And any updates with an estimate for the bugfix would be more than welcome. Regards, Vladimir ... View more

Is there a limit on the number of sub-attributes? I may have hit the same issue after I added the 15th sub-attribute. ... View more

Once it gets messed up it has other consequences too - even though the definition claims to have a TRACK_ID field it later claims that such doesn't exist: TRAC_ID does exist: and when yet trying to create a stream output it claims it doesn't have it: I am not sure what did I change or did to make this issue reappear. Somehow the previous few times all of this worked fine and then it stopped. Regards, Vladimir ... View more

Another update - as soon as any field is auto-discovered I hit the issue. I can tell if I will have the issue when I go to the nested attribute details - e.g. the URL would be like "https://geoevent.host.local:6143/geoevent/manager/attributefield.html?guid=394aa517-f7e8-412a-9c8a-90b3e25c32ad". If that page displays all sub-attribute then everything works fine. In the cases when I hit the issue that page displays a blank list of sub-attributes. In my test I manually created a definition with sub-attributes and everything worked fine until I activated "learning mode" in the input service and it added a few more sub-attributes.  I also see a few error messages in the log that look like: com.esri.ges.messaging.jms.GeoEventImplSerializer An unexpected error occurred while attempting to serialize the GeoEvent to a Byte Array. Error: Index: 80, Size: 19. preceeded by: com.esri.ges.messaging.jms.GeoEventImplSerializer Index: 80, Size: 19 java.lang.IndexOutOfBoundsException: Index: 80, Size: 19 at java.util.ArrayList.rangeCheck(ArrayList.java:653)[:1.8.0_121] at java.util.ArrayList.get(ArrayList.java:429)[:1.8.0_121] at com.esotericsoftware.kryo.util.MapReferenceResolver.getReadObject(MapReferenceResolver.java:60)[389:com.esotericsoftware.kryo:3.0.3] at com.esotericsoftware.kryo.Kryo.readReferenceOrNull(Kryo.java:834)[389:com.esotericsoftware.kryo:3.0.3] at com.esotericsoftware.kryo.Kryo.readObjectOrNull(Kryo.java:728)[389:com.esotericsoftware.kryo:3.0.3] at com.esri.ges.messaging.jms.GeoEventImplSerializer.readField(GeoEventImplSerializer.java:182)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.read(GeoEventImplSerializer.java:159)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.readFieldGroup(GeoEventImplSerializer.java:213)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.readField(GeoEventImplSerializer.java:201)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.read(GeoEventImplSerializer.java:159)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.read(GeoEventImplSerializer.java:106)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.GeoEventImplSerializer.read(GeoEventImplSerializer.java:34)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esotericsoftware.kryo.Kryo.readObject(Kryo.java:708)[389:com.esotericsoftware.kryo:3.0.3] at com.esri.ges.messaging.jms.GeoEventImplSerializer.fromBytes(GeoEventImplSerializer.java:65)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.amqp.AmqpMessagingFactory$AmqpGeoEventConsumer.receive(AmqpMessagingFactory.java:292)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.ges.messaging.jms.MessagingImpl$ConsumerThread.run(MessagingImpl.java:193)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] I am not sure if those are related, but they happen when I activate the "learning mode". I suppose as part of the "learning" mode might be okay to guess wrong and thus cause those. Hopefully this helps. Regards, Vladimir ... View more

I just did another test - I manually created a nested definition and everything worked. However with auto-generated ones the issue reappears. ... View more

Hi Chris - thanks for the quick reply! And yes, I can reproduce it on demand. You are correct that it happens on 1) auto-generated definitions that have 2) nested (groupped) JSON. My JSON has two groups - geometry and attributes. When creating the definition I can tell it to look at just the "attributes" group (by putting the name - "attributes" in "JSON Object Name:") and then it doesn't create a nested definition. When it is not nested everything works (but I lose the geometry). To reproduce it - consume a JSON by subscribing to a web socket. If the incoming JSON has nested attributes I hit this issue. Regards, Vladimir ... View more

Probably a related observation - this most often happens on auto-generated definitions. I don't remember seeing it happen on a definition that I've created manually. ... View more