April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBWEB-107) Cross Domain JSESSIONID Cookie

by Mike Millson (JIRA)

Cross Domain JSESSIONID Cookie ------------------------------ Key: JBWEB-107 URL: http://jira.jboss.com/jira/browse/JBWEB-107 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Mike Millson Assigned To: Mladen Turk Currently the JSESSIONID cookie domain is set to the domain name of the Host that emits the cookie (e.g. www.domain.com). This is an issue with customers using Aliases (e.g. secure.domain.com, zzz.domain.com, etc.), as the session is lost when switching between the main domain and any aliases. In these cases, it would be useful to be able to specify the domain to be "domain.com" so the same JSESSIONID cookie is used across the aliases and converges to the same session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-9235) @ConcurrencyManagement type BEAN on a singleton EJB leads to deployment exception

by jaikiran pai (JIRA)

@ConcurrencyManagement type BEAN on a singleton EJB leads to deployment exception --------------------------------------------------------------------------------- Key: JBAS-9235 URL: https://issues.jboss.org/browse/JBAS-9235 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 7.0.0.Beta2 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.0.Beta3 A singleton EJB with BEAN concurrency management leads to: {code} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected concurrency management type: BEAN on bean SingletonBean at org.jboss.as.ejb3.deployment.processors.ConcurrencyManagementAnnotationProcessor.processAnnotations(ConcurrencyManagementAnnotationProcessor.java:87) at org.jboss.as.ejb3.deployment.processors.ConcurrencyManagementAnnotationProcessor.processAnnotations(ConcurrencyManagementAnnotationProcessor.java:46) at org.jboss.as.ejb3.deployment.processors.AbstractAnnotationEJBProcessor.processComponentConfig(AbstractAnnotationEJBProcessor.java:54) at org.jboss.as.ee.component.AbstractComponentConfigProcessor.deploy(AbstractComponentConfigProcessor.java:53) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more {code} The ConcurrencyManagementAnnotationProcessor is missing a "break" statement in the switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2242) Allow embedded usage in failsafe and surefire plugin

by Carlo de Wolf (JIRA)

Allow embedded usage in failsafe and surefire plugin ---------------------------------------------------- Key: EJBTHREE-2242 URL: https://issues.jboss.org/browse/EJBTHREE-2242 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Because AS 6 doesn't shutdown cleanly a test must always be forked off. This has the implication that java.class.path does not reflect the true class path, instead surefire.test.class.path must be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2083) Create "embedded" component for EJB 3.1 EJBContainer implementation

by Andrew Lee Rubinger (JIRA)

Create "embedded" component for EJB 3.1 EJBContainer implementation ------------------------------------------------------------------- Key: EJBTHREE-2083 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2083 Project: EJB 3.0 Issue Type: Feature Request Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Start porting in local development towards the EJB 3.1 Embedded container support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1999) Create "embedded" component

by Andrew Lee Rubinger (JIRA)

Create "embedded" component --------------------------- Key: EJBTHREE-1999 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1999 Project: EJB 3.0 Issue Type: Task Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Create a component w/ SPI/API, build, and impl modules to house the E-EJB3 configuration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8963) Inject Persistence Context into Hibernate session

by Scott Marlow (JIRA)

Inject Persistence Context into Hibernate session ------------------------------------------------- Key: JBAS-8963 URL: https://issues.jboss.org/browse/JBAS-8963 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott Marlow This will probably use unwrap and should be independent of Hibernate, so that other PersistenceProvider classes can also be handled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (JBAS-9112) Create an "operation-header" section in operation requests

by Brian Stansberry (JIRA)

Create an "operation-header" section in operation requests ---------------------------------------------------------- Key: JBAS-9112 URL: https://issues.jboss.org/browse/JBAS-9112 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta2 For the oddball stuff that goes along with some ops: "operation-headers"=>{"rollout-plan"=>{..},"rollback-on-runtime-failure"=>false, "ignore-restart-required"=>true,...} "operation" and "address" would not move -- too disruptive -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9195) Incomplete warning message when starting a started server

by Heiko Rupp (JIRA)

Incomplete warning message when starting a started server --------------------------------------------------------- Key: JBAS-9195 URL: https://issues.jboss.org/browse/JBAS-9195 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp Priority: Minor When issuing a start request on an already started server, the following message shows up in the server log [Host Controller] 22:33:04,244 WARN [org.jboss.as.host.controller] (pool-1-thread-7) existing server [%s] with state: STARTED Note the %s, which is probably supposed to be replaced by the server name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9225) LOOPBACK_ADDRESS handling missing from CommonXml.writePropertyInterfaceCriteria

by Scott Stark (JIRA)

LOOPBACK_ADDRESS handling missing from CommonXml.writePropertyInterfaceCriteria ------------------------------------------------------------------------------- Key: JBAS-9225 URL: https://issues.jboss.org/browse/JBAS-9225 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Scott Stark Assignee: Scott Stark Fix For: 7.0.0.Beta3 Support for a loopback-address criterion was added to the CommonXml.parseSimpleInterfaceCriterion, but the writing of this was not added to the CommonXml.writePropertyInterfaceCriteria, so when the standard.xml configuration is persisted, the following error is seen: 10:58:21,807 WARN [org.jboss.as.controller] (pool-6-thread-2) Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to store configuration: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to store configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:97) at org.jboss.as.controller.BasicModelController.persistConfiguration(BasicModelController.java:308) at org.jboss.as.server.ServerControllerImpl.persistConfiguration(ServerControllerImpl.java:215) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.updateModelAndPersist(BasicModelController.java:668) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.recordModelComplete(BasicModelController.java:652) at org.jboss.as.server.ServerControllerImpl$ServerMultiStepOperationController.recordModelComplete(ServerControllerImpl.java:475) at org.jboss.as.controller.BasicModelController$MultiStepOperationController.execute(BasicModelController.java:707) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:248) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:216) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:77) at org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousOperationSupport.java:88) at org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:40) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1052) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1043) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [:1.6.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [:1.6.0_17] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) [:1.6.0_17] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) [:1.6.0_17] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_17] at java.lang.Thread.run(Thread.java:636) [:1.6.0_17] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to write configuration at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:108) at org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:90) ... 20 more Caused by: java.lang.RuntimeException: Unknown property in interface criteria list: org.jboss.dmr.Property@fbb8694 at org.jboss.as.controller.parsing.CommonXml.writePropertyInterfaceCriteria(CommonXml.java:1311) at org.jboss.as.controller.parsing.CommonXml.writeInterfaceCriteria(CommonXml.java:1277) at org.jboss.as.controller.parsing.CommonXml.writeInterfaces(CommonXml.java:1262) at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:435) at org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:77) at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78) at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73) at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:102) ... 21 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8411) Interface specified at host level but not at domain is accepted

by Brian Stansberry (JIRA)

Interface specified at host level but not at domain is accepted --------------------------------------------------------------- Key: JBAS-8411 URL: https://jira.jboss.org/browse/JBAS-8411 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 The current build/src/main/resources/domain/configuration/host.xml includes the declaration of an <interface name="public" at the host level and that interface is not declared in the domain. It's used in the <domain-controller><local> element but I think it should be required to be declared there. Interfaces directly under host should be used to clarify the host-specific IP address mapping for stuff declared in domain.xml. If the address name is only used in the DC config, then declare it there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011