Webdispacther + J2EE Cluster wrong balancing

Hello,
We have a problem.
We have a webdispatcher that sends information to a J2EE cluster with 3 nodes with 2 serves each.
The problem is that it does not do the balancing correctly. It only balances to the 1 and 3 node. How can I check or configure so the balancing goes to the 3 nodes instead of the 2 nodes?.
The configuration of the webdispatcher is:
SAPSYSTEMNAME = WPE
SAPGLOBALHOST = madrsiwd03
SAPSYSTEM = 10
INSTANCE_NAME = W10
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_CT_RUN)
rdisp/mshost = madrsiep03.indra.es
ms/http_port = 8101
icm/max_conn = 16384
icm/max_sockets = 16384
icm/req_queue_len = 6000
icm/min_threads = 100
icm/max_threads = 250
mpi/total_size_MB = 500
mpi/max_pipes = 21000
icm/server_port_0 = PROT=HTTP,PORT=81$$,TIMEOUT=900,PROCTIMEOUT=600
icm/server_port_1 = PROT=ROUTER,PORT=82$$,TIMEOUT=900,PROCTIMEOUT=600,VCLIENT=1
The configuration of the J2EE cluster is:
SAPSYSTEMNAME = XXX
SAPSYSTEM = 01
INSTANCE_NAME = SCS01
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = madarrsiclpee
OS_UNICODE = uc
rdisp/msserv = 0
rdisp/msserv_internal = 3901
ms/standalone = 1
ms/server_port_0 = PROT=HTTP,PORT=81$$
ms/server_port_1 = PROT=HTTPS,PORT=82$$
enque/serverinst = 01
enque/table_size = 4096
rdisp/enqname = $(rdisp/myname)
enque/snapshot_pck_ids = 100
Best Regards.
Pablo Mortera.

If I understand your question, you have 2 J2EE Instances with 1 and 2 Server nodes on each and Web DIspatcher is pushing load only to the Instance with 1 Server node, right?
1. Go to webdisp admin page @ http://host/wdisp/admin  --> click monitor server groups , here you can see the J2EE instances and thier capacity . You can also see how many requests are sent to each instance.
2. You can RIGHT CLICK on the the J2EE Instance and Change the CAPACITY of the desired Instance to send more load.
Thanks
SM

Similar Messages

  • SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

    HI,
    I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
    Error: An error occured while starting a cluster instance.
    Oct 14, 2008 5:14:41 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    Please check if there is an appropriate running cluster instances
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    I am pasting the full LOG File details:-
    Oct 14, 2008 6:32:00 PM  Info: Starting cluster instance processes.
    Oct 14, 2008 6:32:00 PM  Error: An error occured while starting a cluster instance.
    Oct 14, 2008 6:32:00 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    Oct 14, 2008 6:32:00 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Oct 14, 2008 6:32:00 PM  Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
    The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Oct 14, 2008 6:32:04 PM  Info: Starting to save the repository
    Oct 14, 2008 6:32:05 PM  Info: Finished saving the repository
    Oct 14, 2008 6:32:07 PM  Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
    Oct 14, 2008 6:32:07 PM  Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    Failed deployment of SDAs:
    development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
    Please, look at error logs above for more information!
    I have checked the CONFIGTOOl and the properties seem to be OK.
    I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
    Pls suggest.
    Regards,
    Abhijeet
    I

    Hi George,
    Thnx for your reply.
    I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
    Have checked the Visual admin,it is not in SAFE mode,it working normally.
    Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
    About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
    I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
    Kindly suggest what other steps I shud take.
    Regards,
    Abhijeet

  • SDM could not start the J2EE cluster on the host Error on Deployments

    Hi,
    We are sudenly getting this Error when trying to make a Deployment in the NWDE:
    Settings
    SDM host : 10.26.26.198
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
    Aborted: development component 'WDWFApp'/'local'/'LOKAL'/'0.2007.02.16.15.11.28'/'0':SDM could not start the J2EE cluster on the host vmxtbcsapep01! The online deployment is terminated. There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage . The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :|Name:JM_T1171660289517_0_ALMACARVAJAL        |Host:miriamdragustinovis             |State:5|HostAddress:10.21.69.164||Name:JM_T1171656308064_0_vmxtbcsapep01       |Host:cvespinosa                      |State:5|HostAddress:10.26.26.198||Name:JC_vmxtbcsapep01_CPQ_00                 |Host:cvespinosa                      |State:5|HostAddress:10.26.26.198|Please check if there is an appropriate running cluster instances. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Deployment exception : The deployment of at least one item aborted
    And in the sdm log file we got this kind of errors:
    Feb 16, 2007 2:13:46 PM  Error: Unable to compare host[vmxtbcsapep01] and host[miriamdragustinovis] Throwable: java.net.UnknownHostException Throwable message: miriamdragustinovis
    Feb 16, 2007 2:13:46 PM  Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
    Feb 16, 2007 2:13:46 PM  Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
    Feb 16, 2007 2:13:46 PM  Error: An error occured while starting a cluster instance.
    Feb 16, 2007 2:13:46 PM  Error: There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage .
    The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :
    Name:JM_T1171656916610_0_ALMACARVAJAL
    Host:miriamdragustinovis
    State:5
    HostAddress:10.21.69.164
    Name:JM_T1171656308064_0_vmxtbcsapep01
    Host:cvespinosa
    State:5
    HostAddress:10.26.26.198
    Name:JC_vmxtbcsapep01_CPQ_00
    Host:cvespinosa
    State:5
    HostAddress:10.26.26.198
    Any Idea what can be wrong? we have even restarted de AIX Server and starting all the services and it is still not working.
    Thanx in Advanced!
    Gerardo J

    Hi Gerardo,
    I encountered exactly the same error, but had a different solution as I was expecting from the error-message.
    In my case I was forced by the Visual Administrator to change the administration password, since the time was up on it. But as the password for the Visual Administrator is saved within the database, the password for the SDM is stored within the secure store (file-system) and changing the password just in VA will not automatically change it also in the secure store. But since both passwords for the internal usage need to be equalized, I encountered problems afterwards when trying to deploy something and I got the same error message. However the sense of restriction is meant here, the solution on it was rather simple as follows (Just note that you need to enter a dummy-password first, before setting the correct one similar to your visual administrator):
    1. create a telnet session to your J2EE using a command line shell
    2. enter "jump 0" to get on the correct node within your J2EE
    3. enter "add user" to gain access to user-specific commands
    4. enter "password <Administrator> <temporarily new password>"
    5. exit
    6. create another telnet session to your J2EE using a command line shell
    7. after succeeded the login, you will now be forced to enter a new password - so enter "password <Administrator> <origin password of the Visual Administrator>"
    8. exit
    9. now start the config-tool of the engine
    10. apply to the DB-default-question with "yes"
    11. select the Secure Store on the left
    12. select the entry "admin/password/..." that you can see it in the bottom lines.
    13. click "Remove" to delete it from the list
    14. set the password similar to the Visual Administrator password within the "Value" line (take care as you can not see the digits).
    15. click "Add" to add it back to the list
    16. click the disc symbol in the top of the UI to save the new password (if you don't get a dialog afterwards that the data has been stored, something may hasn't worked fine when removing/adding the password-entry, in this case repeat the action on it).
    17. After exiting the config-tool, you need to restart the entire J2EE.
    18. Your hopefully finished by success ;o))
    Best regards
    Jochen

  • Cluster/load balance weblogic using L4 switch like Alteon

    Can I install weblogic as a standalone server on 2 or more server and
              cluster/load balance weblogic using a hardware balancer like Alteon Layer4
              switch (of course I will use a centralised storage to maintain a single copy
              of data which will eliminate syncronizing problem among servers)?
              BTW, Alteon can support persistent binding. The reason to use a Layer 4
              switch is that it is very fast, and this will make the application server
              layer transparent to client, the client can think this is a single server
              (it don't need to know whether there are 5 weblogic servers or 20 weblogic
              servers behind switch), and hardware are more reliable, sacalable and fast.
              I am not sure whether the normal weblogic clustered servers need to
              share/exchange info on the running memory, if it does, this approach will
              fail.
              

    So My understanding is:
              Alteon with WL 6.0 can do load balancing for:
              entity bean
              stateless session bean
              but can't do load balancing for:
              stateful session bean (will persistent/sticky binding solve part of the
              problem except fail-over)
              in-memory replication
              am I right?
              Pao Wan
              "Don Ferguson" <[email protected]> wrote in message
              news:[email protected]...
              > It is possible to configure Alteon to understand the WebLogic 6.0 cookie
              format
              > and have a proxy-less cluster configuration that performs load balancing
              and
              > fail over of session state.
              >
              > It is also possible to configure Alteon's hardware-based SSL decryption
              for really
              > fast HTTPS processing.
              >
              > We are working on a white paper that describes how to configure Alteon for
              use
              > with WebLogic Server 6.0.
              >
              > -Don
              >
              >
              > Robert Patrick wrote:
              >
              > > Cameron,
              > >
              > > I believe that BEA tested their new proxy-less web clustering solution
              with
              > > load-balancing products from Alteon and several other vendors
              (Arrowpoint ?--
              > > which is now Cisco). However, it was my understanding that these
              products do
              > > not understand how to decrypt our cookies and extract IP addresses but
              rather
              > > these products are capable of doing sticky load balancing based on the
              Session
              > > ID contained in our cookie.
              > >
              > > If this is correct, then what this means is that when the primary server
              fails,
              > > the request will be routed to "some other server" in the cluster but not
              > > necessarily the one that holds the secondary copy of the user's session.
              The
              > > change in WLS 6.0 is that WLS will accept these misdirected requests and
              it will
              > > go out to the correct server and "migrate" the session to the server
              that
              > > received the request making that server the new primary (and
              regenerating the
              > > Session ID).
              > >
              > > I am sure if this is wrong that our product manager or one of our
              engineers will
              > > correct me (please?)...
              > >
              > > Hope this helps,
              > > Robert
              > >
              > > Cameron Purdy wrote:
              > >
              > > > Hi Robert,
              > > >
              > > > FWIW - There are several vendors (Primeon? Arrowpoint?) who claim to
              > > > understand WL cookies and parse the IPs out. (I haven't verified it
              myself
              > > > though.)
              > > >
              > > > --
              > > > Cameron Purdy
              > > > Tangosol, Inc.
              > > > http://www.tangosol.com
              > > > +1.617.623.5782
              > > > WebLogic Consulting Available
              > > >
              > > > "Robert Patrick" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > There are not any hardware vendors (yet) that can understand
              WebLogic's
              > > > session
              > > > > ID. While you might be able to use the load balancer without the
              proxy on
              > > > 5.1,
              > > > > you would not be able to take advantage of in-memory replication
              failover
              > > > unless
              > > > > you only had two machines in the cluster. Like you said, everything
              will
              > > > work
              > > > > with 6.0 regardless of how the load balancer works (though you
              really,
              > > > really
              > > > > want to minimize the number of times the requests come into the
              wrong
              > > > server by
              > > > > utilizing sticky load balancing).
              > > > >
              > > > > Hope this helps,
              > > > > Robert
              > > > >
              > > > > Cameron Purdy wrote:
              > > > >
              > > > > > Rajesh,
              > > > > >
              > > > > > I meant that it would work in lieu of a proxy (such as Apache or
              NES)
              > > > with
              > > > > > 5.1, but only if both the hw load balancer and WL were set up to
              use
              > > > > > cookies. Some hw load balancers rely on IP and that doesn't
              work -- AOL
              > > > > > connections for example can change the source IP on the fly.
              Others
              > > > produce
              > > > > > their own cookies, that will work. Some even can use WL cookies
              and
              > > > parse
              > > > > > them to determine where to go. According to what I've read, with
              6.0 if
              > > > the
              > > > > > WL primary dies or for some other reason the request shows up at
              the
              > > > "wrong"
              > > > > > server, it will be handled correctly. That means you are pretty
              safe
              > > > with
              > > > > > hw load balancers and 6.0, almost regardless of the sticky
              > > > implementation
              > > > > > that they use.
              > > > > >
              > > > > > --
              > > > > > Cameron Purdy
              > > > > > Tangosol, Inc.
              > > > > > http://www.tangosol.com
              > > > > > +1.617.623.5782
              > > > > > WebLogic Consulting Available
              > > > > >
              > > > > > "Rajesh" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > >
              > > > > > > Hi Cameron,
              > > > > > > Can you elaborate on how it would work with WL5.1 since no in
              memory
              > > > > > replication
              > > > > > > would happen if the servers are standalone.
              > > > > > >
              > > > > > > "Cameron Purdy" <[email protected]> wrote:
              > > > > > > >Yes, this will work fine with WL6. (WL5.1 will work fine as
              long as
              > > > > > cookies
              > > > > > > >are used by the load balancer.)
              > > > > > > >
              > > > > > > >--
              > > > > > > >Cameron Purdy
              > > > > > > >Tangosol, Inc.
              > > > > > > >http://www.tangosol.com
              > > > > > > >+1.617.623.5782
              > > > > > > >WebLogic Consulting Available
              > > > > > > >
              > > > > > > >
              > > > > > > >"paowan" <[email protected]> wrote in message
              > > > > > > >news:[email protected]...
              > > > > > > >> Can I install weblogic as a standalone server on 2 or more
              server
              > > > and
              > > > > > > >> cluster/load balance weblogic using a hardware balancer like
              Alteon
              > > > > > Layer4
              > > > > > > >> switch (of course I will use a centralised storage to
              maintain a
              > > > single
              > > > > > > >copy
              > > > > > > >> of data which will eliminate syncronizing problem among
              servers)?
              > > > > > > >>
              > > > > > > >> BTW, Alteon can support persistent binding. The reason to use
              a
              > > > Layer
              > > > > > > >4
              > > > > > > >> switch is that it is very fast, and this will make the
              application
              > > > > > server
              > > > > > > >> layer transparent to client, the client can think this is a
              single
              > > > > > server
              > > > > > > >> (it don't need to know whether there are 5 weblogic servers
              or 20
              > > > > > weblogic
              > > > > > > >> servers behind switch), and hardware are more reliable,
              sacalable
              > > > and
              > > > > > > >fast.
              > > > > > > >>
              > > > > > > >> I am not sure whether the normal weblogic clustered servers
              need to
              > > > > > > >> share/exchange info on the running memory, if it does, this
              > > > approach
              > > > > > will
              > > > > > > >> fail.
              > > > > > > >>
              > > > > > > >>
              > > > > > > >
              > > > > > > >
              > > > > > >
              > > > >
              >
              

  • "Invoice History Report "show wrong balance for supplier invoice with USD

    Invoice History Report show wrong balance for supplier invoice with USD Currency
    After I run this report i see in the last of this report there is difference between the supplier total
    USD (Currency ) and the open Balance USD , it is decreased the open balance
    for supplier with 2300 USD with out any reasons
    bellow is some data copy of the report
    ======================================================
    Supplier Site Total: SAR 34,700.00
    Supplier Site Total: USD 39,000.00
    Supplier Total: SAR 34,700.00
    Supplier Total: USD 39,000.00
    Open Balance: SAR 34,700.00
    Open Balance: USD 36,700.00
    *** End of Report ***
    ==============================================
    please advise me from where can this differenc ( 39000 - 36,700=2300 )COMMING
    or it is bug in this report , becuase i compare this report with other report in account payable like
    -supplier open balance letter
    -invoice register report
    -invoice aging report
    all this report give me the amount for supplier USD =39000
    BUT AGIN FROM WHERE THE SYSTEM DECREASED THE AMOUNT TO 36,700
    thanks

    Can you try running Create Accounting For payments just before you run the Invoice History Report and re-check .
    Thanks

  • J2EE cluster error while deploying "EAR" file from SDM tool

    Hi all,
    I am new to CRM ISA development side. I am learning how to build b2c ear file base on b2c.ear and then how to deploy through SDM. Everything is working fine till build tool. Successfully build my own b2c_ashish.ear file. then I started SDM GUI and try to deploy it. In SAP MMC all process are running. J2EE engine is also running fine. I have describe below which step I took.
    PL. go through it an let me know about my mistake.
    I am just pasting that portion of error which I am getting when I am accessing "/b2c_kce/b2c/init.do"
    ===================
    A runtime error occurred
    Contact the administrator
    Start application
    ==================
    do you have any idea in which log file it writes error so I can open that file and . I tried to access log file from "Admin" page.
    If I am trying to access "/b2c_kce/admin/index.jsp" I am able to access those pages without problem only "/b2c_kce/b2c/init.do" I am getting problem like above "run time error Occured"
    When I click on "Start Application" it is opening new window and showing same text.
    I checked SAP MMC. it is showing all node Green "dgntisa", "dgntisa1" and "dgntisa0" Also All process like under "dgntisa0" process "jcontrol.exe" and "igswd.exe "  are green.
    I build "b2c_ashish" new by using build tool. It was also successful.
    I start SDM server by "StartServer.bat" and after that I start SDM remote GUI.
    I select "Deployment" tab and add "crm.b2c_ashish" for deployment then I click on Start button and I got below error for "J2EE Cluster" that "SDM could not start J2EE cluster on the host dgntisa"
    Pl. if you have any idea then pl. let me know how to solve this error.
    Deployment started Sun May 14 14:24:50 PDT 2006
    ===========================================================================
    Starting Deployment of crm.b2c_ashish
    Aborted: development component 'crm.b2c_ashish'/'sap.com'/'SAP AG'/'400.200605141307':
    SDM could not start the J2EE cluster on the host dgntisa! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Deployment of crm.b2c_ashish finished with Error (Duration 3250 ms)
    ===========================================================================
    Above error start ater restarting "WAS" server. Now You can not deploy or undeploy any SDA or SCA component.
    I follow above mentioned steps 2 time after restarting "WAS" server. but it seems that one service for J2EE cluster is not started.  I also chekced the running mode of SDM and SAP J2EE version. SDM Runing mode is "integrated" and SAP J2EE version is " 6.30" While using a build file it is showing J2EE engin version.
    =======================================================

    Would you post the same thread under SAP Netweaver or WAS?

  • J2EE Cluster Error while deploying ISA b2c.ear file.

    Hi All,
    I am trying to deploy b2c.ear file through SDM deploytool.
    My build tool is working fine. In SAP MMC all node is green. All J2EE service is running. But when I try to deploy file through SDM i am getting below error.
    Deployment started Sun May 14 14:24:50 PDT 2006
    ===========================================================================
    Starting Deployment of crm.b2c_ashish
    Aborted: development component 'crm.b2c_ashish'/'sap.com'/'SAP AG'/'400.200605141307':
    SDM could not start the J2EE cluster on the host dgntisa! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Deployment of crm.b2c_ashish finished with Error (Duration 3250 ms)
    ===========================================================================
    IF some one has any idea then pl. show me the way. I am new to CRM ISA side so pl. help me out.
    Thanks in advance.
    Ashish Patel.

    Hi Rajesh,
    Below is the part of the log file.
    ==============================
    #1.5#0013D4B7BFFF002600000001000001A800041439E82CD452#1148138847796#com.sap.engine.services.monitor.common.Template##com.sap.engine.services.monitor.common.Template######25430f40e81511da9ca50013d4b7bfff#SAPEngine_System_Thread[impl:5]_52##0#0#Error##Plain###javax.management.InstanceNotFoundException: com.sap.default:name=com.sapmarkets.isa.core.jmx.ext.MyXCMInstProvider,SAP_J2EEApplicationPerNode=sap.com/crm.b2c_dgn,j2eeType=SAP_ApplicationResourcePerNode,SAP_J2EEClusterNode=8527350,SAP_J2EECluster=ITG not in repository
         at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1291)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
         at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:300)
         at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
         at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:559)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
         at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData(Template.java:891)
         at com.sap.engine.services.monitor.mbeans.Template.handleNotification(Template.java:847)
         at com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)
         at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:94)
         at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:61)
         at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:407)
         at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
         at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:50)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
    =========================
    According to log file it says that
    SAP_J2EECLUSTER = ITG is not in Repository.
    It looks like that some parameter setting is missing. Do you have any idea where I can set "SAP_J2EECLUSTER" Parameter.
    Thanks.
    Ashish Patel.

  • Seeburger logging in j2ee\cluster\tmp

    Hello all,
    We are experiencing massive logging in \j2ee\cluster\tmp. Numerous files (today over 5000 of them) with an .swp extention are created. In the files, the following text can be found:
    InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.TradacomDocReader Exception, offset[126(read Segment : STX)]: unexpected Subelement delimiter found : field STDS expected. : Group STX:STDS : Error at casting Group Description.
    Maybe a field with the same name is existing...
    DESCRIPTION: [not specified] at position [not specified] causes a general exception: [not specified]
    Can somebody tell me where these files are comming from and how we can dam the flood of these files?
    Kind regards, Wilbert

    Hello all,
    We are experiencing massive logging in \j2ee\cluster\tmp. Numerous files (today over 5000 of them) with an .swp extention are created. In the files, the following text can be found:
    InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.TradacomDocReader Exception, offset[126(read Segment : STX)]: unexpected Subelement delimiter found : field STDS expected. : Group STX:STDS : Error at casting Group Description.
    Maybe a field with the same name is existing...
    DESCRIPTION: [not specified] at position [not specified] causes a general exception: [not specified]
    Can somebody tell me where these files are comming from and how we can dam the flood of these files?
    Kind regards, Wilbert

  • EP 6.0 SP2  P4  J2EE Cluster -   503! - Initialization of Dispatcher failed

    Hello,
    I have the following problem:
    SAP EP-Version: J2EE Cluster with SAP EP 6.0 SP2 Patch 4 and J2EE PL23
    After the Installation on the second Clusternode,
    -> "Additional SAP J2EE System for a portal Cluster" I get after the call of the URL: "http://<Servername>:50000/irj" the following error message: "Service Unavailable <b>503! - javax.servlet.UnavailableException: Initialization of Dispatcher failed</b>".
    It looks like, that after the synchronisation no applications would have been copied to the second Clusternode. -> There are no irj-Folder as sample on the second Clusternode.
    What is the problem? - How can I deploy the application later now ?
    About your assistance I would be happy.
    Thanks in advance.
    Ralf

    Hello John,
    We have checked the configuration of the ports and none of the used  (join port, open port) ports repeats itself inside the same host, adittional we have change ports that repeat in different host.
    The problem presist.
    Adittional I send error messages:
    1.- When we try to access to EP 60 SP2 in BSC
    Service Unavailable 503!
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    2.- Startup sequence in BSC.
    Service Unavailable 503!
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Portal initialization in progress ...
    Loading core applications:
      Loading application: com.sap.portal.license.runtime
      Loading application: com.sap.portal.pcd.aclservice
      Loading application: com.sap.portal.pcd.basicrolefactory
      Loading application: com.sap.portal.pcd.basictransport
      Loading application: com.sap.portal.pcd.configservice
      Loading application: com.sap.portal.pcd.glservice
      Loading application: com.sap.portal.pcd.lockservice
      Loading application: com.sap.portal.pcd.plconnectionservice
      Loading application: com.sap.portal.pcd.softcacheservice
      Loading application: com.sap.portal.pcd.textrepository
      Loading application: com.sap.portal.pcd.traceservice
      Loading application: com.sap.portal.pcd.umwrapperservice
      Loading application: com.sap.portal.pcm.admin.apiservice
      Loading application: com.sap.portal.runtime.config
      Loading application: com.sap.portal.runtime.system.authentication
      Loading application: com.sap.portal.runtime.system.clusterinformation
      Loading application: com.sap.portal.runtime.system.inqmy
      Loading application: com.sap.portal.runtime.system.notification
      Loading application: com.sap.portal.runtime.system.permission
      Loading application: com.sap.portal.runtime.system.repository
      Loading application: com.sap.portal.umeregistration
      Loading application: com.sap.portal.usermanagement
    Loading services:
      Loading service: com.sap.portal.license.runtime|license
      Loading service: com.sap.portal.pcd.aclservice|aclconnector
      Loading service: com.sap.portal.pcd.basicrolefactory|factory
      Loading service: com.sap.portal.pcd.basictransport|transport
      Loading service: com.sap.portal.pcd.configservice|configuration
      Loading service: com.sap.portal.pcd.glservice|generic_layer
      Loading service: com.sap.portal.pcd.lockservice|locks
      Loading service: com.sap.portal.pcd.plconnectionservice|connections
      Loading service: com.sap.portal.pcd.softcacheservice|softcache
      Loading service: com.sap.portal.pcd.textrepository|TextRepositoryService
      Loading service: com.sap.portal.pcd.traceservice|traces
      Loading service: com.sap.portal.pcd.umwrapperservice|umwrapper
      Loading service: com.sap.portal.pcm.admin.apiservice|default
      Loading service: com.sap.portal.runtime.config|config
      Loading service: com.sap.portal.runtime.config|config_deployment
      Loading service: com.sap.portal.runtime.system.authentication|authentication
      Loading service: com.sap.portal.runtime.system.clusterinformation|clusterinformation
      Loading service: com.sap.portal.runtime.system.notification|notification
      Loading service: com.sap.portal.runtime.system.notification|SAPJ2EEHttpService
      Loading service: com.sap.portal.runtime.system.repository|application_repository
      Loading service: com.sap.portal.umeregistration|ume_registration
      Loading service: com.sap.portal.usermanagement|usermanagement
      Loading service: com.sap.portal.usermanagement|user_management_engine
      Loading service: com.sap.portal.usermanagement|security
    Aug 23, 2004 10:20:55 AM # System_Thread_84     Fatal           [Portal.init] Application Broker - initialization failed.
    com.sapportals.portal.prt.runtime.PortalException: [Portal Application Broker] applications start failed
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1223)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.runtime.PortalException: [PortalServiceItem.startServices] service initialisation step 2 failed: com.sap.portal.usermanagement|user_management_engine
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:915)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sap.ip.portal.service.ume.UserManagementEngine of Portal Service com.sap.portal.usermanagement|user_management_engine because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:747)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.NullPointerException
         at com.sapportals.portal.prt.service.config.ConfigService.findArchiveWithName(ConfigService.java:1247)
         at com.sapportals.portal.prt.service.config.ConfigService.installPortalRootPlugin(ConfigService.java:1229)
         at com.sapportals.portal.prt.service.config.ConfigService.performInitialization(ConfigService.java:1036)
         at com.sapportals.portal.prt.service.config.ConfigService.internalInit(ConfigService.java:945)
         at com.sapportals.portal.prt.service.config.ConfigService.umeInitialized(ConfigService.java:398)
         at com.sap.portal.service.umeRegistration.UMERegistration.fireEvents(UMERegistration.java:123)
         at com.sap.portal.service.umeRegistration.UMERegistration.triggerMe(UMERegistration.java:109)
         at com.sap.ip.portal.service.ume.UserManagementEngine.fireEvents(UserManagementEngine.java:245)
         at com.sap.ip.portal.service.ume.UserManagementEngine.afterInit(UserManagementEngine.java:85)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1262)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1218)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1152)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:343)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    java.security.PrivilegedActionException: com.sapportals.portal.prt.core.PortalCoreInitializerException: Main initialization of plugin failed
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:134)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.IllegalStateException: [Portal.init] Application Broker - initialization failed.
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:349)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    WARNING: Dispatcher could not be set up:
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
    javax.servlet.UnavailableException: Initialization of Dispatcher failed
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:370)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:124)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    com.sapportals.portal.prt.dispatcher.DispatcherException: Previous dispatcher initialization failed. Check logs for details.
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:256)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:212)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$400(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:447)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)

  • Directory size of ...../ j2ee/cluster/server ?

    Hi Everybody,
    Can anyone pls tell me if their "server" directory size under ..../j2ee/cluster/server  increased drastically after the installation of the ME 2.1 Server component on J2EE Engine on WAS 6.20.
    A file called "dev_Icom" in the directory .../j2ee/cluster/server is taking away 11Gb.
    Please confirm.
    I am using J2EE SP24.
    Thnx
    Meesum
    Message was edited by: Meesum Kirmani

    HI,
    If you do not enter the cluster ID,the EOIO channel is activated automatically on a different working node.
    This configuration ensures node failover by the adapter in a clustered environment.
    Regards,
    Akshay Jamgaonkar.
    Dont forget to give points.

  • Cluster / Load balancing and no. of user

    Hi
    Just wondering what kind of cluster / load balancing setup is need for e.g. 50 concurrent users ? and what's the deciding factor that will justify additional presentation service / BI server to be added to an existing cluster farm ?
    Or maybe if you guys could share what's the cluster setup that you have and the number of users that would greatly help me to get a rough idea of the kind of setup needed. E.g. 2x presentation services and 2x BI server with 100 users, estimated 50 concurrent users, etc..
    Thanks in advance !

    If there are 50 concurrent users, I don't think that you need to go for clustering. You can use more resources like increasing the RAM size and increasing th CPU count.
    If you opt for 64 bit operating system ,it would give you better performance.
    Regards
    Rajesh J

  • WDRuntimeException: Failed to create J2EE cluster node in SLD

    Hello,
    I am getting the below error, but to my knowledge I have everything set up properly.  Let me briefly outline the logistics (I am running everything LOCALLY (will move to remote later)):
    WAS 6.4 <b>SP12</b>
    Set up JCo and tests fine
    Set up Visual Administrator / SLD Data Supplier / HTTP and CIM configured and seem to test fine
    Created SLD and it tests OK
    Created Technical Landscape
    I have noticed that in SP12, in the SLD config I actually have a NEW category called "<b>System Landscape</b>" above my "Technical Landscape" link.  I have not seen this option in previous versions SP9 or SP11.  Is it mandatory to configure this?
    Also, I created a model for Adaptive RFC and found the function I needed successfully.
    Anyway, here is the error when trying to deploy...
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.bc347792': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.bc347792"
    Any help will be appreciated!

    I figured it out for those that may have a similar problem.
    Although I had created and tested my JCo's properly and they were working fine, somehow, and I still don't know why, they went RED in the JCo Maintainence screen. 
    I had to "create" again and it works fine now.

  • Zip files in j2ee/cluster/server0/log/archive,  Can somebody explain these?

    Our file system is filling up on our PI system, I see allot of .ZIP files in this directory,  can I just delete them?
    j2ee/cluster/server0/log/archive

    Hi David,
    as you can read [here|http://help.sap.com/saphelp_sem60ep1/helpdata/EN/f6/7d814282cfc153e10000000a1550b0/frameset.htm] the ZIP files contain old log files so you can delete them to free up space.
    Hope this helps,
    Robert

  • J2EE Cluster is not created during system copy.

    Hi all,
    Iu2019ve been trying to perform a system copy on our PI 7.0 sp14 test system & create a second system on the same server.
    I used the standard Sapinst tools for this because it is a PI ABAP+JAVA system.
    The copy process went smooth but after it finished I realized that the ABAP side has been installed correctly but when I tried running "SXMB_IFR" I saw that the system points me to the source system J2EE process.
    Looking into the file system of the target system, I saw that under the path \usr\sap\<SID>\<Instance>\j2ee\cluster only the bootstrap folder exists. Of course that in the SAP MMC, you cannot see any J2EE process under the new system process list.
    I tried using a newer sapinst but that didnu2019t help.
    Anyone ever encounter anything like that?
    Thanks for your help.
    Regards,
    Yoav Zilberman

    He again,
    Now i finally managed to make all the J2EE  process work but i keep having issues with the "server0" process in both systems on the server.
    the first system i starts works fine but the second one will get the error: [Thr 8944] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\XIQ\DVEBMGS00\exe\jvmx.jar ; (SID changes according to which system started first).
    Thanks,
    Yoav

  • Wrong balances in FAGLFLEXT table

    Dear All,
    I am using datasource 0FI_GL_10 to extract data into BI from SAP AFS 5.0. We are using the new general ledger. extraction is fine and delta extraction happens without any issue.
    The issue is that when i look at a account balance in BI and take a trial balance in SAP and compare the account values. there are a few accounts which have differences. When i looked into it i found out that the FAGLFLEXT table which carries the totals for the accounts have wrong balances for a few accounts. I'm not sure why this is but it is a definite showstopper at the moment. I have searched for notes related to it but have not been able to find an answer to it.
    Have any of you experienced this issue before? would appreciate any help you could provide me.
    Thank you,
    dilanke

    Dear All,
    This is a bug in SAP and they are looking at it to correct the issue. closing thread.

Maybe you are looking for

  • There is no disk in the Drive

    When we try to import a song or on occasion we we click on a song to play it we get an error message no number that says "there is not disk in the drive, please insert a disk. Then there is 3 buttons cancel, retry, or skip, I think. Sometimes you hav

  • Scrambled picture in background on photo booth

    Have just installed leopard and have been trying to use the new background features in photo booth but the picture is breaking up and scrambling, i have both re started and power off'd but this has not helped. does anyone have a solution please?????

  • Loading Exception.jar from NERP

    Hi everyone, I am getting XI started on my sytem first time but i have had some problems. After i try to start Integration repository , Java webstart is starting and immediately i get this message it says " Loading Exception.jar from NERP". Read 53k

  • How to get to the first unread post in a visited topic.

    The title seems self-explanatory. Also, is there a way to see in the discussions lists, those we have posted in? Thanks, and happy new year!

  • RSCOLL00 OS collector job is cancelled and getting TIME_OUT dump

    Hi... Am using ECC 5.0 , In our PRD system progaram name RSCOLL00 OS collector job and its getting TIME_OUT dump for the particular job. And i've seen that an error SQL error 3997 occuredin that job log. And this are the dump following search criteri