jboss-jira April 2012

jboss-jira@lists.jboss.org

1 participants
1674 discussions

[JBoss JIRA] (AS7-4337) TCCL not set correctly when activating MDB endpoint

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4337: ----------------------------------- Summary: TCCL not set correctly when activating MDB endpoint Key: AS7-4337 URL: https://issues.jboss.org/browse/AS7-4337 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.2.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

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-4198) default value in infinispan subsystem schema is ignored

by Michal Linhard (JIRA)

Michal Linhard created AS7-4198: ----------------------------------- Summary: default value in infinispan subsystem schema is ignored Key: AS7-4198 URL: https://issues.jboss.org/browse/AS7-4198 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Michal Linhard Assignee: Paul Ferraro Priority: Minor Because of the way the infinispan subsystem is parsed: https://github.com/jbossas/jboss-as/blob/master/clustering/infinispan/src... The default value for l1-lifespan attribute specified here: https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... is ignored. Could we changed it to zero in the schema, so that there aren't doubts whether L1 is or is not enabled by default when this attribute is omitted ? Correct behaviour IMO should be: L1 is disabled by default. And that is the way it is, this default value just adds to confusion. -- 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

14 years

4
12
0 / 0

[JBoss JIRA] (AS7-3755) JSR88 deployment causes errors because of invalid paths

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created AS7-3755: ----------------------------------- Summary: JSR88 deployment causes errors because of invalid paths Key: AS7-3755 URL: https://issues.jboss.org/browse/AS7-3755 Project: Application Server 7 Issue Type: Bug Components: JSR88 Affects Versions: 7.1.0.CR1 Reporter: Wolfgang Knauf Assignee: Thomas Diesler I observed two problems when performing JSR88 deployment. Though they are at completely different places, it seems they both have the same root cause: a JSR88 module name, which contains the path to the temp dir, seems to be treated a a file name later. First observation is this error message when deploying the EAR file attached to #AS7-3474 : 21:24:44,781 ERROR [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014132: Could not create directory C:\temp\jboss-as-7.1.0.Final-SNAPSHOT\standalone\data\timer-service-data\file:\C:\DOCUME~1\Knuffi\LOCALS~1\Temp\Stateless.StatelessEJB.GeometricModelBean to persist EJB timers. I don't know whether this breaks something, I just noticed the error message. And the second problem happened when deploying a small Struts2 sample: 21:23:10,875 FATAL [org.apache.jasper.EmbeddedServletOptions] (MSC service thread 1-4) The scratchDir you specified: C:\temp\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\work\jboss.web\default-host\file:_C:_DOCUME~1_Knuffi_LOCALS~1_Temp_StrutsBasics is unusable. The path is different, but the problem seems to be the same (here ":" is not removed from the path name). This caused a failed deployment, thus is is really a problem. I posted the second error plus a small sample (including my famous JSR88 deployer client ;-)) in the JBossWeb forum, but did not receive a reply up to now. See here for the sample: https://community.jboss.org/thread/194841 -- 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

14 years

3
6
0 / 0

[JBoss JIRA] (JBMESSAGING-1920) MessagingXAResource.isSameRm() should differentiate between resources coming from connections created with different user accounts

by Yong Hao Gao (JIRA)

Yong Hao Gao created JBMESSAGING-1920: ----------------------------------------- Summary: MessagingXAResource.isSameRm() should differentiate between resources coming from connections created with different user accounts Key: JBMESSAGING-1920 URL: https://issues.jboss.org/browse/JBMESSAGING-1920 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.SP6, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP7 The MessagingXAResource doesn't treat resources from different user accounts as different RMs, therefore TM may optimize the commit of a transaction enlisting two such resources into a one-phase commit, which may result in security violation at the server security check, as in case of JBPAPP-8546. -- 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

14 years

1
1
0 / 0

← Newer
1
...
165
166
167
168
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012