Issue with use RAM 7.5 client jar with RAM 7.2 server
We are using the RAM 7.2 server but plan to upgrade to 7.5 soon. Before that, we plan to test if RAM 7.5 client jar is workable while connect to RAM 7.2.
When I directly connect to RAM 7.2 by call 7.5 client jar, seems no problem. But after one or two days, it can not find RAM session if we want to call RAM API. We not sure if RAM session can not found is caused by this using 7.5 client jar behavior.
Is RAM support using 7.5 client jar to connect 7.2 server?
Thanks.
When I directly connect to RAM 7.2 by call 7.5 client jar, seems no problem. But after one or two days, it can not find RAM session if we want to call RAM API. We not sure if RAM session can not found is caused by this using 7.5 client jar behavior.
Is RAM support using 7.5 client jar to connect 7.2 server?
Thanks.
13 answers
Fraid not. Each session is individually owned.
But I have a question of why you have so many sessions in the first place?
If you create multiple RAM sessions in the same Java VM instance that
connects to the same RAM server (using identical URLs) and for the same
user then only two host sessions should be used up. All such RAMSessions
in that VM will share the same two sessions.
If you are kicking off multiple and separate Java VM instances that are
long running but all for the same user then that could cause your problem.
--
Rich Kulp
Rational Asset Manager developer
But I have a question of why you have so many sessions in the first place?
If you create multiple RAM sessions in the same Java VM instance that
connects to the same RAM server (using identical URLs) and for the same
user then only two host sessions should be used up. All such RAMSessions
in that VM will share the same two sessions.
If you are kicking off multiple and separate Java VM instances that are
long running but all for the same user then that could cause your problem.
--
Rich Kulp
Rational Asset Manager developer
page 2of 1 pagesof 2 pages