[JBoss JIRA] (WFLY-3295) AsyncContext#start runs in caller thread
by Philippe Marschall (JIRA)
Philippe Marschall created WFLY-3295:
----------------------------------------
Summary: AsyncContext#start runs in caller thread
Key: WFLY-3295
URL: https://issues.jboss.org/browse/WFLY-3295
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Undertow)
Affects Versions: 8.1.0.CR1
Reporter: Philippe Marschall
Assignee: Stuart Douglas
{{javax.servlet.AsyncContext.start(Runnable)}} seems to run the runnable in the caller thread. In order for this method to be useful it should be run in a different thread.
I'll attach a class to demonstrate the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-3294) Improve wildfly-init-debian.sh
by Jorge Solorzano (JIRA)
Jorge Solorzano created WFLY-3294:
-------------------------------------
Summary: Improve wildfly-init-debian.sh
Key: WFLY-3294
URL: https://issues.jboss.org/browse/WFLY-3294
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Scripts
Affects Versions: 8.1.0.CR1
Environment: Debian based OS
Reporter: Jorge Solorzano
Assignee: Tomaz Cerar
Priority: Trivial
The script wildfly-init-debian.sh needs to check if the user running the server is owner of the wildfly server and add the possibility to even if the path has spaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-3294) Improve wildfly-init-debian.sh
by Jorge Solorzano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3294?page=com.atlassian.jira.plugin.... ]
Jorge Solorzano updated WFLY-3294:
----------------------------------
Description: The script wildfly-init-debian.sh needs to check if the user running the server is owner of the wildfly folder and add the possibility to run even if the path has spaces. (was: The script wildfly-init-debian.sh needs to check if the user running the server is owner of the wildfly server and add the possibility to even if the path has spaces.)
> Improve wildfly-init-debian.sh
> ------------------------------
>
> Key: WFLY-3294
> URL: https://issues.jboss.org/browse/WFLY-3294
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scripts
> Affects Versions: 8.1.0.CR1
> Environment: Debian based OS
> Reporter: Jorge Solorzano
> Assignee: Tomaz Cerar
> Priority: Trivial
>
> The script wildfly-init-debian.sh needs to check if the user running the server is owner of the wildfly folder and add the possibility to run even if the path has spaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1820:
--------------------------------
OK, so I added a new annotation {{@XmlAttribute}} which lists all attributes which need to be inserted into the generated schema. This doesn't include custom {{AuthToken}} subclasses, but covers all existing tokens in JGroups.
Partially backported to 3.4 as well.
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JGRP-1820) XML schema broken for AUTH
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1820.
----------------------------
Resolution: Done
> XML schema broken for AUTH
> --------------------------
>
> Key: JGRP-1820
> URL: https://issues.jboss.org/browse/JGRP-1820
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The XML schema does not pass validation for AUTH.
> AUTH merges in properties for the pluggable auth_class, which are not currently included in the schema.
> For example the fixed_members_value when using FixedMembershipToken is not included in the schema and fails validation:
> <AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
> fixed_members_value="localhost/7900">
> </AUTH>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JGRP-1828) Allow protocols to define inline XML config
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1828?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1828:
--------------------------------
OK, schema generation is done, too. We use {{@XmlInclude}} and {{@XmlElement}} to generate the schema. See {{FORK}} and {{RELAY2}} for examples.
> Allow protocols to define inline XML config
> -------------------------------------------
>
> Key: JGRP-1828
> URL: https://issues.jboss.org/browse/JGRP-1828
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> Some protocols (e.g. RELAY2 or FORK) need additional configuration, which is usually defined in a separate XML file, e.g.
> {code:xml}
> <FORK config="/home/bela/fork-stacks.xml"/>
> {code}
> File {{fork-stacks.xml}} is:
> {code:xml}
> <fork-stacks xmlns="fork-stacks">
> <fork-stack id="counter">
> <config>
> <COUNTER bypass_bundling="true"/>
> <COMPRESS/>
> </config>
> </fork-stack>
> <fork-stack id="locking">
> <config>
> <CENTRAL_LOCK num_backups="2"/>
> </config>
> </fork-stack>
> </fork-stacks>
> {code}
> It would be nice to be able to optionally define such additional configuration inline, e.g.
> {code:xml}
> <FORK>
> <fork-stacks xmlns="fork-stacks">
> <fork-stack id="counter">
> <config>
> <COUNTER bypass_bundling="true"/>
> <COMPRESS/>
> </config>
> </fork-stack>
> <fork-stack id="locking">
> <config>
> <CENTRAL_LOCK num_backups="2"/>
> </config>
> </fork-stack>
> </fork-stacks>
> </FORK>
> {code}
> As the schema for config files is *generated*, we would have to able to tell the generator ({{XMLSchemaGenerator}}) to include a schema fragment defined by any protocol.
> A schema fragment could be defined via an annotation, e.g. {{@IncludeSchema(schema="fork-stacks.xsd"}}.
> Investigate whether this is feasible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (JGRP-1828) Allow protocols to define inline XML config
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1828?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1828.
----------------------------
Resolution: Done
> Allow protocols to define inline XML config
> -------------------------------------------
>
> Key: JGRP-1828
> URL: https://issues.jboss.org/browse/JGRP-1828
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> Some protocols (e.g. RELAY2 or FORK) need additional configuration, which is usually defined in a separate XML file, e.g.
> {code:xml}
> <FORK config="/home/bela/fork-stacks.xml"/>
> {code}
> File {{fork-stacks.xml}} is:
> {code:xml}
> <fork-stacks xmlns="fork-stacks">
> <fork-stack id="counter">
> <config>
> <COUNTER bypass_bundling="true"/>
> <COMPRESS/>
> </config>
> </fork-stack>
> <fork-stack id="locking">
> <config>
> <CENTRAL_LOCK num_backups="2"/>
> </config>
> </fork-stack>
> </fork-stacks>
> {code}
> It would be nice to be able to optionally define such additional configuration inline, e.g.
> {code:xml}
> <FORK>
> <fork-stacks xmlns="fork-stacks">
> <fork-stack id="counter">
> <config>
> <COUNTER bypass_bundling="true"/>
> <COMPRESS/>
> </config>
> </fork-stack>
> <fork-stack id="locking">
> <config>
> <CENTRAL_LOCK num_backups="2"/>
> </config>
> </fork-stack>
> </fork-stacks>
> </FORK>
> {code}
> As the schema for config files is *generated*, we would have to able to tell the generator ({{XMLSchemaGenerator}}) to include a schema fragment defined by any protocol.
> A schema fragment could be defined via an annotation, e.g. {{@IncludeSchema(schema="fork-stacks.xsd"}}.
> Investigate whether this is feasible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-3293) Excessive ERROR logging on JBAS014559: Invocation cannot proceed as component is shutting dow
by Thomas Frühbeck (JIRA)
Thomas Frühbeck created WFLY-3293:
-------------------------------------
Summary: Excessive ERROR logging on JBAS014559: Invocation cannot proceed as component is shutting dow
Key: WFLY-3293
URL: https://issues.jboss.org/browse/WFLY-3293
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 8.0.0.Final
Reporter: Thomas Frühbeck
Assignee: David Lloyd
Priority: Minor
on server shutdown excessive ERROR logs are produced related to EJB invocations on beans in state shutdown.
2014-04-26 09:38:43,059 ERROR [org.jboss.as.ejb3.invocation] (ServerService Thread Pool -- 377) JBAS014134: EJB Invocation failed on component SMSQueueConsumer for method public void at.telekom.sms.esms.service.
common.queue.SMSQueueConsumer.stopping(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: JBAS014559: Invocation cannot proceed as component is shutting down
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:59) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
IMHO this is definitely no error and is very alarming for production environments, INFO w/o stacktrace, in level DEBUG full stacktrace would suffice.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (WFLY-3261) Security constraint does not protect URL
by Dino Tsoumakis (JIRA)
[ https://issues.jboss.org/browse/WFLY-3261?page=com.atlassian.jira.plugin.... ]
Dino Tsoumakis commented on WFLY-3261:
--------------------------------------
I recognized that if no 'hashEncoding' is set, the default is 'base64'. After explicitly setting it to 'HEX' the security constraint works as expected on Wildfly 8 and also on 8.1.0.RC1. No problem here.
> Security constraint does not protect URL
> ----------------------------------------
>
> Key: WFLY-3261
> URL: https://issues.jboss.org/browse/WFLY-3261
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.1.0.CR1
> Reporter: Simon Martinelli
> Assignee: Stuart Douglas
>
> Security constraint works as expected on JBoss EAP 6.2.2 and JBoss AS 7.1.1.Final but no on Wildfly
> *web.xml*
> {code:xml}
> <security-constraint>
> <display-name>Spaces</display-name>
> <web-resource-collection>
> <web-resource-name>spaces</web-resource-name>
> <url-pattern>/spaces/*</url-pattern>
> </web-resource-collection>
> <auth-constraint>
> <role-name>user</role-name>
> </auth-constraint>
> </security-constraint>
> {code}
> *jboss-web.xml*
> {code:xml}
> <jboss-web>
> <context-root>/jtaf</context-root>
> <security-domain>jtaf</security-domain>
> </jboss-web>
> {code}
> *standalone.xml*
> {code:xml}
> <security-domain name="jtaf" cache-type="default">
> <authentication>
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/MysqlDS"/>
> <module-option name="principalsQuery" value="select secret from securityuser where email = ?"/>
> <module-option name="rolesQuery" value="select name, 'Roles' from securitygroup where email = ?"/>
> <module-option name="password-stacking" value="useFirstPass"/>
> <module-option name="hashAlgorithm" value="MD5"/>
> <module-option name="hashEncoding" value="base64"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months