Multiple Server nodes in Java Instance

Hello Experts,
We have NW 700 SP17 Java system running with 5 server nodes. Would appreciate, if you clarify following doubts:
1. How can we check which user has landed up into which server node.
2. Is there any possibility of check logs (like defaulttrace,etc) for all the server nodes from a single location (like NWA).
3. How can we check the load on each of the server node.
4. Where can we find documentation on configuring and operating Java instance with multiple server nodes.
Thanks
Davinder

1. How can we check which user has landed up into which server node.
Ask the user to execute this: javascript:document.cookie
while they are in the Java pages.
2. Is there any possibility of check logs (like defaulttrace,etc) for all the server nodes from a single location (like NWA).
- Yes, SAP LogViewer should give you that options
3. How can we check the load on each of the server node -
- Consider configuring Solution Manager Diagnostics, is it very nice tool for Java Load Monitoring
4. Where can we find documentation on configuring and operating Java instance with multiple server nodes
- If you asking about how many nodes requires on a java instance, you might want to use the SAP Quick Sizer to size your systems, then it will give you total Memory it requirsts then you need to divide that by 2.5 GB (64 bit OS) or for 32 bits they recommend you not to exceed your heap size beyond 1 GB.
Added Nodes is very simple via Configtool, then you might have to setup your server with same settings as your previous nodes.
Kumar

Similar Messages

Does GRC AC 5.2 supports multiple server nodes

Hello Experts,
Does GRC AC 5.2 is supported with multiple server nodes.
Thanks
Davinder

Thanks once again Harleen,
For AC 5.2 i will raise an SAP OSS message and share the results with community.
For AC 5.3, we have configured SAP logger and make neccesary changes in NWA. But log information over here is not as detailed (background job information is missing) as we get in RAR -> Background Jobs ->View Logs.
I have generated another thread for this issue (GRC AC 5.3 Logging strategy in multi server nodes), would appreciate if you can show some light on this issue
Thanks
Davinder

Options to change jdbc adapter for multiple server nodes without flag in db

Due to load, we are about to add a new server node for additional J2EE memory within XI. Reading the notes and discussions about this, it is apparent that the server nodes don't distinguish between themselves in terms of polling. i.e. If we have a jdbc channel that polls every 24 hours, and you have 2 server nodes, it polls twice at the approximate same time every 24 hours.
Question I have is how have people got around this issue where you cannot update the information to say that the data has been read. i.e. Our scenario is reading the complete table contents every day and sending all information to another system.
Hence, if we have 2 server nodes, we will execute this message twice. When we add a 3rd server node, we will have 3 messages sent at the same time per day.
One complicated option (I think) is to use an application client on XI to schedule a job which calls an ABAP Proxy on the integration client which starts off a ccBPM which in turn reads the database hence single threading this process.
Anyone got any sensible ideas?
Regards,
Matt
ps. Ignore the obvious design flaws with this approach as there is no other option in this scenario due to restrictions in the end system.

Hi Matt,
Extending Bhavesh's point, and assuming the receiver system is SAP, then why not schedule your calls on the receiver system, as the consumer of the data.
The report name and optionally a date range can be written from the RFC via XI to a separate table in the database. The select statement can join the table to the existing view. The update statement can update the new table as your source table or view is obviously out of bounds.
The advantage of this approach is that it results in a classic request response where XI is transparent.
We are planning to do something very similar in our own project.
Best Regards,
Bill

Java Server Nodes / Dialog Instance

Hi All,
When do we go for increase of Java Server nodes and Dialog instance?
Can i know the pros and cons of the same
my server is very slow in responding. I have tried the option of increasing the heap size but then i have little sucess
Rgds
aditya

Install a server process when the incoming request are many and the you can utilize more RAM memory
for eg if there are 8GB RAM and you have 1 server process the maximum u can give it is 2GB while the max 4GB can be utilized by any of the server processes in all in this system
Do not increase this heap size on the same server process (in windows u cant do it also max is 2GB) since then the garbage collection would take longer and also would run in few intervals
A Dialog instance is used when the system resources is completely exhausted and then we go for another hardware and install a fresh dailog instance there.. Its always recommended to use a Web Dispatcher in between the outside world and the SAP server in cluster mode
Hope i am right since i didnt find this information anywhere its based on my understanding and brainstorming sessions with other admins
RGds
Aditya

GRC AC 5.3 Logging strategy in multi server nodes

Hello Experts,
We have GRC AC 5.3 SP6 and 5.2 10 landscapes and PRD system are running with multiple server nodes. SAP recomends to use SAP Logger instead of Java Logger in multi server environment, but i am not able to find out complete documentation on this.
Can someone please give pointers on configuring GRC logging in NWA - which all Categories needs to be defined,etc,etc.
And after this configuration, will we be able to see the logs of scheduled jobs with same details as shown in GRC --> Background Job -> View Logs.
Thanks
Davinder

Hello Harleen,
Thanks for your time. Here are my observations
1. When we have created categories and then deinfed Logging and Tracing (with Severity level ALL) in NWA - these entries have also been reflected in Visual Administrator -> Log Configuration.
2. We will have to restart SAP system after changing logging strategy from Java Logger to SAP Logger.
3. After this change and restart, only upcoming new jobs scheduled/run will be displayed in NWA, jobs ran in the past will never be displayed in NWA.
Severe Problems faced when checking logs through NWA:
1. Logs through NWA are not at all readble as one entry is displayed in one row, whereas checking logs in RAR - VIew Logs was very convenient (similar to reading a text file).
Is it possible to customize the display format of log files in NWA to something like text files,etc?
2. When we try to donwload the logs from NWA, server produces huge dumps files of size in GBs (hpfa files which are memory dumps) - and before this download is completed - server crashes after around 15 minutes of starting log downloads - no free space availbale as everything has been taken by these memroy dumps (around 7GB).
Any further pointers on handling GRC AC logs (multiple server nodes) in NWA would be highly appreciated.
Thanks
Davinder

Time out parameters for ABAP and JAVA instance

Hello All,
We are looking for Time out parameters for our ABAP and JAVA instances.
As users are complaining that they are getting time out error
while they are trying to access Cprojects from Portal.
I was able to check/collect the ABAP instance parameters from SMICM Tcode.
Can anybody tell me which parameters we need to look for JAVA instance.
Thanks in advance.
Regards,
Amber S

jstart/shutdownTimeout
(jstartup/shutdown_timeout)
Specifies the shutdown timeout, i.e. the grace period for the AS Java instance to shut down before the Java process terminates itself. Unt is in Seconds. Default is 120
j2ee/ms/connectTimeout
(jstartup/wait_for_scs)
Specifies the timeout for the first connection to the message server. The AS Java instance fails to start if this timeout expires.Unt is in Seconds.Default is 60
j2ee/ms/reconnectTimeout
(jstartup/wait_for_reconnect)
Specifies the timeout for the reconnecting to the message server.The AS Java instance shuts down when this timeout expires.Unt is inSeconds.Default is 3600 (one hour)
Thanks

Migration server nodes

Hi,
I'm preparing a migration from ep6sp2 to nw04sp15.
On the source machine there are 2 server nodes.
Do you know if on the target machine must be also 2 server nodes??
Florin

No, that's not required. You can migrate to a single
node single instance installation and add server nodes
and dialog instances later on.

JNDI Lookup for multiple server instances with multiple cluster nodes

Hi Experts,
I need help with retreiving log files for multiple server instances with multiple cluster nodes. The system is Netweaver 7.01.
There are 3 server instances all instances with 3 cluster nodes.
There are EJB session beans deployed on them to retreive the log information for each server node.
In the session bean there is a method:
public List getServers() {
List servers = new ArrayList();
ClassLoader saveLoader = Thread.currentThread().getContextClassLoader();
try {
   Properties prop = new Properties();
   prop.setProperty(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
   prop.put(Context.SECURITY_AUTHENTICATION, "none");
   Thread.currentThread().setContextClassLoader((com.sap.engine.services.adminadapter.interfaces.RemoteAdminInterface.class).getClassLoader());
   InitialContext mInitialContext = new InitialContext(prop);
   RemoteAdminInterface rai = (RemoteAdminInterface) mInitialContext.lookup("adminadapter");
   ClusterAdministrator cadm = rai.getClusterAdministrator();
   ConvenienceEngineAdministrator cea = rai.getConvenienceEngineAdministrator();
   int nodeId[] = cea.getClusterNodeIds();
   int dispatcherId = 0;
   String dispatcherIP = null;
   String p4Port = null;
   for (int i = 0; i < nodeId.length; i++) {
    if (cea.getClusterNodeType(nodeId[i]) != 1)
     continue;
    Properties dispatcherProp = cadm.getNodeInfo(nodeId[i]);
    dispatcherIP = dispatcherProp.getProperty("Host", "localhost");
    p4Port = cea.getServiceProperty(nodeId[i], "p4", "port");
    String[] loc = new String[3];
    loc[0] = dispatcherIP;
    loc[1] = p4Port;
    loc[2] = null;
    servers.add(loc);
   mInitialContext.close();
} catch (NamingException e) {
} catch (RemoteException e) {
} finally {
   Thread.currentThread().setContextClassLoader(saveLoader);
return servers;
and the retreived server information used here in another class:
public void run() {
ReadLogsSession readLogsSession;
int total = servers.size();
for (Iterator iter = servers.iterator(); iter.hasNext();) {
   if (keepAlive) {
    try {
     Thread.sleep(500);
    } catch (InterruptedException e) {
     status = status + e.getMessage();
     System.err.println("LogReader Thread Exception" + e.toString());
     e.printStackTrace();
    String[] serverLocs = (String[]) iter.next();
    searchFilter.setDetails("[" + serverLocs[1] + "]");
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    prop.put(Context.PROVIDER_URL, serverLocs[0] + ":" + serverLocs[1]);
    System.err.println("LogReader run [" + serverLocs[0] + ":" + serverLocs[1] + "]");
    status = " Reading :[" + serverLocs[0] + ":" + serverLocs[1] + "] servers :[" + currentIndex + "/" + total + " ] ";
    prop.put("force_remote", "true");
    prop.put(Context.SECURITY_AUTHENTICATION, "none");
    try {
     Context ctx = new InitialContext(prop);
     Object ob = ctx.lookup("com.xom.sia.ReadLogsSession");
     ReadLogsSessionHome readLogsSessionHome = (ReadLogsSessionHome) PortableRemoteObject.narrow(ob, ReadLogsSessionHome.class);
     status = status + "Found ReadLogsSessionHome ["+readLogsSessionHome+"]";
     readLogsSession = readLogsSessionHome.create();
     if(readLogsSession!=null){
      status = status + " Created ["+readLogsSession+"]";
      List l = readLogsSession.getAuditLogs(searchFilter);
      serverLocs[2] = String.valueOf(l.size());
      status = status + serverLocs[2];
      allRecords.addAll(l);
     }else{
      status = status + " unable to create readLogsSession ";
     ctx.close();
    } catch (NamingException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (CreateException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (IOException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (Exception e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
   currentIndex++;
jobComplete = true;
The application is working for multiple server instances with a single cluster node but not working for multiple cusltered environment.
Anybody knows what should be changed to handle more cluster nodes?
Thanks,
Gergely

Thanks for the response.
I was afraid that it would be something like that although
was hoping for
something closer to the application pools we use with IIS to
isolate sites
and limit the impact one badly behaving one can have on
another.
mmr
"Ian Skinner" <[email protected]> wrote in message
news:fe5u5v$pue$[email protected]..
> Run CF with one instance. Look at your processes and see
how much memory
> the "JRun" process is using, multiply this by number of
other CF
> instances.
>
> You are most likely going to end up on implementing a
"handful" of
> instances versus "dozens" of instance on all but the
beefiest of servers.
>
> This can be affected by how much memory each instance
uses. An
> application that puts major amounts of data into
persistent scopes such as
> application and|or session will have a larger foot print
then a leaner
> application that does not put much data into memory
and|or leave it there
> for a very long time.
>
> I know the first time we made use of CF in it's
multi-home flavor, we went
> a bit overboard and created way too many. After nearly
bringing a
> moderate server to its knees, we consolidated until we
had three or four
> or so IIRC. A couple dedicated to to each of our largest
and most
> critical applications and a couple general instances
that ran many smaller
> applications each.
>
>
>
>
>

Central CCMS Alert for Java instance server node crash

Hi,
Is it possible to trigger an alert of an Java system server node crash using central CCMS alerts.
J2EE instance CCMS alert does show some MTEs, however they do not trigger alerts. I got this info from below link
http://help.sap.com/saphelp_nwce711/helpdata/en/46/11aaf352da14dce10000000a155369/frameset.htm
Any idea how to trigger the alert for server node crash.
I understand that server node crash should be investigated for permanent fix, however we need this as a proactive measure to know the crash if they happen.
Thanks
Imtiaz

Hi Imtiaz,
Do you see any error on the view>status auto-reaction? Have you been able to assign an auto-reaction to this MTE?
Cheers,
Maurício

Adding Java Server nodes Causes msgs to send multiple times

i added 2 more server nodes in our system for load distribution and after turning on the comm channel, i see that every msg goes three times now.
I have tried removing these 2 server nodes and then it sends it one time only. I dont know whats wrong and why it sends a msg three times with three server nodes.
Can anybody help me with this?
Thanks
Farrukh

With which adapter(s) are you having this issue ? I had a consultant from SAP tell me to avoid multiple JVM nodes with JDBC, and maybe he said file too. He didn't have a solution, just sounds like it doesn't work too well (yet).

Multiple Weblogic nodes on single Windows server - Dispatcher question?

Hi All,
My experience is with other J2EE web servers (SAP's Netweaver predominantly) and typical installations on this platform include the installation of a dispatcher J2EE node which balances load across potentially multiple J2EE nodes on a single server. Does Weblogic have a similar set-up, as it appears when you create multiple nodes in Weblogic, you need to set-up a load balancer to achieve this same effect (that is installed by default on other platforms).
Obviously creating a single node is pretty useless for the majority of production installations; hence what is the recommended option (without setting up a dedicated load balancer) to achieve this on a single (albeit large) server?
Thanks,
Matt

Hi,
I had just remembered another option, we can set up weblogic as webserver which does the load balancing. Below are the two ways you can do that.
1. While creating the domain using "config.sh" you will get an option to set up "weblogic server as webserver". This option is enabled only on condition "cluster must be created, and few managed servers needs to assigned to cluster". For example if we create 3 managed servers and we assign 2 managed to cluster then "Http Proxt screen" would be enabled where remaining server can be set up as "http proxy webserver".
2. Below is the lengthy procedure.
a. Create a standalone weblogic server.
b. We need to create a dummy war, which just contains below "web.xml" adn "weblogic.xml", let me know if you have trouble creating this war file.
Contents of "web.xml"
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<servlet>

<servlet-name>HttpClusterServlet</servlet-name>
<servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
<init-param>
<param-name>WebLogicCluster</param-name>
<param-value>127.0.0.1:7003|127.0.0.1:7005|127.0.0.1:7007</param-value>
</init-param>
</servlet>

<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>browsestore</url-pattern>
</servlet-mapping>
</web-app>
Contents of "weblogic.xml" . This deployment descriptor is used to deploy this application as "default application".
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<context-root>/</context-root>
</weblogic-web-app>
c. Now deploy this war file to standalone weblogic server.
d. Lets suppose you had deploy application "vas.war" on managed server "VASMS1", "VASMS2", which are running on host "vasunix1" and "vasunix2" on ports 8002. You can access the application directly "http://vasunix1:8001/vas" or "http://vasunix2:8002/vas".
Now since you had set up "http proxy webserver" which does the load balancing, you can directly hit "http proxy webserver" url and it redirects traffic to "VASMS1" or "VASMS2". Lets suppose "Http proxy webserver" "VASMS3" is running on "vasunix1" on port "8003". You can access the application "http://vasunix1:8003/vas", this request is directed to MS1 or MS2.
I hope this is what you are looking for. Have great day.
Vijay Bheemineni.

Problem with JDBC cc with new java server node

Hi experts,
I have the next situation I hope you can help me.
I created an additional java server node in a PI 7.1 system, this because helpful performance.
Bought nodes started ok.
The problem was when I saw in the RW that all the jdbc channels was in status ??? and in the Short Log "not adapter engine assigned".
I did the complete refresh cache en the SXI_CACHE.
I read that I can restart the Adapter Engine, unfortunately I don't have a System Administrator. Would you tell me how to restart the adapter engine?
If anybody have other option, please tell me.
Thanks in advance.

Thanks Spantaleoni.
I'm doing a restart of the instance right now.
I complement the error. When I start or stop the cc has the next error.
com.sap.aii.af.service.administration.api.AdminException: No adapter registered for channel 18996fb1cfda31ff9dca269f4c71e43c
at com.sap.aii.af.service.administration.impl.AdminManagerImpl.notifyChannelActivationStateChanged(AdminManagerImpl.java:851)
at com.sap.aii.af.service.administration.impl.cluster.ClusterManager.eventReceivedSync(ClusterManager.java:426)
at com.sap.aii.af.service.event.impl.worker.sync.SyncLocalWorker.work(SyncLocalWorker.java:52)
at com.sap.aii.af.service.event.impl.worker.sync.AbstractSyncWorker.startWork(AbstractSyncWorker.java:40)
at com.sap.aii.af.service.event.impl.EventManagerImpl.sendEventAndWaitForAnswer(EventManagerImpl.java:484)
at com.sap.aii.af.service.event.impl.EventManagerImpl.sendEventAndWaitForAnswer(EventManagerImpl.java:348)
at com.sap.aii.af.service.administration.impl.cluster.ClusterManager.notifyChannelActivationStateChanged(ClusterManager.java:280)
at com.sap.aii.af.service.administration.impl.AdminManagerImpl.setChannelActivationState(AdminManagerImpl.java:699)
at com.sap.aii.af.service.administration.impl.AdminManagerImpl.setChannelActivationState(AdminManagerImpl.java:625)
at com.sap.aii.af.service.administration.impl.AdminManagerImpl.setChannelActivationState(AdminManagerImpl.java:618)
at com.sap.aii.mdt.amt.channelmonitoring.SummaryChannelList.setChannelsActivationState(SummaryChannelList.java:1041)
at com.sap.aii.mdt.amt.channelmonitoring.ChannelMonitoringDynPage.process_deactivate(ChannelMonitoringDynPage.java:1990)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:102)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Thanks

AS JAVA server nodes

Hi,,
How can I decidethe the numbrer of the server node.
Heap size? CPU thered?

Hi
When you install your Java instance, SAPInst automatically configures the number of server processes based on the hardware resources that are available.
If you need to add more server processes to an existing Java instance, you can do that manually using the J2EE Engine Config Tool
Check the below link to add more server processes
http://help.sap.com/saphelp_nw70/helpdata/EN/6e/dd0041aafdf123e10000000a155106/frameset.htm
Hope help you
Regards,
Sureshram.

Too many session in the AS java server node?

I have install a Netweaver JAVA portal system for customer , this is cluster system one CI and 10 DIs, I found there are too many active session in each server node , I konw , the user can login anyone instance through the web dispatcher , but I found nearly 3000 active session in each server node after a work day in average, and there are too many iterative session , sometime one user can have 30-40 session in each server node after a work day .
I think the memmory is critical if there are have too many session , and sometimes, the log off fution of portal can't work ,so I decided to set a time-out parameter of the session (4 hours),but this is active method to delete the session of the user ,no matter the user is working with system .
Who can tell me how to effective control and enhance user's session managment of Netweaver Java server .

Check note 873190 or 376915
thanks
G. Lakshmipathi

Java Dispatcher not coming up,Server node and SDM is running.

Hi Everyone,
While starting my Java instance, Dispatcher is stopped with return code "666",Server node and SDM is running.This is all of sudden not sure what has changed.
I have changed the heap size value of dispatcher ,Did cleanipc ,But still no luck.
My heap size parameters are according to SAP note:
Note 0001024539 - Recommended Settings for NW04 >= SP14, NW 7.0 >= SP6 on AIX-BPBO.
Java version :
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20080923 (SR12) (JIT enabled: jitc))
Please find below dispatcher error log.
Mon Jan 10 15:36:04 2011
JVMDUMP006I Processing Dump Event "systhrow", detail "java/lang/OutOfMemoryError" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/core.20110110.153604.2523266.0001.dmp'
Note: "Enable full CORE dump" in smit is set to FALSE and as a result there will be limited threading information in core file.
Mon Jan 10 15:36:14 2011
JVMDUMP010I System Dump written to /usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/core.20110110.153604.2523266.0001.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/Snap.20110110.153604.2523266.0002.trc'
JVMDUMP010I Snap Dump written to /usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/Snap.20110110.153604.2523266.0002.trc
JVMDUMP007I JVM Requesting Heap Dump using '/usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/heapdump.20110110.153604.2523266.0003.phd'
Mon Jan 10 15:36:15 2011
JVMDUMP010I Heap Dump written to /usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/heapdump.20110110.153604.2523266.0003.phd
JVMDUMP007I JVM Requesting Java Dump using '/usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/javacore.20110110.153604.2523266.0004.txt'
JVMDUMP010I Java Dump written to /usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher/javacore.20110110.153604.2523266.0004.txt
JVMDUMP013I Processed Dump Event "systhrow", detail "java/lang/OutOfMemoryError".
</verbosegc>
[Thr 6428] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 6428] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 6428] SigISetIgnoreAction : SIG_IGN for signal 20
[Thr 6428] JLaunchCloseProgram: good bye (exitcode = 666)
Could somebody help...
Thanks

Hi John ,Thanks
The dispatcher connects to only one server node.dev_dispatcher content details below.
JStartupIReadSection: read node properties [ID18122300]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : /usr/java14_64
-> java parameters    : -Xmn70M -Xgcpolicy:gencon -verbose:gc -Xj9 -Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError,request=exclusive+prepwalk -Djava.security.policy=.\java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1
-> java vm version    : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142-20080923 (JIT enabled)
-> java vm vendor     : IBM J9 VM (IBM Corporation)
-> java vm type       : server
-> java vm cpu        : ppc64
-> heap size          : 200M
-> init heap size     : 200M
-> root path          : /usr/sap/D10/DVEBMGS01/j2ee/cluster/dispatcher
-> class path         : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> OS libs path       : /usr/sap/D10/DVEBMGS01/j2ee/os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : /usr/sap/D10/DVEBMGS01/exe/jstartup.jar:/usr/sap/D10/DVEBMGS01/exe/jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50000
-> shutdown timeout   : 120000
[Thr 1] JLaunchISetDebugMode: set debug mode [no]
[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Xmn70M
-> arg[ 4]: -Xgcpolicy:gencon
-> arg[ 5]: -verbose:gc
-> arg[ 6]: -Xj9
-> arg[ 7]: -Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError,request=exclusive+prepwalk
-> arg[ 8]: -Djava.security.policy=.\java.policy
-> arg[ 9]: -Djava.security.egd=file:/dev/urandom
-> arg[ 10]: -Djco.jarm=1
-> arg[ 11]: -Dsys.global.dir=/usr/sap/D10/SYS/global
-> arg[ 12]: -Dapplication.home=/usr/sap/D10/DVEBMGS01/exe
-> arg[ 13]: -Djava.class.path=/usr/sap/D10/DVEBMGS01/exe/jstartup.jar:/usr/sap/D10/DVEBMGS01/exe/jvmx.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
-> arg[ 14]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/D10/DVEBMGS01/exe:
/usr/sap/D10/DVEBMGS01/exe:/usr/sap/D10/DVEBMGS01/exe:/usr/TDAccess2.4.1:/usr/sap/D10/SYS/exe/run:/oracle/client/10x_64/instantclient:/
usr/java14_64/jre/bin/j9vm:/usr/sap/D10/DVEBMGS01/exe::/usr/lib:/usr/sap/D10/DVEBMGS01/j2ee/os_libs:/usr/sap/D10/DVEBMGS01/exe:/usr/sap/D10
/DVEBMGS01/exe:/usr/sap/D10/DVEBMGS01/exe:/usr/TDAccess2.4.1:/usr/sap/D10/SYS/exe/run:/oracle/client/10x_64/instantclient
-> arg[ 15]: -Dmemory.manager=200M
-> arg[ 16]: -Xmx200M
-> arg[ 17]: -Xms200M
-> arg[ 18]: -DLoadBalanceRestricted=no
-> arg[ 19]: -Djstartup.mode=JCONTROL
-> arg[ 20]: -Djstartup.ownProcessId=2748598
-> arg[ 21]: -Djstartup.ownHardwareId=U0234126406
-> arg[ 22]: -Djstartup.whoami=dispatcher
-> arg[ 23]: -Djstartup.debuggable=no
-> arg[ 24]: -DSAPINFO=D10_01_dispatcher
-> arg[ 25]: -DSAPSTART=1
-> arg[ 26]: -DCONNECT_PORT=64999
-> arg[ 27]: -DSAPSYSTEM=01
-> arg[ 28]: -DSAPSYSTEMNAME=D10
-> arg[ 29]: -DSAPMYNAME=eccdcs1s_D10_01
-> arg[ 30]: -DSAPPROFILE=/usr/sap/D10/SYS/profile/D10_DVEBMGS01_xxxxxxx
-> arg[ 31]: -DFRFC_FALLBACK=ON
-> arg[ 32]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 33]: -DSAPSTARTUP=1
-> arg[ 34]: -DSAPSYSTEM=01
-> arg[ 35]: -DSAPSYSTEMNAME=D10
-> arg[ 36]: -DSAPMYNAME=xxxxxxxx_D10_01
-> arg[ 37]: -DSAPDBHOST=xxxxxxx
-> arg[ 38]: -Dj2ee.dbhost=xxxxxx
Edited by: Khaiser Khan Mohammed on Jan 18, 2011 11:19 AM

Multiple Server nodes in Java Instance

Similar Messages

Maybe you are looking for