Hi!

Just as a chrioisty, do you have tried G1 too?

Il mar 7 feb 2017, 22:07 abhijith <topcoderabhij...@gmail.com> ha scritto:

> Hi,
>
> Has there any test done for Artemis using CMS GC?
>
> Context:  We were using default parallel GC with 6G RAM and were facing an
> issue where old gen was filling up without full GC being run.  We use Netty
> Transport configuration and have one master/slave setup with static
> configuration.  Our monitoring alerts for total memory usage were firing.
> So we ran some tests and found that old gen was growing very slowly in case
> of CMS, but very rapidly in case of parallel GC.
>
> We switched to using CMS, but after changing to CMS we started seeing
> connection errors when session factory is trying to create a new
> connection.
> This was happening consistently which forced us to roll back.  After
> rollback with parallel gc we do not see this issue at all.  We are kind of
> confused on how selection of GC can affect creating new connections.  Any
> insight would be really helpful.
>
> GG parameters:  "-XX:+UseFastAccessorMethods -Xms8G -Xmx8G
> -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
> -XX:CMSIncrementalDutyCycleMin=10 -XX:CMSIncrementalDutyCycle=20
> -XX:+CMSIncrementalPacing -XX:+CMSClassUnloadingEnabled "
>
> Caused by:
> org.apache.activemq.artemis.api.core.ActiveMQIllegalStateException:
> AMQ119024: Could not select a TransportConfiguration to create
> SessionFactory
>         at
>
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:773)
> ~[artemis-core-client-1.4.0.jar:1.4.0]
>         at
>
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:756)
> ~[artemis-jms-client-1.4.0.jar:1.4.0]
>         ... 122 common frames omitted
>
> Thanks
> Abhi
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Artems-ParallelGC-vs-CMS-tp4721722.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Reply via email to