November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-929) JGroups 3.2.2.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-929: ------------------------------------- Summary: JGroups 3.2.2.Final Key: JBJCA-929 URL: https://issues.jboss.org/browse/JBJCA-929 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta3 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWEB-256) startAsync() cannot be called multiple times

by Richard Opalka (JIRA)

Richard Opalka created JBWEB-256: ------------------------------------ Summary: startAsync() cannot be called multiple times Key: JBWEB-256 URL: https://issues.jboss.org/browse/JBWEB-256 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Reporter: Richard Opalka Assignee: Remy Maucherat Fix For: JBossWeb-7.2.0.Beta1 According to startAsync() javadoc: http://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#sta... the startAsync method can be called multiple times. This is not possible with JBossWeb 7.2.0.Alpha5, because in: org.apache.catalina.connector.Request.startAsync(ServletRequest,ServletResponse) is line: {code} canStartAsync = false; {code} preventing multiple calls of this method. -- 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

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-4009) Domain Mode JMX access through the HostController

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4009: ------------------------------------- Summary: Domain Mode JMX access through the HostController Key: AS7-4009 URL: https://issues.jboss.org/browse/AS7-4009 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 This task is first to review if this should be considered. At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. The main motivation being to separate management and app traffic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-4742) Security Realm Plug-Ins to provide their own configuration parsers.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4742: ------------------------------------- Summary: Security Realm Plug-Ins to provide their own configuration parsers. Key: AS7-4742 URL: https://issues.jboss.org/browse/AS7-4742 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 Security realm plug-ins are currently configured with name / value pairs - to make plug-ins easier to use by those that did not implement them we should consider allowing a custom XML parser to allow new configuration elements to be defined. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

[JBoss JIRA] (AS7-3406) Authorization check for JMX

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3406: ------------------------------------- Summary: Authorization check for JMX Key: AS7-3406 URL: https://issues.jboss.org/browse/AS7-3406 Project: Application Server 7 Issue Type: Sub-task Components: JMX, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (AS7-3407) Authorization check for JNDI

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3407: ------------------------------------- Summary: Authorization check for JNDI Key: AS7-3407 URL: https://issues.jboss.org/browse/AS7-3407 Project: Application Server 7 Issue Type: Sub-task Components: Naming, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (AS7-6033) Add start/stop operations to hornetq-server resource

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6033: -------------------------------- Summary: Add start/stop operations to hornetq-server resource Key: AS7-6033 URL: https://issues.jboss.org/browse/AS7-6033 Project: Application Server 7 Issue Type: Enhancement Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1 Currently it is not possible to start/stop a hornetq-server resource without removing or adding it. For HornetQ replicated nodes, it'd be useful to be able to start/stop the node (runtime operations) without changing its configuration. That'd be necessary to restart replicated backup servers that have fallen back -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6032) Update to jbosgi-framework-2.1.x

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6032: ----------------------------------- Summary: Update to jbosgi-framework-2.1.x Key: AS7-6032 URL: https://issues.jboss.org/browse/AS7-6032 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-3690) Property Reactive: bitmask not being correctly calculated when field name is 'empty'

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3690: ----------------------------------------- Summary: Property Reactive: bitmask not being correctly calculated when field name is 'empty' Key: JBRULES-3690 URL: https://issues.jboss.org/browse/JBRULES-3690 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.5.0.Final Reporter: Esteban Aliverti Assignee: Mario Fusco When using Property Reactive facts, the property name 'empty' prevents rules to be activated. If the property name is changed, rules work as expected. The problem could be related to the fact that 'empty' is internally translated to 'isEmpty()' and this could cause problems when the pattern's bitmask is calculated. -- 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

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3414) Symbolic links inside deployed ear/war are not followed by web server

by Ronen Angluster (JIRA)

Ronen Angluster created AS7-3414: ------------------------------------ Summary: Symbolic links inside deployed ear/war are not followed by web server Key: AS7-3414 URL: https://issues.jboss.org/browse/AS7-3414 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1, 7.1.0.Beta1 Environment: Fedora 16 Reporter: Ronen Angluster Assignee: Alessio Soldano when creating a symbolic link inside a deployed ear/war the symbolic link's target is not followed when accessing it from a web browser i.e. in jboss-as/standalone/deplyoment/somedomain.ear/files we created a symbolic link named "version.js" which points to /usr/share/something/version.js the target file (/usr/share/...) is accessible by all (chmod'd to 777) and is readable by the jboss-as user which runs the Jboss application server. when accessing http://domain:8080/something/files/version.js we get an 404 error, seems like the file is not found by the server. when placing the file instead of symbolic link, the file is accessible and all is well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012