Hello there .. Trying to deploy a simple JMS sample that uses classic and simplified API. The sample is available at: https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receiv... But the deployment is failing with: 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread - 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => [ "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue is missing [jboss.naming.context.java.global.jms.myQueue2]", "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue is missing [jboss.naming.context.java.global.jms.myQueue2]", "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue is missing [jboss.naming.context.java.global.jms.myQueue2]", "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue is missing [jboss.naming.context.java.global.jms.myQueue2]" ]} Any suggestions ? Arun -- Blog: http://blog.arungupta.me Twitter: http://twitter.com/arungupta _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Both of these should not be required for Java EE 7. The sample has: @JMSDestinationDefinitions({@JMSDestinationDefinition(name = "java:global/jms/myQueue2", interfaceName = "javax.jms.Queue") }) so the destination should be created as part of deployment. And JMSContext relies upon default JMS Connection Factory. Arun On Wed, Oct 30, 2013 at 7:08 AM, Nick Mpallas <mpallas(a)gmail.com&gt; wrote: > Arun, > you have to create the queues + the name of the exposed ConnectionFactory > depends if you are connecting from an in-vm factory or you want a remote > connection factory. > > > On Wed, Oct 30, 2013 at 3:05 PM, Arun Gupta <arun.gupta(a)gmail.com&gt; wrote: >> >> Hello there .. >> >> Trying to deploy a simple JMS sample that uses classic and simplified >> API. The sample is available at: >> >> >> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receiv... >> >> But the deployment is failing with: >> >> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread - >> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was >> rolled back with the following failure message: >> {"JBAS014771: Services with missing/unavailable dependencies" => [ >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory >> is missing >> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory >> is missing >> [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]" >> ]} >> >> >> Any suggestions ? >> >> Arun >> -- >> Blog: http://blog.arungupta.me >> Twitter: http://twitter.com/arungupta >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > > -- > \n\m > "camel is a horse made up in a laboratory" -- Blog: http://blog.arungupta.me Twitter: http://twitter.com/arungupta

On 30 Oct 2013, at 15:05, Arun Gupta <arun.gupta(a)gmail.com&gt; wrote: > Hello there .. > > Trying to deploy a simple JMS sample that uses classic and simplified > API. The sample is available at: > > https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receiv... > > But the deployment is failing with: > > 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread - > 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was > rolled back with the following failure message: > {"JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory > is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory > is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue > is missing [jboss.naming.context.java.global.jms.myQueue2]", > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue > is missing [jboss.naming.context.java.global.jms.myQueue2]", > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue > is missing [jboss.naming.context.java.global.jms.myQueue2]", > "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue > is missing [jboss.naming.context.java.global.jms.myQueue2]" > ]} > > > Any suggestions ? which standalone configuration are your using? JMS is part of standalone-full.xml and not in standalone.xml. jeff -- Jeff Mesnil JBoss, a division of Red Hat http://jmesnil.net/

Ah, that might be it. Noob question then ... How do you tell standalone.sh to use standalone-full.xml ? Arun On Wed, Oct 30, 2013 at 7:10 AM, Jeff Mesnil <jmesnil(a)redhat.com&gt; wrote: > > On 30 Oct 2013, at 15:05, Arun Gupta <arun.gupta(a)gmail.com&gt; wrote: > >> Hello there .. >> >> Trying to deploy a simple JMS sample that uses classic and simplified >> API. The sample is available at: >> >> https://github.com/arun-gupta/javaee7-samples/tree/master/jms/send-receiv... >> >> But the deployment is failing with: >> >> 07:01:10,423 ERROR [org.jboss.as.server] (management-handler-thread - >> 28) JBAS015870: Deploy of deployment "send-receive-simple.war" was >> rolled back with the following failure message: >> {"JBAS014771: Services with missing/unavailable dependencies" => [ >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".connectionFactory >> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".connectionFactory >> is missing [jboss.naming.context.java.module.send-receive-simple.send-receive-simple.DefaultJMSConnectionFactory]", >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageReceiver\".myQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageSender\".demoQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.ClassicMessageReceiver\".demoQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]", >> "jboss.naming.context.java.module.send-receive-simple.send-receive-simple.env.\"org.javaee7.jms.send.receive.simple.SimplifiedMessageSender\".myQueue >> is missing [jboss.naming.context.java.global.jms.myQueue2]" >> ]} >> >> >> Any suggestions ? > > which standalone configuration are your using? > > JMS is part of standalone-full.xml and not in standalone.xml. > > jeff > > -- > Jeff Mesnil > JBoss, a division of Red Hat > http://jmesnil.net/ > -- Blog: http://blog.arungupta.me Twitter: http://twitter.com/arungupta _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On 30 Oct 2013, at 15:12, Arun Gupta <arun.gupta(a)gmail.com&gt; wrote: > Ah, that might be it. > > Noob question then ... > > How do you tell standalone.sh to use standalone-full.xml ? standalone.sh -c standalone-full.xml

bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack.

jeff -- Jeff Mesnil JBoss, a division of Red Hat http://jmesnil.net/

> > What is the idea behind specifying the complete configuration file > name (including extension) instead of just the file name ? I think the > latter is less verbose. > You mean why not just bin/standalone.sh -c standalone-full ? No particular reason. It never occurred to me. Thinking back on it, it partly arose because in AS < 7 the -c value was basically a reference to a dir name, while in AS7 it's a ref to a file name. The entire structure of the AS dist is radically different in AS7. Being more explicit about that difference was more important at the time than it is now. If bin/standalone.sh -c st<tab complete to andalone/configuration/standalone-full.xml> would work I'd be real tempted to support that.

>>> What is the idea behind specifying the complete configuration file >>> name (including extension) instead of just the file name ? I think the >>> latter is less verbose. >>> >> >> You mean why not just bin/standalone.sh -c standalone-full ? >> >> No particular reason. It never occurred to me. Thinking back on it, it >> partly arose because in AS < 7 the -c value was basically a reference to >> a dir name, while in AS7 it's a ref to a file name. The entire structure >> of the AS dist is radically different in AS7. Being more explicit about >> that difference was more important at the time than it is now. >> >> If bin/standalone.sh -c st<tab complete to >> andalone/configuration/standalone-full.xml> would work I'd be real >> tempted to support that. > > This would be really nice, simplicity and intuitiveness go a long way > in better developer experience. Wonder how that would work together with -Djboss.server.base.dir and/or -Djboss.server.config.dir [1]. A great potential for confusion I see.

[1] https://docs.jboss.org/author/display/WFLY8/Command+line+parameters LT _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On 30/10/13 15:14, Jeff Mesnil wrote: > standalone.sh -c standalone-full.xml > > bear in mind that the standalone.xml corresponds to the Web profile (and JMS is not part of it) while standalone-full.xml corresponds to the whole EE7 stack. Not really a problem here :-), but just FYI standalone.xml has more then the minimum required for Web profile, as it comes with webservices subsystem (hence JSR 224, JSR 181, JSR 109) enabled. But still, for the whole EE7 stack, standalone-full.xml is required.