[aerogear-dev] [simplepush] Netty Subsystem

[Daniel Bevenius]

Hey Seb,

this is actually logged at info level by Netty. I've fixed this locally as
part of some threading work and should be able to check this in tomorrow.
You'll still see this in the log but the log level will be corrent.

/Dan


On 14 May 2013 16:55, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi Dan,
> When following your instructions after starting the server I got this
> error in the output :
>
> 16:52:15,790 ERROR [stderr] (MSC service thread 1-6) [MSC service thread
> 1-6] INFO io.netty.util.internal.PlatformDependent - You don't have
> Javassist in your class path or you don't have enough permission to load
> dynamically generated classes.  Please check the configuration for better
> performance.
> 16:52:15,791 ERROR [stderr] (MSC service thread 1-6) [MSC service thread
> 1-6] INFO io.netty.util.internal.PlatformDependent - Your platform does not
> provide complete low-level API for accessing direct buffers reliably.
> Unless explicitly requested, heap buffer will always be preferred to avoid
> potential system unstability.
>
> Anything to do with Wildfly Alpha ?
>
> Seb
>
>
>
> On Tue, May 14, 2013 at 2:34 PM, Lucas Holmquist <lholmqui at redhat.com>wrote:
>
>> awesome!!
>>
>> On May 14, 2013, at 7:06 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> Cool stuff :)
>>
>>
>> On Tue, May 14, 2013 at 10:08 AM, Daniel Bevenius <
>> daniel.bevenius at gmail.com> wrote:
>>
>>> This thread will discuss our deployment strategy for the SimplePush
>>> Server with AS7.x/WildFly.
>>>
>>> A description of the goals of this subsystem and its usage can be found
>>> in the readme:
>>> https://github.com/danbev/netty-subsystem
>>>
>>> As described in the readme, we want to have a way of running Netty based
>>> servers, but have them managed by AS7.x/WildFly. What we mean is that
>>> things like network interfaces, ports, thread factories, etc. should be
>>> configurable and managed by the application server.
>>> So, we are trying to find a user friendly way of doing this and at the
>>> same time make sure we play nicely with the application server when it
>>> comes to resources usage.
>>> The current implementation far from ready, but we'd like to get feedback
>>> on our approach sooner rather than later.
>>>
>>> Let us know if you have any comments/suggestions!
>>>
>>> /Dan
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130514/6351e3b6/attachment.html