java.lang.IllegalArgumentException: MQ:Topic:Invalid Topic Name - jms/Topic / Thanks, Sahoo Sahoo wrote: > I think it is an issue with context class loader. Can you configure > your Spring DM OSGi service to run in the context of the calling > Servlet if such a configuration option available? > > Thanks, > Sahoo > > glassfish@javadesktop.org wrote: >> I'm trying to get a simple JMS Topic application running and I'm >> having problems. My message producer is a pojo that's inside n OSGi >> bundle that I've deployed. It gets called from within a service >> that's exposed using Spring DM to a web servlet. >> The code for the message producer: >> >> public void sendMessage(String data) >> { >> Context theContext = new InitialContext(); >> System.out.println("Getting Connection Factory."); >> TopicConnectionFactory topicFactory = >> (TopicConnectionFactory) theContext.lookup("jms/TopicFactory"); >> >> System.out.println("Getting Topic."); >> Topic topic = (Topic) theContext.lookup("jmsTopic"); >> // Here's where it fails >> >> topicConnection = topicFactory.createTopicConnection(); >> session = topicConnection.createTopicSession(false, >> Session.AUTO_ACKNOWLEDGE); >> publisher = session.createPublisher(topic); >> message = session.createTextMessage(data); >> >> System.out.println("Sending Message."); >> publisher.publish(message); >> } >> >> I've created the Factory and the Topic using the Glassfish Admin >> console (Resources->JMS Resources->Destination Resources). I also >> tried it with creating the physical resource (Configuration->Java >> Messaging Service->Physical Destinations). >> >> Stack Trace: >> >> [#|2010-04-19T09:01:37.462-0400|SEVERE|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=40;_ThreadName=Thread-8;|javax.naming.CommunicationException: >> Communication exception for SerialContext [Root exception is >> com.sun.appserv.connectors.internal.api.PoolingException] >> at >> com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:475) >> >>

Oracle Community | ltouve | 7 years ago
  1. 0

    JMS Using Spring

    Oracle Community | 7 years ago | ltouve
    java.lang.IllegalArgumentException: MQ:Topic:Invalid Topic Name - jms/Topic / Thanks, Sahoo Sahoo wrote: > I think it is an issue with context class loader. Can you configure > your Spring DM OSGi service to run in the context of the calling > Servlet if such a configuration option available? > > Thanks, > Sahoo > > glassfish@javadesktop.org wrote: >> I'm trying to get a simple JMS Topic application running and I'm >> having problems. My message producer is a pojo that's inside n OSGi >> bundle that I've deployed. It gets called from within a service >> that's exposed using Spring DM to a web servlet. >> The code for the message producer: >> >> public void sendMessage(String data) >> { >> Context theContext = new InitialContext(); >> System.out.println("Getting Connection Factory."); >> TopicConnectionFactory topicFactory = >> (TopicConnectionFactory) theContext.lookup("jms/TopicFactory"); >> >> System.out.println("Getting Topic."); >> Topic topic = (Topic) theContext.lookup("jmsTopic"); >> // Here's where it fails >> >> topicConnection = topicFactory.createTopicConnection(); >> session = topicConnection.createTopicSession(false, >> Session.AUTO_ACKNOWLEDGE); >> publisher = session.createPublisher(topic); >> message = session.createTextMessage(data); >> >> System.out.println("Sending Message."); >> publisher.publish(message); >> } >> >> I've created the Factory and the Topic using the Glassfish Admin >> console (Resources->JMS Resources->Destination Resources). I also >> tried it with creating the physical resource (Configuration->Java >> Messaging Service->Physical Destinations). >> >> Stack Trace: >> >> [#|2010-04-19T09:01:37.462-0400|SEVERE|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=40;_ThreadName=Thread-8;|javax.naming.CommunicationException: >> Communication exception for SerialContext [Root exception is >> com.sun.appserv.connectors.internal.api.PoolingException] >> at >> com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:475) >> >>
  2. 0

    JMS Using Spring

    Oracle Community | 7 years ago | ltouve
    javax.naming.CommunicationException: Communication exception for SerialContext [Root exception is com.sun.appserv.connectors.internal.api.PoolingException]
  3. 0

    JMS Using Spring

    Oracle Community | 7 years ago | ltouve
    java.lang.IllegalArgumentException: MQ:Topic:Invalid Topic >> Name - jms/Topic >>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    spring3 jpa2.0 tomcat error java.lang.IllegalArgumentException: Object: com.web.emscs.entity.Student@1edf83b is not a known entity type

    programask.com | 1 year ago
    java.lang.IllegalArgumentException: n must be positive when I ... I have create an SP which return Dynamic Resultsets so i have created a complex type for mapping the result sets in to entity. While executing this procedure i got the exception No mapping exists ... I want to secure my admin pages in tomcat with web.xml and tomcat-users.xml.It doesn't works. Here is my contents of my tomcat-users.xml <?xml version='1.0' encoding='utf-8'?> ... I have a script User.groovy and UserController.groovy. When I run it, I'm getting Caught: No signature of method: com.vasco.gs.User.addToUserRoles() is applicable for argument types: ... After another SO poster(Vinicius Miana) resolved my issue to insert a List[DBObject] ... // Bulk insert all documents collection.insert(MongoDBList(docs)) // docs is List[DBObject] Now, I'm seeing ... public static String getFilePathFromUri(Uri uri, Context c) { try { String filePath = null; String scheme = uri.getScheme(); if (scheme != null && ... Cursor ck = db.rawQuery("select name,title,text,type from abstracts_item,abstract_author,authors_abstract where abstract_author._id == authors_abstract.abstractauthor_id and abstracts_item._id == ... Im learning to code Android in NDK on WINDOWS Eclipse.... been following a Tutorial Book by Sylvain Ratabouil. So im in Run | External Tools | External Tools Configurations… creating a new ... In a larger playframework 2.1.3 application, I started to use JClouds blobstorage. I added the dependencies "org.apache.jclouds" % "jclouds-allblobstore" % "1.6.1-incubating", ... I am calling .net webservice in JAVA class which will read string from text file and UTF8 encode that and return that string to JAVA .Some times the correct output is coming . but sometimes this is ... I am using Cobertura to code coverage for Integration test. I am facing below issue while deploying instrumented jar in JBoss server. DEPLOYMENTS IN ERROR: Deployment ... I had asked this question a few days back but did not know where the log files were located. I have the config settings in core-site.xml as follows <configuration> <property> ... I am getting the following Exception in my code... IllegalArgumentException: View not attached to window manager
  6. 0

    jndi unknown source with jms

    Oracle Community | 5 years ago | 932533
    nternal.api.ConnectorRuntimeException

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      MQ:Topic:Invalid Topic Name - jms/Topic / Thanks, Sahoo Sahoo wrote: > I think it is an issue with context class loader. Can you configure > your Spring DM OSGi service to run in the context of the calling > Servlet if such a configuration option available? > > Thanks, > Sahoo > > glassfish@javadesktop.org wrote: >> I'm trying to get a simple JMS Topic application running and I'm >> having problems. My message producer is a pojo that's inside n OSGi >> bundle that I've deployed. It gets called from within a service >> that's exposed using Spring DM to a web servlet. >> The code for the message producer: >> >> public void sendMessage(String data) >> { >> Context theContext = new InitialContext(); >> System.out.println("Getting Connection Factory."); >> TopicConnectionFactory topicFactory = >> (TopicConnectionFactory) theContext.lookup("jms/TopicFactory"); >> >> System.out.println("Getting Topic."); >> Topic topic = (Topic) theContext.lookup("jmsTopic"); >> // Here's where it fails >> >> topicConnection = topicFactory.createTopicConnection(); >> session = topicConnection.createTopicSession(false, >> Session.AUTO_ACKNOWLEDGE); >> publisher = session.createPublisher(topic); >> message = session.createTextMessage(data); >> >> System.out.println("Sending Message."); >> publisher.publish(message); >> } >> >> I've created the Factory and the Topic using the Glassfish Admin >> console (Resources->JMS Resources->Destination Resources). I also >> tried it with creating the physical resource (Configuration->Java >> Messaging Service->Physical Destinations). >> >> Stack Trace: >> >> [#|2010-04-19T09:01:37.462-0400|SEVERE|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=40;_ThreadName=Thread-8;|javax.naming.CommunicationException: >> Communication exception for SerialContext [Root exception is >> com.sun.appserv.connectors.internal.api.PoolingException] >> at >> com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:475) >> >>

      at javax.naming.InitialContext.lookup()
    2. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:392)
      2. javax.naming.InitialContext.lookup(InitialContext.java:392)
      2 frames