November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1079) Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment

by Galder Zamarreno (JIRA)

Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment --------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1079 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1079 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno Assigned To: Carlo de Wolf Ejb3HandlerFactory.getInstance() could do with some DEBUG logging to indicate whether an ejb-jar.xml and/or jboss.xml was included in the deployment or not. -- 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

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1078) EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference

by Galder Zamarreno (JIRA)

EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference ----------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1078 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1078 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno EJB3InterceptorsFactory.createPerJoinpoint() InterceptorInfo[] infos = container.getInterceptorRepository().getBusinessInterceptors(container, method); ... log.debug("Bound interceptors for joinpoint: " + method + " - " + infos); The log message is meaningless. It will print an array reference. This should be instead: log.debug("Bound interceptors for joinpoint: " + method + " - " + Arrays.toString(infos)); InterceptorInfo implements toString() -- 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

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4320) The EJB2 timer service with persistencePolicy=database can not start on MySQL

by Joshua Jackson (JIRA)

The EJB2 timer service with persistencePolicy=database can not start on MySQL ----------------------------------------------------------------------------- Key: JBAS-4320 URL: http://jira.jboss.com/jira/browse/JBAS-4320 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, Scheduling/Timers Affects Versions: JBossAS-5.0.0.Beta2 Environment: MySQL Reporter: Joshua Jackson Assigned To: Scott M Stark 2007-04-11 22:36:30,937 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Starting failed jboss.ejb:service=EJBTimerService,persistencePolicy=database java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=DefaultDS,service=metadata at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.init(GeneralPurposeDatabasePersistencePlugin.java:104) at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:83) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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:184) at $Proxy0.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:238) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:335) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:205) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.start(ServiceController.java:431) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:142) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:103) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110) at org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:53) at org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_381299.invoke(MainDeployerAspect_z_process_381299.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPContainerProxy$0.process(AOPContainerProxy$0.java) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:371) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:247) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:522) at java.lang.Thread.run(Thread.java:595) 2007-04-11 22:36:30,937 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=DefaultDS,service=metadata at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.init(GeneralPurposeDatabasePersistencePlugin.java:104) at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:83) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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:184) at $Proxy0.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:238) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:335) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:205) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.start(ServiceController.java:431) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:142) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:103) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110) at org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:53) at org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_381299.invoke(MainDeployerAspect_z_process_381299.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPContainerProxy$0.process(AOPContainerProxy$0.java) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:371) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:247) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:522) at java.lang.Thread.run(Thread.java:595) 2007-04-11 22:36:30,937 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Destroying jboss.ejb:service=EJBTimerService,persistencePolicy=database 2007-04-11 22:36:30,937 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Destroyed jboss.ejb:service=EJBTimerService,persistencePolicy=database -- 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

18 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAOP-458) Enable Generic Tests on JDK14

by Flavia Rainone (JIRA)

Enable Generic Tests on JDK14 ----------------------------- Key: JBAOP-458 URL: http://jira.jboss.com/jira/browse/JBAOP-458 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5 Reporter: Flavia Rainone Priority: Minor The generic tests are being temporarily removed from jdk14 test suite. -- 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

18 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1048) EJB3 JACC migration to Unified MetaModel

by Anil Saldhana (JIRA)

EJB3 JACC migration to Unified MetaModel ---------------------------------------- Key: EJBTHREE-1048 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1048 Project: EJB 3.0 Issue Type: Task Components: Security Reporter: Anil Saldhana EJB2/Web world is aligned with the JaccPolicy service bean in the JBoss MC in AS5. EJB3 JACC layer is not aligned with this. Once the EJB3 metamodel is aligned with the unified meta model, EJB3 JACC layer can get aligned with the top level JaccPolicy concept. JBAS-4506 is the issue for the unification of metadata. -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1241) Redirect after login

by Adam Warski (JIRA)

Redirect after login -------------------- Key: JBPORTAL-1241 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1241 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Security Reporter: Adam Warski Assigned To: Julien Viet Fix For: 2.6.Beta1 After logging in, the user should be redirected to the page he was last viewing (that is, when clicking "login"). -- 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

18 years, 3 months

5
6
0 / 0

[JBoss JIRA] Created: (SECURITY-8) LdapExtLoginModule should detect communication failures midstream

by Anil Saldhana (JIRA)

LdapExtLoginModule should detect communication failures midstream ------------------------------------------------------------------ Key: SECURITY-8 URL: http://jira.jboss.com/jira/browse/SECURITY-8 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 http://jira.jboss.com/jira/browse/JBAS-3661 There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the: http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotifi... such that it can do graceful processing. -- 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

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5026) NPE in JvmRouteVale.handleJvmRoute

by Philippe Sevestre (JIRA)

NPE in JvmRouteVale.handleJvmRoute ---------------------------------- Key: JBAS-5026 URL: http://jira.jboss.com/jira/browse/JBAS-5026 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Environment: https + apache 2.0.52 + mod_jk + jboss + ClusteredSSO Reporter: Philippe Sevestre Assigned To: Remy Maucherat Client is a rich app (swing) that does soap calls to an app. Some of those WebServices are secured by a "BASIC" security constraint. When client calls the first password protected service, JBoss tries to set SSO and Session cookies. Then client make some more non-restricted calls that work just fine. After that, the first secured call fails with a NPE at JvmRouteValve, detailed bellow: 2007-11-30 18:16:36,144 ERROR [org.apache.catalina.connector.CoyoteAdapter] An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.jboss.web.tomcat.service.session.JvmRouteValve.handleJvmRoute(JvmRouteValve.java:125) at org.jboss.web.tomcat.service.session.JvmRouteValve.checkJvmRoute(JvmRouteValve.java:112) at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:81) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn.invoke(ClusteredSingleSignOn.java:637) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Checking the code, the only way I see that this could happen is when checkJvmRoute passes a null to handleJvmRoute on its first parameter (oldsessionId). In turn, this implies that getRequestedSessionId() returned null AND getSession(false) didn't. What I can see from packet dumps in the APJ connection is that the client is *not* passing a JSESSIONID header along the call, but, since all calls use *the same tcp/ip connection*, it seems that the session manager still "remembers" that it has a session. Therefore, in this scenario, oldessionId == null (since the client didn't send any session cookie) and session !=null, causing this NPE. A simple fix would be test oldsessionId for null at line 91, returning if it is. -- 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

18 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-957) Implement message destination link resolving

by Carlo de Wolf (JIRA)

Implement message destination link resolving -------------------------------------------- Key: EJBTHREE-957 URL: http://jira.jboss.com/jira/browse/EJBTHREE-957 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-60) XACML SPI

by Anil Saldhana (JIRA)

XACML SPI --------- Key: SECURITY-60 URL: http://jira.jboss.com/jira/browse/SECURITY-60 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Provide a XACML SPI in the JBossSX implementation such that external xacml implementations can be plugged in. The XACML module should make use of this spi. -- 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

18 years, 3 months

1
2
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 November 2007