Skip to main content

I have a Visibroker 4.5 server in JAVA (6). I am currently porting the client from JAVA to CSharp using VisiNet 8.0.

For some IDL, I have a MARSHALL Exception on the server with the Visinet client (no pb with visibroker 4.5 client). It's look like very closed to the problem described here:

community.microfocus.com/.../15881.backward-compatibility-issue-with-visinotify-6-5-using-typecode-optimization.aspx

Unfortunately, setting vbroker.typecode.noIndirection=true has no effect.

Does Visinet supports this property ? Any over idea on the problem ?

I have a Visibroker 4.5 server in JAVA (6). I am currently porting the client from JAVA to CSharp using VisiNet 8.0.

For some IDL, I have a MARSHALL Exception on the server with the Visinet client (no pb with visibroker 4.5 client). It's look like very closed to the problem described here:

community.microfocus.com/.../15881.backward-compatibility-issue-with-visinotify-6-5-using-typecode-optimization.aspx

Unfortunately, setting vbroker.typecode.noIndirection=true has no effect.

Does Visinet supports this property ? Any over idea on the problem ?

From the limited information provide, it is difficult to make any conclusion.

Are you still using VisiBroker for Java 4.5 with JAVA 6 at the server side now? FYI, Visibroker 4.5 is very old and is also not certified with JAVA 6.

Can you try using Visibroker for Java 8.5 at the server side to verify whether the issue still occur when using the newer version ?

I have a Visibroker 4.5 server in JAVA (6). I am currently porting the client from JAVA to CSharp using VisiNet 8.0.

For some IDL, I have a MARSHALL Exception on the server with the Visinet client (no pb with visibroker 4.5 client). It's look like very closed to the problem described here:

community.microfocus.com/.../15881.backward-compatibility-issue-with-visinotify-6-5-using-typecode-optimization.aspx

Unfortunately, setting vbroker.typecode.noIndirection=true has no effect.

Does Visinet supports this property ? Any over idea on the problem ?

Setting the undocumented vbroker.orb.backCompatAlign property to true, solves the problem.

VisiBroker 4.5 aligns types such as double on double word memory boundary. Setting this property on the client side sets the same behaviour.

I have a Visibroker 4.5 server in JAVA (6). I am currently porting the client from JAVA to CSharp using VisiNet 8.0.

For some IDL, I have a MARSHALL Exception on the server with the Visinet client (no pb with visibroker 4.5 client). It's look like very closed to the problem described here:

community.microfocus.com/.../15881.backward-compatibility-issue-with-visinotify-6-5-using-typecode-optimization.aspx

Unfortunately, setting vbroker.typecode.noIndirection=true has no effect.

Does Visinet supports this property ? Any over idea on the problem ?

Sebastien, That's great debugging skill !!

The solution that you've contributed to this forum will be very helpful to the VisiBroker community.

Terms & ConditionsAccessibility statement