A lot of CALL_FUNCTION_OPEN_ERROR in production environment

Hello
We have a lot of CALL_FUNCTION_OPEN_ERROR in our production environment.
An error occurred when executing a Remote Function Call.
"Protocol error when communicating with SAPGUI."
Status of connection.... "RFC DRV=GUI INPUT"
Internal error code.... "RFC_IO20"
When communicating with SAPGUI, a protocol error was detected.
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_FLUSH_CALL_INTERNAL".
The main program was "RSPOLPRF ".
WE get these errors when user have 5 sessions open and then they start a printout.

Hi,
I am not sure about what is causing the roblem in your system. Did try to find the error on the forum. Most of them refer sapnote 1079446 . Kindly have a look if this can be of any help.
Thanks,
Bhavnesh

Similar Messages

Redeploy in cluster in production environment

There is a cluster consisting two node in a production environment. The purpose is to make it possible, to upgrade a deployed application to a new version, with the highest avaibility. Is it possible to do it faster than the standard Redeploy method? Couse it lasts an hour at least, and during that time the application cannot be accessed.
          Ideal would be that it could be done without service breakdown. /On one node the application keeps running, on the other at first it is redeployed, than the while the second is restarting the former stops and then that is redeployed too./
          Is it Possible? Or any other way to solve that?

Hello Mathers,
          Why does it take an hour to redoply your app, are you precompiling JSPs on startup or do you have a vast number of EJBs, lots of connection pools with connections that are all created on deployment etc?
          Can you explain your deployment process and are you using WLS staging?
          A redeployment of the application I am currently working on (three ear files approx 100 EJBs and 3 web apps) takes about 15 minutes on each managed server, so we have about 15 minutes of down time. But I think I can get this down to 5 minutes without too much trouble.
          cheers
          Hussein Badakhchani
          www.orbism.com

RE: Production Environment Definition

Brad,
We use connected environments so that we do not have a single point of
failure.
We use multiple environments and connect them together in a star topology
for reliability of service. Our servers (23 in total) sit out at branches
in the back of beyond and the WAN connections between the servers are
unreliable. One needs a reliable connection to the Name Service which sits
on each Environment Manager. We have thus created 23 connected
environments with an Environment Manager on each LAN. Connected
environments are still a bit buggy but Tech Support is currently working on
fixing the last of the problems. We are still on ver 2H15 for this reason.
Disadvantages of this topology are that making distributions take a long
time because referenced partitioning cannot be scripted in fscript and
econsole only connects to one environment at a time.
There is a Forté consultant in Denver called Pieter Pretorius who has had a
lot of experience with our connected environments. It may be worth
chatting to him.
Regards,
Richard Stobart
Technical Consultant for Forté
E-mail [email protected]
Quick-mail: [email protected]
Voice: (+ 27 83) 269 1942
(+27 11) 456 2238
Fax: (+ 27 83) 8269 1942
-----Original Message-----
From: Brad Wells [SMTP:[email protected]]
Sent: Tuesday, February 10, 1998 11:52 PM
To: 'Forte Users - Sage'
Subject: Production Environment Definition
Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

SOA OSB Deployment best practices in Production environment.

Hi All
I just wanted to know the best practices followed in production environment for deploying OSB and SOA Code. As you are aware that both require libraries from either (Jdev or SOA Suite) and (OEPE and OSB)? Should one rip the libraries and package them with the ANT scripts (I am not sure but SOA would require its internal ANT scripts and lot of libraries to be bundled, OSB requires only a few OEPE and OSB libraries) or we simply use the below:
1) Use the production run time (SOA Server and OSB Server) to build and deploy the code. OEPE would not be present here, so we would just have to deploy the already created sbconfig.jar (We would build this in a local environment where OEPE and OSB would be installed). The code is checked out from a repository and transferred to this linux machine.
2) Use a windows machine (which has access to prod environment) and have Jdeveloper, OEPE and OSB installed to build\deploy the code to production server. The code is checked out from a repository.
Please let us know your personal experiences with the deployment in PROD. Thanks a lot!

There are two approaches for deployment of OSB and SOA code.
1. Use a machine specifically for build and deployment which will have access to all production environments (where deployment needs to be done). Install all the required software (oepe, OSB etc..) and use remote deployment for deploying the code.
2. Bundle all the build and deployment related libraries and ship them as a deployment package on the target server and proceed with the deployment.
Most commonly followed approach is approach#1.
Regards
Vivek

Production Environment Definition

Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

I want to deploy AIR application in production environment. Will the licence for AIR is free?

Please let me know the licence details. Shall i have to pay any thing if i want to use in production environment.

Just after the 2012 Macs were released there were a lot of crashes involving those machines that Chrome got the blame for. By the time I got my hands on a 2012 MBA Chrome had been updated at least twice (plus it was never clear which version of Chrome was implicated, assuming it was the cause to begin with). All I can say now is that I've not replicated the issue with the last two versions of Chrome.

Deploy in production environment

Hi,
I have to deploy a bpel client application in OracleAS 10.1.3 in production environment. In bpel_services.properties and wf_client_config.xml there are informations unknown to the developer. The deployer knows this information but he doesn't want to modify the ear file.
Is it possible to configure the informations in this files during deploy without modify the ear file ?
Thanks

Thanks a lot!
So it seems that .rpd file IS NOT portable between environments, but it is possible to change params via scripting.
It is surely better than changing via interface, though not ideal.
Any other idea around?
Edited by: user10676624 on 19-dic-2008 1.13

Spawn setting in production environment

Has anyone heard or been told by oracle analyst that Oracle doesn't support spawn setting in production environment?
Answer that I received was enabling spawn can be flaky. The domain may easily hang without explanation and it's always been like that, so we don't support spawn in production.
We have 16 GB of memory
[PSAPPSRV]
Min 10
Max 25
Spawn Threshold=1,30:2,10
According peopletools performance guideline, CRM and HRMS use about 100-150 MB per application server process. We have lots of customization, so I will just bump it up to 250MB. If we are to disable spawn by setting min = max to 25, this means the app server process will constantly use at least 6GB of memory. We should still be able to avoid the memory issue, right? Unless my calculation is wrong...
I would like to hear more opinion and advice here.

Hi,
created Asset number ranges-AS08

Topology for production environment

this question is related to production environment deployment and clustering.
we have 1 physical server where we have webcenter domain. this domain has 1 admin server and 1 managed server (custom web center portal managed server).
our plan is to deploy our application on this managed server.
this is no clustered environment and not recommended (no failover, no load balancing).
what shall we do?
shall we create another managed server (custom web center portal managed server) and deploy our application on these 2 managed servers? there will be a load balancer in front to take care of transferring request to both the servers...
what's your suggestions?
please note that i know specific answer will depend on NFR (user load, performance etc) but i am looking for general guidance and reference around same like -
how many managed server recommended?
what kind of topology recommended for web center application?
etc
thanks.

jiri.machotka wrote:
I'd recommend you to start with this document: http://docs.oracle.com/cd/E11035_01/wls100/cluster/overview.html as a lot of this question is related to Weblogic clustering than WebCenter.
Note that whilst clustering has many pros, it has also few cons; among those:
- you might require additional hardware/software, or used components (like filesystem) will have to have features that you don't need in a non-clustered environment
- though small, scaling does consume some resources (I've heard that WebCenter Content takes 1-2% of Solaris, but up-to 25% on Windows Servers!)
- it's always at least a bit more expensive
Therefore, you should not go for a cluster, because it's cool, but because you have damn good reasons for that (that you didn't mention!), stemming from SLAs, or requirements for Disaster Recovery.
You write that you have just one physical server, so you already have one potential single point of failure.
I think I've heard that Weblogic Server itself is capable of self-recovery; this means, that a server may go down (you will lose all the current sessions), but is capable of auto-recovery. If your users survive that from time to time they will lose uncommitted work, then maybe a need for clustering (HA) won't be that strong (you might also go just for tuning your Weblogic Server).
On the other hand, where clustering might be necessary, if you need to scale, especially, if you need cloud-like increase/decrease of resources. I doubt it is possible to say up-front how many servers is recommended, but you may tune this later - whilst going from 1 node to 2 is relatively a big leap, going from 2 to 3, or 3 to 4 is then quite easy.
Either way, I'd recommend you to be in sync with your app server admin.thanks jiri. this was helpful.
while i agree that any architectural decision should be justifiable to requirements but as far as my experience goes clustering is basic thing in any production environment... in case 1 managed server goes down, other can still serve requests...
i'll read link provided by you and ask specific questions if any...
thanks.

Unable to import the Internet servivce into Production Environment

Hi,
We put the internet service and its HTML templates in a custom package for integrated ITSMobile. We got everything but the internet service ZXXX in the production. Has anyone come across this before? We were able to transport to the quality system. But it did not create the internet service in the production environment. Is it authorization issue? Your input will be highly appreciated.
Regards,
Subbu

Hi Subbu,
I suggest you to as your basis guys how are familiar with transports between systems. They will find out what the reason is. Without being able to look into transport protocols it is unlikeliy that someone here can advise you.
Regards,
Klaus

Issue in production environment

Hi,
We got an issue in the production environment on last Friday and yet not able to find out the root cause of the issue.
Environment
GUI : .Net
Server : Java
Application Server: Jboss
Database: Sqlserver
The Java application is deployed into Jboss application server which connects to SQL server as back end. GUI makes the web service call to server for data communication
Issue
Friday at 2 PM users reported the slowness of the application (Not getting the response from server in GUI), all the request from GUI were getting timed out.
Restart of Jboss didn't help
Restarted the Jboss and sqlserver for the second time and than the environment became stable
Analysis
1. From the thread dump of Jboss log we see that there are many threads waiting on a socket for database connection(according to database team all the connections are open and available at that particular time).
2. The size of transaction log is almost doubled during this period (when the issue was reported).
We couldn't find a reason why this issue is happened. Is it a database issue or something else? Please suggest...
Thanks,
Manoj

Hi Manoj,
According to your description, when running the web application, many threads are waiting for the socket from database which cause requests from front GUI time out. Right?
In this scenario, user can access the front GUI, which means the application server is working. Since the connections are all open at that particular time, it should not be issue on your JDBC. It seems to be a deadlock issue which cause other threads
waiting and hang. I recommend check and optimize your code. On database side, I suggest you open the SQL profiler, select DeadLock Graph, it will record when deadlock occurs. Please refer to links below:
Detecting and Ending Deadlocks
Analyze Deadlocks with SQL Server Profiler
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Development and product environment

Dear all,
I want to setup two databases in seperated server. One for development purpose and another for product environment.
Which good method/tool in oracle can transfer data (like pl/sql,tables,fields) from
development to product environment?
Thanks you

I would strongly suggest cloning the database from Development to Production, using RMAN. You get a proper copy that way - and it isn't hard to do. Howard Rogers has all the answers here: http://www.dizwell.com/prod/node/9

APO-DP - Change in Calculation Type of Key Figure in Production Environment

Hi Team,
I wish to know how to make a change in Calculation Type of Key Figure in Production Environment. I wish to change calculation type from "P" to "S" and also wish to enter Disaggregated Key Figure.
Regards,
Tarun Jha

HI,
The TR will not move the changes as you are expecting here.
Any changes to planning area, below 5.0 need to de-intialize the planning area.
just like
1. hold the latest back up
2. de-intialize planning area
3. make the required changes to planning area
4. initialize planning area and do conisistency checks
5. load back the data to planning area at all CVC level
all the steps need to perfom, in Dev and Quality and Production servers,
Plan the activity for a weekend so that users will not get disturb*
All the best
ARUN R Y

Security Issue httpOnlyCookies="true" is not working with production environment

Dear All,
I have tired to make set cookie value as httpOnly
The development environment is working fine and give me an output like that
Set-Cookie
WSS_KeepSessionAuthenticated={3644d93c-d1d3-46cd-845f-42c01640ab21};
path=/;
HttpOnly
But when implement the same changes in web.config production environment its not working
Set-Cookie NLSessionCdomainweb=a98q9jnsy0vXk5+RHeHnlKmM+HnneA9KmhIAR6g1bJiwTs8sD6d7dfV1gBffc8HiJXBowxdO8LhZAiIEKiFY6PzNWySyRs5rvgCfPu8XIFnqKcN4XQ4UL9PN3JI3f4E6;path=/;domain=.domain.com
I am using sharepoint 2010, under web.config i made the following changes
Add following tags under system.web
<httpRuntime maxRequestLength="2097151" enableVersionHeader="false"
/>
<httpCookies httpOnlyCookies="true"/>
Add following tags under <system.webServer>
  <httpProtocol>
      <customHeaders>
               <remove name="X-Powered-By" />
             <remove name="MicrosoftSharePointTeamServices" />
      </customHeaders>
    </httpProtocol>
Can any one tell me why it's happening i have checked all possible reasons from my side but no success
Regards
Rashid Bilgrami
RB

Hi,
From your description, I know you want to set cookie value as httpOnly but it is not work.
Please try to add codes below to your global.asax file:
<SCRIPT language="C#" runat="server">
protected void Session_Start(Object sender, EventArgs e)
try
if (Request.IsSecureConnection == true)
                Response.Cookies ["ASP.NET_SessionId"].Secure = true;
catch (Exception)
</SCRIPT>
Please refer to this article:
https://social.technet.microsoft.com/Forums/sharepoint/en-US/0fe55c13-3911-422e-af17-cb5c1ab2abd7/missing-secure-httponly-flags-on-sharepoint-2010-cookie?forum=sharepointadminprevious.
Best Regards
Vincent Han
TechNet Community Support

Problem on developing SSRS report in a production environment

Any problem could be caused if have to develop SSRS report in a production environment ?
If so, how it can be prevented?
Thanks!

Hi ,
As per my understanding, Normally our environment setup contains Development,testing,preproduction,production and its varies from company to company.
We develop SSRS report in development environment and after testing we deploy it to production report server.
Development environment use development database for creating report like your database IP and credential will use development environment
setup. and production environment use production database for creating report like your database IP and credential will use production environment setup.
Thanks
Neha Prajapati Please Mark This As Answer or vote for Helpful Post if this helps you to solve your question/problem.

A lot of CALL_FUNCTION_OPEN_ERROR in production environment

Similar Messages

Maybe you are looking for