[JBoss JIRA] Assigned: (EJBTHREE-592) Deployment of EJB3s using Interceptors fails
by Carlo de Wolf (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-592?page=all ]
Carlo de Wolf reassigned EJBTHREE-592:
--------------------------------------
Assignee: Carlo de Wolf
> Deployment of EJB3s using Interceptors fails
> --------------------------------------------
>
> Key: EJBTHREE-592
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-592
> Project: EJB 3.0
> Issue Type: Bug
> Components: EJB3 Extensions
> Affects Versions: EJB 3.0 RC6 - PFD
> Reporter: J?rg Henne
> Assigned To: Carlo de Wolf
>
> Deployment of EJB3s using Interceptors fails with this Exception
> java.lang.TypeNotPresentException: Type javax.ejb.Interceptors not present
> at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:98)
> at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:107)
> at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:31)
> at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:351)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:175)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52)
> at java.lang.Class.initAnnotationsIfNecessary(Class.java:2998)
> at java.lang.Class.getAnnotation(Class.java:2958)
> at org.jboss.aop.annotation.AnnotationElement.getVisibleAnnotation(AnnotationElement.java:88)
> at org.jboss.aop.Advisor.resolveAnnotation(Advisor.java:327)
> at org.jboss.ejb3.ProxyDeployer.initializeRemoteBindingMetadata(ProxyDeployer.java:127)
> at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:70)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:573)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:555)
> at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:536)
> at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:508)
> at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463)
> at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:125)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 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:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> ...
> The exception isn't terribly surprising consindering that the annotation class just isn't there, which one is already told about by the build script referencing $JBOSS_HOME/server/xxx/deploy/ejb3.deployer/*.jar
--
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
19 years, 3 months
[JBoss JIRA] Created: (JBESB-335) File.getParent can return null
by Mark Little (JIRA)
File.getParent can return null
------------------------------
Key: JBESB-335
URL: http://jira.jboss.com/jira/browse/JBESB-335
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.0 CR2
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.0
FileCourier.postFile relies on getParent never returning null so it can get the post directory if one is not specified in the EPR. It even does a comparison later on without checking for null. Unfortunately it is legal for getParent to return null. However, in that situation we should throw an exception at the very least. The signature doesn't allow for it and I'm not changing it yet. If a post directory is not specified we will assume a relative default directory of 'post'.
--
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
19 years, 3 months
[JBoss JIRA] Created: (JBESB-303) exception in helloworld_ftp_action
by Mark Little (JIRA)
exception in helloworld_ftp_action
----------------------------------
Key: JBESB-303
URL: http://jira.jboss.com/jira/browse/JBESB-303
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.0 RC1
Reporter: Mark Little
Assigned To: Burr Sutter
Fix For: 4.0
[java] java.lang.reflect.InvocationTargetException
[java] at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.run(ActionProcessingPipeline.java:90)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.lang.NullPointerException
[java] at java.lang.String.<init>(String.java:479)
[java] at quickstart.hw_ftp_action.MyAction.displayMessage(Unknown Source)
[java] ... 7 more
[java] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
[java] 16:37:29,332 ERROR [pool-1-thread-1][ActionProcessingPipeline] Process method threw Exception
[java] java.lang.reflect.InvocationTargetException
[java] at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.run(ActionProcessingPipeline.java:90)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.lang.NullPointerException
[java] at java.lang.String.<init>(String.java:479)
[java] at quickstart.hw_ftp_action.MyAction.displayMessage(Unknown Source)
[java] ... 7 more
[java] 16:37:49,491 ERROR [Thread-5][AbstractFileGateway] Can't retrieve file list
[java] org.jboss.soa.esb.listeners.gateway.GatewayException: com.enterprisedt.net.ftp.FTPException: NLST command failed
[java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.getFileList(RemoteGatewayListener.java:131)
[java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.run(AbstractFileGateway.java:102)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: com.enterprisedt.net.ftp.FTPException: NLST command failed
[java] at com.enterprisedt.net.ftp.FTPControlSocket.validateReply(FTPControlSocket.java:800)
[java] at com.enterprisedt.net.ftp.FTPClient.dir(FTPClient.java:2087)
[java] at com.enterprisedt.net.ftp.FTPClient.dir(FTPClient.java:2022)
[java] at org.jboss.internal.soa.esb.util.EdtFtpImpl.getFileListFromRemoteDir(EdtFtpImpl.java:293)
[java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.getFileList(RemoteGatewayListener.java:122)
--
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
19 years, 3 months
[JBoss JIRA] Resolved: (EJBTHREE-433) PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration
by Carlo de Wolf (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-433?page=all ]
Carlo de Wolf resolved EJBTHREE-433.
------------------------------------
Resolution: Done
Fix Version/s: EJB 3.0 RC10 - FD
Fixed 59350
> PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration
> -----------------------------------------------------------------------
>
> Key: EJBTHREE-433
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-433
> Project: EJB 3.0
> Issue Type: Bug
> Affects Versions: EJB 3.0 RC6 - PFD
> Reporter: Christian Bauer
> Assigned To: Carlo de Wolf
> Priority: Critical
> Fix For: EJB 3.0 RC10 - FD
>
>
> Trying to deploy a persistence.xml with a resource local persistence unit:
> <persistence-unit name="caveatemptorLocalDatabase" transaction-type="RESOURCE_LOCAL">
> <properties>
> <property name="hibernate.ejb.cfgfile" value="/hibernate.cfg.xml"/>
> <property name="hibernate.archive.autodetection" value="none"/>
> </properties>
> </persistence-unit>
> 02:23:23,241 INFO MCKernelAbstraction:79 - installing bean: persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase with dependencies:
> 02:23:23,247 ERROR AbstractKernelController:350 - Error installing to Start: name=persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase state=Create
> java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: caveatemptorLocalDatabase
> at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
> 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.joinpoint.plugins.reflect.ReflectMethodJoinPoint.dispatch(ReflectMethodJoinPoint.java:72)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:96)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:476)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:171)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
> at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79)
> at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73)
> at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:86)
> at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:599)
> at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:452)
> at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:450)
> at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:199)
> at org.hibernate.ce.auction.test.runtime.EJB3Container.startup(Unknown Source)
--
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
19 years, 3 months
[JBoss JIRA] Assigned: (EJBTHREE-433) PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration
by Carlo de Wolf (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-433?page=all ]
Carlo de Wolf reassigned EJBTHREE-433:
--------------------------------------
Assignee: Carlo de Wolf
> PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration
> -----------------------------------------------------------------------
>
> Key: EJBTHREE-433
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-433
> Project: EJB 3.0
> Issue Type: Bug
> Affects Versions: EJB 3.0 RC6 - PFD
> Reporter: Christian Bauer
> Assigned To: Carlo de Wolf
> Priority: Critical
>
> Trying to deploy a persistence.xml with a resource local persistence unit:
> <persistence-unit name="caveatemptorLocalDatabase" transaction-type="RESOURCE_LOCAL">
> <properties>
> <property name="hibernate.ejb.cfgfile" value="/hibernate.cfg.xml"/>
> <property name="hibernate.archive.autodetection" value="none"/>
> </properties>
> </persistence-unit>
> 02:23:23,241 INFO MCKernelAbstraction:79 - installing bean: persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase with dependencies:
> 02:23:23,247 ERROR AbstractKernelController:350 - Error installing to Start: name=persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase state=Create
> java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: caveatemptorLocalDatabase
> at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
> 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.joinpoint.plugins.reflect.ReflectMethodJoinPoint.dispatch(ReflectMethodJoinPoint.java:72)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:96)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:476)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:171)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
> at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79)
> at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73)
> at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:86)
> at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:599)
> at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:452)
> at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:450)
> at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:199)
> at org.hibernate.ce.auction.test.runtime.EJB3Container.startup(Unknown Source)
--
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
19 years, 3 months
[JBoss JIRA] Closed: (JBAS-1853) Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1853?page=all ]
Dimitris Andreadis closed JBAS-1853.
------------------------------------
> Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
> ---------------------------------------------------------------------------------
>
> Key: JBAS-1853
> URL: http://jira.jboss.com/jira/browse/JBAS-1853
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.2 Final
> Reporter: Scott M Stark
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.CR1
>
>
> The default logging configuration location mechanism of log4j will find the server conf/log4j.xml file. One simple isolation step is to rename this file conf/jboss-log4j.xml since we do not rely on the default logging configuration location mechanism of log4j. The next level of isolation is to actually create a unique LoggerRepository for use by the jboss Logger in the Log4jService. The concern is that components like jgroups, hibernate, tomcat, etc. using commons logging will fail to pickup the Log4jService LoggerRepository. We probably need to configure commons logging as well from the Log4jService with a flag that can disable this.
--
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
19 years, 3 months
[JBoss JIRA] Resolved: (JBAS-1853) Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1853?page=all ]
Dimitris Andreadis resolved JBAS-1853.
--------------------------------------
Assignee: Dimitris Andreadis
Resolution: Done
As a first step, renamed conf/log4j.xml to conf/jboss-log4j.xml.
Leaving the RepositorySelector changes to JBAS-1313.
If you see any issue with the rename, please re-open the case.
> Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
> ---------------------------------------------------------------------------------
>
> Key: JBAS-1853
> URL: http://jira.jboss.com/jira/browse/JBAS-1853
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.2 Final
> Reporter: Scott M Stark
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.CR1
>
>
> The default logging configuration location mechanism of log4j will find the server conf/log4j.xml file. One simple isolation step is to rename this file conf/jboss-log4j.xml since we do not rely on the default logging configuration location mechanism of log4j. The next level of isolation is to actually create a unique LoggerRepository for use by the jboss Logger in the Log4jService. The concern is that components like jgroups, hibernate, tomcat, etc. using commons logging will fail to pickup the Log4jService LoggerRepository. We probably need to configure commons logging as well from the Log4jService with a flag that can disable this.
--
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
19 years, 3 months
[JBoss JIRA] Updated: (JBAS-1853) Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1853?page=all ]
Dimitris Andreadis updated JBAS-1853:
-------------------------------------
Summary: Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override. (was: Better isolate the server log4j usage)
Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)])
> Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
> ---------------------------------------------------------------------------------
>
> Key: JBAS-1853
> URL: http://jira.jboss.com/jira/browse/JBAS-1853
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.2 Final
> Reporter: Scott M Stark
> Fix For: JBossAS-4.2.0.CR1
>
>
> The default logging configuration location mechanism of log4j will find the server conf/log4j.xml file. One simple isolation step is to rename this file conf/jboss-log4j.xml since we do not rely on the default logging configuration location mechanism of log4j. The next level of isolation is to actually create a unique LoggerRepository for use by the jboss Logger in the Log4jService. The concern is that components like jgroups, hibernate, tomcat, etc. using commons logging will fail to pickup the Log4jService LoggerRepository. We probably need to configure commons logging as well from the Log4jService with a flag that can disable this.
--
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
19 years, 3 months