Announcement

**claudiobosticco** · 18 Jul 2019, 05:14

same problem with
SmartClient Version: SNAPSHOT_v12.1d_2019-07-17/Enterprise Deployment (built 2019-07-17)

and also I see a series of warning in the developer console, like that:

Code:

*15:13:00.866:WARN:DataSource:JOFC_DOMANDE_AFFILIAZIONE:Field has includeFrom specified as :JOFC_INDIRIZZI.JPC_COMUNI.NOME format not understood - clearing this property

**Isomorphic** · 18 Jul 2019, 10:08

Looking into whether we can reproduce your crash is assigned, although it does look like it could be a class loader confusion problem (eg two copies of Commons Collcetions jars around).

As far as that warning, if you have an includeFrom field like that, that is indeed invalid. There should be one period at most, since neither DataSource names nor field names allow periods.

**claudiobosticco** · 18 Jul 2019, 12:41

Originally posted by Isomorphic View Post

Looking into whether we can reproduce your crash is assigned, although it does look like it could be a class loader confusion problem (eg two copies of Commons Collcetions jars around).

thanks for the hint, but actually I've just updated the isomorphic jars, which in my case are:
isomorphic_assembly.jar
isomorphic_compression.jar
isomorphic_contentexport.jar
isomorphic_core_rpc.jar
isomorphic_js_parser.jar
isomorphic_realtime_messaging.jar
isomorphic_spring.jar
isomorphic_sql.jar
isomorphic_tools.jar

But the strange thing I just realized is that I've got a few validators equals to that field, which are not raising any error.

Originally posted by Isomorphic View Post

As far as that warning, if you have an includeFrom field like that, that is indeed invalid. There should be one period at most, since neither DataSource names nor field names allow periods.

Actually it's a 'multiple indirection' https://www.smartclient.com/smartcli...eld.includeVia

JOFC_INDIRIZZI and JPC_COMUNI are dataSources and NOME is a field.

**claudiobosticco** · 18 Jul 2019, 12:43

I may also try other versions to understand which stopped working for me, for now I'm sure that this was working: SmartClient_SNAPSHOT_v121d_2019-06-25_Evaluation

**claudiobosticco** · 18 Jul 2019, 13:48

Hello, this works for me:
SmartClient_SNAPSHOT_v121d_2019-06-29_Enterprise

this doesn't work:
SmartClient_SNAPSHOT_v121d_2019-07-04_Enterprise

**Isomorphic** · 18 Jul 2019, 14:32

Thank you very much for narrowing it to such a small date range, we're pretty sure we know what checkin caused the issue with the odd stack trace, although it's not clear how yet.

About the includeVia attribute, yes, that's a valid includeVia attribute. Is that warning also something that only just started happening with development builds, and does it seem to be related to the same date range?

**claudiobosticco** · 19 Jul 2019, 02:25

Originally posted by Isomorphic View Post

About the includeVia attribute, yes, that's a valid includeVia attribute. Is that warning also something that only just started happening with development builds, and does it seem to be related to the same date range?

nope, those client-side warning appeared with SmartClient_SNAPSHOT_v121d_2019-07-17_Enterprise (with SmartClient_SNAPSHOT_v121d_2019-07-16_Enterprise there aren't such warnings)

**Isomorphic** · 19 Jul 2019, 17:41

The recently introduced crash (related to java.util.Arrays$ArrayList) should be fixed as of today's build, dated 2019-07-19. Only SC 12.1d should've been affected.

**claudiobosticco** · 20 Jul 2019, 04:55

SNAPSHOT_v12.1d_2019-07-20/Enterprise Deployment

I can confirm it's fixed, thank you very much.
Also, no more warnings.

Announcement

Error while loading dataSource with latest build

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment