Description of problem: Tried to create a JMS Queue. This failed with java.lang.reflect.InvocationTargetException:null -> java.lang.RuntimeException:Failed to process template. -> java.io.FileNotFoundException:/var/folders/m9/m9pXAK2WHoyq22G2P9J8LTI/-Tmp-/JmsDestinationTemplate6780606229493193287-service.xml snert:~ hrupp$ ls /var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-/ 25f6ca5f-128f808e80a--6c31567341063383340175.upload Jetty_0_0_0_0_50090_secondary____y6aanv 3F2B3850-4B74-4B2F-94AD-5AC60CB8F42D MediaCache Jetty_0_0_0_0_50030_job____yn7qmk com.apple.notify.196.22 Jetty_0_0_0_0_50060_task____.2vcltf hsperfdata_hrupp Jetty_0_0_0_0_50070_hdfs____w2cu08 sprite.jpg Jetty_0_0_0_0_50075_datanode____hwtdwq
Created attachment 421180 [details] Screenshot of debugger variables Looks like for some reasons there are spaces in the temp file path, that may no be correctly handled. Exception happens in CreateChildResourceFacetDelegate:103 managementView.applyTemplate(componentName, template); EAP 5.0.1 server log shows 2010-06-04 11:49:51,253 DEBUG [org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget] (WorkerThread#1 [172.31.7.7:51719]) Begin distribute: names=[queue_MyQ-service.xml], copyContent=true, description=vfsfile:/var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-/JmsDestinationTemplate1027497348895621707-service.xml snert:~ hrupp$ ls /var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-/JmsDestinationTemplate1027497348895621707-service.xml ls: /var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-/JmsDestinationTemplate1027497348895621707-service.xml: No such file or directory snert:~ hrupp$ ls /var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-/ 25f6ca5f-128f808e80a--6c31567341063383340175.upload Jetty_0_0_0_0_50090_secondary____y6aanv 3F2B3850-4B74-4B2F-94AD-5AC60CB8F42D MediaCache Jetty_0_0_0_0_50030_job____yn7qmk WebStartIcon_90470 Jetty_0_0_0_0_50060_task____.2vcltf com.apple.notify.196.22 Jetty_0_0_0_0_50070_hdfs____w2cu08 hsperfdata_hrupp Jetty_0_0_0_0_50075_datanode____hwtdwq sprite.jpg So this looks very much like an issue with in EAP 5.0.1 that we can't do anything about in RHQ.
This works on RHEL 5.5 with sun jdk and EAP 5.0.1
I wasn't able to reproduce this, but I agree, it looks like a JBAS bug. I'll create a JBAS JIRA issue for it.
I've created https://jira.jboss.org/browse/JBPAPP-4514.
QA Closing - bug in JBAS, not rhq