[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-1650: ------------------------------- Priority: Minor (was: Major) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-1650. --------------------------------------- Release Notes Text: need more info thus rejecting as incomplete and assume not related to tools. reopen if more info gathered. Resolution: Incomplete Description -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Koen Aers commented on JBDS-1650: --------------------------------- Len, can you please document in detail what this issue is about? - What is your operating environment? - What are the steps to reproduce? - What is the unwanted behaviour and why is it unwanted? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Koen Aers commented on JBDS-1650: --------------------------------- But AFAICS this is not at all jBPM related then. If you would create a random project in JBDS with a HSQLDB config in it and you mark it deployable and try to deploy it to the SOA-P server than the same thing would happen, right? Anyway, I suspect that this behaviour would not occur if you remove the jbpm-hsqldb-ds.xml file from the 'config' folder in the jbpm project. Can you verify if that is the case? If it is, the issue can be solved by not including this file in the jBPM runtime that is shipped with SOA-P. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Koen Aers commented on JBDS-1650: --------------------------------- Len, I am completely clueless as to how to reproduce this issue. I did the following: - install new copy of SOA-P 5.1 - install new copy of JBDS 4.1.0.CR1 - fire up the new JBDS in a new workspace - add SOA-P 5.1 as a new server in JBDS - start the server (did you know that this does *not* work in Fedora 15, I had to use my Mac) - create a new jBPM 3 project - right-click the project and select 'Mark as Deployable...' The only result that I get are two exceptions in my 'Error View'. The first one of these reads: "JBossTools was unable to pause the JBoss deployment scanner. Your deployment may not be recognized by the server. Please ensure your version of JBoss includes an unsecured JMX adapter." The second one: JBossTools was unable to resume the JBoss deployment scanner. Your deployment may not be recognized by the server. Please ensure your version of JBoss includes an unsecured JMX adapter. In both cases I get an exception stack trace looking like the following: java.lang.SecurityException: Failed to authenticate principal=admin, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) It looks like there is a security setting that I'm missing. Can you please provide me with some more details as to how I should try to reproduce this. Also, can you please detail the 'unwanted' behaviour? Which Hypersonic DB artifacts do I have to see and where and how can I find them? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1650?page=com.atlassian.jira.plugin.... ] Vlado Pakan closed JBDS-1650. ----------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira