on 01-23-2006 3:39 PM
Hi Everbody,
reading all entries to this topic I found a lot of solutions. Unfortunately not the right one for my problem. So I hope to get some responses when I explain it:
I had a<b> NW04 (6.40 ABAP)-System</b>. In addition I installed the <b>WAS 6.40 Java-Ad</b>dIn. Directly after the installaion both instances startet correctly, and I also could connect to the visual Administrator (VM). Connection-profile: default (J2EE-ADMIN).
After this I restartes the server.
From now it is not possible to logon to the VM. Trying this, I get the message:
<b>"http://<host>:8101/msgserver/text/logon returned empty list of connection parameters."</b>
I tryed to connect with new profile:
type: direct connection
user name: J2EE_ADMIN
host: <host>
port: 8101
result: "<b>cannot open connection on host: <ip> and port: 8101</b>"
I am thankful for every help...
David
Unable to login in Visual admin is a error when java server is not running.Check whether j2ee is able to connect to database.
Try to increase your Max Heap size in configtool if its is not set up correctly
Regards
Santosh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
Are both the instances running correctly after restarting
the server, in the SAP MMC?
Also you can check whether the J2EE start page http://<FullyQualifiedHostName>:5xx00/index.html is
opening correctly. If its not, then the J2EE Engine is
not properly running.
Regards
Srikishan
Message was edited by: Srikishan D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srikishan,
both instances are running correctly in the MMC.
But the http://<FullyQualifiedHostName>:5xx00/index.html is not available. What should i do?
Regards
David
Hi David,
reading the output of your dev_jcontrol I am wondering why your J2EE cannot connect to the message server because this it what keeps the J2EE from not starting correctly. This is just a rough guess but maybe you do have some other process running on the port 3601 and therefore the message server cannot start correctly.
Try to connect to the message server with a telnet client just to see if there is something running on port 3601
You might also want to look at the SCS instance profile under /usr/sap/<SID>/SYS/profile/. Look for a file with a name similar to the schema <SID>_SCS01_<SERVERNAME> in there you can find a parameter named rdisp/msserv. This is the parameter which points the system to your message server of the SCS Instance of the Installation. This is just to be sure your message server is running on the correct port or at least trying to connect to the correct port.
If nothing of this helps, there might be a zombie process still being connected to 3601. Then I would suggest a complete reboot of the machine if possible.
regards Ingo
Hi David,
If the message server is not connected, then the status in
the SAP MMC cannot be fine. The system status cannot be
green. What is the status of the processes: msg_server.exe
, disp+work.exe, etc?
Also please check the P4 port value in the ConfigTool, if
it matches. Also confirm whether the JDK version and the
profile parameters are correct(use note 741289). Check
whether jcontrol or jlaunch processes are running in the
Task manager. Use tcode smicm to check the Engine data.
As suggested, you may as well try to restart the entire
machine, if possible.
Regards
Srikishan
Hi,
As far as I know, the following connection parameters
should work fine, if both instances run properly. I find
something wrong in the port number you are using.
connection type: direct
user name: J2EE_ADMIN
host: fully qualified domain name of the host
port: Using the P4 port 5<xx>04 where xx is the central
instance number.
Please correct me if I am wrong anywhere, but the P4 port
is usually used in the visual admin.
Regards
Srikishan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
David,
I have seen this kind of problem when the J2EE engine doesn't come up completely.
Check the default trace in your server0 log-directory and also dev_jcontrol, dev_server0 in the instance work directory.
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
dev_jcontrol:
[Thr 5212] Fri Jan 20 13:47:18 2006
[Thr 5212] *** ERROR => MsIAttachEx: NiBufConnect to <host>/3601 failed (rc=NIECONN_REFUSED) [msxxi.c 633]
[Thr 5212] *** WARNING => Can't reconnect to message server (<host>/3601) [rc = -100]-> reconnect [jcntrms.c 295]
[Thr 4564] Fri Jan 20 13:47:22 2006
[Thr 4564] *** ERROR => Can't terminate process (pid=4284,handle=000006CC,err=5) [jstartnt.c 644]
[Thr 4564] *** ERROR => Critical error, can't terminate process server0 (pid:4284) (rc=-2) [jcntrxxi.c 340]
[Thr 4564] JControlICheckProcessList: process server0 (pid:4284) died (STOPPING)
[Thr 4564] JControlIResetProcess: reset process server0
[Thr 4564] *** ERROR => MsIModState: not_attached [msxxi.c 3658]
[Thr 4564] *** ERROR => Can't modify state (state=7, rc=-3) [jcntrms.c 667]
[Thr 4564] JControlCloseProgram: started (exitcode = 0)
[Thr 4564] JControlCloseProgram: good bye... (exitcode=0)
server0 log-directory:
#
#1.5#000D9D962801005F0000000B000010BC00040AC9ACA3593A#1137761208006#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#J2EE_GUEST#2####9e33cd7089b211da8638000d9d962801#Thread[Thread-77,5,main]##0#0#Error##Plain###Timeout while stopping service webdynpro.#
#1.5#000D9D962801006200000008000010BC00040AC9ACA63347#1137761208193#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.run()######9f438fc089b211dac09c000d9d962801#Thread[Thread-78,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Java###Reconnect to message server failed ().#1#Connection refused: connect# #1.5#000D9D962801005E00000047000010BC00040AC9ACA7DC48#1137761208302#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E00000049000010BC00040AC9ACD4EE3F#1137761211256#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E0000004B000010BC00040AC9ACD4EF08#1137761211256#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 31 times# #1.5#000D9D962801005E0000004D000010BC00040AC9AD01FCB2#1137761214209#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E0000004F000010BC00040AC9AD2F0ABE#1137761217162#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E00000051000010BC00040AC9AD5DC512#1137761220224#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E00000053000010BC00040AC9AD8C7FEA#1137761223287#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D962801005E00000055000010BC00040AC9ADB98F90#1137761226240#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)# #1.5#000D9D96280100620000000A000010BC00040AC9ADDAF21D#1137761228428#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.run()######9f438fc089b211dac09c000d9d962801#Thread[Thread-78,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Java###Reconnect to message server failed ().#1#Connection refused: connect#
#1.5#000D9D962801005E00000057000010BC00040AC9ADE69E78#1137761229193#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)#
#1.5#000D9D962801005E00000059000010BC00040AC9AE13ADF1#1137761232147#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)#
#1.5#000D9D962801005E0000005B000010BC00040AC9AE40BD60#1137761235100#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######99e3fb5089b211da92a1000d9d962801#SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to q4de3csy073/3201(Connection refused: connect)#
Regards,
David
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.