https://github.com/netty/netty/issues/6931
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-1-Spring-MessageListener-Netty-StackOverflow-tp4728139p4728291.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Mind sharing the link where that was said? Just curious now.
On Thu, Jul 6, 2017 at 1:27 PM, abhijith wrote:
> To close this loop, Netty guys suggested to increase stack size(Xss) instead
> of downgrading version. Bumping stack size from 256K to 1024K worked and we
> don't see the error anymore.
To close this loop, Netty guys suggested to increase stack size(Xss) instead
of downgrading version. Bumping stack size from 256K to 1024K worked and we
don't see the error anymore.
Thanks everyone for quick help
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v
Ignore you stated already this is tried. My apologies
Sent from my iPad
> On 1 Jul 2017, at 06:14, Michael André Pearce
> wrote:
>
>
> The chm was removed in Feb, does this occur if you use 4.1.12?
>
> https://github.com/netty/netty/commit/84188395be36893b214fcf63cea1544e35b2a654
>
> Sent f
The chm was removed in Feb, does this occur if you use 4.1.12?
https://github.com/netty/netty/commit/84188395be36893b214fcf63cea1544e35b2a654
Sent from my iPad
> On 1 Jul 2017, at 02:12, Clebert Suconic wrote:
>
> If you have a way to replicate it... Norman was looking for a
> replicator on t
If you have a way to replicate it... Norman was looking for a
replicator on that thread. He's usually responsive if it's easy to
replicate.. (him or other guys maintaining netty).
if you have an easy way to replicate.. don't be shy.. talk on the
netty issue Justin showed you.
On Fri, Jun 30, 2017
The issue seems isolated to Spring + Solaris at this point so I don't think
there's reason to change the dependency right now - especially since
there's a workaround (i.e. downgrading to 4.1.4). That said, if we find
the issue isn't quite so isolated and/or the Netty developers are slow to
resolve
https://github.com/netty/netty/issues/6931 -- Opened an issue in Netty
backlog
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-1-Spring-MessageListener-Netty-StackOverflow-tp4728139p4728150.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks Justin...appreciate your quick help on this. Looks like v4.1.4.final
is working. Will run some more tests and confirm next week.
It is netty issue and I will raise a bug for them. But, since Artemis is
really dependent on this, should Artemis have netty 4.1.4.final dependency
instead of 4
In any event, it appears this is a Netty issue so it would probably be best
to work with the Netty community on it.
Justin
On Fri, Jun 30, 2017 at 5:00 PM, Justin Bertram wrote:
> The actual problem occurs in a call to
> PlatformDependent.newConcurrentHashMap()
> introduced here [1] in Netty
The actual problem occurs in a call to
PlatformDependent.newConcurrentHashMap() introduced here [1] in Netty
4.1.5.Final. Try using Netty 4.1.4.Final. If the behavior here really is
platform dependent that might explain why you're only seeing it on Solaris.
Justin
[1]
https://github.com/netty/
Please find above stacktrace. I will try to get test case for this, but it
is not repeatable on my Mac. I can get this only on Solaris. Will see if I
can repeat it consistently.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-1-Spring-MessageListener-Netty-S
FWIW, it appears this commit [1] from 2013 is the one that changed the
behavior as compared to Netty 4.0.39.Final which was used in Artemis
1.4.0. That commit is in every version of Netty 4.1 so it's not surprising
you saw the same behavior using 4.1.12.Final.
As far as reverting back to a pre-4.
Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'messageListenerContainer' defined in c.p.c.MySpringConfiguration:
Invocation of init method failed; nested exception is
java.lang.StackOverflowError
at
org.springframework.bean
Is that the full stack-trace? I imagine there is something before the call
to org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.
createSessionFactory().
Also, this Netty issue [1] looks similar. It involves a stack overflow
with Spring and java.security.SecureClassLoader.defineClass
We have a load balancer in front on Artemis which does ssl offloading. To
handle this we have custom ConnectionLoadBalancingPolicy. This policy
determines which transport configuration to use for initial connection
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis
What do you mean by "custom policy"?
Justin
On Fri, Jun 30, 2017 at 3:18 PM, abhijith
wrote:
> Hi all,
>
> We are facing a weird issue while using Spring
> DefaultMessageListenerContainer with Artemis v2.1 client.
>
> We have below piece of code on our custom policy which is run on a Solaris
>
Hi all,
We are facing a weird issue while using Spring
DefaultMessageListenerContainer with Artemis v2.1 client.
We have below piece of code on our custom policy which is run on a Solaris
box.
try (ServerLocatorImpl serverLocator = new ServerLocatorImpl(false,
transportConfiguration)) {
18 matches
Mail list logo
