January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8426) Formatting in section 1.4.2 of Installation and Getting Started Guide

by Heather McCartney (JIRA)

Formatting in section 1.4.2 of Installation and Getting Started Guide --------------------------------------------------------------------- Key: JBAS-8426 URL: https://jira.jboss.org/browse/JBAS-8426 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.1.0.GA Environment: Windows XP SP 3 Firefox 3.6.10 Reporter: Heather McCartney In section 1.4.2 of the Getting Started Guide, should the first three headings (aspects, bootstrap, build) appear in bold, like the others? Also, in Firefox, spaces are missing before or after some of the links: - under "build", "See Section 5.3, "Building with Apache ANT"Building" has no space after the link - under "console", "See JBoss Embedded Consoleproject" has no space after the link - under "embedded", "has been moved toSVN embedded for further development" has no space before the link -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8142) Ensure HornetQ security events are sent to the audit framework

by Anil Saldhana (JIRA)

Ensure HornetQ security events are sent to the audit framework -------------------------------------------------------------- Key: JBAS-8142 URL: https://jira.jboss.org/browse/JBAS-8142 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Clebert Suconic Clebert, the ejb and web layers send successful/failed security events to the audit framework. It makes sense to send the hornetq security events to the audit framework. Marcus Moyses can guide you in this integration. It will be very simple. Few lines of code. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8711) Unable to deploy Apache Axis2.war version 1.5.3

by David Thompson (JIRA)

Unable to deploy Apache Axis2.war version 1.5.3 ----------------------------------------------- Key: JBAS-8711 URL: https://jira.jboss.org/browse/JBAS-8711 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Ubuntu 10.10, jboss-6.0.0.CR1, openjdk 6 1.6.0_20, jbossweb-standalone server Reporter: David Thompson Deployed the war downloaded from here http://www.eng.lsu.edu/mirrors/apache//axis/axis2/java/core/1.5.3/axis2-1... And immediately you get the following errors as well as lots more. [org.jboss.detailed.classloader.ClassLoaderManager] Unexpected error during load of:org.w3c.dom.UserDataHandler: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) previously initiated loading for a different type with name "org/w3c/dom/UserDataHandler" at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_20] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8757) GeneralPurposeDatabasePersistencePlugin not closing ResultSet in isNextDateColumnPresent

by Brad Maxwell (JIRA)

GeneralPurposeDatabasePersistencePlugin not closing ResultSet in isNextDateColumnPresent ---------------------------------------------------------------------------------------- Key: JBAS-8757 URL: https://issues.jboss.org/browse/JBAS-8757 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: TBD Reporter: Brad Maxwell Assignee: Alexey Loubyansky Fix For: TBD I created a ejbtimerDS-ds.xml which uses MySQL. The GeneralPurposeDatabasePersistencePlugin in $JBOSS_HOME/server/$PROFILE/deploy/ejb2-timers-service.xml uses the GeneralPurposeDatabasePersistencePlugin for MySQL. The exception below occurs on startup when JBoss starts. With debug=true for the CachedConnectionManager in $JBOSS_HOME/server/$PROFILE//deploy/jca-jboss-beans.xml 17:17:06,041 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ejbtimerDS' to JNDI name 'java:ejbtimerDS' 17:17:06,521 WARN [WrappedConnection] Closing a result set you left open! Please close it yourself. java.lang.Throwable: STACKTRACE at org.jboss.resource.adapter.jdbc.WrappedStatement.registerResultSet(WrappedStatement.java:909) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:343) at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.isNextDateColumnPresent(GeneralPurposeDatabasePersistencePlugin.java:595) at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:178) at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:104) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189) at $Proxy38.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) 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.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7917) Fix commented out JMS config in cache-invalidation-service.xml

by Brian Stansberry (JIRA)

Fix commented out JMS config in cache-invalidation-service.xml -------------------------------------------------------------- Key: JBAS-7917 URL: https://jira.jboss.org/jira/browse/JBAS-7917 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Fix For: JBossAS-6.0.0.CR1 It's a JBM mbean config, which won't work with HornetQ. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8000) Create a "tests-clustering-full" target

by Brian Stansberry (JIRA)

Create a "tests-clustering-full" target --------------------------------------- Key: JBAS-8000 URL: https://jira.jboss.org/jira/browse/JBAS-8000 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.CR1 Convenience target to encapsulate all the clustering targets that are starting to be a bit scattered: tests-clustering-all-stacks tests-clustered-profileservice tests-ha-mod_cluster tomcat-sso-clustered-tests Shouldn't run the clustered classloader leak tests, as those are run by a separate hudson job. The regular testsuite job should run this "tests-clustering-full" target instead of the ones listed above. This new target should also be controllable via a system property such that instead of running tests-clustering-all-stacks it runs tests-clustering (i.e. without testing with JGroups using TCP). Or perhaps use a separate convenience target. The intent of this target is to let devs easily run the clustering tests. -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8534) Security Credential is shared between threads

by Rajesh Bhabu (JIRA)

Security Credential is shared between threads --------------------------------------------- Key: JBAS-8534 URL: https://jira.jboss.org/browse/JBAS-8534 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.2.3.GA Environment: JBOSS AS 4.2.3 on Linux Reporter: Rajesh Bhabu Assignee: Anil Saldhana Because of the Anonymous issue as reported in https://jira.jboss.org/browse/JBAS-3945, we did coding something similar as following to workaround the issue. This was suggested by the JBOSS support team. --------------------------------------------------------------------------------------------- When we are changing the principal (performing another login) we need to call these Jboss APIs in our login module: SecurityAssociation.popRunAsRole() SecurityAssociation.pushRunAsRole() This will pop the old run-as role and push the new run as role (which we want the second transaction to run as). Change the JAAS login module to explicitly set the new principal and credentials during login. This was after the callback handler handle method was invoked and we had the principal and credentials: SecurityAssociation.setPrincipal(new SimplePrincipal(username)); SecurityAssociation.setCredential(password); -------------------------------------------------------------------------------------------------------------------------- After doing this, we started seeing priniciple is shared amoung the threads. For example, user 1 logs in and see's information about user 2. This happens only after heavy load testing. This is also reproducible after couple of hours of running load test. If we remove the above code, then the issue goes away. But anonymous issue appears. Any Help is appreciated in helping finding the root cause of the issue. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8106) Move MC/Weld deployer into AS

by Kabir Khan (JIRA)

Move MC/Weld deployer into AS ----------------------------- Key: JBAS-8106 URL: https://jira.jboss.org/browse/JBAS-8106 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 6.0.0.M4 Since the rest of weld-int (JBAS-7938) now lives in AS, this lives here too now. Until this feature is final, all jars are in weld.deployer, but it is disabled. To enable, uncomment this part of weld-deployers-jboss-beans.xml    -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-8610) Revise Weld tests from testsuite

by Marius Bogoevici (JIRA)

Revise Weld tests from testsuite -------------------------------- Key: JBAS-8610 URL: https://jira.jboss.org/browse/JBAS-8610 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite, Weld/CDI Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 6.0.0.CR1 -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8691) Embedded server run using moduled

by Kabir Khan (JIRA)

Embedded server run using moduled --------------------------------- Key: JBAS-8691 URL: https://jira.jboss.org/browse/JBAS-8691 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011