Call drop when VXML server goes down

Can somebody tell me what should ideally happen in the below given scenario?
We have two media/vxml servers. We have a ACE load balancer which sends calls to these two servers. When the customer call is sent to CVP for self service (VXML application) , if the VXML server is shut down (via the CVP OAMP) , should the call drop ? or survivability kicks in the gateway ?
What we saw is the call is dropped after 2-3 seconds of silence.
We see in the CVP PIM logs that " called party disconnect" event and ends the call. Similarly in the gateway we see the transport down message and discnnects the call. is this correct?
Is there any way to preserve this call and treat it?

Hi Shravan,
If you had configured survivability then ideally that call should hit the survivabilty. Normally on the VXML Gateways survivability is not auto configured, we would need to configure accordingly depending on the requirement. If survivability is not configured then the call would disconnect
Additionally, could you please let us know the call flow for the self service in your setup
Thanks,
Dass
Please rate useful posts

Similar Messages

ACE slowness issue when one server goes down

Hi,
We are having two application servers.Both are load balanced using ACE.
When we bring down one server, we find that when we upload some files into the second application server, its too slow.
But when primary server comes up again the performance increases.This issue happens only when we bring the primary server down.
We are using cookie based stickiness.Any ideas where we can look into.
Rgds.,
Sachin

Depending on the load-balancing algorithm or predictor that you configure, the ACE performs a series of checks and calculations to determine which server can best service each client request. The ACE bases server selection on several factors including the source or destination address, cookies, URLs, HTTP headers, or the server with the fewest connections with respect to load.
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA1_7_/configuration/slb/guide/classlb.html

How to show an error Page in Weblogic when the server is down

Hi ,
I heard that every container has the facility to show an error page when the server is down and (when the request has arrived at that time ).
Please tell me how to configure this in BEA weblogic ??
Thanks .

Hi,
From my understanding weblogic dose not provide the thing which you are asking for, reason is given below.
- An application is deployed only on managed server one (MS-1)
- Now if the request comes to the server (MS-1) when it was running and then for some reason MS-1 goes down then weblogic server would be able to send any response back to the client as its down.
- Hence nothing can be done as the request object is been lost when the server goes down or even cant redirect to an error page as for doing that too the server has to be up and running.
However there are other way round which can help you overcome this issue as shown below
- Use Clusters with few managed servers in it which gives you high availability and load-balancing.
- Use any web servers like Apache in front of weblogic servers.
Using the above things you can also use customized HTTP Error Responses with error-page element in web.xml and create your own error pages which can be re-directed for the web server side also. For more information go through the below links
Topic: Customizing HTTP Error Responses
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webapp/configurejsp.html#wp157884
Topic: error-page
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/web_xml.html#1017571
Topic: ErrorPage
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1155425
Hope above information helps you.
Regards,
Ravish

Server Goes Down Alert

Hello,
I am running SCOM 2012 R2 and I am trying to setup an alert to let me know when a server goes down. I tried creating a rule that monitored the Management Server's "Operations Manager" Event Log for ID 20022. I also configured
the rule that parameter #2 must have my servers name. I also tried EventDescription conatains my servers name. None of them worked. But I looked in the Event Log of my Management Server and as I looked at all of the 20022 entries, I noticed
the computer I was on was listed as not heartbeating. Two of my other servers that are currently on were listed as not heartbeating. So obviously monitoring this 20022 entry is not reliable. I do not want to setup a monitor for something
like Ping Status. I want to try to avoid using monitors because they could be taxing on the servers, my management server, and my network.

Hi
yes event id 20022 is not reliable and never go for windows event id monitor for server shutdown or unavailability on agent , as scom health service will be stopped or connection closed with MS at the time of shutdown on agent.
you need to go for ICMP port monitoring for server availability, as port monitoring run from remote server(watcher node) and can capture server unavailability and ping test.
refer below link for port monitoring
http://technet.microsoft.com/en-us/library/hh457544.aspx
http://www.systemcentercentral.com/custom-tcp-port-monitoring-management-pack-for-scom-2012/
regards
sridhar v

How can a JMS Listener Notified get when a Topic Server Goes Down?

I'm in the process of looking into pub/sub model for a centeralized data source where vertical applications subscribe to a topic to get updates on person demographic information.
          I was playing with the JMS topic examples and noticed that when I have a Durable Subscriber listener (java main) and the topic Server goes down. It never gets notified. When I restart the Topic server and send msgs to the topic, the Durable Listener doesn't get them.
          Once I restart the Durable Listener (java main), it receives all the messages that were pending.
          I implemented the ExceptionListener and it never gets a shutdown msg either. I shutdown the Topic server via Ctrl-C, Graceful Shutdown and Forced Shutdown.
          Is there a way for the client listener to determine when the Topic Server went down, came backup, and restore the connection to it automatically? Or do we have to implement some type of ping mechanism on the client listener and re-create the connection ourselves?
          Thanks. Later...
          - Wayne
          Edited by wlau1000 at 03/07/2007 8:34 AM

Hi Wayne,
          I think the exception listener should have fired. Some comments/questions:
          - Does your app call "connection.setExceptionListener" in addition to implementing ExceptionListener?
          - Which version and maintenance/service pack are you using?
          - Is the client using the wl* "thin" client jars or the "thick" client jar?
          - Version 9.2 provides an automatic reconnection capability for consumers. This behavior isn't enabled by default due to natural side effects that some apps might not be prepared to handle (needles to say, I recommend reading the doc thoroughly).
          http://edocs.bea.com/wls/docs92/jms/recover.html#wp1320125
          Tom

JMS Exception when server goes down (Urgent) ?

Hi All,
I have three topics in the JMS Server which is on the top of Web logic server 8.1.
On the client side I have Swing thick cleint.For each topic I have a listener.
When the web logic server goes down ( I shut down manually ) Only one listener is recieving the Exception and the Swing client reacts accordingly.
After this ,
Client continousoly checks whether the server is up or not. Once the server is up again the Exception is thrown that server is down ( I guess now the second listener is recieving the message).
After some time again the third listener recives the message.....
and the client reacts on that exception 3 times.
How can I get rid of this ?
thanks in advance.
san

Hi,
this is probably a very good question to ask support. 'Logical' deployment sequence
was added to the WebLogic only recently (6.1sp?) ('logical' means that first datasources
are deployed, then EJB's and then web-apps, deployment-order parameter was added etc).
So, for applications where shutdown sequence is important there must be a document which
describes how server shutdown works.
On the other hand, this may not be as important as deployment sequence, because running
instance can crash at any time and it should not affect anything.
Jen <[email protected]> wrote:
Repost
Hi,
Most of my ejbs use connection from the connection pool. At the weblogic server shut
down time (heavy load), I can see the jsps call the ejb, sometime jsp can't find
the bean because it's removed from jndi. sometime jsp found the bean but when the
bean try to talk to database, ejb can't use the connection because the datasource
is removed from jndi. Also my shutdown class waits for the threads finish up, and
the threads calls the ejb and do the db operation, and the conn is cut when the db
operation is half way. So, the order of events when server shut down is important
to me. I am wondering how other people deal with it. Thanks --
Dimitri

Planning server goes down when I try to delete a member in Planning Web

Hi,
Planning server goes down when I try to delete a member in Planning Web. I am using Hyperion Planning 4 with Tomcat 4.1.30 and Windows Server 2003.
I am not sure whats happening. This is the exception log I am looking at:
2009-07-24 18:19:22 ApplicationDispatcher[HyperionPlanning] Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
     at org.apache.catalina.valves.ErrorDispatcherValve.custom(ErrorDispatcherValve.java:420)
     at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve.java:327)
     at org.apache.catalina.valves.ErrorDispatcherValve.throwable(ErrorDispatcherValve.java:277)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:179)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
java.lang.OutOfMemoryError
2009-07-24 18:19:22 ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=500, location=/Error.jsp]
javax.servlet.ServletException
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
     at org.apache.catalina.valves.ErrorDispatcherValve.custom(ErrorDispatcherValve.java:420)
     at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve.java:327)
     at org.apache.catalina.valves.ErrorDispatcherValve.throwable(ErrorDispatcherValve.java:277)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:179)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
java.lang.OutOfMemoryError
Please do help me........ how to resolve this.
Thanks.

Hi,
You could try increasing the java heap size, though sometimes an issue can occur if you are trying to delete a member when a workflow process has started, do you have one running?
Cheers
John
http://john-goodwin.blogspot.com/

Is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down?

Question:
When the Database is shutdown gracefully everything was fine.
But when the Database is brought down with shutdown abort the MDB consumer will never consume messages from the topic again. And we need to restart the WebLogic Server in order to get the messages consumed again.
So is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down? If not, what type of failures will require the JMS/WLS restart?

On a DB failure, a WL JDBC store service will make a brief attempt to reconnect before shutting itself down along with any services that depend on the store.
It isn't necessary to restart the entire WebLogic Server JVM to bring the affected service(s) back if you can use the Automatic Service Migration feature. ASM can automatically restart a failed service on a different WL Server in the same cluster, and/or can try a restart-in-place for the service if the service's original host WL Server JVM is still running. The Automatic Service Migration (pdf) white-paper has a thorough discussion of this area.
In addition to ASM, there's also a "whole server migration" option that can automatically restart or migrate an entire WL server.
Tom

Redirect to a custom error page when Forms Server shuts down

Hi,
I want the forms application to redirect to a custom error page whenever Forms Server goes down. (like network issues, unscheduled shutdown...) Whenever this happens, the user gets a pop up with FRM messages and user has to acknowledge the pop up. Since the application is used in the shop floor, there will not be any user always in front of the screen and will be a very big issue as there are at least 70-80 PC's on the floor which will be attended fewer times(only when there is issue with the machine) other wise the application displays important events of the machine,etc.,
I am trying to develop a simple HTML error page(may be with applet) which will keep querying the forms server and once the forms server is up and running, the error page will revert back to the application which the user was working earlier to shutdown. Other option is the redirect to main menu of the application (this may be a PSP or a JSP or a Oracle Forms Menu ).
Is there any event in forms to capture the loss of connection to forms server ??
BTW, I am using Oracle Application Server 10g Forms and Reports on Windows 2000 Server...
Any ideas...
Thanks in advance
Purush

I don't think it will be easily possible in Forms for a couple of reasons.
1. In Forms you do not have query rights, and as soon as you want to edit data, you have to log in. In Forms you log in once, and this sets your rights for the whole session. You will have to do some programming in Forms to achieve what you want. E.g. as soon as you hit the Save button you are asked for a username and password.
2. A refresh cannot be done in Forms. Remember that Forms is a Java applet. The URL in the browser is just pointing to the startup page only. If you refresh your screen, you are taken back to the login screen of Forms again.
Well, there will probably be ways around these problems. I'm thinking in the line of calling every form in a separate URL instead of starting a Forms application where one form is called from another form. The default 'query only' form can be called from a startup html page. This page can be refreshed. As soon as the user wants to update data, he clicks on a link or button and is taken to a login form.
If the refresh is unsuccessful you are taken to a custom error page, like in your ASP application.
A problem with an automatich refresh may be hanging sessions. Forms server does not always kill sessions.
And also, how would you avoid a refresh if a user is currently using the form?

Load balancing - what happens if a server goes down?

Hi, Just an academic question.
Assume I have 2 DA servers behind a BIG-IP load balancer, named DA1 and DA2.
If I enable Load Balancing (BIG-IP in my case), what happens to the clients already Connected to DA1 when IP-HTTPS is used?
For example:
Client1 is connected to BIG-IP, which in turn redirect this client to DA1-Server. Assume that DA1-server goes down, what happens with the client then? I assume the Client will be redirected to DA2-server by BIG-IP after some time, meaning it will have to establish
the connection from scratch. Is this correct and roughly how long does it take for the clients to connect to the DA2-Server?
Since IP-HTTPS is using it's own pool and IPv6 prefix per DA server, I assume this will happen? And the DA client1 will receive a new IPv6 address from DA2 ?
Thanks!

Hi,
It depends of the way your Big-IP is checking the servers in your pool.
The client will try to reconnect to the HTTPS interface and still be redirected to server1 until your Big-IP validate that the server1 is not responding and disable it.
And yes, you'll receive a new IPv6 address because each server in a DirectAccess NLB cluster has a specific IPv6 range for the clients.
Gerald

Problem in creating Jtree instance when X server is down

I am facing this problem while trying to build JTree object when X Server is down
I am using Redhat 8 and jdk1.3.1
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Problem creating javax.swing.plaf.metal.MetalLookAndFeel with method getSystemTextFont and args { : java.lang.reflec
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:993)
at javax.swing.UIDefaults$ProxyLazyValue.createValue(UIDefaults.java:670)
at javax.swing.UIDefaults.get(UIDefaults.java:145)
at javax.swing.MultiUIDefaults.get(MultiUIDefaults.java:46)
at javax.swing.UIDefaults.getFont(UIDefaults.java:223)
at javax.swing.UIManager.getFont(UIManager.java:456)
at javax.swing.plaf.basic.BasicTreeUI.installDefaults(BasicTreeUI.java:5Xlib: No protocol specified
Problem creating javax.swing.plaf.metal.MetalLookAndFeel with method getSystemTextFont and args { : java.lang.reflec
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:993)
at javax.swing.UIDefaults$ProxyLazyValue.createValue(UIDefaults.java:670)
at javax.swing.UIDefaults.get(UIDefaults.java:145)
at javax.swing.MultiUIDefaults.get(MultiUIDefaults.java:46)
at javax.swing.UIDefaults.getFont(UIDefaults.java:223)
at javax.swing.UIManager.getFont(UIManager.java:456)
at javax.swing.plaf.basic.BasicTreeUI.installDefaults(BasicTreeUI.java:591)
at javax.swing.plaf.basic.BasicTreeUI.installUI(BasicTreeUI.java:525)
at javax.swing.plaf.metal.MetalTreeUI.installUI(MetalTreeUI.java:83)
at javax.swing.JComponent.setUI(JComponent.java:322)
at javax.swing.JTree.setUI(JTree.java:537)
at javax.swing.JTree.updateUI(JTree.java:553)
at javax.swing.JTree.<init>(JTree.java:513)
at javax.swing.JTree.<init>(JTree.java:489)
at javax.swing.JTree.<init>(JTree.java:472)
at com.cygnet.constel.cygSdk.cygJS.CygTree.<init>(CygTree.java:15)
at com.cygnet.constel.cservs.cygManageIpInit.StringCreator.getDetails(StringCreator.java:54)
SampleTree.java Source code .
import javax.swing.tree.* ;
import javax.swing.* ;
public class SampleTree extends JTree
     public SampleTree() {
          super() ;
     public SampleTree( Object[] value ) {
          super( value ) ;
     public SampleTree( TreeModel newModel ) {
          super( newModel ) ;
this is the line creating problem
when my class is trying to call super( root )
     public SampleTree( TreeNode root ) {
          super( root ) ;
     public SampleTree( TreeNode root, boolean asksAllowsChildren ) {
          super( root , asksAllowsChildren ) ;
NOTE : when i log in to X server JTree object gets constructed properly
My requirment is it should also get constructed properly , even if X is down.
i tried hard and i am frusted
any help is appreciated
thank in advance
-- Nilesh

thanks thomas for your reply
but i think , we need to find out the point where it actually gets environment settings
there must be 2 things done before creation is done.
1]
Actual Construction of the Tree
2]
then getting look and feel of the underlaying OS
if we can find out step between 1 and 2 , we will get the problem ...
what say ??
dont think i am giving any suggestions to you . this is just what i think.
Please let me know if any of ur friends are facing the same problem.
-- Nilesh

OCILogon returns success when TimesTen server is down which causes app core

In our failover testing, when the primary TimesTen server was brought down, the OCILogon call returned OCI_SUCCESS with a service handler. However the OCIServerVersion call which immediately follows the OCILogon call caused the application to core with signal 11.
Below is the stack trace in the core:
#4 0x00000001001e7ab0 in crash_handler (sig=11) at Main.cpp:1632
#5 <signal handler called>
#6 0xffffffff7ccc736c in lsfp ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#7 0xffffffff7c5ecc70 in x10verVersion ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#8 0xffffffff7c5e42d4 in x10odr ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#9 0xffffffff7c31df94 in upirtrc ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#10 0xffffffff7c31d63c in upirtr ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#11 0xffffffff7c5dfcf8 in upiver ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#12 0xffffffff7c461a98 in kpuvers ()
from /tools/timesten-11.2.1.5-64bit/TimesTen/ttclnt/ttoracle_home/instantclient_11_1/libclntsh.so.11.1
#13 0x00000001002451e4 in COCISession::get_server_version (this=0x1029b6ad0) at ocisess.cpp:270
Does anyone know why OCILogon returns success when the server is down? And how can I tell if the server is down?
Thanks!
Cathy

Hi Cathy,
I'm not in a position to check this out right now but it certainly looks like a bug. Are you able to log an SR on this so we can get it into the system?
Thanks,
Chris

IOException when remote client goes down in Linux

Hello all -
This my first post here. I have ran into a bit of an issue with some code I have written. I have written a small client/server application that works on the premise that if the remote application ends, the socket will be broken, and an IOException will be thrown. I then catch the IOException and then end the particular thread associated with that socket. This works fine in Windows, but when I kill the remote application in Linux, an IOException is never thrown on the server, it's as if the socket is still there even tho the application ended. I'm thinking there is something different that happens when I kill a process in Linux vs Windows. I have tried using the SIGINT, and SIGTERM switches for kill but they made no difference. Does anyone have any idea, admittedly I am a Linux noob, thanks!
-Kam

If the server is reading when the client goes down it won't get an IOException, it will get an EOS condition: read() returns -1, readLine() returns null, readXXX() for any other X throws an EOFException.

Functionalities Available if Server Goes Down?

Hello! As a structural question...... I have a web server that holds my web application (includes My Sites), and an application server with CA and all of the other services.
Suppose the web server goes down. Does that mean my users no longer have access to the site, their profile, and their document libraries?
Conversely, if the application server goes down, will my users still have access to the site, but none of the services will work? (IE. Will the site still communicate with the databases to pull documents information from their documents library; I just can't
use search, etc.)?
Thank you!

Suppose the web server goes down. Does that mean my users no longer have access to the site, their profile, and their document libraries?
Correct. If the server hosting the Microsoft SharePoint Foundation Web Application Service goes down then you will lose all access to the sites.
Conversely, if the application server goes down, will my users still have access to the site, but none of the services will work? (IE. Will the site still communicate with the databases to pull documents information from their documents library;
I just can't use search, etc.)?
Thank you!
Again correct.
Depending on what exactly you've put on the App tier and on the WFE tier you may still have working sites. If there's a component that is needed to render a page such as the MMS or Excel Services that runs on the App tier then that page will throw an error
but the general document library pages and so on will probably still work for the most part.

Why Portal server goes down?

Hi All,
We are currently running on EP7, SP9.
Suddenly one day our portal server went down.We checked the logs but could not find the correct information. Can any one of help me as why our server went down at that particular time.
Please reply as soon as possible.
Thanks in Advance.
Regards,
Ramalakshmi.S

Portal server goes down for several reasons:
1) Check the portal license. If the trial license expired, it goes down every 30 mins.
2) Check your J2EE settings. If the portal cannot handle the user requests, you should increase the MaxThreadCount and other parameters.
3) Check the trace files at D:\usr\sap\<SID>\JC01\j2ee\cluster\server0\log
Hope this helps.
~Yasin

Call drop when VXML server goes down

Similar Messages

Maybe you are looking for