Message Queue in XI is stuck

Hi,
I am using Idoc adapter to implement an ECC-XI-ECC scenario.
My scenario works fine. But the problem is that the XI is throwing out messages to the target system (ECC) one by one.
It means that once an inbound message comes into XI, it pushes the message already in the XI queue to the receiver system and my existing inbound message just sits in the queue waiting to be pushed again.
Please tell me how to solve this problem.
I am sending a PO Idoc from sender to target.
Thanks & Regards,
Shobhit

Hi Ravikiran,
There was no problem. I got confused because the Incoming IDoc and outgoing IDoc numbers were different and I was under a wrong impression that they should be the same.
But I got to learn 2 new Tcodes from you. I was looking for that exactly. 10 points to you!!!
Thanks Michal, my queues were already registered.
Regards,
Shobhit

Similar Messages

Clearing JAVA Message Queue in PI 7.1

Hi Experts
I am working on a file to File Scenario, and file has been picked up on the sender CC and mesaages have been sent to JAVA queues, But the messages are stuck on the JAVA queues,
Java Queue name: File_http://sap.com/xi/XI/SystemRecv
How can I clear the JAVA message queue in PI 7.1
Thanks
PR

If the messages are on the queue, usually one of the actions must be performed: a) Fix the related scenario and restart the messages or b) Manually cancel the messages. This is also advised on the note below under item "3. Troubleshooting Archiving / Deletion in the Adapter Framework"
[Note 872388 - Troubleshooting Archiving and Deletion in PI|https://service.sap.com/sap/support/notes/872388]
If you are having performance problems, please check if the messages are taking long time in TBDL/Holding status. Let us know if this is the case.

The event queue appears to be stuck.

Hi,
I am getting the below erros
2010-05-06 11:25:19.046/5.281 Oracle Coherence GE 3.5.3/465 <Warning> (thread=ExtendTcpCacheService:TcpInitiator:TcpReader, member=n/a): The event queue appears to be stuck.
2010-05-06 11:25:19.046/5.281 Oracle Coherence GE 3.5.3/465 <Error> (thread=ExtendTcpCacheService:TcpInitiator:TcpReader, member=n/a): Full Thread Dump
I am getting all cache events back to my client application.
is there any way to tune the event queue or something like that ?
Regards
S

Hi Gene,
The below is the thread dump.
2010-05-06 15:50:33.952/7.625 Oracle Coherence GE 3.5.3/465 <Warning> (thread=ExtendTcpCacheService:TcpInitiator:TcpReader, member=n/a): The event queue appears to be stuck.
2010-05-06 15:50:33.968/7.641 Oracle Coherence GE 3.5.3/465 <Error> (thread=ExtendTcpCacheService:TcpInitiator:TcpReader, member=n/a): Full Thread Dump
Thread[Reference Handler,10,system]
     java.lang.Object.wait(Native Method)
     java.lang.Object.wait(Object.java:485)
     java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
Thread[Attach Listener,5,system]
Thread[ExtendTcpCacheService:TcpInitiator:EventDispatcher,5,main]
     java.io.FileOutputStream.writeBytes(Native Method)
     java.io.FileOutputStream.write(FileOutputStream.java:260)
     java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
     java.io.PrintStream.write(PrintStream.java:430)
     sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
     sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
     sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85)
     java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168)
     java.io.PrintStream.write(PrintStream.java:477)
     java.io.PrintStream.print(PrintStream.java:619)
     java.io.PrintStream.println(PrintStream.java:773)
     com.test.coherence.samples.SimpleListener.onMapEvent(SimpleListener.java:11)
     com.tangosol.util.MultiplexingMapListener.entryInserted(MultiplexingMapListener.java:33)
     com.tangosol.util.MapEvent.dispatch(MapEvent.java:266)
     com.tangosol.util.MapEvent.dispatch(MapEvent.java:226)
     com.tangosol.util.MapListenerSupport.fireEvent(MapListenerSupport.java:556)
     com.tangosol.coherence.component.util.SafeNamedCache.translateMapEvent(SafeNamedCache.CDB:7)
     com.tangosol.coherence.component.util.SafeNamedCache.entryInserted(SafeNamedCache.CDB:1)
     com.tangosol.util.MapEvent.dispatch(MapEvent.java:266)
     com.tangosol.coherence.component.net.extend.RemoteNamedCache$ConverterListener.dispatch(RemoteNamedCache.CDB:5)
     com.tangosol.coherence.component.net.extend.RemoteNamedCache$ConverterListener.entryInserted(RemoteNamedCache.CDB:1)
     com.tangosol.util.MapEvent.dispatch(MapEvent.java:266)
     com.tangosol.coherence.component.util.CacheEvent.run(CacheEvent.CDB:18)
     com.tangosol.coherence.component.util.daemon.queueProcessor.Service$EventDispatcher.onNotify(Service.CDB:26)
     com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     java.lang.Thread.run(Thread.java:619)
Thread[ExtendTcpCacheService:TcpInitiator:TcpReader,5,main]
     java.lang.Thread.dumpThreads(Native Method)
     java.lang.Thread.getAllStackTraces(Thread.java:1477)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:597)
     com.tangosol.net.GuardSupport.logStackTraces(GuardSupport.java:791)
     com.tangosol.coherence.component.util.daemon.queueProcessor.Service$EventDispatcher.drainOverflow(Service.CDB:45)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.post(Peer.CDB:9)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.receive(Peer.CDB:26)
     com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator$TcpConnection$TcpReader.onNotify(TcpInitiator.CDB:39)
     com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     java.lang.Thread.run(Thread.java:619)
Thread[Logger@27602911 3.5.3/465,3,main]
     java.lang.Object.wait(Native Method)
     com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
     com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
     java.lang.Thread.run(Thread.java:619)
Thread[main,5,main]
     java.lang.Object.wait(Native Method)
     com.tangosol.coherence.component.net.extend.message.Request$Status.waitForResponse(Request.CDB:43)
     com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:20)
     com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:1)
     com.tangosol.coherence.component.net.extend.RemoteNamedCache$BinaryCache.putAll(RemoteNamedCache.CDB:10)
     com.tangosol.util.ConverterCollections$ConverterMap.putAll(ConverterCollections.java:1595)
     com.tangosol.coherence.component.net.extend.RemoteNamedCache.putAll(RemoteNamedCache.CDB:1)
     com.tangosol.coherence.component.util.SafeNamedCache.putAll(SafeNamedCache.CDB:1)
     SimpleCacheTest.main(SimpleCacheTest.java:29)
Thread[Signal Dispatcher,9,system]
Thread[ExtendTcpCacheService:TcpInitiator,5,main]
     java.lang.Object.wait(Native Method)
     com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
     com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
     java.lang.Thread.run(Thread.java:619)
Thread[Finalizer,8,system]
     java.lang.Object.wait(Native Method)
     java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
     java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
     java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Message Queued for submission" performance counter high for Exchange Server 2010 Database

Hi,
We are receiving SCOM Alert as "Mail Submission service is experiencing issue: Messages Queued for Submission-sustained for 15 mins-RED (>25)".
After checking the "Messages queued for Submission" counter on the repective server it was found that the value is 66 but when we check the queue viewer we dont observe any messages stuck in Submission queue.
Would like to know what aspects can be checked here, in order to troubleshoot the issue?
The counter shows 0 value in perfmon for all other mailbox databases.
Thanks & Regards.

Hi,
This is a known issue with Exchange Server 2007 and Exchange Server 2010. We do not recommend that you use this counter for health alerts.
I recommend you refer to the following article:
http://support.microsoft.com/kb/2921142/en-us
It is caused by the MailSubmission service submits a message for delivery multiple times, the counter is incremented two times but decremented only one time. This situation can leave the counter with a positive value even though there
is no message in the queue. When you restart the service, the counter is reset.
Here is an similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/c9b485a5-ef0e-4b9a-851e-28c4a4c0606a/msexchangeis-mailbox-messages-queued-for-submission-keeps-increasing?forum=exchangesvradminlegacy
Thanks.
Niko Cheng
TechNet Community Support

Troubleshoot Poison Message queue

We are currently in the process of migrating from Exchange 2010 (SP3) to Exchange 2013 (CU5).
I have approximately 20 pilot users migrated to 2013. Everything appears to be working properly except meeting invites sent by Exchange 2010 users to the Exchange 2013 pilot users are getting stuck in the Poison Message queue.
I've exported the meeting invites and the messages appears to be fine. Additionally I am unable to "resume\retry" those messages. They end up back in the Poison queue.
Does anyone have any suggestion on how I can troubleshoot why the meeting invites are specificially getting stuck in the Poison Message queue.
Thank you!

Hi mgouldthorp1,
Thank you for your post.
Whether all the meeting requests from Exchange 2010 are stuck in the poison queue?
You try to create a new test user on Exchange 2010 and exchange 2013. Does the issue still occur to them?
You try to make sure the latest RU are installed on both Exchange 2010 and 2013 serve.
Then, you use “Get-TransportService servername |ft ”(servername is a name of exchange Server) to check the value of “TransportSyncAccountPoisonAccountThreshold”, it is 2 by default.
When you export the meeting invite, you could check the time zone whether it is same with the exchange server.
If there are any questions regarding this issue, please be free to let me know.
Best regard,
Jim

Problem with GlassFish and Sun Java System Message Queue

Hi,
I used application server PE.8 and I upgraded to Sun Java System Application Server Platform Edition 9.0 Update 1 Patch 1, and I changed all my CLASSPATH and everything. My system is working fine, but the Sun Java System Message Queue that I used before is still showing the queues and physical queues of the previous application server, not the new one. Do you know if there is way to change that and link it to the new version?
thanks

Use an ESB like ServiceMix to bridge JMS providers
http://servicemix.org/
Or write your own MessageListener to consume from one JMS and publish on another one. Be careful with queues to avoid loosing the ordering - so you probably want to use a single MessageListener per subscription/queue - or to take advantage of Tibco's exclusive queues to ensure ordering is preserved. If ordering doesn't matter then don't worry too much about it and maybe have a pool of consumers to improve throughput
James
http://logicblaze.com/

Ile system or message queue is no longer available

Hi All,
We are using DB2 and AIX. We getting below error message in db2 log file.Please advise on this issue.
2014-08-13-05.09.08.624033+060 I12752832A1291     LEVEL: Error (OS)
PID     : 25756258             TID : 1           PROC : db2fmp (168768) 0
INSTANCE: db2fdf               NODE : 000
APPID   : 10.144.69.239.57155.140801190410
EDUID   : 1                    EDUNAME: db2fmp (168768) 0
FUNCTION: DB2 Common, OSSe, OSSMountListing::getNext, probe:90
MESSAGE : ECF=0x90000034=-1879048140=ECF_FILE_REMOTE_SYSTEM_NOT_ACTIVE
          File is on a remote system and the link to that system is not active
CALLED : OS, -, statvfs
OSERR   : ESTALE (52) "A file, file system or message queue is no longer available."
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x09000000074F5548 pdOSSeLoggingCallback + 0x34
[1] 0x0900000008F0A6C4 oss_log__FP9OSSLogFacUiN32UlN26iPPc + 0x1C4
[2] 0x0900000008F0AB70 ossLogSysRC + 0x70
[3] 0x0900000008F2EB90 getNext__15OSSMountListingFCPC23OSSMountListingGetParamCP12OSSMountInfo + 0x4B0
[4] 0x09000000020314A4 db2sap_mount_info + 0x3C4
[5] 0x0900000007760EE4 sqloInvokeFnArgs + 0xB4
[6] 0x0900000007760D44 @76@sqlerRunRoutine__FP13sqleInvokerCBPi + 0x168
[7] 0x0900000007760AD0 sqlerDyload + 0x140
[8] 0x090000000774AA40 sqlerFmpListener + 0x154
[9] 0x0000000100001230 main + 0x910
Regards,
Raj

Hi,
I have checked with AIX team filesyetm every thing fine.Please tell me which filesystem caused thi issue.
Reagrds,
Raj

Oracle tuxedo and Oracle tuxedo message queue on top of a virtual machine.

Hi buddies.
how is it going?
A quick question.
So we are going to go live using Oracle Tuxedo 12.1.1.0 with Distinguished Bulletin Board Liaison and Oracle Tuxedo Message Queue 12.1.1.0 on top of a Virtual Machine (VMWARE) running Oracle Linux 6.2. However we want to know if there are any recommendations or mishaps in which we may face ahead by running Oracle Tuxedo on a virtual machine?
I mean, I am wondering if I have to worry about kernel parameters, virtual machine parameters or any other thing from which could mess up everything.
Another question.
Does oracle also provide virtual machines certification where Oracle tuxedo would run on top of ?
Todd Little-Oracle
Maurice G

Hi Bruno,
I'm not sure what you mean with Distinguished Bulletin Board Liaison. I'm guessing you mean a clustered or MP configuration? And is it truly a clustered configuration or just a single machine MP configuration?
Regarding configuration, are you using Tuxedo services as well or just Tuxedo Message Queue? The biggest issue related to OS configuration is around IPC resources. If you do a tmloadcf -c on your UBBCONFIG file, it will help you determine the minimum IPC resources required. In general I suggest configuring significantly more resources than the minimum to allow for future changes and for some of the parameters for heavier loads. In particular IPC message queue parameters are heavily dependent upon load. So make sure the maximum message size and queue size are large enough for your anticipated workload. You can monitor them under load using the ipcs command.
We don't certify virtual machine environment but support them as long as the VM vendor assures compatibility, which obviously VMware and Oracle VM both do.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

App Server Install fails - due to incompatible Message Queue

I had JES 2005 q1 installed in one of the test machines...now I am trying to set up JES 2005q4 on that. I cud install a Web Server on that ut when I tried to set up the App Server it throws up a msg stating that there is an incompatible version of Message Queue installed and hence installation cannot go ahead.
I am not able to find any instance of Message Queu setup....how do I detect and uninstall old versions of Message Queue??
thx
anand

I assume you are talking about appserver install on Solaris. Message Queue on Solaris is a package based install. The easiest way to uninstall the old version of MQ is: "pkginfo -i | grep Message" ---> "pkgrm all MQ packages".

Get/set message Queue ID in PI 7.1 Adapter module

Hello,
I have a special requirment to get and set message Queue ID in PI 7.1 adapter module.
I tried to use the method setConversationID for the Message Class, but this doest seem to available any more.
Any pointers to which class and method can be used.
Thanks in advance
Regards,
Abhishek

Hi, try [setSequenceId|http://help.sap.com/javadocs/pi/pi711sp03/com/sap/engine/interfaces/messaging/api/Message.html#setSequenceId(java.lang.String)]. Maybe you have to use setDeliverySemantics before in order to set EOIO.
regards, Martin

Message Queue Blocking / MSGMNI Setting

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Malcolm,
Your information and explanations behind these error messages are very useful.
It allow me to further understand Tuxedo internal processing and at the same time
give me a chance to start analysing these fields.
I am reluctant to ask further questions at the mean time. I will use your suggestions
as a starting point.
I will certainly keep you posted of the outcome when I have made the changes in
my UBB config and machine parameters.
Many thanks with your help/explanations Malcolm. It helps alot!
Cheers.
David.
"Malcolm Freeman" <[email protected]> wrote:
>
Hi David,
The MSGTQL reference you give (Solution S-00488) refers to the BEA MessageQ
product
and is not relevant to Tuxedo.
The error messages indicate that the queue buildup is probably due to
a restartable
server failing. What happens is this:
When a restartable server fails its IPC queue remains in place and continues
to
receive messages (which will be processed when the server restarts).
Depending
on the time taken to restart, the queue could become full and unable
to receive
any more messages, and this is probably why you got the message CMDTUX_CAT:1380
indicating that the BRIDGE process was unable to put a message on the
server's
queue.
A server is only restarted when the BBL does a SANITYSCAN check. If,
for example,
your SANITYSCAN interval is 300 seconds and your server fails immediately
after
the previous scan, then there will be a delay of almost 5 minutes before
the failure
is detected and the server restarted - plenty of time for the queue to
fill up.
There are a few things you could do:
The key thing would be to find out why the server is failing, and fix
the problem.
If this is not possible immediately, consider some of the other ideas
below.
Have several servers form an MSSQ to service this queue; then if one
fails the
others will continue processing the messages while the failed server
restarts
(this assumes, of course, that your application does not require the
messages
to be processed in strict order through the server).
Reduce the SANITYSCAN interval (but don't make it too small). This would
reduce
the average time taken to restart the server.
Increase the size of the IPC queue (MSGMNB) so that it can hold more
messages.
I'm not sure why you got a LIBTUX_CAT:1485 message, but this could be
due to a
BRIDGE failure as a result of the congestion.
The NETLOAD parameter would reduce the number of messages going to the
remote
machine, but only if the local machine offers the same service. If the
remote
machine is the only source of the service then NETLOAD will have no effect.
I
recommend you do a search of this newsgroup for postings on "load balancing"
there's some good stuff which will explain how load balancing works.
Depending how things go, it might not be a bad idea to open a case with
BEA Support
and ask for guidance (remember to submit your ubbconfig (or preferably
do a tmunloadcf)
together with the complete ULOGs from both the master and the slave machine).
Hope this helps some.
Regards,
Malcolm.
"Dave" <[email protected]> wrote:
Hi Malcolm,
Thank you for your reply. Interesting point you have made about theMSGTQL
value.
Based on your suggestion I went hunting around the BEA site and found
the following
snipplet:
"- The MSGTQL parameter must be set to a value greater than or
equal to the MSGMNI setting."
(http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=msq/S-00488.htm)
If the above point is valid, then my MSGTQL is definitely way too low.
IF this
be the case, would you know of a method to work out what my MSGTQL bytes
value
should be?
Additionally, I have looked at other parameters which I could tune,and
would
adding a NETLOAD parameter in the *MACHINES section will reduce remote
servers
call? Which potentially, maybe reduce message queue blocking?
FYI:
The error messages I am seeing in my ULOG file are:
"LIBTUX_CAT: 1477 : ERROR .SysServerDied
LIBTUX_CAT: 1476 : ERROR: .SysServerRestarting"
Which then leads to message queue blocking
"CMDTUX_CAT: 1380 : ERROR: Message queue blocking prevented delivery,
Qaddr=..."
and potentially "LIBTUX_CAT: 1485 .SysNetworkDropped."
Many Thanks. Hope to hear from you (Malcolm) or other parties out there
that can
assists.
Thanks.
David

Message Queue Blocking/MSGMNI Confirmations

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

InterConnect - FTP adapter:Message queue empty

Hi,
I have installed oracle InterConnect 9.0.4.
The send point and receive end point are configured as separate folders
ota.send.endpoint=ftp://hcsdlx01/interexample/sender/
ota.receive.endpoint=ftp://hcsdlx01/interexample/receiver
We have placed an xml file at the sender location.
And trying to retrieve at reciever end point
But we are getting a message saying message queue empty in the oailog.txt
can anyone shed the possible sources of error.
Regards
Venkat

Finally succeeded in spotting error.
The FTP adapter.ini file was not configured properly
The point is that The send point and receive points should be as per the file system.
In our case the endpoint as we see in browser say:
ftp://example/endpoint
but in the file in Unix server was
<dir1>/<dir2>/endpoint
In the adapter.ini we changed to endpoint = <dir1>/<dir2>/endpoint.
It started working properly,
Thank u marcus

Message Queue 4.4 doesn't know "jms.properties" ?

Sun JMS Tutorial illustrates using a properties file to supply context properties. You define a System property "jms.properties" to point to the location of the properties file:
java -Djms.properties=%J2EE_HOME%\config\jms_client.propertiesInside of said file is the properties in question (these are a surmise; the contents are nowhere documented).
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:///C:/TempThen a call to InitialContext() will succeed.
But the Tutorial assumes you're running under J2EE, and I'm not. I'm using the stand-alone Message Queue 4.4. If I define the properties on the command line,
java -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Djava.naming.provider.url=file:///C:/Tempthen InitialContext() succeeds.
If I explicitly dump the contents of the file into System.properties,
       String
       prop = System.getProperty( "jms.properties" );
       Properties props = System.getProperties();
       try {
           java.io.File pf = new java.io.File( prop );
           props.load( new java.io.FileInputStream(pf) );
       catch( Exception ex ) { ex.printStackTrace(); }Then they get defined and InitialContext() tries to use them. But if I don't then they never get defined. Obviously the Tutorial expects that someone will do that, but who? AFAIK, both environments use the same naming library.
Has the behavior of MQ changed since version 1.3 of the tutorial? Or is J2EE doing something that the standalone product doesn't?

This is all about JNDI configuration. Before you can look up an object in a JNDI repository you need to tell the JNDI runtime which JNDI provider to use. This means you need to set the system properties java.naming.factory.initial and java.naming.provider.url to specify which JNDI provider to use and where the data is located. There's a bit about this in the JNDI tutorial [http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html|http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html] .
The tutorial you are running uses the simple file-based JNDI provider known as "fscontext" and included in fscontext.jar.
That tutorial seems to be reading the jms.properties property and importing its contents, though I can't see where that is supposed to happen and so am not surprised it doesn't work. jms.properties is not, as far as I can see, a standard property name.
The MQ 4.4 documentation describes how to configure an InitialContext to use fscontext by configuring those properties directly. This would definitely work!
[http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view|http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view]
Note that your JNDI datastore (which you've defined to be in C:\Temp) will start off empty, so any lookups will fail unless you've inserted connection factories or destinations in there yourself. I see that is covered elsewhere in the JMS tutorial you were following. There's also a simple MQ GUI tool that can do this. [http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view|http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view]
Finally, if you're simply trying to learn about JMS and MQ you can skip the use of JNDI completely and simply instantiate the underlying connection factories explicitly. This wouldn't be appropriate in a production environment (where it is recommended to store such objects in a central store) but for developmeht purposes would work just fine.
Nigel
http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view

Java Message Queue/ JMS Vendor performance.

Hi,
I need some help from you folks. In our system we are dealing with large number (tens of thousands) of operations per second. I'm doing some research in order to determine if we can use JavaTM Message Service (JMS) API in this system. I red that Java Message Queue was voted "Best Java Messaging Tool" by Java Developer's Journal readers and JMQ now marked by iPlanet[tm] E-Commerce Solutions. So I'm looking for numbers. How many clients/operations iPlanet or other JMS vendors can support per second. Unfortunately I didn't find any concrete example of built systems, number of maximum operation supported per second.
Please response to [email protected] also.
Thanks in advance,
Daniel Drazner

Following configuration: pIII 1GHz, standard vm settings, JBoss 2.4.4, jdk1.3.3 sun
My project (probably good optimized) has following performance:
- asynchronous sending message to queue:20 ms
- synchronous (send/replay) 200 ms
This are statistics for single thread, but this is some how scalable, so for 20 parallel threads you will have the same performance.
Topics are much faster, but I need PTP messaging

Message Queue in XI is stuck

Similar Messages

Maybe you are looking for