March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-400) XACML Conformance Tests: Mandatory - attribute references, functions, combination algos

by Anil Saldhana (JIRA)

XACML Conformance Tests: Mandatory - attribute references, functions, combination algos --------------------------------------------------------------------------------------- Key: SECURITY-400 URL: https://jira.jboss.org/jira/browse/SECURITY-400 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jboss-sunxacml Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossXACML_2.0.3.CR4 -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6612) Hot deploying a web app fails

by Charles Crouch (JIRA)

Hot deploying a web app fails ----------------------------- Key: JBAS-6612 URL: https://jira.jboss.org/jira/browse/JBAS-6612 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: r85733 Reporter: Charles Crouch Fix For: JBossAS-5.1.0.Beta1 When I dropped the embedded console into the /deploy folder I got the following exception. But when I simply restarted the app server it deployed fine. 16:50:26,062 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build: SVNTag=JBoss_5_1_0_Beta1 date=200903111033)] Sta rted in 1m:22s:891ms 17:00:10,796 WARN [HDScanner] Scan failed org.jboss.deployers.spi.DeploymentException: Error determining structure: jbas5-admin-console.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.vfs.plugins.structure.explicit.DeclaredStructure.determineStructure(DeclaredStructure.java:89 ) at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.ja va:73) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersI mpl.java:196) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImp l.java:221) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeploy ers.java:77) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1000) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:317) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:229) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java: 65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java :142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.util.zip.ZipException: The process cannot access the file because it is being us ed by another process at org.jboss.virtual.plugins.context.AbstractExceptionHandler.handleZipEntriesInitException(AbstractExceptionHandler .java:39) at org.jboss.virtual.plugins.context.helpers.NamesExceptionHandler.handleZipEntriesInitException(NamesExceptionHandl er.java:63) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:610) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:757) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:801) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java: 681) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165) at org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107) at org.jboss.virtual.VirtualFile.getChild(VirtualFile.java:481) at org.jboss.deployers.vfs.plugins.structure.explicit.DeclaredStructure.determineStructure(DeclaredStructure.java:64 ) ... 20 more Caused by: java.util.zip.ZipException: The process cannot access the file because it is being used by another process at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:203) at java.util.zip.ZipFile.<init>(ZipFile.java:234) at org.jboss.virtual.plugins.context.zip.ZipFileWrapper.ensureZipFile(ZipFileWrapper.java:175) at org.jboss.virtual.plugins.context.zip.ZipFileWrapper.acquire(ZipFileWrapper.java:245) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:470) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:603) ... 28 more -- 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

15 years, 9 months

4
8
0 / 0

[JBoss JIRA] Updated: (JBAS-6535) java.lang.LinkageErrors seen during start of JBoss AS 5.1 with admin-console.war deployed

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6535?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-6535: ---------------------------------- Component/s: XML services > java.lang.LinkageErrors seen during start of JBoss AS 5.1 with admin-console.war deployed > ----------------------------------------------------------------------------------------- > > Key: JBAS-6535 > URL: https://jira.jboss.org/jira/browse/JBAS-6535 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML services > Environment: JBoss AS Branch_5_x r84532, embjopr r162 > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JBossAS-5.1.0.CR1 > > Attachments: Injector.java, jaxb-impl.jar > > > During the inialization of the administration console, the rhq-platform-plugin gets loaded, searches jaxb.properties for a JAXB implementation and finds jaxb-impl.jar from $JBOSS_HOME/lib > 2009-02-20 15:20:41,594 INFO [org.jboss.on.embedded.BootstrapAction] (main) Bootstrapping Administration Console v1.1.1-SNAPSHOT... > 2009-02-20 15:20:41,594 DEBUG [org.jboss.on.embedded.BootstrapAction] (main) Reconfiguring JDK logging... > 2009-02-20 15:20:41,617 DEBUG [org.jboss.on.embedded.BootstrapAction] (main) Configuring Mock Scenario Loader... > 2009-02-20 15:20:41,618 INFO [org.rhq.core.pc.PluginContainer] (main) Initializing Plugin Container v1.2.0-SNAPSHOT... > 2009-02-20 15:20:41,723 DEBUG [org.rhq.core.pc.PluginContainer] (main) Starting and configuring container service: PluginManager > 2009-02-20 15:20:41,737 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Plugin found at: jndi:/localhost/admin-console/plugins/rhq-platform-plugin-1.2.0-SNAPSHOT.jar > 2009-02-20 15:20:41,741 DEBUG [org.rhq.core.clientapi.descriptor.AgentPluginDescriptorUtil] (main) Loading plugin descriptor from plugin jar at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin-1.2.0-SNAPSHOT.jar]... > 2009-02-20 15:20:41,741 FINE [javax.xml.bind] (main) Searching jaxb.properties > 2009-02-20 15:20:41,742 FINE [javax.xml.bind] (main) Searching the system property > 2009-02-20 15:20:41,742 FINE [javax.xml.bind] (main) Searching META-INF/services > 2009-02-20 15:20:41,743 FINE [javax.xml.bind] (main) Trying to load com.sun.xml.bind.v2.ContextFactory > 2009-02-20 15:20:41,744 FINE [javax.xml.bind] (main) loaded com.sun.xml.bind.v2.ContextFactory from vfszip:/home/smcgowan2/workspace/Branch_5_x/build/output/jboss-5.1.0.Beta1/lib/jaxb-impl.jar/com/sun/xml/bind/v2/ContextFactory.class > 2009-02-20 15:20:41,748 FINE [com.sun.xml.bind.v2.ContextFactory] (main) Property com.sun.xml.bind.XmlAccessorFactoryis not active. Using JAXB's implementation > 2009-02-20 15:20:41,947 FINE [com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory] (main) Using optimized Accessor for protected org.rhq.core.clientapi.descriptor.plugin.Version org.rhq.core.clientapi.descriptor.plugin.ResourceDescriptor.version > : > : > Next, while loading jopr-jboss-as-5-plugin, the same seach occurs but this time loading the class results in an exception: > 2009-02-20 15:20:44,006 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Loading independent plugin [JBossAS5] from URL: jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar > 2009-02-20 15:20:44,006 DEBUG [org.rhq.core.pc.plugin.PluginManager] (main) Loading plugin from: jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar > 2009-02-20 15:20:44,026 DEBUG [org.rhq.core.pc.plugin.PluginDescriptorLoader] (main) Created classloader for plugin [jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar] > 2009-02-20 15:20:44,026 DEBUG [org.rhq.core.clientapi.descriptor.AgentPluginDescriptorUtil] (main) Loading plugin descriptor from plugin jar at [jndi:/localhost/admin-console/plugins/jopr-jboss-as-5-plugin-2.2.0-SNAPSHOT.jar]... > 2009-02-20 15:20:44,026 FINE [javax.xml.bind] (main) Searching jaxb.properties > 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Searching the system property > 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Searching META-INF/services > 2009-02-20 15:20:44,027 FINE [javax.xml.bind] (main) Trying to load com.sun.xml.bind.v2.ContextFactory > 2009-02-20 15:20:44,028 FINE [javax.xml.bind] (main) loaded com.sun.xml.bind.v2.ContextFactory from vfszip:/home/smcgowan2/workspace/Branch_5_x/build/output/jboss-5.1.0.Beta1/lib/jaxb-impl.jar/com/sun/xml/bind/v2/ContextFactory.class > 2009-02-20 15:20:44,029 FINE [com.sun.xml.bind.v2.ContextFactory] (main) Property com.sun.xml.bind.XmlAccessorFactoryis not active. Using JAXB's implementation > 2009-02-20 15:20:44,308 FINE [com.sun.xml.bind.v2.runtime.reflect.opt.Injector] (main) Unable to inject org/rhq/core/clientapi/descriptor/plugin/ResourceDescriptor$JaxbAccessorF_version > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.sun.xml.bind.v2.runtime.reflect.opt.Injector.inject(Injector.java:181) > at com.sun.xml.bind.v2.runtime.reflect.opt.Injector.inject(Injector.java:85) > at com.sun.xml.bind.v2.runtime.reflect.opt.AccessorInjector.prepare(AccessorInjector.java:87) > at com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:165) > at com.sun.xml.bind.v2.runtime.reflect.Accessor$FieldReflection.optimize(Accessor.java:253) > at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.<init>(SingleElementNodeProperty.java:89) > at sun.reflect.GeneratedConstructorAccessor47.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at com.sun.xml.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:124) > Caused by: java.lang.LinkageError: duplicate class definition: org/rhq/core/clientapi/descriptor/plugin/ResourceDescriptor$JaxbAccessorF_version > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at java.lang.ClassLoader.defineClass(ClassLoader.java:465) > The server does start. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6643) restoring a null managed object fails

by Emanuel Muckenhuber (JIRA)

restoring a null managed object fails ------------------------------------- Key: JBAS-6643 URL: https://jira.jboss.org/jira/browse/JBAS-6643 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.Beta1 Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: JBossAS-5.1.0.CR1 null managed objects should not be restored when applying admin edits. -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-2391) Need to review PropertyManager

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2391?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-2391: ---------------------------------- Fix Version/s: Backlog (was: JBossAS-5.1.0.CR1) > Need to review PropertyManager > ------------------------------ > > Key: JBAS-2391 > URL: https://jira.jboss.org/jira/browse/JBAS-2391 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Deployers > Affects Versions: JBossAS-4.0.3 Final > Reporter: Adrian Brock > Priority: Optional > Fix For: Backlog > > > The PropertyManager installs itself as the system properties inorder to allow listeners to be registered > on property changes. > This should at least be configurable. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5965) introduce jboss_init_osx.sh

by Marc Lustig (JIRA)

introduce jboss_init_osx.sh ---------------------------- Key: JBAS-5965 URL: https://jira.jboss.org/jira/browse/JBAS-5965 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Environment: Mac OSX Reporter: Marc Lustig Priority: Minor Fix For: JBossAS-5.0.0.GA Using run.sh of AS 4.2.3, bash reports an error message. To fix this, introduce jboss_init_osx.sh I am ready to provide the script. Btw, beside that I have not identified any issues on OSX. -- 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

15 years, 9 months

6
17
0 / 0

[JBoss JIRA] Created: (SECURITY-399) XACML: Apply->evaluate method tries to encode an attributeValue that can be a bag

by Anil Saldhana (JIRA)

XACML: Apply->evaluate method tries to encode an attributeValue that can be a bag --------------------------------------------------------------------------------- Key: SECURITY-399 URL: https://jira.jboss.org/jira/browse/SECURITY-399 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-sunxacml Affects Versions: JBossXACML_2.0.3.CR3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossXACML_2.0.3.CR4 -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Deleted: (SECURITY-398) XACML: Attribute.java can throw NPE in the absence of required AttributeId

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/jira/browse/SECURITY-398?page=com.atlassian.jira.p... ] Anil Saldhana deleted SECURITY-398: ----------------------------------- > XACML: Attribute.java can throw NPE in the absence of required AttributeId > -------------------------------------------------------------------------- > > Key: SECURITY-398 > URL: https://jira.jboss.org/jira/browse/SECURITY-398 > Project: JBoss Security and Identity Management > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Anil Saldhana > Assignee: Anil Saldhana > -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2639) Retire setConfig contract in AbstractWebContainer

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2639?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-2639: ---------------------------------- Fix Version/s: Backlog (was: JBossAS-5.1.0.CR1) > Retire setConfig contract in AbstractWebContainer > ------------------------------------------------- > > Key: JBAS-2639 > URL: https://jira.jboss.org/jira/browse/JBAS-2639 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Anil Saldhana > Priority: Minor > Fix For: Backlog > > > With the JBXB style of config injection, there is little need for the unused "setConfig" contract of the AbstractWebContainer. > It should be retired in favor of the JBossXB Style configuration as described in the wiki: > http://wiki.jboss.org/wiki/Wiki.jsp?page=SERVICEdotXML -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1768) Isolating the test harness

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1768?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-1768: ---------------------------------- Fix Version/s: Backlog (was: JBossAS-6.0.0.Alpha1) Moving to backlog. > Isolating the test harness > -------------------------- > > Key: JBAS-1768 > URL: https://jira.jboss.org/jira/browse/JBAS-1768 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1 > Reporter: Adrian Brock > Fix For: Backlog > > > Since some projects are already using the test harness > org.jboss.test (from the testsuite) > this needs to be isolated to break the circular build dependency. > Additionally, we should look at making this available to users > 1) For their own use > 2) When reporting problems -- 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

15 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009