-
15. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
starksm64 Mar 15, 2008 2:12 PM (in response to starksm64)This is noise coming from the org.jboss.messaging.util.ExceptionUtil in terms of the error logging. The ServiceMetaDataICF attempting to get the value just ignores this and moves on without a value. I don't see why this prevents other existing resources from being seen.
So what is the point at which the profile service is queried? I'll have to see why subsequent requerying would not show the updated view. -
16. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 17, 2008 6:08 PM (in response to starksm64)Not sure what I can really add.
Here is the code that runs while discovering the resource.
First at the AS discovery level we runProfileServiceFactory.refreshCurrentProfileView(); which looks like this. try { Profile activeProfile = getProfileService().getActiveProfile(); ProfileKey activeKey = activeProfile.getKey(); getCurrentProfileView().loadProfile(activeKey); } catch (Exception e) { LOG.error("Could not find default Profile in Current Profile View", e); } The following is the getProfileService() method call in the first line public static ProfileService getProfileService() { if (profileService == null) { InitialContext initialContext; try { initialContext = new InitialContext(); } catch (NamingException e) { LOG.error("Unable to get an InitialContext to JBoss AS 5", e); return null; } try { profileService = (ProfileService) initialContext.lookup("ProfileService"); /*ManagementView view = getCurrentProfileView(); ComponentType type = new ComponentType("DataSource", "LocalTx"); Set<ManagedComponent> components = view.getComponentsForType(type);*/ } catch (NamingException e) { LOG.error("Could not find ProfileService Name on JBoss AS 5", e); } catch (Exception e) { LOG.error("Exception thrown when looking up ProfileService on JBoss AS 5", e); } } return profileService; }
Then for each ComponentType it will run the following codeComponentType componentType = ConversionUtil.getComponentType(resourceType); ManagementView mgtView = ProfileServiceFactory.getCurrentProfileView(); Set<ManagedComponent> components = null; try { components = mgtView.getComponentsForType(componentType); } catch (Exception e) { LOG.error("Unable to get component for type " + componentType, e); } The factory call to getCurrentProfileView() is here /** * Get the current profile's Management view. This will get the domains from the profile service * and return the first one in the list. * * @return ManagementView the management view of the first domain */ public static ManagementView getCurrentProfileView() { if (currentProfileView == null) { currentProfileView = getProfileService().getViewManager(); refreshCurrentProfileView(); } return currentProfileView; } the refreshCurrentProfileView() call above is below, but it is one and the same as you saw at the beginning of the code I just posted. :) /** * This will refresh the managementView to have all the newest resources. * It simply nulls out the "singleton" reference in this factory and calls * getCurrentProfileView to reload the view with loadProfile(); */ public static void refreshCurrentProfileView() { try { Profile activeProfile = getProfileService().getActiveProfile(); ProfileKey activeKey = activeProfile.getKey(); getCurrentProfileView().loadProfile(activeKey); } catch (Exception e) { LOG.error("Could not find default Profile in Current Profile View", e); } }
This is the code that was working before to discovering the Datasources and refreshing when creating and deleting datasource.
Mark -
17. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 19, 2008 5:08 PM (in response to starksm64)After building from JBoss-head/trunk and running the server created in the build/output directory, I am see the following exceptions.
On to running the test.
13:24:01,062 INFO [ManagementViewImpl] Creating hsqldb-ds.xml ManagedDeployment
13:24:02,078 WARN [ManagementViewImpl] Failed to create ManagedDeployment for: vfsfile:/C:/JBossSVN/jboss-head/build/ou
tput/jboss-5.0.0.CR1/server/default/deploy/messaging/
org.jboss.deployers.spi.DeploymentException: Error building managed objects for vfsfile:/C:/JBossSVN/jboss-head/build/ou
tput/jboss-5.0.0.CR1/server/default/deploy/messaging/destinations-service.xml
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.build(DeployerWrapper.java:221)
at org.jboss.deployers.plugins.deployers.DeployersImpl.getManagedObjects(DeployersImpl.java:364)
at org.jboss.deployers.plugins.main.MainDeployerImpl.getManagedObjects(MainDeployerImpl.java:774)
at org.jboss.deployers.plugins.main.MainDeployerImpl.processManagedDeployment(MainDeployerImpl.java:823)
at org.jboss.deployers.plugins.main.MainDeployerImpl.getManagedDeployment(MainDeployerImpl.java:755)
at org.jboss.profileservice.management.ManagementViewImpl.loadProfile(ManagementViewImpl.java:186)
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.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java
:56)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:847)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
at org.jboss.remoting.Client.invoke(Client.java:1685)
at org.jboss.remoting.Client.invoke(Client.java:589)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:1
02)
at org.rhq.plugins.jbossas5.ProfileJBossServerDiscoveryComponent.discoverResources(ProfileJBossServerDiscoveryCo
mponent.java:54)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.pluginDiscovery(AutoDiscoveryExecutor.java:189)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:98)
at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:65)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.j
ava:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168
)
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: Error creating annotation for @org.jboss.system.deployers.managed.ManagementObjec
tClass(code=org.jboss.jms.server.destination.QueueServiceMO)
at org.jboss.system.metadata.ServiceAnnotationMetaData.getAnnotationInstance(ServiceAnnotationMetaData.java:109)
at org.jboss.system.deployers.managed.ServiceMetaDataICF.getManagedObjectClass(ServiceMetaDataICF.java:100)
at org.jboss.system.deployers.managed.ServiceMetaDataICF.getManagedObjectClass(ServiceMetaDataICF.java:55)
at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory
.java:170)
at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.getValue(AbstractManagedObjectFactory.java:760
)
at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.populateValues(AbstractManagedObjectFactory.ja
va:600)
at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.populateManagedObject(AbstractManagedObjectFac
tory.java:549)
at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory
.java:183)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.build(AbstractParsingDeployerWithO
utput.java:311)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.build(DeployerWrapper.java:217)
... 35 more
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.jboss.jms.server.destination.QueueServiceMO
at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:228)
at org.jboss.annotation.factory.ast.ASTIdentifier.jjtAccept(ASTIdentifier.java:37)
at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:102)
at org.jboss.annotation.factory.ast.ASTMemberValuePair.jjtAccept(ASTMemberValuePair.java:37)
at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:364)
at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:386)
at org.jboss.system.metadata.ServiceAnnotationMetaData.getAnnotationInstance(ServiceAnnotationMetaData.java:105)
... 44 more
Caused by: java.lang.ClassNotFoundException: org.jboss.jms.server.destination.QueueServiceMO
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:162)
... 50 more -
18. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 19, 2008 5:09 PM (in response to starksm64)Testsuite for JMS is also failing to run
I get this with both a build downloaded from Hudson, and also the one in the build/output directory
Testsuite: org.jboss.test.profileservice.test.JmsDestinationUnitTestCase
Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 1.375 sec
Testcase: testDLQ took 1.093 sec
Caused an ERROR
Profile root does not exists: C:\JBossServers\jboss-5.0.0.CR1\server\profileservice
org.jboss.profileservice.spi.NoSuchProfileException: Profile root does not exists: C:\JBossServers\jboss-5.0.0.CR1\server\profileservice
at org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository.load(SerializableDeploymentRepository.java:479)
at org.jboss.system.server.profileservice.repository.FileProfileRepository.getProfileDeploymentRepository(FileProfileRepository.java:135)
at org.jboss.system.server.profileservice.repository.ProfileServiceImpl.getProfile(ProfileServiceImpl.java:155)
at org.jboss.profileservice.management.ManagementViewImpl.loadProfile(ManagementViewImpl.java:169)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:56)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:847)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:682)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:635)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:459)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:197)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:203)
at org.jboss.remoting.Client.invoke(Client.java:1685)
at org.jboss.remoting.Client.invoke(Client.java:589)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.test.profileservice.test.AbstractProfileServiceTest.getManagementView(AbstractProfileServiceTest.java:147)
at org.jboss.test.profileservice.test.JmsDestinationUnitTestCase.testDLQ(JmsDestinationUnitTestCase.java:66)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.test.profileservice.test.AbstractProfileServiceTest.getManagementView(AbstractProfileServiceTest.java:147)
at org.jboss.test.profileservice.test.JmsDestinationUnitTestCase.testDLQ(JmsDestinationUnitTestCase.java:66) -
19. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
starksm64 Mar 19, 2008 7:44 PM (in response to starksm64)How are you running the tests? Based on the error it seems the profileservice config has not been created. There is profileservice-config target in the testsuite/build.xml that creates the config and runs the tests. Currently I do see new failures:
[junit] Running org.jboss.test.profileservice.test.JmsDestinationUnitTestCase [junit] Tests run: 5, Failures: 1, Errors: 2, Time elapsed: 2.086 sec [junit] Test org.jboss.test.profileservice.test.JmsDestinationUnitTestCase FAILED [junit] Running org.jboss.test.profileservice.test.ProfileServiceUnitTestCase [junit] Tests run: 22, Failures: 2, Errors: 3, Time elapsed: 4.793 sec [junit] Test org.jboss.test.profileservice.test.ProfileServiceUnitTestCase FAILED
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.jboss.jms.server.destination.QueueServiceMO at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:228) at org.jboss.annotation.factory.ast.ASTIdentifier.jjtAccept(ASTIdentifier.java:37) at org.jboss.annotation.factory.AnnotationCreator.visit(AnnotationCreator.java:102) at org.jboss.annotation.factory.ast.ASTMemberValuePair.jjtAccept(ASTMemberValuePair.java:37) at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:364) at org.jboss.annotation.factory.AnnotationCreator.createAnnotation(AnnotationCreator.java:386) at org.jboss.system.metadata.ServiceAnnotationMetaData.getAnnotationInstance(ServiceAnnotationMetaData.java:105)
Looking into it. -
20. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 19, 2008 8:02 PM (in response to starksm64)I start up an AS 5 instance, either the one in the build/output directory or I run it against a Hudson Build that I downloaded
In the testsuite directory I run
build one-test -Dtest=org.jboss.test.profileservice.test.ProfileServiceUnitTestCase
Thanks
Mark -
21. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
starksm64 Mar 19, 2008 8:43 PM (in response to starksm64)The CNFE is a side-effect of JBDEPLOY-7/JBMICROCONT-231 being seen now. It looks like the BasicXMLDeployer is not establishing the deployment class loader as the context class loader properly.
-
22. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
starksm64 Mar 19, 2008 10:40 PM (in response to starksm64)With the fix for JBAS-5330 I just comitted, the jms destination tests are running again:
[junit] Running org.jboss.test.profileservice.test.JmsDestinationUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.174 sec [junit] Running org.jboss.test.profileservice.test.ProfileServiceUnitTestCase [junit] Tests run: 22, Failures: 1, Errors: 3, Time elapsed: 4.747 sec [junit] Test org.jboss.test.profileservice.test.ProfileServiceUnitTestCase FAILED
Still 2 unexpected ProfileServiceUnitTestCase test problems I'll look at next. -
23. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 25, 2008 8:45 PM (in response to starksm64)Ok, so now I was able to get a trunk build, but now the testsuite build fails. I also downloaded rev 1252 of AS to try to deploy the embedded console but now get
17:36:16,203 INFO [TomcatDeployment] deploy, ctxPath=/embedded-console, vfsUrl=embedded-console.war
17:36:16,250 ERROR [BaseModelMBean] Exception invoking method addChild
java.lang.RuntimeException: mapped-name is required for timerService of deployment embedded-console.war
Mark -
24. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
alesj Mar 26, 2008 7:13 AM (in response to starksm64)This is the same issue as here:
- http://www.seamframework.org/Community/SeamExamplesOnJBoss5beta4
And afaik it's not been established yet on what is the real cause. -
25. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
starksm64 Mar 28, 2008 3:22 AM (in response to starksm64)I'm not seeing these type of errors with the current trunk, and the tests are running at the expected levels:
[echo] Starting patternset=profileservice.includes config=profileservice [junit] Running org.jboss.test.profileservice.test.JmsDestinationUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.57 sec [junit] Running org.jboss.test.profileservice.test.ProfileServiceUnitTestCase [junit] Tests run: 22, Failures: 1, Errors: 2, Time elapsed: 6 sec [junit] Test org.jboss.test.profileservice.test.ProfileServiceUnitTestCase FAILED
-
26. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 28, 2008 11:02 AM (in response to starksm64)Yeah, I just svn up and still can't build the testsuite. I get
BUILD FAILED
C:\JBossSVN\jboss-head\testsuite\build.xml:467: Reference jboss.jboss.reflect.classpath not found.
Total time: 4 seconds
Mark -
27. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 28, 2008 11:32 AM (in response to starksm64)OK, I managed to get the testsuite built by fiddling with those ref classpath vars, but now when I run the Jms test I get the following error
Testsuite: org.jboss.test.profileservice.test.JmsDestinationUnitTestCase
Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 1.516 sec
Testcase: testDLQ took 1.234 sec
Caused an ERROR
Profile root does not exists: C:\JBossServers\jboss-5.0.0.CR1\server\profileservice
org.jboss.profileservice.spi.NoSuchProfileException: Profile root does not exists: C:\JBossServers\jboss-5.0.0.CR1\server\profileservice
at org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository.load(SerializableDeploymentRepository.java:479)
at org.jboss.system.server.profileservice.repository.FileProfileRepository.getProfileDeploymentRepository(FileProfileRepository.java:135)
at org.jboss.system.server.profileservice.repository.ProfileServiceImpl.getProfile(ProfileServiceImpl.java:155)
at org.jboss.profileservice.management.ManagementViewImpl.loadProfile(ManagementViewImpl.java:169)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:56)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:847)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:682)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:635)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:459)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:197)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:203)
at org.jboss.remoting.Client.invoke(Client.java:1685)
at org.jboss.remoting.Client.invoke(Client.java:589)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.test.profileservice.test.AbstractProfileServiceTest.getManagementView(AbstractProfileServiceTest.java:147)
at org.jboss.test.profileservice.test.JmsDestinationUnitTestCase.testDLQ(JmsDestinationUnitTestCase.java:66)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.test.profileservice.test.AbstractProfileServiceTest.getManagementView(AbstractProfileServiceTest.java:147)
at org.jboss.test.profileservice.test.JmsDestinationUnitTestCase.testDLQ(JmsDestinationUnitTestCase.java:66)
Mark -
28. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 28, 2008 12:05 PM (in response to starksm64)OK, another change to some code and now I get successful running of the UnitTest
one-test:
[junit] Running org.jboss.test.profileservice.test.JmsDestinationUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 10.188 sec
BUILD SUCCESSFUL
Total time: 52 seconds
So now to figure out what could be the difference between the testcase and my code.
Mark -
29. Re: JBAS-5259, JMS Destination Names is showing as QueueServ
bytor99999 Mar 28, 2008 4:37 PM (in response to starksm64)"alesj" wrote:
This is the same issue as here:
- http://www.seamframework.org/Community/SeamExamplesOnJBoss5beta4
And afaik it's not been established yet on what is the real cause.
Well in that thread that was for Beta 4. This is with the latest Hudson builds, which between Beta 4 release and these builds, I was deploying the web app fine. It is something recently added.
I can always create a Cactus Unit Test and run it in AS 5 without needing Seam, and see if that helps.
Mark