MessageQ keep-alive. Info about client disconnect

Hi,
I'm using BEA MEssageQ to recieve messages from clients. But i need information if client is disconnected. Is there any keep-alive mechanism which tell me if client disconnected. Or maybe there is a message to check if client is connected?

Hi,
I asked one of the developers and got this response:
Actually OMQ has no pre-defined keep alive mechanism. OMQ is always accept the requests from clients passively, it cannot check the connectivity of client automatically.
OMQ can provide information about the status of the queue that the client attaches. If you can accept the hypothesis that client is connected if the its primary queue is attached, then one possible solution for your request may be: create an application which registers to receive availability (attached/detached) messages of the target queue from local Avail Server process. If the queue is available/attached, it means the corresponding client is connected. And if the queue is unavailable/detached, it means the corresponding client is disconnected.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Similar Messages

Weblogic proxy plugin closes keep-alive connections to clients randomly

In short we have following arhitecture:
clients ---> wl proxy plugin 1 ----> weblogic 1
clients ---> wl proxy plugin 2 ----> weblogic 2
Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
Trace (replaced sensitive information):
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
!!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
WL proxy plugin conf params are:
WebLogicCluster $IP$:$PORT$
DynamicServerList OFF
KeepAliveTimeout 90
MaxKeepAliveRequests 0
KeepAliveSecs 55
Apache worker configuration is:
<IfModule mpm_worker_module>
PidFile var/run/httpd-worker.pid
LockFile var/run/accept-worker.lock
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 200
ThreadsPerChild 200
MaxClients 2000
MaxRequestsPerChild 0
AcceptMutex pthread
</IfModule>
Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
Any help?

If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

LB configuration - Keep Alive.

I need to help configure proper load balancing between 2 building modules of Portal server.
SetUp:
Server A - Portal 1,Access Manager 1 , Directory 1
Server B - Portal 2, Access Manager 2, Directory 2
Logical Architecture.
-------- Server A
User Request -------------------->LB ------------>
------ Server B
I need to configure LB in a way that It has keep Alive info for Server A and B.I think there is a configuration required in some xml/property file so that If lets say server A goes down...the LB will automatically direct the next request to server B.
Can somebody point me in the right direction?
Thanks.

Do you need the SSO session created on Server A to failover to Server B or is it ok that the user has to reauthenticate if Server A goes down?
In any case you can either configure the LB for s.c. active cookie based persistence (LB is inserting it's own cookie) or s.c. passive cookie based persistence (LB is using a predefined cookie). I guess this is what you mean by 'keep-alive info' - correct?
Of course this does only work if no SSL is used or if SSL is terminated at the LB.
If SSL is used the only solution is to use client-IP based persistence.
All the above is only needed to prevent cross-talk between AM instances.
-Bernhard

Question about Keep Alive feature in Forte 3.

Does anyone use Keep Alive feature under Forte 3.0F.2 environment.
I got trouble and encounters the following problem in the service objects
daily:
INFORMATION: An abnormal disconnect from partition
(CFFE2500-85B0-11D1-B37F-E2F7F3F1AA77:0xec254) was received. Since there
are
no method invocations outstanding to this partition, no notification could
be
given of this disconnect (by indicating a method invocation failed).
Therefore, the information associated with this disconnect is being
reported
to the log.
Class: qqsp_DistAccessException
Error #: [601, 119]
INFORMATION: The connection to the partner was terminated by the
Communication Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: Failed to establish connection: OS Error 61: Connection
refused
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::SetError at 5
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: hose 15 STATE_CONNECTING (EXT_RECEIVED) from
qqcm_HoseFSM::IssueConnect (after EstablishConnection)
Class: qqsp_ErrorDescriptor
Detected at: qqcm_HoseFSM::SetError at 1
Error Time: Fri Nov 26 17:45:39
It seems that Keep Alive sometimes disconnects the connection between the
service objects and the environmental manager.
So that any further connection request from the client encounters the
abnormal exception.
Forte seems not to recommend to use this feature in the Forte Relase note
3.0J1.
She states that "Sites that chooses to test KeepAlives should report all
problems to Technical Support ( and let
Technical Support know that you have enabled this capability)"
Should I disable Keep Alive feature under Forte 3.0F2 environment?
Rgds
Tom

Hey Marco,
I can`t find a view that is named like "APEX_APPLICATION_PAGE_IR%". Is it not available on the evaluation instance.
I don`t want to use the build-in CSV download, becaus I want to export thousands of data sets. I got this already to work with APEX 3.0 and I get the sql from the application views. The procedure which creates the file runs a few hours and after that it is inserted into a table from which the user can download the file. In the procedure there happens a few other things, which are very import, so I have to create my custom solution.
And for that I thought it would be very very very cool if I can get the sql behind the interactive report with the filters ant those things.
Don`t you think that would be possible? I guess the APEX create a SQL although, or am I wrong?
Thank you,
Tim

Asking about how server can handle client disconnection

Dear sir/madam,
i'm doing my final year project and it is about a java client/server big2 game.But now i have a difficulties in dealing with the server side.
That is about how to take action on the serverside if the client suddenly disconnected.
I have read many java client/server programming scripts.But all of them doesn't mention this problem.The scrpits only assume the client side never disconnect suddenly.
I hope if you can give me some suggestions on this problem.

For my mud written in java, I used TCP/IP for the connections. When a client connects, he gets his own thread. Those threads are held in a vector in a manager class. each tick of the server does a quick run thru the vector and if the current thread/socket its on is null or !isAlive() its remove from the vector(which in turn removes it from getting any more game updates. This removal can be caused by two things. The clients disconnects by accident(kills his game, locks up has an internet connection hiccup, etc.) or he uses the games "quit" method. The quit method calls a method that does any player saving of data, etc then closes the socket, and sets it to null. thus the manager sees this and removes him frm the vecotr list on the next server tick. Seems to work great form a mud and worked really well in a multiplayer applet game I had up for a while.

HT5085 Gathering Info About your iTunes Library - Keep getting Network error

I bought iTunes Match yesterday, and so far have not been able to use it.
It gets to Stage 1: Gathering Info About Your iTunes Library and makes progress, but right at the end an error box appears saying:
"We could not complete your iTunes request. The network connection was reset.
Make sure your network connection is active and try again"
Well I know the network connection is active as I was able to be charged for iTunes Match and have had no problems making other purchases. I went to Advance > Run Diagnostics Tests from Help in iTunes and ran the Network Connectivity Diagnostics and it reported no problems.
Now I know how much Apple hate giving back refunds, but if people can't help, does anyone know how I can get my money back? If I click "Report a Problem" it simply takes me to the help pages. I tried contacting support but I received an email saying they can't help.
I'm getting quite frustrated now, so I'm reaching out and hoping someone can help me?
I've copied the diagnostic results below:
Microsoft Windows 7 x64 Home Premium Edition Service Pack 1 (Build 7601)
Dell Inc. Dell System XPS L502X
iTunes 10.6.1.7
QuickTime 7.7.2
FairPlay 1.14.37
Apple Application Support 2.1.7
iPod Updater Library 10.0d2
CD Driver 2.2.0.1
CD Driver DLL 2.1.1.1
Apple Mobile Device 5.1.1.4
Apple Mobile Device Driver 1.59.0.0
Bonjour 3.0.0.10 (333.10)
Gracenote SDK 1.9.5.502
Gracenote MusicID 1.9.5.115
Gracenote Submit 1.9.5.143
Gracenote DSP 1.9.5.45
iTunes Serial Number 003CA7C40B1E98E0
Current user is not an administrator.
The current local date and time is 2012-05-18 20:20:20.
iTunes is not running in safe mode.
WebKit accelerated compositing is enabled.
HDCP is supported.
Core Media is supported.
Video Display Information
NVIDIA, NVIDIA GeForce GT 540M
Intel Corporation, Intel(R) HD Graphics Family
**** External Plug-ins Information ****
No external plug-ins installed.
Genius ID: bb5c046694c1f4c590202360da9f2bc5
iPodService 10.6.1.7 (x64) is currently running.
iTunesHelper 10.6.1.7 is currently running.
Apple Mobile Device service 3.3.0.0 is currently running.
**** Network Connectivity Tests ****
Network Adapter Information
Adapter Name:          {444AF521-4D63-434F-AC33-8F05DA9C6C64}
Description:          Microsoft Virtual WiFi Miniport Adapter #2
IP Address:          0.0.0.0
Subnet Mask:          0.0.0.0
Default Gateway:          0.0.0.0
DHCP Enabled:          Yes
DHCP Server:
Lease Obtained:          Thu Jan 01 00:00:00 1970
Lease Expires:          Thu Jan 01 00:00:00 1970
DNS Servers:
Adapter Name:          {4F46CBF3-C53C-4615-AF14-B46B9785D100}
Description:          Microsoft Virtual WiFi Miniport Adapter
IP Address:          0.0.0.0
Subnet Mask:          0.0.0.0
Default Gateway:          0.0.0.0
DHCP Enabled:          Yes
DHCP Server:
Lease Obtained:          Thu Jan 01 00:00:00 1970
Lease Expires:          Thu Jan 01 00:00:00 1970
DNS Servers:
Adapter Name:          {6D3CAB28-0C0B-4701-A440-B1A90BE75551}
Description:          Dell Wireless 5540 HSPA Mini-Card Network Adapter
IP Address:          0.0.0.0
Subnet Mask:          0.0.0.0
Default Gateway:          0.0.0.0
DHCP Enabled:          No
DHCP Server:
Lease Obtained:          Thu Jan 01 00:00:00 1970
Lease Expires:          Thu Jan 01 00:00:00 1970
DNS Servers:
Adapter Name:          {8C130DAB-E810-4FA6-8946-1600FFE0DB2F}
Description:          Intel(R) WiFi Link 1000 BGN
IP Address:          192.168.1.69
Subnet Mask:          255.255.255.0
Default Gateway:          192.168.1.254
DHCP Enabled:          Yes
DHCP Server:          192.168.1.254
Lease Obtained:          Fri May 18 20:01:40 2012
Lease Expires:          Sat May 19 20:01:40 2012
DNS Servers:          192.168.1.254
Adapter Name:          {B32D9395-8937-42EC-BC5F-352D07958EDF}
Description:          Realtek PCIe GBE Family Controller
IP Address:          0.0.0.0
Subnet Mask:          0.0.0.0
Default Gateway:          0.0.0.0
DHCP Enabled:          Yes
DHCP Server:
Lease Obtained:          Thu Jan 01 00:00:00 1970
Lease Expires:          Thu Jan 01 00:00:00 1970
DNS Servers:
Active Connection:          LAN Connection
Connected:          Yes
Online:                    Yes
Using Modem:          No
Using LAN:          Yes
Using Proxy:          No
Firewall Information
Windows Firewall is on.
iTunes is NOT enabled in Windows Firewall.
Connection attempt to Apple web site was successful.
Connection attempt to browsing iTunes Store was successful.
Connection attempt to purchasing from iTunes Store was successful.
Connection attempt to iPhone activation server was successful.
Connection attempt to firmware update server was successful.
Connection attempt to Gracenote server was successful.
Last successful iTunes Store access was 2012-05-18 20:14:07.

@ deggie, I wasn't threatening ANYONE. I was simply saying how frustrating this has become, seeing how I have been trying on my own to figure this issue out for more then a month with no results. Like I said in the beginning, I have not used any other account to purchase apps or other products on my phone. I have only ever used one account. There are 23 apps that are saying they can't sync. It directs me to authorize the computer, which I do but it doesn't change the outcome. If I proceed, I lose those 23 apps correct? Do I also lose all my text messages saved, and other things such as documents in the "notes"?

Workstation keep-alive and connectivity failure detection

Dear all,
I intend to automatically detect network failures from my workstation client and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive option. If I understood correctly you can have the workstation generate periodic keep-alive messages to the server and if these are not acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for a disconnection? Otherwise network failures might go by unnoticed if there are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically discriminate if the cause is a network disconnection? It is a pretty generic error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a network failure, can the system recover on its own? or must I reconnect to the server? What I mean is, maybe some keep alive messages where lost, the system passes to the 'disconnected' state, but then the K.A. messages keep being generated and upon correct acknowledgement of these, subsequent ATMI calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep alive message? or is there some sort of tolerance like, say, 'If N messages in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Cacho,
1. I assume that you're talking about the WSL CLOPT option "-K
{client|handler|both|none}", which causes periodic keepalive messages to be
sent. When this option is used, there is no need for the WSC to perform any
periodic operations to keep the network connection alive.
However, if you are worried that the network might suffer a transient
failure and you want to perform your first ATMI call after an extended
period of inactivity as quickly as possible without waiting for another
tpinit(), you may want to perform periodic dummy operations so that you can
reissue the tpinit() if needed as soon as the network connection is
restored.
One option is to make a tpcall() to the ".TMIB" service with an FML32 buffer
where TA_OPERATION is set to "GET" and the other fields are set to retrieve
some system attribute. There is an example of how to call .TMIB at the end
of the TM_MIB(5) manual page. You would want to perform a GET operation
rather than the SET operation shown in that example.
Another option is to write a null service in one of your application servers
which just calls tpreturn() and have your client make periodic cals to that
service.
Calling a verb such as tpalloc() or tpconvert() would not be sufficient,
since these calls do not result in any network traffic.
2. The tperrordetail() function is available in newer releases of Tuxedo to
provide additional information about certain Tuxedo errors. When a
workstation client is disconnected, tperrordetail(0) will return TPED_TERM.
3. If there is a network failure, workstation clients must call tpinit() to
reauthenticate to the system. This is necessary for security reasons.
4. The keepalive option is passed down to the underlying network provider
and Tuxedo has no further involvement with keepalive once it informs the
network of this option. For Sockets the option passed is SO_KEEPALIVE; you
can do a web search on SO_KEEPALIVE to see exactly how the network treats
keepalive messages on your particular platform.
Ed
<Cacho Nakamura> wrote in message news:[email protected]...
Dear all,
I intend to automatically detect network failures from my workstation client
and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive
option. If I understood correctly you can have the workstation generate
periodic keep-alive messages to the server and if these are not
acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for
a disconnection? Otherwise network failures might go by unnoticed if there
are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically
discriminate if the cause is a network disconnection? It is a pretty generic
error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a
network failure, can the system recover on its own? or must I reconnect to
the server? What I mean is, maybe some keep alive messages where lost, the
system passes to the 'disconnected' state, but then the K.A. messages keep
being generated and upon correct acknowledgement of these, subsequent ATMI
calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep
alive message? or is there some sort of tolerance like, say, 'If N messages
in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation
nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Need info about programming with InCopy

Hi,
I have a client who has stored thousands of InCopy documents with valid styles applied to segments of it.
Now my requirement is to create a template which has XML tag -> Style mapping.
Considering that template, I am suppose to open all the InCopy documents, apply that Tag -> Style mapping to it and then convert all of them to XML and persist the data in DB.
Is there a programmatic way as to apply XML tags to a document based on the styles used?
Please educate. I am a complete newbie to InCopy - so please bare with my questions,
Thank you, Appreciate your help.
Regards,
Chintan

You could download and deploy "struts-example.war" from apache website.
          [That Struts 1.0.2 I think.]
          ---Nam
          Jordy wrote:
          > I want to find out how to use it with WL 7.0. Would anyone give me any info about it? :) Thanks
          And God said
          Let there be numbers
          And there were numbers.
          Odd and even created he them,
          He said to them be fruitful and multiply,
          And he commanded them to keep the laws of induction.
          [Bill Taylor [email protected]]
          [nam_nguyen.vcf]

Need deeper info about RPC paradigm

Having scoured the Web for info about RPC, I find the same few discussions repeated widely, but certain things left unexplored. I therefore have particular questions that remain unanswered.
1) RPC server behavior appears predicated around "connect-call-disconnect, connect-call-disconnect, ..." behavior on the part of the RPC client; that is, a connect-and-disconnect around every remote procedure call. I, on the other hand, need my clients to implement "connect-wait-call-wait-call-wait-call-...-disconnect" behavior; that is, to connect, REMAIN connected for an extended period of time across multiple procedure calls, and disconnect only when the client is ready to terminate all use of the server. It appears that svc_run() supports this, but I want to avoid surprises; is there any restriction on this usage of svc_run()? Can this paradigm be supported by appropriate use of the RPC library routines available for replacing svc_run() with my own code?
2) The only "documentation" I have been able to find about how to write actual RPC programs dates back to 1992 and does not come from Sun. Virtually all of the routines appearing in its example programs are designated "obsolete" or "for backward compatibility" in their manpages on Solaris 8. Can you recommend/point to an instructional text that describes RPC programming as it would be done with "today's" interface?
3) Probably the largest single obstacle to my organization's possible use of RPC in "real," critical applications, is RPC's continuing C-specificity. We write all our applications in C++, and mostly object-oriented C++ at that -- whereas RPC appears not to have advanced beyond the "C with global variables" architecture (with one possible exception, following). Code generated by RPCGEN (without the -C switch, I admit; I haven't gotten that far in my trial-and-error experiments, yet) requires extensive hand-editing in order to compile C++ code that uses it, or link successfully with compiled C++ code. This obstacle is severe enough to potentially render RPC an unacceptable solution for us.
The possible exception I mentioned is that I found a webpage that discussed something called 'rpcc,' which appeared to be an object-oriented, C++ implementation of RPC. The page said this was available "on Sun machines," but I don't find it on MY Sun machines. Other searches do not turn up other references. Such a thing would be a godsend if it existed, and it would seem not to be so difficult for Sun's professional developers to create. So does it exist? If so, how can I get my hands on it?
4) Different sources contradict each other as to the "semantics" of an RPC procedure call. Sun's ONC manual says flat-out that Sun RPC provides only "at least once" semantics -- but then, the manual takes the approach that one is using RPC in a "transport-independent" manner. Other references discuss the issue at greater length (hint, hint) and imply that any RPC implementation can provide "exactly once" semantics, providing that one specifically force it to use "a reliable transport such as TCP." It is not clear how much to infer, or disregard, in Sun's simple statement. I need to know FOR SURE whether Sun RPC can be made, forced, tricked, etc. into providing "exactly once" semantics. If so, is "use of TCP" sufficient? Or are other tricks needed? Please outline the necessary steps that might be needed in addition to using TCP.
5) (Related to 4. Sun documentation contains language to the effect that Sun RPC provides "at least once" semantics because providing "exactly once" semantics "would be too difficult." However, a graduate student (at Syracuse U if I recall correctly) posts a research paper in which he describes an RPC facility, developed from scratch, that provides "exactly once" semantics. Apparently it's not THAT difficult, after all. The fact that it's "too difficult" for Sun does not exactly flatter the company. They may want to revisit this, and provide yet another RPC interface (in C++ while they're at it). I won't even charge a finder's fee. ;-) )
Thanks in advance,
Chris

I agree fully.
None of the example code applies to todays
"real-world" applications. Im trying to implement
multithreaded RPC on Solaris using rpcgen's -N
"NewStyle", -A "Auto multithreaded" and -C "ANSI C"
options but none of the examples anywhere show how to
do this. Is their a better technology that everyone
is using now that does a similar thing?I have an example that might help. It's a multi-threaded
NIS server that's been running in production for several
years. There are a few tricks in the source that might help.
You can download the source with anonymous FTP at
ftp.cc.umanitoba.ca. Look in the `src' directory for
midas.tar.Z.

Keep alive a session in CRM

Dear CRM folks -
I am calling CRM using BAPIs. The BAPIs are published as Web Services.
I would like that the session between 2 BAPI calls is maintained in an optimized way so I don't make specific calls to the DB to store my session info.
Anyone knows a way of keeping alive a session in the CRM between 2 BAPI calls?
Thanks !

BAPIs are just basically function modules. Two function modules which are in the same function group are able to share information while the session is open.
If your two BAPIs are not in the same function group(you didn't mention the names or I could have checked) then you can create a wrapper function module which has it's own variables to store the information. Unfortunately once the RFC session/ICM Web Session is closed then you'll lose that in-memory information.
I assume that you're making the two BAPI calls at different times which is why you're having this problem. Like one to get user information and then one more to get some other detailed info once the user inputs something.
Without knowing much about what you are really trying to do, my quick idea is to create a Stateful BSP in CRM which accepts all your requests. The BSP can simply call the BAPIs(eliminate the need for the web service - unless you have some reason you need it) and then between the first and second BAPI call, the BSP will keep the state of the BAPI results in-memory.
If you give more info, might be easier to answer your question.

Keep-alive connection between app and servlet

Hi,
I have searched the forum for information about how to keep a
connection alive between a client app and a servlet, but I have not been
able to find anything.
Does someone have an example of how to do this? Please send it!
Thanks!

HTTP connections are transient, they're not meant to be kept open.
HTTP 1.1 can support this feature, check the RFC and servlet specification (and probably the appserver documentation for configuration).
Best use another protocol though, ftp for example (or something else entirely).

I'm trying to add my airport express to my network. The airport utility shows a message that its gathering info about my network then suddenly an unexpected error message appears. Why is that?

i'm trying to add my airport express to my network. The airport utility shows a message that its gathering info about my network then suddenly an unexpected error message appears. Why is that?

Until Bob Timmons gets back to you, first decide what you would like the Express to do. I understand you want it for AirPlay remote speakers, which you can certainly do.
I am assuming that you are not using an Apple AirPort router; if that's not the case stop here and let me know.
If your existing router is not an Apple AirPort Base Station, the Express:
can "join" an existing wireless network as a client, for the sole purpose of streaming music. If that's what you want to do, do not connect it to your router with an Ethernet cable.
can "extend" an existing wired network to serve as an additional wireless access point, which can also stream music. If that's what you want to do, connect its WAN port to an available LAN port on your router using an Ethernet cable.
Then, "hard reset" the Express according to the instructions below, and configure it. The prompts should be self-explanatory. If you run into trouble, describe which of the above two configurations you decided upon, and the point at which you're getting the "unexpected problem".
To "hard reset" an AirPort Base Station: make sure it's powered up, then gently press and hold its tiny reset button. Don't apply any more force than required to feel a tactile click. Keep it depressed for five to ten seconds, long enough for its LED to flash amber rapidly. Release the reset button. Then, the LED will glow amber steadily for about a minute. Then, it will flash amber, slowly, about once every second or two, waiting for you to configure it with AirPort Utility.

TCP KEEP ALIVE

Hello we have a problem with TCP/IP keep settings.
We have an apllication that after a while (2 hours) doesnt keep its connection,And after that we are taking of timeouts and disconnection from this application.We saw some threads that there a registery TCP/KEEP ALIVE,we already change this registery but
it doesnt help still.Could it be any other solution?Or advice?

I want to configure it to a lower value so that the connection is not closed by routers/firewalls assuming the connection to be idle.For all TCP clients and servers?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime 30000 30 seconds is an absurdly low value. Routers and firewalls will typically close connections after an hour, if at all. So setting it to 30 minutes should be adequate. Setting it as low as you have only exposes you to more network problems: if someone has a cable out for 30 seconds you will get disconnected, even if the cable was put back after 31 seconds and even if your application doesn't actually exchange data every 30 seconds. Don't do this.
Is there a standard way in which the keep alive time can be configured on all OS platforms? No.
If not, is this a standard way of changing keep alive time for java applications on windows?The registry keys might differ from version to version. It's a Windows question, not a Java question.
Is it necessary that the machine be restarted on changing keep alive time or is there a specific time by which the new keep alive time would be picked up during run time or on restarting the java application?Another Windows question.
But I would review your requirement. More likely you should be building application pings into the applications that actually need them.

HFM Web Sever Configuration--Keep Alive and Session Time Out Optimal Config

We recently implemented an HFM 9.3.1 environment. We are using Windows 2003 Enterprise SP2 servers with IIS6. We have two HFM Web servers connecting to an application cluster with two application servers in the cluster. We were getting some errors when trying to unlock HFM cells in Workspace, but we were able to perform the functions fine on the application using the WIN32 client.
I opened a ticket with support and they recommended modifying the subcontext.properties file located in %HYPERION_HOME%\deployments\WebLogic9\servers\Workspace\webapps\workspace\conf. They recommended changing the following settings:
#KeepAliveInterval=30
#SessionTimeout=60
From what I understand, these settings are for the communication between the HFM Web Servers and the application cluster servers. I'm wondering how changing these settings may affect our environment. Are there negative effects and/or trade-offs for changing these settings? Is there a recommended threshold or maximum value?

Hi Dinesh,
This cannot be achieved without development enhancements to some standard SAP framework component, to introduce a "keep-alive" concept. If you are using a CMS for CTI or email integration, you need to ensure it supports keeping the communications session alive also.
Sincerely,
Glenn
Glenn Abel
Covington Creative
www.covingtoncreative.com

Keep-alive problem in apache/weblogic

I have a server with Weblogic 5.1 and Apache
1.3.12 with the weblogic-plugin.
When apache serves pages, the keep-alive works
fine.
When weblogic serves pages, the keep-alive works
fine.
When i added a handler in apache so all requests
to apache should go to weblogic through the
plugin, the keep-alive stopped working.
Anyone seen this before?
Gunnar

send a message to [email protected] with as much info as you can. i d
on't think they're watching the newsgroups for bug reports.
maybe someone who frequents the newsgroups regularly could do a FAQ...
anyone actually got time?
"Gunnar" <[email protected]> wrote in message
news:3a51995e$[email protected]..
In case anyone wondered:
I tried with sp5 and sp7 and everything worked fine. It seems sp6 is
buggy...
Gunnar <[email protected]> skrev i
meldingsnyheter:3a41e618$[email protected]..
I have a server with Weblogic 5.1 and Apache
1.3.12 with the weblogic-plugin.
When apache serves pages, the keep-alive works
fine.
When weblogic serves pages, the keep-alive works
fine.
When i added a handler in apache so all requests
to apache should go to weblogic through the
plugin, the keep-alive stopped working.
Anyone seen this before?
Gunnar

MessageQ keep-alive. Info about client disconnect

Similar Messages

Maybe you are looking for