The ProfileServiceUnitTestCase.testJmsDestinationComponents is broken because there is a disconnect between the profile deployment names and MainDeployer.getManagedDeployment(String name). The messaging destinations are being seen as children of the deploy/messaging/ deployment, and this is not a managable deployment. Some deployment processing logic has changed since this test was last working. if I move the messaging deployments to the deploy directory, the managed objects are created, but they are again referencing non-serializable values. This time its an AnnotationProxy that cannot be marshalled: | java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: | java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.annotation.factory.AnnotationProxy | at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:669) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.getComponentsForType(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testJmsDestinationComponents(ProfileServiceUnitTestCase.java:305) | This looks like it should in fact be Serializable as its just a generic annotation implementation. Not sure what is pulling in the AnnotationProxy at this point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113844#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...