OE 11 requiring Xmx parameters for Ubroker components

upgrading from 10.2B to 11.5.
start the admin server - works fine.
start asbroker1 or NS1 - fail with no error.
If I add the -Xms32m -Xmx512m to asbroker1, then asbroker1 will start.

has anyone else experienced something like this ?

Not with that particular set of releases but the general "upgrade, oops, need more memory for Java" problem being solved with a -Xm*.

I haven't heard of that happening yet. We run 10.2B and 11.3, and we're transitioning to 11.4.

Solaris 10 64Bit.

We ran into that some years ago (OE 10.1c). That is because we have up to 10 different AppServer brokers started for different mandators. Usually we saw something like "not enough space" in the log files of the broker. Therefore we added the -Xmx512 ( I guess to the But the AdminServerPlugins.properties file ). But the error might be misleading as you might also see it when the system runs out of memory.

http://knowledgebase.progress.com/articles/Article/P188382

Heavy Regards, RealHeavyDude.

Done quite quite a few 10.1 / 10.2 to 11.4 upgrades, not had to do this so far either.