January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1417) Provide Arquillian clustering example for domain server

by Karel Piwko (JIRA)

Provide Arquillian clustering example for domain server ------------------------------------------------------- Key: AS7-1417 URL: https://issues.jboss.org/browse/AS7-1417 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.0.0.CR1 Reporter: Karel Piwko Assignee: Andrew Rubinger Create an example which is using a domain controller and starts two domains on a single machine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (AS7-3204) Fail to deploy war with reference to more than one virtual-host

by Luis Barreiro (Created) (JIRA)

Fail to deploy war with reference to more than one virtual-host --------------------------------------------------------------- Key: AS7-3204 URL: https://issues.jboss.org/browse/AS7-3204 Project: Application Server 7 Issue Type: Bug Components: Web Reporter: Luis Barreiro Assignee: Jean-Frederic Clere When deploying a war with the following jboss-web.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> <jboss-web> <virtual-host>virtual.host</virtual-host> <virtual-host>virtual.alias</virtual-host> </jboss-web> one gets the exception MSC00001: Failed to start service jboss.deployment.unit."jbossweb-virtual-host.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbossweb-virtual-host.war".PARSE: Failed to process phase PARSE of deployment "jbossweb-virtual-host.war" [...] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/jbossweb-virtual-host.war/WEB-INF/jboss-web.xml" at [5,5] at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:68) [...] that is, at least, misleading, because the XML is well formatted and is valid. -- 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
2
0 / 0

[JBoss JIRA] (AS7-3196) ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described

by Kamal Suriyakumar (Created) (JIRA)

ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described ------------------------------------------------------------------------------------------------------- Key: AS7-3196 URL: https://issues.jboss.org/browse/AS7-3196 Project: Application Server 7 Issue Type: Clarification Components: Server Affects Versions: 7.1.0.Final, Open To Community Environment: Jboss as7 server Reporter: Kamal Suriyakumar Assignee: Jason Greene Priority: Blocker Fix For: Open To Community ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153) at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106) at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:282) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:103) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70) at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:66) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:91) at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:161) at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:722) Failed to boot JBoss: java.lang.IllegalStateException: Incompletely deployed: DEPLOYMENTS IN ERROR: Deployment "AttachmentStore" is in error due to: java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File] -- 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
3
0 / 0

[JBoss JIRA] (AS7-3211) If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation

by Scott Marlow (Created) (JIRA)

If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation ----------------------------------------------------------------------------------------------- Key: AS7-3211 URL: https://issues.jboss.org/browse/AS7-3211 Project: Application Server 7 Issue Type: Task Reporter: Scott Marlow Priority: Minor Fix For: 7.2.0.Alpha1 For Queries, handoff the EntityManager to a Query object wrapper and have the Query object finalizer close the EntityManager. Make sure that we respect JPA 2.0 section 3.8.6 (detach objects returned from Query object). 1. Methods that return a Query, will hand off the EM to the Query object wrapper. 2. Other methods will close the EM at the end of the EM method invocation. When making this change, make sure that performance doesn't degrade. The cost of this change, will be that each (transaction scoped non-tx) EM invocation will create a new persistence context, but we can eliminate the NonTxEmCloser which has its own overhead. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1484) Validate Apache Tomcat SingleSignonValve

by Anil Saldhana (JIRA)

Validate Apache Tomcat SingleSignonValve ---------------------------------------- Key: AS7-1484 URL: https://issues.jboss.org/browse/AS7-1484 Project: Application Server 7 Issue Type: Task Components: Web Reporter: Anil Saldhana Assignee: Marcus Moyses We need to validate the Apache SSO Valve in AS7. We need a wiki article that describes the setup for the valve. Please see the end of http://community.jboss.org/wiki/JBossAS7SecurityDomainModel to do valve configuration in jboss-web.xml of the web archive. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
8
0 / 0

[JBoss JIRA] (AS7-3208) Improve CLI output of "help" command in Windows cmd box

by Wolfgang Knauf (Created) (JIRA)

Improve CLI output of "help" command in Windows cmd box ------------------------------------------------------- Key: AS7-3208 URL: https://issues.jboss.org/browse/AS7-3208 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1 Environment: Any Windows version Reporter: Wolfgang Knauf Assignee: Alexey Loubyansky Priority: Minor Attachments: clihelp.PNG Attached is a screenshot of the output of the CLI command "help" in a standard windows command window. It is very hard to read, as a dosbox by default has a width of 80 chars. Any change to improve the line wrapping? -- 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

2
1
0 / 0

[JBoss JIRA] (AS7-3209) Make platform-mbean module conform to ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Make platform-mbean module conform to ANDIAMO-2 ----------------------------------------------- Key: AS7-3209 URL: https://issues.jboss.org/browse/AS7-3209 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Final Make use of the Logger and Messages classes that are already there. -- 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
0
0 / 0

[JBoss JIRA] (AS7-3207) Make the management-client-content module conform to ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Make the management-client-content module conform to ANDIAMO-2 -------------------------------------------------------------- Key: AS7-3207 URL: https://issues.jboss.org/browse/AS7-3207 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Final I added this module but did not create the i18n Logger or Messages class for it. Fix that. -- 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
0
0 / 0

[JBoss JIRA] (AS7-2508) Upgrade to a GA release of JBoss Negotiation

by Darran Lofthouse (Created) (JIRA)

Upgrade to a GA release of JBoss Negotiation -------------------------------------------- Key: AS7-2508 URL: https://issues.jboss.org/browse/AS7-2508 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.0.CR1 JBoss Negotiation needs tagging and AS7 updating to the GA version. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3103) "A and not(B after A)" type rules don't fire when session clock has negative values (pre Unix epoch)

by Richard Calmbach (JIRA)

"A and not(B after A)" type rules don't fire when session clock has negative values (pre Unix epoch) ---------------------------------------------------------------------------------------------------- Key: JBRULES-3103 URL: https://issues.jboss.org/browse/JBRULES-3103 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.2.0.Final Reporter: Richard Calmbach Assignee: Mark Proctor See JBRULES-3100 for the gory details. The implementation described there causes two bugs, so THIS IS NOT A DUPLICATE of JBRULES-3100. Rather, the bugs are related, and because it is possible to fix one without the other, it makes sense to track both bugs explicitly, so that the developers can ensure that both bugs get fixed. The summary of this issue also conveys to users that this particular bug has already been reported. So, *this* bug prevents rules of the form $a: A() not(B(this after $a)) or "A and not(B after A)" in pseudocode, from firing when they should if the session clock has a negative value, say during a simulation or if the system clock is turned back pre Unix epoch. This is confirmed for the pseudo clock, and I believe the real-time clock is equally affected. The root of the problem is that "A and not(B after A)" type rules get a duration of Long.MAX_VALUE assigned. When that gets added to a non-positive current time, it results in a very large positive number for the trigger time, which will never be reached by the session clock, preventing the rule from ever firing. The fix is probably to add the activation for such a rule to the agenda immediately, rather than schedule it for adding. This would yield the same behavior as when you compare the timestamps explicitly. For now, comparing timestamps explicitly instead of using "after" is a workaround for this bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012