on 02-16-2012 4:01 PM
Hello,
We did a Homogeneous system copy of Portal and created a sandbox for ESS deployment. Copy was made from our DEV Portal system and the sandbox Portal is running fine without any issues. Recently we deployed ESS 603 SP09 in our Portal sandbox and it went fine with some warnings (see below).
Some components were deployed but not started, so we tried to start the same from NWA but no luck. Instead we get below error:
Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 11206050, message [ JMX request (java) v1.0 len: 165 | src: cluster target-node: 11206050 req: queryNames params-number: 2 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=11206050, null ]
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:518)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.queryNames(MBeanServerConnectionImpl.java:493)
at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.queryNames(MBeanServerConnectionSecurityWrapper.java:254)
at com.sap.engine.services.jmx.ClusterInterceptor.queryNames(ClusterInterceptor.java:1060)
... 54 more
Caused by: com.sap.engine.frame.cluster.message.DestinationNotAvailableException: Participant 11,206,050 is not available.
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(ClusterManagerImpl.java:2436)
But we have checked the Instance cluster (12060) and we cannot find the node with ID 11206050. We have server node with ID 1206050 and dispatcher node (1206000), but in the error it is trying to connect to 11206050.
We also deployed ESS in our DEV Portal yesterday and got the same warnings which we got in sandbox Portal, but we were able to start the components from NWA in DEV Portal.
Could anyone of you provide some hint were could be the issue.
Thanks in advance.
Deployment of SDAs below finished with warnings:
development component 'ess/fi/fam'/'sap.com'/'MAIN_ERP53VAL_C'/'10959664'/'1'
development component 'ess/jp/yeainsform'/'sap.com'/'MAIN_ERP53VAL_C'/'10959705'/'1'
development component 'ess/in/sec80c'/'sap.com'/'MAIN_ERP53VAL_C'/'10959596'/'1'
development component 'ess/au/hdaps'/'sap.com'/'MAIN_ERP53VAL_C'/'10959647'/'1'
development component 'ess/in/f16'/'sap.com'/'MAIN_ERP53VAL_C'/'10959690'/'1'
development component 'ess/gb/additionalpdata'/'sap.com'/'MAIN_ERP53VAL_C'/'10959575'/'1'
System details:
Portal: NW 7 EHP1
OS: AIX 6.1
DB: Oracle 10.2.0.4
Please do the following:
1)Logon to config tool and go to configuration editor mode or
config editor (accessible with the "Switch to
configuration editor mode" button in the Config Tool) navigate to:
Configurations -> cluster_data -> dispatcher -> ID<disp_ID> -> kernel
-> Propertysheet ClusterManager (for the dispatcher) and
place the value as : dispatcher 0 nn_nnnnn
E.g. if the instance id is : 634718, the value above should be
dispatcher 0 6_34718
Configurations -> cluster_data -> server -> ID<server_ID> -> kernel
-> Propertysheet ClusterManager (for the server node)
Taking the above example please check the value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vipin,
Bulls eye!! Thanks for your answer..that solved my issue.
Regards,
Yoganand.V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.