Message producer waiting queue response

how do a producer (cient servlet) get response from the queue. I want to know whether messages delivered properly and send the response from the queue to the calling application.

Can you provide some more details? You might want to check out the JMS
examples if you're looking for basic JMS request/response code.
-- Rob
sujith wrote:
how do a producer (cient servlet) get response from the queue. I want to know whether messages delivered properly and send the response from the queue to the calling application.

Similar Messages

Error Message "waiting for response from user"

When some people invite me to chat on Ichat, they get an error message saying "waiting for response from user." On my end, I never get the invite. Other people are able to invite me without any problem. How do I fix this? Is the problem on my end?
Thank you!

Hi,
I can see now where the issue is.
A Jabber Buddy list can only accept Jabber Buddies.
A Buddy List that Logs into AIM such as your @Me.com name can only add Valid AIM Names to it as Buddies.
The main problem is that both Jabber IDs and AIM names can have the @symbol on them and look like email addresses.
Example Jabber IDs
Example "AIM " Names
[email protected]
ralphjonhsr (No @)
[email protected]
[email protected] (Apple ID type)
[email protected]
[email protected] (Apple ID type)
any Facebook name
[email protected] (Email registered with AIM)
So your Jabber Buddy List will find that there is No (@)me.com Jabber server and say the message cannot be delivered.
The AIM (@Me.com) Buddy never gets the Request for Authorisation for the same reason and the auto response of adding An ID/Name to Send a Message to starts iChat wanting that person to Accept or Decline being a Buddy- which they cannot do - so you get the name with the "Waiting for..." message.
Either everyone gets a Jabber ID or everyone gets a Valid AIM Name.
8:39 PM Friday; October 28, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Streams AQ: waiting for messages in the queue

Hi,
For some reason, I've to run the owb mapping manually. First I try to run it in this way:
declare
n_result number;
begin
n_result:=dwrr104.wb_rt_api_exec.run_task('LOC_ZONE2_DW','PLSQL','MAP_RMS_CUSTOMER');
dbms_output.put_line('result :='||n_result);
end;
This script just kept running endlessly. I noticed The wait event in database for this session was: "Streams AQ: waiting for messages in the queue"
However, if I run the 'main' function of this mapping directly like this:
declare
-- Non-scalar parameters require additional processing
p_env dw.wb_rt_mapaudit.wb_rt_name_values;
begin
-- Call the function
:result := dw.map_rms_web_ptrackcode.main(p_env => p_env);
end;
it can work without any problem.
Any ideas?
Jeffrey

Hi Jeffrey,
need to change them?Yes, you need to increase value for AQ_TM_PROCESSES parameter (set it to at least 1).
It is a requirements for target database (database where runtime services is run):
Look at OWB installation guide (it is for OWB 10gR1 but for later OWB versions requirements is the same):
http://download.oracle.com/docs/cd/E10926_01/doc/owb.101/b12150/appaprepdb.htm#i1008228
Regards,
Oleg

FCGI1031: timed out waiting for response body

Hello,
I can not see the remote computer to the test.php
I see logs
for host 33.180.164.9 trying to GET /test.php, responder-fastcgi reports: FCGI1031: timed out waiting for response body from c:/program files/oracle/webserver7/https-testnet4/docs/test.php
My obj.conf
Service type="magnus-internal/php"
fn="responder-fastcgi"
app-path="C:/Program Files/Oracle/WebServer7/plugins/php/php-cgi.exe"
bind-path="https-testnet4--php_cgi"
app-env="PHPRC=C:/Program Files/Oracle/WebServer7/plugins/php"
app-env="PHP_FCGI_CHILDREN=2"
app-env="PHP_FCGI_MAX_REQUESTS=200"
bucket="php-bucket"
I see the internal computer test.php but test.php will not appear on the remote computer.
Regards

Good day.
I have a similar problem and I have managed to pinpoint when it fails but unfortunately I don't know how to fix it yet.
In my scenario, I have 2 separate processes:
the first process reads data from a Seebeyond SRE instance and stores it on a local Java CAPS queue.
The second process is an EVision process that reads the data from this queue and displays it on a page.
Whenever I am not connected to the network linking my Java CAPS instance to the Seebeyond SRE instance (first process cannot connect ) I get this problem on the EVision side every second time I request a page. This means I can view the first message on the queue and then I have to restart the Logical Host
This doesn't make sense to me, since The EVision process is a completely separate process, deployed in it's own WAR file.

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

Destroying a message producer

We have a Sun MQ JMS provider which provides us destinations. The process is something like this:
1. There is a queue, where a message is posted.
2. I have a java consumer, which listens on this queue. (via JNDI lookup).
3. I do some processes and based on the status (success or failure) i put a response message in a different queue(Q2).
4. This Q2 is obtained from the JMS message header (getJMSReplyTo()).
5. sender = session.createSender(Q2);
sender.send(msg, javax.jms.DeliveryMode.PERSISTENT, message.getJMSPriority(), getLifetime());6. message is the textMessage obtained from Q1.
7. In a finally block, i am calling sender.close(); The session is still open and will be used for the next message received from Q1.
All is well and good, except for the fact that number of producers on Q2 is getting accumulated for every send() call. The sender.close() is executed(i debugged in eclipse and no JMS exception for the close() call).
The problem here is in the JMS provider, we have a limitation of 100 producers on Q2. Since every send() call leaves a producer on Q2, after 100 replies, i am getting an error on the SunMQ side "producer cannot be added to the queue. Limit of 100 producers will be exceeded".
This results in a JMS Exception during the session.createSender(Q2) line.
I don't know what i am missing here, and i am pretty new to JMS (as you might have imagined by now).
Do we have to explicitly close the session also along with the sender.close() or do we have to do anything other than closing the sender ?
I'd be happy to hear some suggestions and opinions.

Hmm, so the culprit here is the sender#close() method
The standard JMS API, doesn't say anything about the close() operation. It must be implementation specific, in your case SunMQ,
You should be getting into the API and look for the details on what the close() method actually does, whether it really destroys the message producer or not
As Far As developing a JMS Client, I do this way
Get a ConnectionFactory and Destination
Create a Connection and Session
Create a MessageConsumer
Create a MessageProducer
Create message/s
Send message/s
Receive message/s synchronously or asynchronously
Exit Session and Connection
Wonder why you would like to have a new Producer each time, but that depends on you and your requirement :)
Cheers,
Edited by: anamupota on Jan 22, 2009 7:53 AM

GUI Login to System "Waiting for Response"

Dear all,
I´ve installed a new SAP-System with ABAP and JAVA.
The installation was successfull, but when I want to login to the System
the GUI write "Waiting for Response". That´s all.
Can anyone help me?

The disp_dev writes:
trc file: "dev_disp", trc level: 1, release: "700"
sysno      01
sid        CCC
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    111
intno      20050900
make:      multithreaded, Unicode, optimized
pid        3732
Sat Aug 16 09:45:36 2008
kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 3732) [dpxxdisp.c   1239]
     shared lib "dw_xml.dll" version 111 successfully loaded
     shared lib "dw_xtc.dll" version 111 successfully loaded
     shared lib "dw_stl.dll" version 111 successfully loaded
     shared lib "dw_gui.dll" version 111 successfully loaded
     shared lib "dw_mdm.dll" version 111 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3901
Sat Aug 16 09:45:41 2008
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5361]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >solman_CCC_01                           <
DpShMCreate: sizeof(wp_adm)          18672     (1436)
DpShMCreate: sizeof(tm_adm)          4232256     (21056)
DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm)          528064     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1536)
DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 06420040, size: 4892312)
DpShMCreate: allocated sys_adm at 06420040
DpShMCreate: allocated wp_adm at 06422090
DpShMCreate: allocated tm_adm_list at 06426980
DpShMCreate: allocated tm_adm at 064269B0
DpShMCreate: allocated wp_ca_adm at 0682FDF0
DpShMCreate: allocated appc_ca_adm at 06835BB0
DpShMCreate: allocated comm_adm at 06837AF0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 068B89B0
DpShMCreate: allocated gw_adm at 068B89F0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 068B8A20
DpShMCreate: allocated wall_adm at 068B8A28
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
J2EE server info
start = TRUE
state = STARTED
pid = 4056
argv[0] = C:\usr\sap\CCC\DVEBMGS01\exe\jcontrol.EXE
argv[1] = C:\usr\sap\CCC\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=C:\usr\sap\CCC\SYS\profile\CCC_DVEBMGS01_solman
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1127
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=CCC
argv[7] = -DSAPMYNAME=solman_CCC_01
argv[8] = -DSAPPROFILE=C:\usr\sap\CCC\SYS\profile\CCC_DVEBMGS01_solman
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
Sat Aug 16 09:45:42 2008
DpJ2eeStart: j2ee state = STARTED
Sat Aug 16 09:45:44 2008
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1629]
***LOG Q0K=> DpMsAttach, mscon ( solman) [dpxxdisp.c   11753]
DpStartStopMsg: send start message (myname is >solman_CCC_01                           <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 111
Release check o.K.
Sat Aug 16 09:45:46 2008
DpJ2eeLogin: j2ee state = CONNECTED
Sat Aug 16 09:46:08 2008
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Sat Aug 16 09:46:16 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Sat Aug 16 09:46:53 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Sat Aug 16 09:47:13 2008
SoftCancel request for T14 U15 M0 received from IC_MAN
SoftCancel request for T13 U14 M0 received from IC_MAN
Sat Aug 16 09:52:24 2008
WARNING => DpEnvCheck: no answer from msg server since 20 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:52:44 2008
WARNING => DpEnvCheck: no answer from msg server since 40 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:04 2008
WARNING => DpEnvCheck: no answer from msg server since 60 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:24 2008
WARNING => DpEnvCheck: no answer from msg server since 80 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:53:44 2008
WARNING => DpEnvCheck: no answer from msg server since 100 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:54:04 2008
WARNING => DpEnvCheck: no answer from msg server since 120 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:54:24 2008
WARNING => DpEnvCheck: no answer from msg server since 140 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c   7224]
Sat Aug 16 09:59:46 2008
J2EE server info
start = TRUE
state = ACTIVE
pid = 4056
http = 50100
https = 50101
load balance = 1
start_lazy = 0
start_control = SAP J2EE startup framework
Mon Aug 18 08:24:32 2008
DpSigQuit: caught signal 3
Mon Aug 18 08:24:45 2008
DpModState: change server state from ACTIVE to SHUTDOWN
Softshutdown of server...
send softshutdown to gateway
there are still entries in queues: 2
Mon Aug 18 08:25:05 2008
Softshutdown of server...
send softshutdown to gateway
DpHalt: shutdown server >solman_CCC_01                           < (normal)
Mon Aug 18 08:25:06 2008
Stop work processes
Mon Aug 18 08:25:07 2008
Stop gateway
Stop icman
Terminate gui connections
wait for end of work processes
waiting for termination of work processes ...
Mon Aug 18 08:25:08 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:09 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:11 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:12 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:13 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:14 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:15 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:16 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:17 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:18 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:19 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:20 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:21 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:23 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:24 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:25 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:26 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:27 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:28 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:29 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:30 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:31 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:32 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:33 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:34 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:35 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:36 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:37 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:38 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:39 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:40 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:41 2008
waiting for termination of work processes ...
Mon Aug 18 08:25:42 2008
wait for end of gateway
wait for end of icman
DpHalt: disconnect j2ee listener
DpHalt: wait for end of j2ee server
waiting for termination of J2EE server ...
Mon Aug 18 08:25:43 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:44 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:46 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:47 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:48 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:49 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:50 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:51 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:52 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:53 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:54 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:55 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:56 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:57 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:58 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:25:59 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:00 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:01 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:02 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:03 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:04 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:05 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:06 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:07 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:08 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:09 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:10 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:11 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:12 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:13 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:14 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:15 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:16 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:17 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:18 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:19 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:20 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:21 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:22 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:23 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:24 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:25 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:26 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:27 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:28 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:29 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:30 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:31 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:32 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:33 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:34 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:35 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:36 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:37 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:38 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:39 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:40 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:41 2008
waiting for termination of J2EE server ...
Mon Aug 18 08:26:42 2008
ERROR => DpHalt: J2EE (pid 4056) still alive ... [dpxxdisp.c   10223]
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4056)
DpIJ2eeShutdown: j2ee state = SHUTDOWN
waiting for termination of J2EE server ...
Mon Aug 18 08:26:43 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:44 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:45 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:46 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:47 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:48 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:49 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:50 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:51 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:52 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:53 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:54 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:55 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:56 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:57 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:58 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:26:59 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:00 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:01 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:02 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:03 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:04 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:05 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:06 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:07 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:08 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:09 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:10 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:11 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:12 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:13 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:14 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:15 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:16 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:17 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:18 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:19 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:20 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:21 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:22 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:23 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:24 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:25 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:26 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:27 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:28 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:29 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:30 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:31 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:32 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:33 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:34 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:35 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:36 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:37 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:38 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:39 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:40 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:41 2008
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:42 2008
ERROR => DpHalt: J2EE (pid 4056) still alive [dpxxdisp.c   10255]
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
DpJ2eeEmergencyShutdown: try to kill SAP J2EE startup framework (pid=4056)
waiting for termination of J2EE server (2nd chance) ...
Mon Aug 18 08:27:43 2008
DpStartStopMsg: send stop message (myname is >solman_CCC_01                           <)
DpStartStopMsg: stop msg sent
Mon Aug 18 08:27:44 2008
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   12099]
MBUF state OFF
MBUF component DOWN
cleanup EM
Mon Aug 18 08:27:45 2008
***LOG Q05=> DpHalt, DPStop ( 3732) [dpxxdisp.c   10371]
Can you understand, what this means?

Removing superseded messages from the queue

Does JSMQ provide any way for a producer to remove a message from the queue which it queued some time ago but which it no longer wishes to send?
I am investigating the use of JSMQ in a military battlemap application connecting nodes over low bandwidth/unreliable connections. The reason we want to be able to remove messages is as follows: Say a producer sends a low priority message to the queue regarding a unit's position. Later on the same producer sends an update regarding the same unit to the queue. If the first message is still present in the queue (ie has not been sent yet) then we want the producer to be able to remove it as it is now superseded by the new message and we don't want to waste bandwidth sending the old message first.
I know we can set an expiry time on messages, but this doesn't really solve our problem. We want the original message to stay in the queue indefinately (until it is read by the consumer) unless it is superseded by a new message in which case we want to remove it.
Thanks
Roger

Hi Roger,
JMS does not support the removal of messages from a queue
as you described. I can't think of a way to not deliver the old
message once it was already sent.
Alternatives I can think of:
- Adjust the interval at which the consumer reads the messages
off the queue and/or the number of messages that are read;
so that the consumer will see the old and new messages
and can decide which one to use. This does not address the
bandwidth issue but allows the consumer to behave smarter.
- Similar to above, but on the producer side. The producer waits
for some interval before sending a message, in case an
updated position of a unit arrives at the producer. This might not
be good if a consumer needs to know the location of a unit as
soon as it is available.
- Use a topic instead of a queue. When using queues, old
messages (containing old positions) sent to a queue are kept
until the consumer reads it. With topics, if no consumers are
around, the message is tossed. However, if you really need old
messages to lie around (e.g. need to know last position of
unit), this won't suit your needs.
Sorry I don't have a straight answer for you, hope this helps
somewhat.
-i
http://wwws.sun.com/software/products/message_queue/index.html

Request timed out while waiting for response!!

Hi All,
My scenario is PROXY to SOAP. I am getting below error while posting to WEBSERVICE.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">Failed to deliver inbound WS message, code=503 and reason=Request timed out while waiting for response. at com.sonicsw.net.http.ws.WSHttpProtocolHandler$HttpInBrokerHandler.invoke(WSHttpProtocolHandler.java:833) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.sendToSOAPStack(WSHttpProtocolHandler.java:630) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.dispatch(WSHttpProtocolHandler.java:537) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.servicePost(WSHttpProtocolHandler.java:284) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.service(WSHttpProtocolHandler.java:609) at com.sonicsw.net.http.HttpProtocolHandler.handle(HttpProtocolHandler.java:471) at progress.message.net.http.server.HttpConnectionHandler.handle(HttpConnectionHandler.java:170) at progress.message.net.https.server.SonicHttpsConnection.service(SonicHttpsConnection.java:156) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831) at progress.message.net.https.server.SonicHttpsServer.handleConnection(SonicHttpsServer.java:449) at progress.message.net.https.server.SonicHttpsServer.handle(SonicHttpsServer.java:364) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)</ns1:stackTrace>
Any Idea ? Do I need to change anything in my SOAP Channel or BAsis should change the Time Parameter?
Thanks,
Pushkar Patel

Hi,
>>>>>>>Request timed out while waiting for response.
See the below link, it might be helpful to you for timed out issue.
[Link1|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true]
Regards,
Rajesh

Error while sending the messages to JMS Queue

Hi ,
I am trying to pick the file from JMS Queue and send the response xml as outbound message to JMS Queue again using XAI Sender
I Created XAI Sender, Outbound Message Type(DM-RCVRESP) and configured these two with External System.
I am able to pick the file from JMS Queue but unable to send the message through XAI Sender (Real-time)
Plz find below the error trace getting.
[Wed Jun 15 16:12:09 IST 2011] Error while processing sender "UPLOADSTG" : Unable to update response in staging table: Row id not given.
com.splwg.mpl.sending.SameThreadSendingManager$ProcessException
     at com.splwg.mpl.sending.SameThreadSendingManager.processDestination(SameThreadSendingManager.java:341)
     at com.splwg.mpl.sending.SameThreadSendingManager.sendResponse(SameThreadSendingManager.java:293)
     at com.splwg.mpl.sending.SameThreadSendingManager.doSend(SameThreadSendingManager.java:249)
     at com.splwg.mpl.server.async.ExecSendRequestProcessor.ProcessRequest(ExecSendRequestProcessor.java:61)
     at com.splwg.mpl.server.async.RequestProcessingThreadAdapter.run(RequestProcessingThreadAdapter.java:46)
     at com.splwg.mpl.server.PooledThread.run(PooledThread.java:91)
     at java.lang.Thread.run(Thread.java:662)
Please guide me in this regard..
Thanks,
sukumar

What have you configured for the response tab for the sender? Are you using the MPL or the MDB?
Take a look at:
MPL Best Practices (Doc Id 1308165.1)
Oracle WebLogic JMS Integration (Doc Id: 1308181.1)

Messages in inbound queue in status-RUNNING and it is too slow

Hi Experts,
We have a issue there are tons of messages in inbound queue in status-RUNNING and it is too slow!, hence there are more messages getting in the queue every minute.
This is Production enviorment.
We have priority queues
QIN is waiting status.
De-register will not work due to loss of messages fear
Please advice
thanks and regards,
krushi

Hi,
If the queues are hanging due to peak load at sometimes
you can schedule following reports to restart them automatically
(dont have to lock and unlock manually)
RSQIWKEX - Inbound Queues
RSQOWKEX- Outbound Queues
Also you can save the first entry of the queue if its causing problems to process later- smq3
thanks
francis

OC4J 9.0.4: Problem receiving message from JMS queue

I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
If I create a QueueBrowser I can see there are messages in the queue.
Can someone tell me what I do wrong?
Here is the code of my dequeue action:
public String dequeue(int qName) throws RbsSysException
        final String method = "dequeue(int qName)";
        _log.debug(method);
        QueueConnection queueConnection = null;
        try
            queueConnection = _queueConnectionFactory.createQueueConnection();
            QueueSession queueSession = queueConnection.createQueueSession(false,
                    Session.AUTO_ACKNOWLEDGE);
            QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
            _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
            // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
            // 64 kb. Therefore use ObjectMessage.
            Message msg = queueRcv.receiveNoWait();
            _log.debug("msg = " + msg);
            ObjectMessage objMsg = (ObjectMessage)msg;
            //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
            _log.debug("objMsg = " + objMsg);
            if (objMsg != null)
                return (String) objMsg.getObject();
            else
                return null;
        catch (JMSException je)
            throw new RbsSysException(je);
        finally
            if (queueConnection != null)
                try
                    queueConnection.close();
                catch (Exception any)
                    _log.error("Error while closing QueueConnection: ", any);
    }

Did you implement javax.jms.MessageListener and the method onMessage(Message)?
If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
Hope this helps,
Lonneke

** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

MDB is not picking up messages in the Queue

Hi ,
I am trying to implement a MDB (Producer) , that acts as a Message Producer also . This MDB pickes up a message from a Queue and sends it to another Queue(Queue 2) after some processing. The MDB listening to the Queue 2 is not being able to pick this message.
The Weblogic console shows that the message is pending.
The transaction-type is Container and transaction-attribute is 'Required' for the Producer (MDB) ...
I am creating a QueueSession as con.createQueueSession(true, Session.AUTO_ACKNOWLEDGE) . I also tried specifying queuesession.commit() ...
even then the Message is not picked by the MDB listening on the other side...
Please help me out

any one

A bug in message pattern's queue implementation?

Here is how to reproduce the problem.
Have 2 Java program ready.
A is to create a queue and publish 3 messages to the queue.
B is to subscribe to the same queue and try to get all messages from the queue (put the getMessage inside a while(true) loop) then wait for new message.
Step 1. Run A, which put 3 messages into queue.
Step 2. Run B, which get 3 messages out of the queue then waiting on the getMessage() blocking call.
Step 3. Kill program B without unsubscribe() call.
Step 4. Run A, which put 3 messages into the queue again.
Step 5. Run B, this time it only get 2 messages. The 1st message A put in on Step 4 got lost.
Actually, if you run Step 2 multiple times before step 3, you will lost more message. It seems each time when there is a subscription created without a unsubscribe(), it will get one message lost.
I know the propery way is to call unsubscribe(), but the JVM could be killed thus won't have time to do cleanup.

Using message pattern 2.3, command pattern 2.3 and common 1.3
Coherence version is 3.4.2.
BTW, if the unit test program you mentioned is the MessageTests.java included in the src zip file, you won't be able to test this issue.
All unit test inside the MessageTests.java are comsuming exactly number of messages been published then do unscribe() call.
In order to reproduce this issue, you'd need to put your consumer JVM in a blocking getMessage() state (i.e. call getMessage() while there is no message in queue)
then kill the JVM. The unit test codes in MessageTests.java never enter blocking wait state when call getMessage().
Example code -
For the one putting message
MessagingSession messagingSession = DefaultMessagingSession.getInstance();
Identifier topicIdentifier = messagingSession.createQueue("test-queue");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
For the one getting message
MessagingSession messagingSession = DefaultMessagingSession.getInstance();
Identifier topicIdentifier = messagingSession.createQueue("test-queue");
Subscriber subscriber = messagingSession.subscribe("test-queue");
while (true) {
String message = (String)subscriber.getMessage();
System.out.println(message);
}

Message producer waiting queue response

Similar Messages

Maybe you are looking for