Short 8.1 CR2 on its way
by Jason Greene
Hi Everyone,
As soon as we get a clean CI run on the latest master, I plan to cut a 8.1 CR2 for review. We then need to get a TCK & Tools green light and we can rerelease it as a Final (provided no blockers are uncovered).
CR2 fixes some significant issues discovered on CR1, notably a JSF memory leak and some SSL problems on Windows. CR2 also includes the Weld/CR CDI update (1.2 MR spec release), which is why a full TCK rerun is necessary.
Thanks
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11 years, 11 months
Adding timeout section to datasource management GUI
by Philippe Marschall
Hi
We would like to have the <timeout> section from datasource
configuration available in the web based management interface. We tried
to implement it ourselves and then submit submit a pull request. We got
as far as this commit [1] on github. The section and widgets show up in
the management interface but they don't seem connected to the underlying
values. They don't display or update the underlying values. Also the
help does not seem to work. We're still willing to create a pull request
should we be able to get it to work.
[1]
https://github.com/marschall/core/commit/89df3cb84e26ef5fc525858e3529095a...
Cheers
Philippe
11 years, 11 months
Websocket session management
by Hamed Hatami
Hi,
I wanna manage my websocket connection or session when to connecttoserver
at undertow by java client and when the server is not available , the
client try to connect without exception and there is not any timeout to
handle it
Please help me
Regards,
Hamed Hatami
11 years, 11 months
Re: [wildfly-dev] http-executor
by Tomaž Cerar
Hi,
your question is way to generic to properly answer it.
What I can say is that yes we did add few more options to undertow
listeners and few other areas in undertow subsystem.
But without any concrete example what you would like to have or what does
not work for you I cannot help you.
and please, keep discussion about this on wildfly-dev mailing list as it is
interesting topic for many people.
--
tomaz
On Thu, May 8, 2014 at 9:28 AM, Hamed Hatami <hamedhatami2012(a)gmail.com>wrote:
> Hi,
>
> Is it possible that in wildfly 8.1.0 hase more management on websocket
> connection and session at undertow ?
>
> I wanna handle connection timeout to do somethings
>
> Regards,
> Hamed Hatami
> On Feb 18, 2014 1:20 PM, "Tomaž Cerar" <tomaz.cerar(a)gmail.com> wrote:
>
>> Hi,
>>
>> undertow has completely different semantics to what jboss web had before.
>>
>> Undertow uses XNIO worker(s) which are the ones handling the thread pool
>> and few other things.
>> You can configure workers in IO subsystem and tell http listener which
>> one to use.
>>
>> By default in configuration we ship we have one worker named "default"
>> defined and all listeners use it.
>>
>> But if you want to have separate workers (thread pools) per worker, all
>> you need to do is define new worker in IO subsystem and then reference it
>> in http-listener worker="name-of-your-worker-in-io-subsystem"
>>
>> Just bit of note, we did mistake with default values for default worker
>> in 8.0.0.Final release and will fix that in 8.0.1
>>
>> In our testing we got best performance when io-threads ware set to number
>> of logical cpus * 2 and task-max-threads set to number of cpus * 16.
>> This will be defaults we will probably have in 8.0.1 as they perform
>> optimal.
>>
>>
>> --
>> tomaz
>>
>>
>> On Tue, Feb 18, 2014 at 9:37 AM, Hamed Hatami <hamedhatami2012(a)gmail.com>wrote:
>>
>>> Hi,
>>>
>>> I want to use http-executor for my http-listener but it can not possible
>>>
>>> what is the solution?
>>>
>>> Regards,
>>> Hamed Hatami.
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>
>>
11 years, 11 months
Enhancing the HTTP Management Interface Configuration - WFLY-2635
by Darran Lofthouse
I am just about to work on the outstanding task to enhance the
configuration to the HTTP management interface and add some additional
capabilities to it so this mail is really a FYI for those interested as
numerous teams have interest in this area.
The parent Jira issue is here: -
https://issues.jboss.org/browse/WFLY-2635
At the moment there are not many configuration options for the HTTP
interface and we make a lot of decisions ourselves as to how it is
assembled, we now need some additional flexibility.
For the admin console there is a desire to enable alternative
distribution mechanisms so that the console can be served up from
elsewhere. There are no plans to remove the admin console from the
WildFly distribution but users may want to switch to a different
version. For this reason I plan to add configuration for the /console
context to make it possible to either disable the bundles console or to
respond to requests for the console with a redirect.
When we first authentication approaches for the HTTP management
operations we decided to use standard HTTP authentication mechanisms so
that clients could be written in many languages without imposing a
requirement other than the support of standard mechanisms. This in turn
has some problems with web browsers calling the management interface so
cross origin resource sharing has been completely disabled to protect
against malicious cross site scripting attacks. My intention is that
this /management context will remain as a legacy context (not
deprecated) so that clients written to use it can still do so - we may
choose to have it switched off by default but enabling this context will
be a config item.
The next step will be the introduction of a new management context with
a new name, at this stage I am only looking at configuration but this
new context will be updated to support new authentication mechanisms
which will be used directly by the console instead of by the web
browser. By moving credential handling from the web browser to the
console itself we will be able to relax our cross resource sharing
restrictions for this context maybe with configuration of allowed
origins. This will also allow us to remove the current 'Logout' hack
that we have in the console and HTTP interface as the console will be
able to control exactly how long credentials are cached for. This will
also have a useful side effect of allowing a user to open the admin
console multiple times with each instance authenticated as a different user.
At that point it will be possible for the console to be used with
alternative distribution approaches and also will provide a path where
additional SSO mechanisms can be used as these also have a requirement
on CORS.
I will send round some design ideas / config examples next week but if
there are any additional demands on the HTTP management interface in
addition to a path to enabling alternative distribution approaches and
the enablement of SSO not is the time to speak up ;-)
Regards,
Darran Lofthouse.
11 years, 11 months
8.1 CR2 - Patch Tool Testing Heads-Up
by Jason Greene
8.1 will be the first community update to provide a separate download for the patch tool, which allows you to do in-place updates to an existing 8.0 install.
Shortly after CR2 is cut, I will provide a link to a separate and different patch file download, along with some instructions for how to use the update with the patch command. I would appreciate everyone trying this out, and reporting back any issues.
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11 years, 11 months
