SP15, JMS Sender, "Messages not fetched"

JMS Sender Communication Channel, Transport Protocol "Access JMS Provider with JNDI" and Name of JNDI initial ContextFactory "com.sonicsw.jndi.mfcontext.MFContextFactory".
Error in Adapter Monitor "Sender channel. Details: Last Exception during send at Sat Mar 11 07:55:45 EET 2006: Value with name enableDynConfigSender not available."
There is messages in SonicQ Queue but they are not fetched by XI. I've start/stop SAP XI Adapter: JMS, no help.
What does that error actually mean and what should I check next?

Hi Tapio,
If you are on SP14, SAP has introduced 'dynamic headers' with this support Pack. Your problem may be related to this. See the related section in SAP Note#856346 (JMS Adapter - FAQ)
To fix your problem try deactivating your sender communication channel, make a small change to your description and activate it again. Test your scenario to see if it works.
Hope this helps.
Regards,
Sam Raju

Similar Messages

JDBC Sender Adapter - NOT FETCHING RECORDS...

Hello Experts,
I know this was answered in a separate thread (JDBC Sender Adapter - NOT FETCHING RECORDS -PROCESSING STARTED).
However, my question is, Is there a way that we can be notified if a channel has stopped fetching records?
or is there a reporting tool that can be used to check/monitor if a channel is not processing any messages?
Thanks & Kregards,
allar

Hi Sreedhar,
Thanks for your reply.
These case is not being captured by our alert configuration because its not throwing any error.
in the communication channel monitoring, we see only something like this..:
3/16/09 8:25:19 PM Processing started
3/16/09 8:34:20 PM Processing started
3/16/09 8:33:55 PM Processing started
3/16/09 8:32:54 PM Processing started
but no error is being displayed nor sent.
Also, there was a case that the channel just stopped fetching, even though everything is active.
example log:
3/12/09 8:32:54 PM Processing started
We're looking for ways on how we can trap these scenarios as early as possible, get us notified and perform adapter-lock release when needed.
Regards,
allar

JMS-send operation not working in a SessionBean [OC4J10.1.3.1.0-standalone]

Salut,
i am envisaged with a nasty problem calling a message-send operation from
a method (transaction-type="required") inside a session bean (transaction-type="container").
This problem occured in OC4J 10.1.3.1 and may fail also in 10.1.3.0. The same
code run under OC4J 10.1.2.x without any problems.
The adressed JMS type is a OEMS JMS and fails to work regardless if the JMS ressource
is using a file-persistence or is running in-memory. Anyway the factory is a
jms/XAQueueConnectionFactory, so the created queue must support XA transactions.
Another test with an advanced-queue JMS provider succeeded.
As a consequence of this, i believe that the OEMS provider shall cause the problem.
The original code is quite unspectaculary:
* The non-surprising thing is, that the QueueConnectionFactory
* is a XAQueueConnectionFactory.
QueueConnectionFactory qcf = (QueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
c = qcf.createQueueConnection() ;
QueueSession s = c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
[... create a message ]
QueueSender qs = s.createSender(q)
qs.send(m);
qs.close()
s.close();
c.close()
The funny thing is, that the queue-session behaves as it is working outside
of a transaction context. Inside the JMX-Console you will notice the
arrival of a message and ... a cancellation of it. This would not surprise
me, if this code sequence would have been called outside of
a Session bean, cause the absence of a queue-session.commit does not
fix the send message in the jms ressource.
As a matter of fact the code is executed inside a Session bean and
the connection.createQueueSession will notice this and forget both
given parameters, and let the covering transaction take over of the
JMS ressource. But this does not happen (completly).
The acknowledge-mode has been modified (SESSION_TRANSACTED)
but the code still does not work!
After i recognized that the enlist-ment did not work, i
decided to enfore the use of XA transaction by using the
XA classes and methods of JMS.
I startet to cast the jndi-references and:
XAQueueConnectionFactory qcf = (XAQueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
XAQueueConnection c = qcf.createXAQueueConnection() ;
XAQueueSession s = c.createXAQueueSession();
[... create a message ]
QueueSender qs = s.createSender(q)
qs.send(m);
qs.close()
s.close();
c.close()
The funny thing is ... the code worked without any problem until
the send operation, where i received an JMSException, containing
the text:
Oc4jJMS.Session.hpcl057.4e9c06e4:1112674930d:-7fff.41,true,SESSION_TRANSACTED]: An attempt was made to perform work in a XA-backed session without being enlisted. Either the session must be enlisted (using the JMS Connector or JMS Adapter) to participate in the global transaction, or a non-XA connection and a non-XA session should be used to not participate in the global transaction.
How bizarre, i thought the enlistment has been taken place by invoking
the c.createXAQueueSession or c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
How bizarre how bizarre
any clues ????

OC4J JMS was changed to not auto-enlist in XA transactions.
In releases prior to 10.1.3 XA usage was not actually supported. (It did not meet all of the XA requirements when used with OC4J.)
Auto-enlisting by the JMS provider was also a spec violation, which was causing trouble for people who needed to do out-of-transaction work and had no way to do it.
In 10.1.3 XA usage is fully supported, but only when you use the JMS Connector. You can find the JMS Connector ("Oracle's Generic JMS Resource Adapter") demos here:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
The JMS Connector is documented in the OC4J Services Guide, OEMS/JMS chapter.
-Jeff

JDBC Sender Adapter - NOT FETCHING RECORDS -PROCESSING STARTED

Hello all,
I have set up a JDBC sender adapter .With polling interval as 30 Seconds. Polling is done successfully
but it does not fetch the records .
Valid Data is present in the tables.In the Communication Channel Monitoring log shows :
"Processing Started"
after each poll interval.
Adding to this , it was working fine with the same parameters two days back.
I have enabled the Driver Trace but didnot get any information from Trace.
How to resolve this issue?Any help
Regards
Ganga Prasad

Hello maheshwari,
Valid Data is there & many records are there to be fetched.
One more thing Normally in the Communication Channel Monitoring
for an JDBC adapter even if there are no records to fetch we get the Log information in detail that :
Polling interval started.
Processing finished successfully
Processing started
Polling interval started.
Processing finished successfully
Processing started
But here in my case am getting only : (polling interval : is 60 Seconds)
        2/5/08 8:29:19 AM           Processing started
     2/5/08 8:28:19 AM           Processing started
     2/4/08 3:34:54 PM           Processing started
     2/4/08 3:33:54 PM           Processing started
One more observation is that my poll interval is 60 seconds but now it is polling after every 120sec
       2/5/08 11:17:31 AM           Processing started
     2/5/08 11:15:31 AM           Processing started
     2/5/08 11:13:31 AM           Processing started
     2/5/08 11:11:31 AM           Processing started
I have tried refreshing Cache but no change .
Regards
Prasad

JMS send message

Hello,
in my message bean i have method with 3 BigDecimal parameters.
How can i send message from client with 3 BigDecimal parameters?
thanks for help.

No, but you can. use an object stream to serialize the message and you are
          all set.
          _sjz.
          "deezh" <[email protected]> wrote in message
          news:3d23fdbf$[email protected]..
          >
          >

Sending message not working anymore in WL 12 (InvalidDestinationException)

Hello,
after installing a fresh WebLogic 12 sending JMS messages from a WebService doesn't work anymore. Although I'm using only WebLogic JMS stuff (no foreign providers) I receive the following exception upon messageProducer creation:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, SystemModule-MyApp!Queue-MyApp
     at weblogic.jms.common.Destination.checkDestinationType(Destination.java:105)
     at weblogic.jms.client.JMSSession.setupJMSProducer(JMSSession.java:2830)
     at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2858)
     at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2822)
     at weblogic.jms.client.WLSessionImpl.createProducer(WLSessionImpl.java:827)
at the following code
connection = connectionFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
messageProducer = session.createProducer(queue);
At first I thought that there's some config mess which might have happened during JMS ConnectionFactory and Queue creation etc. in WL_Server. But after cross-checking it I've even compared the complete JMS-relevant WL-setup (in the /console) with another WebLogic 11 instance where the stuff is working and found no differences: The only destination used is a regular resource of type "Queue" at the SystemModule and not of type "Foreign Server". So I wonder why I receive a foreign destination exception when no foreign JMS stuff is used...
Do you have any ideas or tips where to investigate further? The only difference is that the codebase tested with WebLogic 12 uses CDI (coming with JavaEE 6) and the WebLogic 11 doesn't use CDI. In case this info is needed: the code trying to send the message to the queue is a simple @WebService.
Thanks in advance.

Thanks for your reply Dongbo!
The point regarding the classname of the Queue object was quite good! Its a org.jboss.weldx.jms.Destination$Queue$1555984123$Proxy$_$$_Weld$Proxy$ class. So this looks to me as if WebLogic uses JBoss Weld internally (for CDI) ??
The CDI-based injection of the Queue object from the JNDI is
@Produces
@MyAppTest
@Resource(name="jms/Queue-MyApp", type=Queue.class)
private Queue queue;
An the JNDI view of jms/Queue-MyApp shows
Binding Name:     jms.Queue-MyApp
Class:     weblogic.jms.common.DestinationImpl
toString Results:     SystemModule-MyApp!Queue-MyApp
Attached the complete stack trace:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, SystemModule-MyApp!Queue-MyApp
     at weblogic.jms.common.Destination.checkDestinationType(Destination.java:105)
     at weblogic.jms.client.JMSSession.setupJMSProducer(JMSSession.java:2830)
     at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2858)
     at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2822)
     at weblogic.jms.client.WLSessionImpl.createProducer(WLSessionImpl.java:827)
     at com.example.myapp.Demo(DemoServiceImpl.java:47)
     at com.example.myapp.Demo(DemoServiceImpl.java:82)
     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 weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
     at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:149)
     at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:95)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:892)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:841)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:804)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:706)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:430)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:640)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:265)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:163)
     at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:171)
     at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
     at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
     at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:336)
     at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:99)
     at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:242)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:216)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:132)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:352)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
     at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3288)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
     at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2163)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2089)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1512)
     at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

JMS Sender Channel not Polling

Hi Guys,
Scenario: BEA Weblogic -
> JMS Queue -
> Sender Channel JMS -
> SAP XI -
> SAP R3
We had initially setup this scenario using MessageSelector because the provider JMS Queue had mutiple message types on it. As Murphy's law would have it, the MessageSelector stopped polling the day before go-live. Basically, if we pointed one JMS SC to the provider JMS Queue using MessageSelector it worked fine, if we pointed multiple JMS SC's no messages were being picked up from the queue. We still haven't identified why the MessageSelector functionality stopped working but as a quick work around to MessageSelector before go-live we used blog:
[/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface|/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface]
Now we have a situation where, BEA Weblogic manages the provider JMS Queue & they perform a health check 4 times a day & if they encounter a problem they bounce the server & JMS Queue service. XI and the SC seem to re-connect fine most of the time when Weblogic & JMS Queue is back up but there are times when I see a green light in RWB for the SC but it's not polling for messages on the JMS Queue. We use Hermes JMS to monitor messages on the Queue to check if there are in fact messages to be picked up & the messages are queued.
What I'm looking for is a best practice guide for how to manage this. I don't want to keep toggling between Hermes JMS & RWB to verify if the SC is in fact polling messages altho' it shows as green in RWB. Please advise. Thanks.
Regards, Trevor

Thanks Kai & Joel.
Joel, I'm not really looking to add another layer with the JMS Connector Service. For me it's just adds another possible point of failure. At the moment the message passes thru 5 systems including SAP R3 & end system & then the response comes back the same route.
Going out from SAP, the Receiver channel to the JMS queue seems to work fine. With the responses coming back, the Sender Channel seems to re-connect ok (I'm assuming) otherwise it wouldn't be green in RWB but doesn't pick up any messages. It's also an intermittant phenomenon. Manually stopping & re-starting the Sender Comm Channel fixes the problem but we won't know if there's a problem until we check if messages are being picked up from the queue.
Kai's notes led me to some things I could possibly look at like additional parameter in JMS channel config, CONNECTION_TEST_POLL (note 948016). I'm still not sure how we can make this work for us because we essentially need to bounce the JMS channel so it starts polling again in the event of a JMS Queue Provider bounce but I need to first establish that the JMS Queue was bounced.
Note 1088675 will also be irrelevant cos the channel looks like it re-connects, just doesn't poll.
Trevor

FTP Sender - Message not reaching XI

Hi,
I am using FTP sender adapter to send an XML file to XI.
The file is being picked up by XI properly from the Source directory on the FTP server which is running on my local machine but it is not reaching the integration server. SXMB_MONI shows no message.
I have checked all the parameters in the communication channel and am sure that the fule is picked up. Alternatively, I am able to put a file on the FTP server. So the FTP server seems to be working fine.
If any of you have any idea of where the error could lie, could you please respond.
Kind Regards,
Dhananjay

Hi Dhananjay,
try setting the file adapter to Delete mode
this way you'll know if your file got picked from the FTP
if you're sure that is was picked then:
http://xiserver:port/MessagingSystem/monitor/monitor.jsp
here you'll find your message if it reached Adapter Framework (file/ftp adapter)
also remember to always check this address:
http://xiserver:port/mdt/amtServlet
Regards,
michal

JMS sender adapter not converting data to XML properly.

Hi,
I am using JMS adapter to read data from MQ. The length of each segment is fixed.
The problem is there is no new line character at the end of each segment .So JMS adapter is just reading the first line and not reading the rest.
What I found out that if I place a new line character at the end of each segment it works fine. But for me I have constraint that in MQ the source system cannot send a new line character at the end of each segment. So can any one tell me how can I solve this issue?
The sample data that I am getting from MQ is:
AA12345
BBXYZXY CC12300
CC456AS
We are using SP13.
The length of each segment is fixed.
Any help is appreciated

Hi Sameer,
fieldFixedLengths is used to divide the data among the elements of a segment.
For example if I have the segment structure like
AA1234567
BB12345
BBXYZ12
Then in the module processor we define
xml.recordsetStructure NameA,1,NameB,*
xml.NameA.fieldNames MyKey,field-nameA
xml.NameA.fieldFixedLengths 2,7
xml.NameA.fieldNames MyKey,field-nameB
xml.NameB.fieldFixedLengths 2,5
As per my understanding goes First it reads the first line till it finds a new line char and then it uses fieldFixedLength to assign data to the fields inside the segments. Here in the above example A1=AA and A2=1234567
But I am not aware if we can use fieldFixedLength to identify the segment it self. If so then how can I use it can u let me know?
Thanks

Mavericks Messages problem sending message: "not registered with iMessage"

I'm on MacBook Air(MBA) and recently installed Mavericks. I try sending a message from MBA MESSAGES to a person's cell phone number (they have an android phone). Their name appears in red and I get: "...is not registered with iMessage." So I was trying to read discussions in here and allot of them say Messages won't work unless a person has an Apple device- iphone, Mac, etc. I want to know if that is true or if there is any other way to send from the MBA a message to them? I also tried from Messages on MBA to their gmail address, which they use on their android cell phone, and get same error.
Is there anyway a non-apple person can "register with iMessage" if they have an android phone?
I know I can email them, but I wanted a fast way for emergency purposes to get a MESSAGE to them from my MBA. Sometimes they can't talk on phone at some times, but are allowed to get instant message for emergency where they work.

Hi,
You have to have otr get an AIM or AIM valid name.
AIM stands for Aol Instant Messenger.
Apple IDs issued by Apple (Those ending in @mac.com or iCloud issued @me.com and @icloud.com) are valid as AIM Screen Names if the password is kept to 16 characters or less. (this is an AIM server limit)
Apple made an Agreement with AOL over the use of names over 10 years ago.
The Original .Mac ID (@mac.com) could be paid for or could be Trial Accounts.
Trial Accounts continued to work after the trial ran out. (i.e. the email stopped but the AIM Screen Name didn't).
The same was true of lapsed accounts.
When MobileMe started people could link, email-wise, their paid for .Mac accounts to the paid for MobileMe (@me.com) accounts.
Any @mac.com still works over the AIM service.
Now also @Me.com names worked - meaning some people had two valid AIM names - they are not liked for use with AIM just that the passwords will be the same.
With the end of MobileMe all those @me.com account died as far as AIM is concerned.
However you could link it to iCloud which effectively moved it to the iCloud server.
(i.e. they are iCloud issued @me.com ID instead of MobileMe ones)
Then Apple started to issue @icloud.com IDs
This could mean that some people have three working IDs for use with AIM (but all linked to one email Account at Apple).
NOTES
From Lion onwards (iChat 6 and Above) Apple have had the app also login in to Apple before it will allow the AIM Servers to "read" the password.
This applies to any iCloud issued ID - the "newer" iCloud linked @Me.com and @iCloud.com IDs
This means you cannot use those IDs in iChat 5 or earlier as those version only do an one point login only.
With the coming of iCloud other Apple IDs could be linked to iCloud which may have given you either @me.com and later an @iCloud.com ID as well or just an @icloud one if you were later to the party as it were.
Whilst in some cases this does give you two valid AIM Screen Name the originating Apple ID does not become one.
9:04 pm Saturday; February 8, 2014
 iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

JMS Queue Messages not picked up.

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

I saw in icloud sending message not encrypted?

Hi, how are you there, I found my icloud account is not crypted , it is normal ? Because it is the first time I found it in red!

Hi, how are you there, I found my icloud account is not crypted , it is normal ? Because it is the first time I found it in red!

JMS sender adapter is not picking up message from MQ

Hi Experts,
I have configured the JMS sender adapter for getting message from Websphere MQ. In RWB the adapter and the communicaiton channel all looking good. The trace file tells me the connection to the queue has been established.
But the problem is this JMS sender adapter is not picking up message from the Queue defined on the MQ site.
Any Idea what could be wrong?
Thanks!
Jason
Jason

Hi,
1) Can you activate the JMS adapter again ( edit save and activate it )
2) Check whether the right Queue is addressed.
Regards
Agasthuri Doss

Send message only if not alredy in jms

Hi
I have messages in my queue, before sending messages into the queue i want the client to test if the message already exist there and only then to send the messages. Is that possible?

Yes, use a QueueBrowser to browse, but not remove, items on the queue. You can apply a message selector if you want to only select certains items to browse, e.g.
Queue queue = ...
QueueSession session = ...
QueueBrowser browser = session.createBrowser(queue, "MyProperty = 'some value'");
Enumeration e = browser.getEnumeration();
// iterate over the enumeration if you need to check further message details,
// or simply find out if the enumeration has more elements if you're message
// selector is selective enough...See http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/QueueBrowser.html for more info.

PI 7.0 SP15 alerts JMS Duplicate message error

Hi all,
We have a scenario where in we receive BAPI calls to R/3 from web through MQ and XI.
WEB -> MQ->XI->R/3 (Request / Response send back similarly)
We have modular configuration in the channel.
All these BAPI messages are queries needed to build an order for example product information / customer information etc.
We have PI 7.0 SP15
Sometimes we receive the error ' Duplicate JMS message with JMS ID##### detected.Duplicate will be ignored' in the sender JMS channel.Because of this error XI is not able to process subsequent messages and the channel keeps on throwing the same error.We need to clear the queue and then restart the channel to make it work.
Can any one please tell me what is the reason for occurence of this error..?
Is this ID generated in JMS or in XI?If so how this could be handled without clearing the queue's..?
When we analyzed the messages in the queue we found out same xml messages been send twice which i would imagine the query been send twice(which is a possiblity from the web) would that have caused this JMS duplcate message error??!!
Also because of this error XI is throwing multiple alert messages at the rate of 3 per second which is causing the huge performance hit as the alert inbox gets filled up..We did put the suppress multiple alert check..but before somebody reacts to these alerts there are numerous of them created..any suggestions on this is much appreciated..
Thanks for your help in advance
Larry

Larry,
Is that alert rule is generic or interface specific? If it is generic then please make it interface specific.
Thanks,
Sunil

SP15, JMS Sender, "Messages not fetched"

Similar Messages

Maybe you are looking for