Doubt in jms

Hi all,
i got a requirement to get data from another application using JMS api
what are the steps need to get data using jms
any 1 help me out
thanks in advance

vveena wrote:
thanks for the reply....
i have read abt JMS api and came to know how to receive,put and read msgs..
i need to get the data using Reuters
so what r the steps i need to do???
im doubt if i use pub/sub how do i know the topic name from thatYou use publish/subscribe if you want to multi-cast your message (one to many), and use point-to-point if you want to send to only consumer(one to one). It depends on your scenario, you can choose the appropriate model. For example, if you want to send all of your consumers some update with the latest information you might choose pub/sub, whereas in some parts you are just connecting to one specific node for certain operations which is not desirable if others do as well. Then, you choose point-to-point. For further information, you can check J2EE/JMS tutorial.
First of all, you are the one who creates the topic/queue in the application server, so you know their names. But how can you can find out to which one you should send or from which you should retrieve your messages, is absolutely hard coded. It means that in your application, you choose to send your request for example in Q1 and receive the response from Q2. ( That was just an example ;),
>
how do get details from that application???I didn't get your question, but if it means how to create those destinations, you just create them in your application servers such as Sun Application Server, JBoss, and etc..

Similar Messages

Doubt in jms content conversion

Hi ,
I m doing content conversion in sender jms channel.
My input is of the format
AAAAAAA#bbbbbbb#ccccccc#
I want to map it to XML Structure
<Root>
<Record>
<item>AAAAA </item>
</Record>
<Record>
<item>bbbbb</item>
</Record>
<Record>
<item>CCCC</item>
</Record>
</Root>
Is it possible?

Resolved

Doubts in JMS Sender adapter configuration (SonicMQ JMS Provider)

Hi All,
I am doing a TIBCO--> XI integration using JMS sender adapter. Adapter status is as follows..
<b>"Sender channel. Details: (No detail information set.)"</b>.
XML Msg in TIBCO-ems queue which JMS adapter access is as follows.....
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Studdetails xmlns:ns0="http://abc.com/xi101/XSLTmap">
   <Records>
      <student_ID>
         <fname>abc</fname>
         <lname>efg</lname>
         <DOB>11/09/1980</DOB>
         <marks>
            <science>90</science>
            <maths>78</maths>
            <lang>80</lang>
         </marks>
      </student_ID>
   </Records>
</ns0:MT_Studdetails>
<u>My Queries...</u>
what will be the Msg selector entry for my JMS sender Adapter? Is it MT_Studdetails???
My sender adapter is green in RWB Adapter Monitor, but I am not able see my msg in SXMB_MONI. why it is so??
regards,
Raks

Hi,
Did you follow the how-to guide available at SAP Marketplace to deploy the JMS Adapter. If so, i believe the information given in that guide is incomplete.
Once you have installed the JMS Driver, you must deploy the Java libraries on the J2EE server so that the JMS adapter can access the required Java classes at runtime.
If you use MQSeries 53x.xxx, you must enter the following JAR files in aii_af_jmsproviderlib.sda.
com.ibm.mq.jar
com.ibm.mqbind.jar
com.ibm.mqjms.jar
connector.jar (use the JAR file from the J2EE client directory)
and if ur question is, "Where do I get the Java Library from "
The required Java libraries are product-specific and can be obtained from either the product vendor or other providers.
And i guess the 4 jar files should be enough. Just remember to add these 4 jar files to 'provider.xml' file inbetween the <jars>..</jars> tag.
Follow the instructions as per the guide,
https://websmp205.sap-ag.de/~sapdownload/011000358700003994312004E/HowTo_ConfigExtAdapters.pdf
But just remember to have all the 4 jar files in aii_af_jmsproviderlib.sda
Regards,
Abhy

Doubt in JMS to proxy scenario

Hi All,
I have a scenario, in which i need to send data from Tibco system to SAP ECC , where i am using JMS adaptor and proxies. For this do i need to create 2 diffrent datatypes, Message types or just i can create 1 datatype and 1 messge type and then create 2 different inbound and outbound? Please let me know. Thanks.
Regards,
Kalpana

Hey kalpana
why do you want to create just 1 data and message type?
is there any reason for that,usually we have to create data type and message type for JMS as well as for proxies.
are u confusing wid proxy?proxies replace adapters,they have nothing to do with data or message type.
is the structure of both sender and receiver exactly the same in ur case?
thanx
ahmad
Message was edited by:
Ahmad

Doubt in JMS Sender Channel

Dear Experts,
I have some queries and an issue also..
First Query : is the JMS sender channel is polling the message from JMS Queue or when ever the channel is connected to the JMS queue then the messages are pushed from JMS ? Simply I want to understand the then message is Puss or Pull. (my understanding is messages are pulled when ever the channel opens the session with JMS provider)
Second Query : is there any provision that the sender channel will have the log When the JMS Queue is empty ??
Issue : we are using WebSphereMQ JMS Provider, with QoS is EO . MQ claims that the messages are missing when the message were sent to PI.
is there any way to trace the issue ? any clue ?
-Danny

Thanks for your help on this.. but please excuse me for asking more layman query..
There no other JMS Client is connected with that Queue. and I am sure the messages are
So you say, only some message are missing, but the most message run correctly? Yes Most of the messages run correctly
Are you sure, that the messages were sent to the queue correctly? Since only the PI channel is connected the message should be forwarded to PI correctly.
Do you have a log for the MS queue? I think there should be mentioned, which KMS client has received the message. --> I don't have the log of MQ side.. But I can request them..
can you please provide the info "what I can ask them the MQ Team?" if I ask them about the "the JMS client details of the message" will it give the information of where that message has been sent.
Thanks for your help
Edited by: Dhanabal Thangavel on Sep 20, 2011 1:21 PM

Message lost during Message Send in weblogic 9.2 JMS

I am using Weblogic Server 9.2 in a clustered environment (2 nodes in separate machines). The application deployed has ejb timers which picks up data from DB, and sends text messages (very small size as its just an ID) to a Queue (using the JMS APIs - QueueSender.send(message)). There is an MDB (with max-beans-in-free-pool) configured to be 20 listenting to this message. There might be 1-20 records picked up from the DB and the id of those records will be sent to the JMS Queue as separate JMS messages. i.e. QueueSender.send will be called as many times as there are record ids to send. The timer after sending the message to the queue sets the status of all the data it picked up to "Busy" in the same transaction as the message send. We are using XA driver and the JMS Connection factory is also XA enabled. We had problems with this XA transaction as weblogic sometimes sends the messages and before db commit happened to set the status to "Busy". We had a workaround to this problem by setting the JMS Connection factory setting "time to Deliver" to 300 so that the messages are visible to the MDB only after 300 ms thereby giving time for db commit to be over as per the suggestion in the following link. http://jayesh-patel.blogspot.com/. We had done this 2 months back and to date we find no problem.
Now we are facing another strange problem. The JMS sometime misses delivering the messages. This is evident from the logs we had printed from the MDB. The logs indicate some messages has reached the MDB and some did not. This problem occurs occasionally. Also what I see is that this had occured under normal load conditions only though this application operates under high loads (number of messages being processed per day may go up to 5000). In the last one month this had occured 3 times. The JMS messaging is becoming unreliable.
This seems to be a bug in Weblogic 9.2 JMS. Is there any workaround to prevent this problem. ?

It is doubtful that JMS is losing messages. Suggestions:
* Try increasing your sheduled message delay. 300 millis is a short delay -- any small network glitch, disk hardware issue, or even a single JVM GC in the JDBC driver can cause the database to take longer than 300 millis to complete its part of the transaction.
* Try "WebLogic JMS Message Lifecycle Logging" if you want to trace message activity.
* Instead of the delay, consider using WebLogic's Datasource "LLR" option, a commonly used solution to your use case. This is an optimization option that yields fully ACID (safe) transactions, and has the very nice side effect of deterministically forcing the TM to always commit the database portion of a transaction before committing any other resources participating in the same transaction.
Links:
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jms_admin/troubleshoot.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jta/llr.html#LLRfailover
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jdbc_admin/jdbc_datasources.html#llr
Tom
Edited by: TomB on May 7, 2010 5:20 PM

JMS adpater

Dear Expertise,
I have some doubts in JMS Adpater.
1. IS JMS adapter in XI is JMS client?
2. If JMS adaper CC is in sender mode, will XI pull the data(queues) from JMS server or JMS server will send the data to XI.
For IDOC to JMS scenario, what are the steps need to be done in repository framework.
My question is how to send that IDOC data to JMS server. For this, is any message mapping and interface determination required, as I want to send the same IDOC data to JMS server queue.
Advaced Thanks,
Gujjeti

Praveen,
To work on JMS adapter first you need to install the drivers. Check this document on how to install the drivers:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
Once when you do this it is just like your normal scenario. Check this weblog for some help on how to configure your receiver JMS adapter:
/people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
Also check this for some info. on JMS adapter:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
---Satish

JMS Client

Hi All,
I have a doubt in JMS. In JMS document, it is specified that JMS(instead of RMI) can be useful in the case of server lies behind the firewall/NAT .
Is it correct?
If So,How it solves the problem. Because in the weblogic jms thin client documentation, it is specified that JMS uses internally RMI. In the case of JBOSS,JNDI is implemented using RMI. How JMS avoids the firewall/NAT issues?
After some R&D, I came to know that JMS is not the replacement for RMI.It can be considered as top layer over RMI. If so, how (can i exactly use) JMS solves this firewall/Nat issue..
Thanks in advance
Maruthi

assuming you are trying to lookup a JMS destination/connection factory
through JNDI,
If you are running the client as a Application Client in application client
container of Sun ONE application server, please see Sun ONE application
server documentation or post question to that forum. If you are running
the client "standalone", please see MQ Administration Guide on how to
setup MQ administered objects using file-based or LDAP store.

Leave message on queue

Hi everyone, I have a doubt about JMS...
The onMessage() method removes incoming messages from the queue or leaves it in the queue??
In case the message is removed, if I want to keep the message in the queue (it fulfills a condition) I have to re-enqueue the message?? (this behavior won't cause a infinite loop, or at least while messages fulfills the condition)??
Any help is appreciatted...

if you are using transacted delivery (i think this is usually the default), then throwing a runtime exception will cause the transaction to be rolled back and the message will be redelivered. obviously, as you mentioned, explicitly requeuing is always an option. lastly, if this is a constant condition, you could possibly use a message filter on you subscription to avoid seeing messages you don't care about.

Doubt in Flat File Format in sender jms queue?

Hi All,
I have a JMS-IDOC scenario with Content Conversion. The input file can have fixed length, multiple records.
Each record comes in a newline.
But , heard, one cannot place a multiline data as a single message in the JMS Queue.
Each new line of the data will be placed as a single separate message.
so for every line , a new xml message gets created and the scenario gets triggered.
But I want the all records (lines) in a single xml message
Could someone tell me what is to be done?

> But , heard, one cannot place a multiline data as a single message in the JMS Queue.
That is wrong. You can put anything in the JMS queue, even binary.
Regards
Stefan

Doubt in WLS 7.0 JMS Cluster Failover

I configured 2 JMS servers JMS1 and JMS2. I also configured 2 JMS file stores FS1 and FS2. JMS server JMS1 using FS1 and JMS2 using FS2. I also configured 1 distributed queue DQ for the cluster server. I also configured 1 local queue LQ1 in JMS1 and 1 local queue LQ2 in JMS2.
          When the JMS2 server failed, I migrate it to the migratable target JMS1. The file store FS2 and all transaction log files have been copied to the JMS1 server with the same path. I first migrated JTA service and then JMS service. The migration procedure worked and no problem. But the messages in the JMS2 did not get processed by the migratable target JMS1.
          What was wrong in my configuration? In my migration procedure? Or in my file store? Or anything? I knew I should use shared disk storage for file store. I just want to simulate the problem and try cluster failover.


          Chan Tong wrote:
          > Tom Barnes <[email protected]> wrote:
          >
          >>
          >>Chan Tong wrote:
          >>
          >>>I configured 2 JMS servers JMS1 and JMS2. I also configured 2 JMS file
          >>
          >>stores FS1 and FS2. JMS server JMS1 using FS1 and JMS2 using FS2. I
          >>also configured 1 distributed queue DQ for the cluster server. I also
          >>configured 1 local queue LQ1 in JMS1 and 1 local queue LQ2 in JMS2.
          >>
          >>>When the JMS2 server failed, I migrate it to the migratable target
          >>
          >>JMS1. The file store FS2 and all transaction log files have been copied
          >>
          >>
          >>>to the JMS1 server with the same path. I first migrated JTA service
          >>
          >>and then JMS service. The migration procedure worked and no problem.
          >>
          >>>But the messages in the JMS2 did not get processed by the migratable
          >>
          >>target JMS1.
          >>
          >>>What was wrong in my configuration? In my migration procedure? Or in
          >>
          >>my file store? Or anything? I knew I should use shared disk storage
          >>for file store. I just want to simulate the problem and try cluster
          >>failover.
          >>
          >>Need more information. What do you mean by "the messages in the JMS2
          >>
          >>did not get processed"? Do JMS2's message counts
          >>show up in console monitoring?
          >>
          >
          > After migrate JMS2 to JMS1, the messages in the JMS2 file store were not processed
          > by the JMS1. Could it be I manual copied the file store? Or I will need to use
          > shared file store that can be access from from both servers?
          Either way yes. The migrated JMS server still needs to be able to
          find its store. Another way to do this is to use a JDBC store - as
          long as the remote database is highly available and your
          applications can tolerate the likely JMS performance reduction.

Doubt on using DB as JMS resource provider

Hi
I am trying to use Oracle DB as JMS resource provider. I am trying to create required tables like following.
connect as sysdba/pwd
CREATE USER TUSER IDENTIFIED BY tiger
GRANT CONNECT, RESOURCE,AQ_ADMINISTRATOR_ROLE TO TUSER
GRANT EXECUTE ON SYS.DBMS_AQ TO TUSER // Hanging
In line 3 it never completes. Looks like some lock is there on that table, But I am not able to understand what lock.
Can anybody explain me what could be wrong. (I am not DBA. Just trying to learn JMS using DB as resource provider. I am using the DB which comes with Infra)
Thanks
Ratheesh

Which database version is this? The hang is likely caused by a lock held on the dbms_aq package. For example, when a session is blocked inside dbms_aq package wating for messages to be delivered, it is not possble to grant/revoke execute permissions on that package to a different db user.
You could try bouncing the db to see if you still see the hang.
Hope this helps,
-Frances

JMS server affinity doubt

          Hi,
          I have two weblogic instances in the cluster and have configured two JMS servers
          one for each instances. Have created a connection factory with server affinity
          enabled. Now if some messages are submitted from server A, does server affinity
          ensures that all messages are processed by jms server A for sure? Even in case
          of JMS server B is idle?
          Any pointer for more info about this is appreciated.
          Thanks,


          Yes It is true. I have tested it.
          "Kiran Kumar" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have two weblogic instances in the cluster and have configured two
          >JMS servers
          >one for each instances. Have created a connection factory with server
          >affinity
          >enabled. Now if some messages are submitted from server A, does server
          >affinity
          >ensures that all messages are processed by jms server A for sure? Even
          >in case
          >of JMS server B is idle?
          >
          >Any pointer for more info about this is appreciated.
          >
          >Thanks,

Problem to send a message with JMS

Hi
I'm doing some tests with the api JMS to know how works. I have got some problems. I have been looking for some information but i don't find so much. I have got too doubts.
I am usinng Netbeans 5.5 with Sun Java System Application Server Platform Edition 9.0_01 (build b14).
I am trying to do it with ejb. Because in the future the application can have got so many connection in the same time.
The server shows me the next errors.
Starting Sun Java System Application Server Platform Edition 9.0_01 (build b14) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_03] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
DPL5400:Exception occurred : error in opening zip file.
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://t1:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
JTS5014: Recoverable JTS instance, serverId = [3700]
About to load the system app: MEjbApp
LDR5010: All ejb(s) of [MEjbApp] loaded successfully!
About to load the system app: __ejb_container_timer_app
EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]
LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
        at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
        at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
        at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
        at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
        at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
        at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
        at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
        at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:198)
        at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
        at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
        at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
        at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
        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:597)
        at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
        ... 17 more
CORE5021: Application NOT loaded: [Chat-ejb]
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
WEB0100: Loading web module [amserver] in virtual server [server] at [/amserver]
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
Using MQ RA for Broker lifecycle control
JMS Service Connection URL is :mq://t1:7676/
MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}
[07/nov/2007:18:35:03 CET]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.6.0_03 Sun Microsystems Inc. D:\sun\Java\jdk1.6.0_03\jre
[07/nov/2007:18:35:03 CET]    IMQ_HOME=D:\sun\AppServer\imq
[07/nov/2007:18:35:03 CET] IMQ_VARHOME=D:\sun\AppServer\domains\domain1\imq
[07/nov/2007:18:35:03 CET] Windows XP 5.1 x86 t1 (1 cpu) pepepc
[07/nov/2007:18:35:03 CET] Java Heap Size: max=506816k, current=46944k
[07/nov/2007:18:35:03 CET] Arguments: -port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686
[07/nov/2007:18:35:04 CET] [B1060]: Loading persistent data...
[07/nov/2007:18:35:04 CET] Using built-in file-based persistent store: D:\sun\AppServer\domains\domain1\imq\instances\imqbroker\
[07/nov/2007:18:35:04 CET] [B1189]: Cluster Service feature is not available
[07/nov/2007:18:35:04 CET] [B1039]: Broker "imqbroker@t1:7676" ready.
MQJMSRA_EB1101: run:EMBEDDED broker started with code =0
MQJMSRA_RA1101: SJSMQ JMS ResourceAdaapter configuration=
        raUID                               =null
        brokerType                          =EMBEDDED
        brokerInstanceName                  =imqbroker
        brokerBindAddress                   =null
        brokerPort                          =7676
        brokerHomeDir                       =D:\Sun\AppServer\imq\bin\..
        brokerVarDir                        =D:/sun/AppServer/domains/domain1\imq
        brokerJavaDir                       =D:/sun/Java/jdk1.6.0_03
        brokerArgs                          =null
        brokerStartTimeout                  =60000
        adminUsername                       =admin
        adminPassFile                       =E:\tempWin\asmq21980.tmp
        useJNDIRmiServiceURL                =true
        rmiRegistryPort                     =8686
        startRmiRegistry                    =false
        useSSLJMXConnector                  =true
        brokerEnableHA                      =false
        clusterId                           =null
        brokerId                            =null
        jmxServiceURL                       =null
        dbType                              =null
        dbProps                             ={}
        dsProps                             ={}
        ConnectionURL                       =
        UserName                            =guest
        ReconnectEnabled                    =true
        ReconnectInterval                   =5000
        ReconnectAttempts                   =3
        AddressListBehavior                 =RANDOM
        AddressListIterations               =3
        InAppClientContainer                =false
        InClusteredContainer                =false
        GroupName                           =null
MQJMSRA_RA1101: start:SJSMQ JMSRA Connection Factory Config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverrideJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=true, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imqJMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http://localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefaultPassword=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=guest, imqReconnectEnabled=false, imqConnectionFlowCount=100, imqAddressListBehavior=PRIORITY, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimestamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueueBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddressList=localhost:7676, imqOverrideJMSHeadersToTemporaryDestinations=false}
MQJMSRA_RA1101: SJSMQ JMSRA Started
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat moduleName=Chat-ejb_jar ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
        at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
        at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
        at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
        at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
        at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
        at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:184)
        at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:113)
        at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
        at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:204)
        at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
        at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
        at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
        at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
        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:597)
        at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
        ... 18 more
Registering ad hoc servlet: WebPathPath: context root = "/Chat", path = "/Chat-app-client'
Java Web Start services started for application com.sun.enterprise.appclient.jws.ApplicationContentOrigin@aabc2d registration name=Chat
    [email protected]56b4 registration name=Chat, context root=/Chat/Chat-app-client, module name=
, parent=Chat
CORE5021: Application NOT loaded: [Chat]
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
JBISE6013: JavaEEServiceEngine : Java EE Service Engine started successfully.
CORE5024: EJB module [Chat-ejb] unloaded successfully!
DeployedItemRef postDeregistration failed. Load Balancer Monitoring MBeans might be lying around if this application is being load balanced
BPEL service engine started
ADM1064:The upload file at [E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar] exists and will be overwritten.
ADM1006:Uploading the file to:[E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar]
deployed with moduleid = Chat-ejb
ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable ejb/Chat-ejb]
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=D__sun_AppServer_domains_domain1_applications_j2ee-modules_Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
        at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
        at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
        at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
        at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
        at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
        at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
        at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:219)
        at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:174)
        at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:406)
        at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleEnabled(StandAloneEJBModulesManager.java:500)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:960)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:941)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:448)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
        at com.sun.enterprise.admin.server.core.AdminNotificationHelper.sendNotification(AdminNotificationHelper.java:128)
        at com.sun.enterprise.admin.server.core.ConfigInterceptor.postInvoke(ConfigInterceptor.java:109)
        at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:97)
        at $Proxy1.invoke(Unknown Source)
        at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
        at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56)
        at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
        at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
        at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
        at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.naming.NameNotFoundException
        at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
        at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
        at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
        ... 54 more
CORE5020: Error while loading ejb module
{code}
I know it is very large. I think the error it is in this line.
{code}
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
{code}
also I am going to put the code.
file PublicarBean.java
{code}
package org.pepes;
import com.sun.tools.ws.processor.model.java.JavaArrayType;
import javax.annotation.Resource;
import javax.ejb.SessionContext;
import javax.ejb.Stateless;
import javax.jms.ConnectionFactory;
import javax.jms.QueueConnectionFactory;
import javax.jms.Topic;
import javax.naming.NamingException;
* @author pepes
@Stateless(mappedName="ejb/publicar")
public class publicarBean implements org.pepes.publicarRemote {
    /** Creates a new instance of publicarBean */
    @Resource(name="jms/QueueConnectionFactory")
    private QueueConnectionFactory connectionFactory;
    @Resource(name="jms/Topic", mappedName="jndi/Topic")
    private Topic topic;
    private javax.naming.InitialContext ctx;
    public publicarBean() {
    public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException {
        try {
            javax.naming.InitialContext ctx = new javax.naming.InitialContext();
            this.connectionFactory = (javax.jms.QueueConnectionFactory)ctx.lookup("jms/QueueConnectionFactory");
            this.topic = (javax.jms.Topic)ctx.lookup("jms/Topic");
            javax.jms.Connection connection = this.connectionFactory.createConnection();
            javax.jms.TopicSession ts = (javax.jms.TopicSession)connection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
            javax.jms.TopicPublisher tp = ts.createPublisher(this.topic);
            javax.jms.TextMessage msg = ts.createTextMessage();
            for (int i = 0; i<3;i++) {
                msg.setText("Prueba: " + i);
                tp.publish(msg);
        catch (javax.jms.JMSException jmex) {
            throw jmex;
{code}
the file publicarRemote.java
{code}
package org.pepes;
import javax.ejb.Remote;
* This is the business interface for publicar enterprise bean.
@Remote
public interface publicarRemote {
     public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException;
{code}
file mensaje.java
{code}
package org.pepes;
import javax.annotation.Resource;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.jms.MessageListener;
* Entity class Mensaje
* @author pepes
@MessageDriven(mappedName = "jms/Mensaje", activationConfig = {
        @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class Mensaje implements MessageListener {
    /** Creates a new instance of Mensaje */
    @Resource
    private MessageDrivenContext mdc;
    public Mensaje() {
    public void onMessage(Message message) {
        javax.jms.TextMessage msg = null;
        try {
            if (message instanceof javax.jms.TextMessage) {
                msg = (javax.jms.TextMessage) message;
                System.out.println(msg.getText());
            } else {
                System.out.println("Message of wrong type: "
                        + message.getClass().getName());
        } catch (javax.jms.JMSException e) {
            e.printStackTrace();
            mdc.setRollbackOnly();
        } catch (Throwable te) {
            te.printStackTrace();
{code}
the file prueba.jsp
{code}
<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%--
The taglib directive below imports the JSTL library. If you uncomment it,
you must also add the JSTL library to the project. The Add Library... action
on Libraries node in Projects view can be used to add the JSTL 1.1 library.
--%>
<%--
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
--%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd">
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>JSP Page</title>
    </head>
    <body>
    <h1>JSP Page</h1>
    <%--
    This example uses JSTL, uncomment the taglib directive above.
    To test, display the page like this: index.jsp?sayHello=true&name=Murphy
    --%>
    <%--
    <c:if test="${param.sayHello}">
        
        Hello ${param.name}!
    </c:if>
    --%>
    <%
        try {
        javax.naming.InitialContext ctx = new javax.naming.InitialContext();
        org.pepes.publicarRemote publisher = (org.pepes.publicarRemote)ctx.lookup("ejb/publicar");
        if (publisher==null) {
            System.out.println("INFO: Es null");
        else {
            System.out.println("INFO: No es null");
        publisher.creaMensaje();
        } catch (javax.naming.NamingException ex) {
            System.out.println("ERROR naming: " + ex.getMessage());
        catch (javax.jms.JMSException jmex) {
            System.out.println("ERROR jms: " + jmex.getMessage());
        catch (java.lang.NullPointerException nullex) {
            System.out.println("ERROR null: " + nullex.getMessage());
%>
    </body>
</html>
{code}
I think the problem is because i don't put destination address. if it is so, the true where do I put this address?. if not where is the problem?
I hope your help.
Thanks you in advanced.

Hi,
Did you create your destinations in your application server? It seems that the destinations such as topics and queues are not created. First you should create them and then start using them.
For example, in here, it says that jndi/Topic is not valid. To check if the destinations are valid or not; you can do it either through the graphical user interface or the command line console.

Some doubts in FI-SL?

hello friends,
I have doubts in fi-sl,
there are two tables, summary table and ledger.
why we activate summary table first?
in ledger selection,why so mnay ledgers la,lb,lc like that is there.
for every single ledger means bank take example ,
shall we have to assign to every single ledger there la or lb or lc.
plz let me know the process wiht one scenarion.
srinu

Hi,
1) a) A Web Server understands and supports only HTTP protocol whereas an Application Server supports HTTP,TCP/IP and many more protocols.
b) Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object.
c) Webserver is used only for jsp and servlets and for static functionality it has limited functionality and it doesn't provide any security ,persistence and it doesn't support EJB and JMS and JAAS like other functionality
whereas Application server provide all functionalities.
In short, Applicaion Server is a super set of which Web Server is a sub set.
2) Two-tier architecture is a client/server architecture , where a request to do some task is sent to the server and the server responds by performing the task.where as a three-tier or a multi tier architecture has client, server and database. Where the client request is sent to the server and the server in turn sends the request to the database. The database sends back the information/data required to the server which inturn sends it to the client.

Doubt in jms

Similar Messages

Maybe you are looking for