Monitoring server connection
Hello,
i'm developing a client-server application with bluetooth and i must control the connection. So if the connection is down i want display a message.
I'm using a while that send a special message to the server.
My question is: there is another solution?
Thanks
Hi Sriram,
Thanks for looking into this.
I am trying to monitor a RFC connection type of TCP/IP (type T in SM59)
Say the destination name is XYZ. I have tried to use the command as below.
rfcping type=T dest=XYZ
It gave me below error.
Group Error group 101
Key RFC_ERROR_PROGRAM
Message RFC server type unknown (only 2, 3 or E available)
Please let me know what is the correct syntax of this tool.
Regards,
Arijit
Similar Messages
-
Error while Deploying Monitoring Server Reports!
Hi,
Trying to install the monitoring role with reporting services but must have missed one or several steps! :)
Have 1 standard edition server and 1 server running Lync monitoring and SQL (that I installed myself, hopefully correct)
Have installed SQL with instance LYNCSQL\LYNSQL (also checked the reporting services feature)
Have intalled the Standard Edition server
Have installed the Monitoring role
Now I want to "Deploy Monitoring Server Reports" from the Lync Server Deployment Wizard.
Specifying Monitoringserver with FQDN (the same server as the acctual SQL server)
Specifying LYNCSQL\LYNCSQL as the Instance\InstanceID
Specifying the systemaccount that I added during the SQL server installation
Don't specifying any usergroup
Receiving the following error:
Could not get objects from namespace root\Microsoft\SqlServer\ReportServer. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)Cannot get the ReportServerWebService
URL. Verify that Reporting Services is deployed and configured properly on the target SQL instance:"LYNCSQL\LYNCSQL", and that WMI is included on the exception list of firewall setting on the server that is running Reporting Services.Invalid parameter
Windows Firewall is Off!
SQL Server 2008 x64 SP2
When looking in the Lync Server Console I see green status of Standard Edition and the Monitoring Server, but from my LYNCSQL\LYNCSQL i have status of N/A.
Where to start? :)
Update:
Logged on to the Reporting services configuration manager and here are the settings:
Use Built in Account: Local System -> correct or should it be sys.lyncsql as I mentioned before?
Virtual Directory: ReportServer_LYNCSQL
URL: http://servername:80/ReportServer_LYNCSQL
SSL: Not SelectedHi,
Firstly, you need make sure Web Service URL and Report Manager URL could be opened in both Lync FE and SQL server.
If prompt authentication chanllenges you have to change the built in account with "Network Service".
Furthermore, make sure firewall is turned off when troubleshooting to rule out ports and connection issue.
Update let us know.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi Ben,
I have a similar problem where I cant deploy reports. Also, I´m prompted when trying to access /Reports and /ReportsServer using IE on reporting services server.
What do you mean with change the built in account with "Network Service ?
Chech my thread:
http://social.technet.microsoft.com/Forums/en-US/ocsmonitoring/thread/7e213177-9e61-4859-b2a8-301813c4298d
Best regards, Daniel
www.twitter.com/danielullmark -
Error in disp+work.EXE - Running, Message Server connection ok...
Hello gurus,
System: Solution Manager
OS: Windows 2003 server R2 X32
DB: Microsoft SQL server 2005
I have an error when I tried to start my solution manager system, after having done a kernel upgrade (for the level 201)
I donu00B4t know why but the error (as you see in following image) itu00B4s in the java stack more particularly in disp+work.EXE Dispatcher with the status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable".
http://img6.imageshack.us/img6/7067/solmanj2eeerror.png
Can you help me whatu00B4s the problem here?
This next text itu00B4s a dev_disp log... maybe with this you get the error and the solution for that! :
trc file: "dev_disp", trc level: 1, release: "700"
sysno 01
sid PSM
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 201
intno 20050900
make: multithreaded, ASCII, optimized
pid 756
Sun Jul 05 21:08:44 2009
kernel runs with dp version 242(ext=110) (@(#) DPLIB-INT-VERSION-242)
length of sys_adm_ext is 364 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 756) [dpxxdisp.c 1287]
shared lib "dw_xml.dll" version 201 successfully loaded
shared lib "dw_xtc.dll" version 201 successfully loaded
shared lib "dw_stl.dll" version 201 successfully loaded
shared lib "dw_gui.dll" version 201 successfully loaded
shared lib "dw_mdm.dll" version 201 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3901
Sun Jul 05 21:08:49 2009
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5518]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >salzburgo_PSM_01 <
DpShMCreate: sizeof(wp_adm) 16464 (1176)
DpShMCreate: sizeof(tm_adm) 3786880 (18840)
DpShMCreate: sizeof(wp_ca_adm) 18048 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm) 528048 (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1296)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 055C0040, size: 4419544)
DpShMCreate: allocated sys_adm at 055C0040
DpShMCreate: allocated wp_adm at 055C1BF8
DpShMCreate: allocated tm_adm_list at 055C5C48
DpShMCreate: allocated tm_adm at 055C5C78
DpShMCreate: allocated wp_ca_adm at 059624F8
DpShMCreate: allocated appc_ca_adm at 05966B78
DpShMCreate: allocated comm_adm at 059682E8
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 059E9198
DpShMCreate: allocated gw_adm at 059E91D8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 059E9208
DpShMCreate: allocated wall_adm at 059E9210
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
J2EE server info
start = TRUE
state = STARTED
pid = 5700
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( salzburgo) [dpxxdisp.c 12527]
DpStartStopMsg: send start message (myname is >salzburgo_PSM_01 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 201
Release check o.K.
Sun Jul 05 21:08:55 2009
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Sun Jul 05 21:08:57 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2040) [nixxi.cpp 4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:09:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:09:49 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2168
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64999
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:09:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1440
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2126) [nixxi.cpp 4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:10:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:10:29 2009
J2EE server info
start = TRUE
state = STARTED
pid = 5484
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64997
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:10:32 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1532
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2133) [nixxi.cpp 4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:10:49 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:11:09 2009
J2EE server info
start = TRUE
state = STARTED
pid = 3348
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64996
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:11:12 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1436
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2144) [nixxi.cpp 4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:11:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:11:49 2009
J2EE server info
start = TRUE
state = STARTED
pid = 1868
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64995
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:11:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2152) [nixxi.cpp 4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:12:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:12:29 2009
DpEnvCheckJ2ee: switch off j2ee start flag
Best regards,
Jou00E3o Dimas - Portugal
Edited by: Jou00E3o Dimas on Jul 5, 2009 11:39 PMHi uday kumar,
First thank you to tried to help me!
--> So... I have a problem... in that checked that you asked, I donu00B4t have acess to all clients in system... Iu00B4m only able to login to client 000 and 100 and in that clients that two users SAPJSF and J2ee_admin donu00B4t exist!! But maybe in 001... I donu00B4t know!! Itu00B4s any other way to know that? I think through configtool in j2ee directory... but I donu00B4t get that, maybe because I donu00B4t have the JAVA part active!!
--> And other thing, you recommed me to "Check the profile parameters once, try change the JVM setting and check were you able to start the server"... What you want to say with JVM setting.. sorry Iu00B4m still newest in sap world... can you explain me better what you wanted to say..?! Thanks.
--> Other think and the last... I checked the sapstartsrv.log in D:\usr\sap\PSM\SCS00\work directory path and in that it said this:
trc file: "sapstartsrv.log", trc level: 0, release: "700"
Mon Mar 09 11:13:46 2009
<<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND
Can you help me?!... thanks a lot!
Best regards,
Jou00E3o Dimas - Portugal -
Reg. JNDI error when starting monitor server
Hi all,
I am installing CCMS for our CRM4.0 Server. At one point of the installation, it asks to start the monitor server. When I start the monitor.bat it throws a error saying "<b>Cannot Connect to Cluster , beacuse of null. ID003814 : JNDI exception in getinitialContext of InitialContextFactoryImpl</b>".
Can anyone please throw some light on this?
Thanks in advance,
Krishna Karthik PStop the existing IS & AS as root or kill the (ois_server,aaa_server) process manually since the pid, pid_watchdog process are catch hold by root user. Logon as normal oracle user and issue the command start_ois_sever_nptl.
-
Scan to email server connection error for HP Envy 5530
Hi, Everyone!
I LOVE my printer. But, I had to add another laptop (both WIndows) - and then had to add a couple of monitors to that laptop (and a docking statiion) and now it doesn't want to scan to my emails any longer after working like gangbusters for months.
I am connected just fine with an excellent signal - but now when I try the Scan to Email feature - a RED X immediately shows up on the right of the control pad and the message says: Server Connection Error. EVEN though I am wirelessly connected just dandy.
I am not a technical person in the least. I have no idea what to do. I tried all the turn off, turn on stuff. Nothing is working.
Thanks for our help!Hello MisoSilly,
Welcome to the HP Forums!
I understand when you scan to email, you're receiving a message stating server connection error using the Envy 5530. I will do my best to assist you! Follow this entire thread on: Re: server connection error.
Please post your results, as I will be looking forward to hearing from you.
Have a great night!
I worked on behalf of HP. -
VMware workstation下goldengate monitor server的配置
java版本：
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing)
ogg版本：
Oracle GoldenGate Command Interpreter for Oracle
Version 11.1.1.1 12733251
Windows (optimized), Oracle 10g
monitor版本：
11.1for window 32位
物理主机
安装goldengate monitor server，ip：192.168.1.52
monitor.properties
monitor.jmx.server.host=192.168.1.52
虚拟主机1
为ogg源端，ip：192.168.1.101
GGSCI (lf) 9> view param mgr
port 8071
DYNAMICPORTLIST 7840-7850
GGSCI (lf) 10> view param ./globals
MGRSERVNAME test
GGSCHEMA ggs
ENABLEMONITORAGENT
config.properties
jagent.host=192.168.1.101
monitor.host=192.168.1.52
agent.type.enabled=OGGMON
虚拟主机2
ogg目标端，ip：192.168.1.102
GGSCI (lf2) 2> view param mgr
port 8072
DYNAMICPORTLIST 7840-7850
GGSCI (lf2) 3> view param ./globals
MGRSERVNAME test
GGSCHEMA ggs
ENABLEMONITORAGENT
config.properties
jagent.host=192.168.1.102
monitor.host=192.168.1.52
agent.type.enabled=OGGMON
目标端jagent.log报错是：
Fail to open connection to Monitor Server; will retry again in 60 seconds
Exception: (Connection timed out: connect).
JAgent connection info: (com.goldengate.monitor.jagent.config.impl.AgentInfoImpl(host=192.168.1.102, port=5555, configDir=cfg, monitorHost=192.168.1.52, monitorPort=5502, dataFileName=null))
请问是哪里配置错误了吗？？？为何连接不上monitor server？monitor server（物理主机win7）:
C:\Users\linfeng>telnet 192.168.1.102 5555
正在连接192.168.1.102...无法打开到主机的连接。 在端口 5555: 连接失败
C:\Users\linfeng>ping 192.168.1.102
正在 Ping 192.168.1.102 具有 32 字节的数据:
来自 192.168.1.102 的回复: 字节=32 时间<1ms TTL=128
来自 192.168.1.102 的回复: 字节=32 时间<1ms TTL=128
来自 192.168.1.102 的回复: 字节=32 时间<1ms TTL=128
来自 192.168.1.102 的回复: 字节=32 时间<1ms TTL=128
192.168.1.102 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 0ms，最长 = 0ms，平均 = 0ms
目标端（虚拟机win2003）：
C:\Documents and Settings\Administrator>telnet 192.168.1.52 5502
正在连接到192.168.1.52...不能打开到主机的连接， 在端口 5502: 连接失败
C:\Documents and Settings\Administrator>ping 192.168.1.52
Pinging 192.168.1.52 with 32 bytes of data:
Reply from 192.168.1.52: bytes=32 time<1ms TTL=64
Reply from 192.168.1.52: bytes=32 time<1ms TTL=64
Reply from 192.168.1.52: bytes=32 time<1ms TTL=64
Reply from 192.168.1.52: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
双方主机均关闭系统防火墙
帖子经 954488编辑过 -
Monitor_jdbc_conn.sql - Script to monitor JDBC connections
Hi
We are using oracle11 (11.5.10.2) on windows 2000 server
i need to monitor JDBC connections for that i want to schedule that script which runs every hour and after completion it creates output in a file with unique name.
How can i create such script?
Thanks
OHHi;
Please follow below for schedule script-task on windows platform:
How To Schedule Tasks in Windows
http://support.microsoft.com/kb/308569
How To Schedule Tasks in Windows
http://www.iopus.com/guides/winscheduler.htm
How do I schedule jobs on Win32 platforms?
http://docs.activestate.com/activeperl/5.10/faq/Windows/ActivePerl-Winfaq4.html#How_do_I_schedule_jobs_on_Win32_
Hope it helps
Regard
Helios -
EP not starting, Error : Dispatcher running but no server connected
Hi all,
i am getting the following error when i try starting the EP.
<b>Dispatcher running but no server connected
Details : No details availaible</b>
and on the mmc i see that for One of the instancce . the process List has 3 processes
1) msg_server.EXE
2) disp+work.EXE
3) igswd.EXE
all are shown as running but seems there is some problem with disp+work.EXE as it is being shown in yellow colour and not green..
please let me know if any one of you have faced this problem.
i tried restarting the server and machine but it din work
thanks,
rohitHi Bryan ,
i had made few changes in EP module and since then my server is not starting properly. i am not able to login to EP module. so i made changes in UME using configtool.
I changed DataSourceConfiguration to use dataSourceConfiguration_r3_rw.xml and used user J2EE_ADMIN . since then while server comes up it gives some error related to service jms_provider.
so before putting the trace here , can any one tell me which is the default dataSourceConfiguration ? and also what user do i specify ??
i just want to fall back to default datasourceconfiguration
here is the current trace when using dataSourceConfiguration_r3_rw.xml
stdout/stderr redirect
node name : server0
pid : 5276
system name : N4S
system nr. : 01
started at : Sat Nov 04 17:37:33 2006
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4632] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 4015 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 125 ms.
Loading: ThreadManager ... 63 ms.
Loading: IpVerificationManager ... 15 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 610 ms.
Loading: LockingManager ... 156 ms.
Loading: ConfigurationManager ... 5797 ms.
Loading: LicensingManager ... 62 ms.
Loading: CacheManager ... 407 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (31 ms).
Service cross started. (47 ms).
Service memory started. (16 ms).
Service timeout started. (859 ms).
Service file started. (1547 ms).
Service trex.service started. (109 ms).
Service p4 started. (10062 ms).
Service classpath_resolver started. (250 ms).
Service caf~eu~cc~api started. (23265 ms).
Service jmx_notification started. (93 ms).
Service userstore started. (0 ms).
Service log_configurator started. (31093 ms).
Service locking started. (16 ms).
Service http started. (828 ms).
Service naming started. (1704 ms).
Service ts started. (203 ms).
Service javamail started. (500 ms).
Service licensing started. (32 ms).
Service failover started. (140 ms).
Service appclient started. (78 ms).
Service jmsconnector started. (79 ms).
Service iiop started. (765 ms).
Service connector started. (219 ms).
Service webservices started. (1235 ms).
Service deploy started. (29500 ms).
Service configuration started. (78 ms).
Service MigrationService started. (31 ms).
Service bi~mmr~deployer started. (109 ms).
Service dbpool started. (4344 ms).
Service caf~eu~gp~mail~cf started. (63 ms).
Service com.sap.security.core.ume.service started. (5875 ms).
Service caf~eu~odi~mnuacc started. (68281 ms).
Service caf~runtime~connectivity~impl started. (45359 ms).
Service security started. (7828 ms).
Service applocking started. (125 ms).
Service keystore started. (1547 ms).
Service classload started. (1343 ms).
Service shell started. (235 ms).
Service tc~sec~securestorage~service started. (187 ms).
Service tc~eCATTPing~service started. (31 ms).
Service jmx started. (2094 ms).
Service servlet_jsp started. (2328 ms).
Service caf~um~metadata~imp started. (94 ms).
Service telnet started. (453 ms).
Service ssl started. (94 ms).
Service caf~um~relgroups~imp started. (438 ms).
Service basicadmin started. (1391 ms).
Service adminadapter started. (469 ms).
Service prtbridge started. (1625 ms).
Service tc~sec~wssec~service started. (282 ms).
Service dsr started. (515 ms).
Service com.adobe~DocumentServicesConfiguration started. (1000 ms).
Service com.adobe~LicenseService started. (1234 ms).
Service ejb started. (1438 ms).
Service apptracing started. (390 ms).
Service tc.CBS.Service started. (46 ms).
Service monitor started. (1828 ms).
Service caf~eu~gp~model started. (31 ms).
Service CUL started. (4422 ms).
Service tc~eu~jwf~ui~wizsvc started. (1781 ms).
Service com.sap.portal.pcd.gl started. (7609 ms).
Service webdynpro started. (10172 ms).
Service com.sap.portal.prt.sapj2ee started. (2500 ms).
Service rfcengine started. (5688 ms).
Service caf~eu~er~service started. (2093 ms).
Service com.adobe~DataManagerService started. (7953 ms).
Service tc~sec~destinations~service started. (10328 ms).
Service com.adobe~TrustManagerService started. (750 ms).
Service pmi started. (391 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (2110 ms).
Service com.adobe~DocumentServicesDestProtoService started. (672 ms).
Service developmentserver started. (9891 ms).
service jms_provider ================= ERROR =================
Cannot start service DQE; it has hard reference to service jms_provider which is not started.
Service tc~sec~vsi~service started. (1187 ms).
Service sld started. (13172 ms).
Service com.adobe~DocumentServicesBinaries2 started. (1657 ms).
Service com.adobe~PDFManipulation started. (18609 ms).
Service tc.monitoring.logviewer started. (28031 ms).
Service com.adobe~FontManagerService started. (36906 ms).
Service com.adobe~XMLFormService started. (6938 ms).
ServiceManager started for 138203 ms.
Framework started for 150360 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel March 23, 2006 18:47 GMT
### Excluding compile: com.sapportals.portal.prt.jndisupport.util.AbstractHierarchicalContext::lookup
Nov 4, 2006 5:42:09 PM ...p.portal.ivs.semantic.systemLandscape [SAPEngine_Application_Thread[impl:3]_26] Fatal: Failed to create initial folders for system landscape
<b>service jms_provider ================= ERROR =================</b>
Nov 4, 2006 5:45:14 PM ...services.webdynpro.WebDynproContainer [SAPEngine_System_Thread[impl:5]_88] Fatal: Error occured during preparation of application startup.
Here is the trace. -
SAP EP Error: Dispatcher running but no server connected!
Hi
Every body
I tried to activate the debug remote, I access on configTool and on the section of process node I activate the options of debugabble, enable debugable , restricted load balancing.
Then I apply the changes and restart the services and my SAP EP didn't run. I try to deploy my app on NWDS and the it can't connect with vm and check whether the SAP J2EE Engine is up and running.
All the services are running.
Then I try to revert the configuration of debug to try deactivate the options, apply and restart the services but my SAP EP get the error:
SAP WebAS Engine is starting...
If this state does not change within a few minutes,
please contact your system administrator.
Check the recommendations in SAP Notes: 943498, 764417
Message: Dispatcher running but no server connected!
Details: No details available
All the services are running.
How can I solve the problem.?This is the log trac.................
trc file: "F:\usr\sap\EPD\JC00\work\dev_server0", trc level: 1, release: "701"
node name : ID1917850
pid : 4544
system name : EPD
system nr. : 00
started at : Tue May 24 10:29:18 2011
arguments :
arg[00] : F:\usr\sap\EPD\JC00\exe\jlaunch.exe
arg[01] : pf=F:\usr\sap\EPD\SYS\profile\EPD_JC00_bvpmepd
arg[02] : -DSAPINFO=EPD_00_server
arg[03] : pf=F:\usr\sap\EPD\SYS\profile\EPD_JC00_bvpmepd
[Thr 4408] Tue May 24 10:29:18 2011
[Thr 4408] *** WARNING => INFO: Unknown property [instance.box.number=EPDJC00bvpmepd] [jstartxx.c 841]
[Thr 4408] *** WARNING => INFO: Unknown property [instance.en.host=bvpmepd] [jstartxx.c 841]
[Thr 4408] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 4408] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties]
-> ms host : bvpmepd
-> ms port : 3901
-> OS libs : F:\usr\sap\EPD\JC00\j2ee\os_libs
-> Admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host : bvpmepd
-> ms port : 3901
-> os libs : F:\usr\sap\EPD\JC00\j2ee\os_libs
-> admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID1917800 : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID1917850 : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID1917800 : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
-> [01] ID1917850 : F:\usr\sap\EPD\JC00\j2ee\cluster\instance.properties
[Thr 4408] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4408] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4376] JLaunchRequestFunc: Thread 4376 started as listener thread for np messages.
[Thr 2556] WaitSyncSemThread: Thread 2556 started as semaphore monitor thread.
[Thr 4408] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4408] CPIC (version=701.2009.01.26)
[Thr 4408] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_19-x64\
[Thr 4408] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\EPD\JC00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID1917850]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_19-x64\
-> java parameters : -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:CompilerThreadStackSize=4096 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HandlePromotionFailure -XX:UseParNewGC -XX:DisableExplicitGC -XX:UseTLAB -XX:PrintGCTimeStamps -XX:PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djco.jarm=1 -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.security.policy=./java.policy -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-201
0-04-22/wily/connectors/AutoProbeConnector.jar;F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=EPD_JC00_server0 -Dcom.wily.introscope.agentProfile=F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/IntroscopeAgent.profile
-> java vm version : 1.4.2_19-rev-b07
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> stack size : 2M
-> root path : F:\usr\sap\EPD\JC00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : F:\usr\sap\EPD\JC00\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 : F:\usr\sap\EPD\JC00\exe\jstartup.jar;F:\usr\sap\EPD\JC00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
[Thr 4408] JLaunchISetDebugMode: set debug mode [no]
[Thr 10136] JLaunchIStartFunc: Thread 10136 started as Java VM thread.
[Thr 10136] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
Java Parameters: -Xss2m
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -XX:MaxNewSize=341M
-> arg[ 4]: -XX:NewSize=341M
-> arg[ 5]: -XX:MaxPermSize=512M
-> arg[ 6]: -XX:PermSize=512M
-> arg[ 7]: -XX:ReservedCodeCacheSize=64M
-> arg[ 8]: -XX:CodeCacheMinimumFreeSpace=2M
-> arg[ 9]: -XX:CompilerThreadStackSize=4096
-> arg[ 10]: -XX:SurvivorRatio=2
-> arg[ 11]: -XX:TargetSurvivorRatio=90
-> arg[ 12]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 13]: -XX:+HandlePromotionFailure
-> arg[ 14]: -XX:+UseParNewGC
-> arg[ 15]: -XX:+DisableExplicitGC
-> arg[ 16]: -XX:+UseTLAB
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -XX:+PrintGCDetails
-> arg[ 19]: -verbose:gc
-> arg[ 20]: -Dsun.io.useCanonCaches=false
-> arg[ 21]: -Djava.awt.headless=true
-> arg[ 22]: -Djco.jarm=1
-> arg[ 23]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 24]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 25]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 26]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 27]: -Djava.security.policy=./java.policy
-> arg[ 28]: -XX:+JavaMonitorsInStackTrace
-> arg[ 29]: -Xbootclasspath/p:F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/connectors/AutoProbeConnector.jar;F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/Agent.jar
-> arg[ 30]: -Dcom.wily.introscope.agent.agentName=EPD_JC00_server0
-> arg[ 31]: -Dcom.wily.introscope.agentProfile=F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/IntroscopeAgent.profile
-> arg[ 32]: -Dsys.global.dir=F:\usr\sap\EPD\SYS\global
-> arg[ 33]: -Dapplication.home=F:\usr\sap\EPD\JC00\exe
-> arg[ 34]: -Djava.class.path=F:\usr\sap\EPD\JC00\exe\jstartup.jar;F:\usr\sap\EPD\JC00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 35]: -Djava.library.path=C:\j2sdk1.4.2_19-x64
jre\bin\server;C:\j2sdk1.4.2_19-x64
jre\bin;C:\j2sdk1.4.2_19-x64
bin;F:\usr\sap\EPD\JC00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_19-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\WinRAR;F:\usr\sap\EPD\SYS\exe\uc\NTAMD64
-> arg[ 36]: -Dmemory.manager=2048M
-> arg[ 37]: -Xmx2048M
-> arg[ 38]: -Xms2048M
-> arg[ 39]: -Xss2M
-> arg[ 40]: -DLoadBalanceRestricted=yes
-> arg[ 41]: -Djstartup.mode=JCONTROL
-> arg[ 42]: -Djstartup.ownProcessId=4544
-> arg[ 43]: -Djstartup.ownHardwareId=W1658296922
-> arg[ 44]: -Djstartup.whoami=server
-> arg[ 45]: -Djstartup.debuggable=no
-> arg[ 46]: -Xss2m
-> arg[ 47]: -DSAPINFO=EPD_00_server
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=00
-> arg[ 50]: -DSAPSYSTEMNAME=EPD
-> arg[ 51]: -DSAPMYNAME=bvpmepd_EPD_00
-> arg[ 52]: -DSAPDBHOST=BVPMEPD
-> arg[ 53]: -Dj2ee.dbhost=BVPMEPD
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 10136] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4852] Tue May 24 10:29:19 2011
[Thr 4852] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4852] Tue May 24 10:29:20 2011
[Thr 4852] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4852] JLaunchISetClusterId: set cluster id 1917850
[Thr 4852] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4852] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Tue May 24 10:29:24 2011
5.804: [GC 5.805: [ParNew: 174592K->12953K(261888K), 0.0158996 secs] 174592K->12953K(2009856K), 0.0159580 secs] -
Dispatcher Running But no Server Connected---- Fluctuate
Hi All,
I found a strange problem in my QA system.
My QA system fluctuates most of the time. It Runs ok but just between 5-10 min after running successfully it suddenly goes down and the connection to the server is lost.
The ABAP stack runs absolutely ok even during that time. But the JAVA stack throws an error like u201CDispatcher is running but no server connected u201C.
Do anyone have any idea on this. The same installation is applied to Dev also and it is working perfectly but the QA is giving me the problem.
Thanks ,
JAY.Yes i got ,,
and here it is...
============================================================================
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[./log/system/server.log]/>
<!PATTERN[server.log]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[ASCII]/>
<!FILESET[0, 5, 10485760]/>
<!PREVIOUSFILE[server.4.log]/>
<!NEXTFILE[server.1.log]/>
<!LOGHEADER[END]/>
#1.5#0003BADBE09F002400000052000059E4000455F2596502B9#1220399277081#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000053000059E4000455F259655E98#1220399277104#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.af finished successfully on server 39925850#
#1.5#0003BADBE09F002400000054000059E4000455F259655F83#1220399277105#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.af finished on current cluster node for 30 ms.#
#1.5#0003BADBE09F002400000055000059E4000455F25965A193#1220399277121#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.security.ws] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000056000059E4000455F259667B9A#1220399277177#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 39925850 during stopApp sap.com/com.sap.aii.security.ws : Application sap.com/com.sap.xi.pck has a weak reference to application sap.com/com.sap.aii.security.ws which is being stopped and it may not work correctly.#
#1.5#0003BADBE09F002400000057000059E4000455F259667CC5#1220399277178#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.security.ws finished successfully on server 39925850#
#1.5#0003BADBE09F002400000058000059E4000455F259667D58#1220399277178#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.security.ws finished on current cluster node for 71 ms.#
#1.5#0003BADBE09F002400000059000059E4000455F25966BE50#1220399277194#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.pmi.adm] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000005A000059E4000455F25966C522#1220399277196#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.pmi.adm finished successfully on server 39925850#
#1.5#0003BADBE09F00240000005B000059E4000455F25966C5C3#1220399277196#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.pmi.adm finished on current cluster node for 15 ms.#
#1.5#0003BADBE09F00240000005C000059E4000455F25966FE56#1220399277211#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.docs.examples] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000005D000059E4000455F25967059D#1220399277213#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.engine.docs.examples finished successfully on server 39925850#
#1.5#0003BADBE09F00240000005E000059E4000455F259670641#1220399277213#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.engine.docs.examples finished on current cluster node for 14 ms.#
#1.5#0003BADBE09F00240000005F000059E4000455F259672D2B#1220399277223#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.adapter.caller] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000060000059E4000455F2596732D6#1220399277224#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.af.adapter.caller finished successfully on server 39925850#
#1.5#0003BADBE09F002400000061000059E4000455F259673370#1220399277224#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.af.adapter.caller finished on current cluster node for 8 ms.#
#1.5#0003BADBE09F002400000062000059E4000455F2596783E9#1220399277245#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.repository] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000063000059E4000455F259692FAB#1220399277354#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.repository' application stopped successfully.#
#1.5#0003BADBE09F002400000064000059E4000455F259693D52#1220399277358#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.xi.repository finished successfully on server 39925850#
#1.5#0003BADBE09F002400000065000059E4000455F259693DF7#1220399277358#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.xi.repository finished on current cluster node for 131 ms.#
#1.5#0003BADBE09F002400000066000059E4000455F259697F45#1220399277375#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.security.core.admin] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000067000059E4000455F25969852C#1220399277376#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.security.core.admin finished successfully on server 39925850#
#1.5#0003BADBE09F002400000068000059E4000455F2596985C6#1220399277376#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.security.core.admin finished on current cluster node for 14 ms.#
#1.5#0003BADBE09F002400000069000059E4000455F25969A7A4#1220399277385#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.ispeak.eventlistener] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000006A000059E4000455F25969ACBF#1220399277386#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.af.ispeak.eventlistener finished successfully on server 39925850#
#1.5#0003BADBE09F00240000006B000059E4000455F25969AD5B#1220399277387#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.af.ispeak.eventlistener finished on current cluster node for 8 ms.#
#1.5#0003BADBE09F00240000006C000059E4000455F25969B9DB#1220399277390#/System/Server##com.sap.bcb.support.DeployEventListener.processApplicationEvent######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.bcb.support.DeployEventListener#Plain###BCB application will be stopped now...#
#1.5#0003BADBE09F00240000006D000059E4000455F2596AFCC1#1220399277472#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcbcbici] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000006E000059E4000455F25975D1C9#1220399278182#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/tcbcbici finished successfully on server 39925850#
#1.5#0003BADBE09F00240000006F000059E4000455F25975D288#1220399278183#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/tcbcbici finished on current cluster node for 794 ms.#
#1.5#0003BADBE09F002400000070000059E4000455F2597620B9#1220399278203#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.directory] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000071000059E4000455F259776E5E#1220399278288#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.directory' application stopped successfully.#
#1.5#0003BADBE09F002400000072000059E4000455F2597779D7#1220399278291#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.xi.directory finished successfully on server 39925850#
#1.5#0003BADBE09F002400000073000059E4000455F259777A78#1220399278291#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.xi.directory finished on current cluster node for 105 ms.#
#1.5#0003BADBE09F002400000074000059E4000455F259779C04#1220399278300#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcwdpdfsvrchal] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000075000059E4000455F25977A12F#1220399278301#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/tcwdpdfsvrchal finished successfully on server 39925850#
#1.5#0003BADBE09F002400000076000059E4000455F25977A1CB#1220399278301#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/tcwdpdfsvrchal finished on current cluster node for 7 ms.#
#1.5#0003BADBE09F002400000077000059E4000455F25977DF6D#1220399278317#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.heartbeat] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000078000059E4000455F259785B52#1220399278349#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.engine.heartbeat finished successfully on server 39925850#
#1.5#0003BADBE09F002400000079000059E4000455F259785C06#1220399278349#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.engine.heartbeat finished on current cluster node for 46 ms.#
#1.5#0003BADBE09F00240000007A000059E4000455F25978A79B#1220399278368#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.mdt] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000007B000059E4000455F25979FC58#1220399278455#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.xi.mdt finished successfully on server 39925850#
#1.5#0003BADBE09F00240000007C000059E4000455F25979FD0E#1220399278456#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.xi.mdt finished on current cluster node for 105 ms.#
#1.5#0003BADBE09F00240000007D000059E4000455F2597A1E57#1220399278464#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.rfc.app] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000007E000059E4000455F2597A2396#1220399278465#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.af.rfc.app finished successfully on server 39925850#
#1.5#0003BADBE09F00240000007F000059E4000455F2597A2431#1220399278466#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.af.rfc.app finished on current cluster node for 8 ms.#
#1.5#0003BADBE09F002400000080000059E4000455F2597A426D#1220399278473#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.class.download] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000081000059E4000455F2597A475A#1220399278475#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.engine.class.download finished successfully on server 39925850#
#1.5#0003BADBE09F002400000082000059E4000455F2597A47F3#1220399278475#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.engine.class.download finished on current cluster node for 7 ms.#
#1.5#0003BADBE09F002400000083000059E4000455F2597A6C56#1220399278484#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.pck] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000084000059E4000455F2597AA4ED#1220399278499#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.pck' application stopped successfully.#
#1.5#0003BADBE09F002400000085000059E4000455F2597AAFAB#1220399278501#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.xi.pck finished successfully on server 39925850#
#1.5#0003BADBE09F002400000086000059E4000455F2597AB05B#1220399278501#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.xi.pck finished on current cluster node for 24 ms.#
#1.5#0003BADBE09F002400000087000059E4000455F2597ACFA9#1220399278509#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.jmsadapter] finished successfully on Web Container.#
#1.5#0003BADBE09F002400000088000059E4000455F2597AD48F#1220399278511#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.aii.af.jmsadapter finished successfully on server 39925850#
#1.5#0003BADBE09F002400000089000059E4000455F2597AD53B#1220399278511#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.aii.af.jmsadapter finished on current cluster node for 7 ms.#
#1.5#0003BADBE09F00240000008A000059E4000455F2597AF7C9#1220399278520#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcTechSrvXML_DAS] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000008B000059E4000455F2597B4D7C#1220399278542#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tcTechSrvXML_DAS' application stopped successfully.#
#1.5#0003BADBE09F00240000008C000059E4000455F2597B5550#1220399278544#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/tcTechSrvXML_DAS finished successfully on server 39925850#
#1.5#0003BADBE09F00240000008D000059E4000455F2597B55EA#1220399278544#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/tcTechSrvXML_DAS finished on current cluster node for 31 ms.#
#1.5#0003BADBE09F00240000008E000059E4000455F2597B7AE9#1220399278553#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcmonitoringsysteminfo] finished successfully on Web Container.#
#1.5#0003BADBE09F00240000008F000059E4000455F2597B7FBE#1220399278555#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tcmonitoringsysteminfo' application stopped successfully.#
#1.5#0003BADBE09F002400000090000059E4000455F2597B8562#1220399278556#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/tcmonitoringsysteminfo finished successfully on server 39925850#
#1.5#0003BADBE09F002400000091000059E4000455F2597B860F#1220399278556#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/tcmonitoringsysteminfo finished on current cluster node for 10 ms.#
#1.5#0003BADBE09F002400000093000059E4000455F2597BBA47#1220399278570#/System/Server##com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame#Plain###Cannot lookup Deploy service.
The error is: java.lang.ClassCastException: null
Exception id: [0003BADBE09F002400000092000059E4000455F2597BB924]#
#1.5#0003BADBE09F004400000015000059E4000455F2597BDE91#1220399278579#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service servlet_jsp stopped.#
#1.5#0003BADBE09F004400000016000059E4000455F2597BE858#1220399278581#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service adminadapter stopped.#
#1.5#0003BADBE09F004400000017000059E4000455F2597F9A9D#1220399278824#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service monitor stopped.#
#1.5#0003BADBE09F004400000018000059E4000455F2598006D9#1220399278851#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service basicadmin stopped.#
#1.5#0003BADBE09F004400000019000059E4000455F259810CCC#1220399278918#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service apptracing stopped.#
#1.5#0003BADBE09F00440000001A000059E4000455F259821AAC#1220399278987#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service jms_provider stopped.#
#1.5#0003BADBE09F0032000000B5000059E4000455F259826C15#1220399279008#/System/Server##com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer######5c5547a0794511dd855e0003badbe09f#Thread[SAPEngine_CCMSCommandConsumer_0,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Info#1#com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#Plain###CCMSGeneration thread was interrupted#
#1.5#0003BADBE09F00440000001B000059E4000455F259826E13#1220399279009#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service tc.monitoring.logviewer stopped.#
#1.5#0003BADBE09F00440000001C000059E4000455F2598277B3#1220399279011#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service jmx stopped.#
#1.5#0003BADBE09F00440000001D000059E4000455F25982BD65#1220399279029#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service webdynpro stopped.#
#1.5#0003BADBE09F00440000001E000059E4000455F25982C474#1220399279031#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service telnet stopped.#
#1.5#0003BADBE09F00440000001F000059E4000455F259832F9D#1220399279058#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service shell stopped.#
#1.5#0003BADBE09F004000000009000059E4000455F2598332E1#1220399279059#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Warning#1#com.sap.engine.services.deploy#Plain###Stopping application sap.com/com.sap.jdo which is in started mode, because the resource applocking with type service is not available.#
#1.5#0003BADBE09F00400000000A000059E4000455F2598357B8#1220399279069#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.jdo' application stopped successfully.#
#1.5#0003BADBE09F00400000000B000059E4000455F259835E58#1220399279070#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application sap.com/com.sap.jdo finished successfully on server 39925850#
#1.5#0003BADBE09F00400000000C000059E4000455F259835EF6#1220399279070#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp on application sap.com/com.sap.jdo finished on current cluster node for 9 ms.#
#1.5#0003BADBE09F002D00000036000059E4000455F25983691D#1220399279073#/System/Server##com.sap.engine.services.applocking.AppLockingApplicationFrame.unbindFromNaming(expectNamingAvailable)######8d473310794911ddc2a40003badbe09f#SAPEngine_System_Thread[impl:5]_63##0#0#Info#1#com.sap.engine.services.applocking.AppLockingApplicationFrame#Java###Successfully unbound from JNDI#1#applocking-service#
#1.5#0003BADBE09F002D00000037000059E4000455F259836A3C#1220399279073#/System/Server##com.sap.engine.services.applocking.AppLockingApplicationFrame.stop()######8d473310794911ddc2a40003badbe09f#SAPEngine_System_Thread[impl:5]_63##0#0#Info#1#com.sap.engine.services.applocking.AppLockingApplicationFrame#Java### stopped successfully#1#applocking-service#
#1.5#0003BADBE09F004400000020000059E4000455F259836CED#1220399279074#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service applocking stopped.#
#1.5#0003BADBE09F004400000021000059E4000455F25983DD86#1220399279103#/System/Server##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service dsr stopped.#
#1.5#0003BADBE09F004900000043000059E4000455F2599103AF#1220399279965#/System/Server##com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#Plain###New thread spawned for generating the ccmstemplates.#
#1.5#0003BADBE09F004900000044000059E4000455F2599141AA#1220399279980#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register a new log#
#1.5#0003BADBE09F006900000008000059E4000455F2599141F8#1220399279981#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register a new log#
#1.5#0003BADBE09F00690000000A000059E4000455F2599148D9#1220399279982#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null#
#1.5#0003BADBE09F004900000046000059E4000455F25991495F#1220399279982#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null#
#1.5#0003BADBE09F004900000048000059E4000455F25991587A#1220399279986#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###Originated from: com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null
at com.sap.engine.services.jmx.JmxFrame.getInnerMBeanServer(JmxFrame.java:467)
at com.sap.engine.services.jmx.ClusterInterceptor.getInnerMBS(ClusterInterceptor.java:119)
at com.sap.engine.services.jmx.ClusterInterceptor.getMBSC(ClusterInterceptor.java:190)
at com.sap.engine.services.jmx.ClusterInterceptor.isRegistered(ClusterInterceptor.java:868)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.isRegistered(MBeanServerInterceptorChain.java:290)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:229)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
at com.sap.tc.logging.LoggingManager.notifyAddLog(LoggingManager.java:342)
at com.sap.tc.logging.LogController.addLog(LogController.java:1328)
at com.sap.tc.logging.PropertiesConfigurator.configure(PropertiesConfigurator.java:1119)
at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:314)
at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:257)
at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)
at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.createQueueConnection(QueueConnectionFactoryImpl.java:162)
at com.sap.engine.services.ejb.message.JMSBridge.createConnection(JMSBridge.java:194)
at com.sap.engine.services.ejb.message.JMSBridge.registerQueueListener(JMSBridge.java:142)
at com.sap.engine.services.ejb.message.JMSBridge.recreateJMSConnection(JMSBridge.java:278)
at com.sap.engine.services.ejb.message.MDBExceptionListener.onException(MDBExceptionListener.java:38)
at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.onException(ConnectionImpl.java:118)
at com.sap.jms.client.connection.Connection.onException(Connection.java:824)
at com.sap.jms.server.ServerClientAdapter$ExceptionListenerCaller.run(ServerClientAdapter.java:366)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0003BADBE09F00690000000C000059E4000455F259915885#1220399279986#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###Originated from: com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null
at com.sap.engine.services.jmx.JmxFrame.getInnerMBeanServer(JmxFrame.java:467)
at com.sap.engine.services.jmx.ClusterInterceptor.getInnerMBS(ClusterInterceptor.java:119)
at com.sap.engine.services.jmx.ClusterInterceptor.getMBSC(ClusterInterceptor.java:190)
at com.sap.engine.services.jmx.ClusterInterceptor.isRegistered(ClusterInterceptor.java:868)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.isRegistered(MBeanServerInterceptorChain.java:290)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:229)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
at com.sap.tc.logging.LoggingManager.notifyAddLog(LoggingManager.java:342)
at com.sap.tc.logging.LogController.addLog(LogController.java:1328)
at com.sap.tc.logging.PropertiesConfigurator.configure(PropertiesConfigurator.java:1119)
at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:314)
at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:257)
at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)
at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.createQueueConnection(QueueConnectionFactoryImpl.java:162)
at com.sap.engine.services.ejb.message.JMSBridge.createConnection(JMSBridge.java:194)
at com.sap.engine.services.ejb.message.JMSBridge.registerQueueListener(JMSBridge.java:142)
at com.sap.engine.services.ejb.message.JMSBridge.recreateJMSConnection(JMSBridge.java:278)
at com.sap.engine.services.ejb.message.MDBExceptionListener.onException(MDBExceptionListener.java:38)
at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.onException(ConnectionImpl.java:118)
at com.sap.jms.client.connection.Connection.onException(Connection.java:824)
at com.sap.jms.server.ServerClientAdapter$ExceptionListenerCaller.run(ServerClientAdapter.java:366)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
================================================================================== -
"timed out obtaining dynamiclink server connection" in After Effects
I've seen a lot of other people have this same problem, none of the solutions ive seen are working for me.
Problem appears when i try to track camera, it goes to 'analyzing in background' then after 2 minutes or so it gives me the "timed out obtaining dynamiclink server connection" error pop-up.
Mac OSX 10.7.5
Using Adobe After effects CC
2 x 2.4ghx quad-core intel xeon
15gb ddr3 ram
I've uninstalled Logmein which appeared as a problem in one of the solutions but that hasn't changed anything. Don't have a firewall running. Tried uninstalling After Effects CS6 and After Effects CC and then reinstalling After Effects CC. Dynamiclinkmanager pops up in activity monitor intermittently, it comes and goes repeatedly when i try to 'Track Camera' but never shows any actual use of memory.
Is anyone able to offer help?
Could it be some confusion in preferences / library files between my CS6 installs and CC installs?
Thanks in advanceRefer to this:
http://myleniumerrors.com/2013/01/27/25-101-4/
Mylenium -
Using control reference with a Sub-vi over a TCP VI Server connection
I tried to use a Call by Reference Node to run a sub-vi on a remote PC through a TCP VI Server. An output of the sub-vi is connected to an indicator in the main vi using a control reference.
The sub-vi started on the remote PC, but the information from the sub-vi was not passed to the control reference in the main vi. However, if I change the client name to the host PC, ie. running the server and client vi on the same machine, the code works as planned. I wonder if control reference is not suppose to work over a TCP VI Server connection?
Any suggestion would be very much appreciated.
Regards,
Calvin Tsang
Attachments:
main_vi.vi 29 KB
sub_vi.vi 20 KBThank Jean-Pierre for pointing out that Refnums are local to an application and so control reference doesn't work between different applications on separate machines.
In addition to the method shown in Jean-Pierre's example vi, I found that the use of "invoke method: GET control value" and "invoke method: SET control value" can produce similar results. See the attached files for an example. In this example, the indicator on the local vi is used to monitor the progress of the remote vi and the local control is used to stop the remote vi. So the data synchronisation between the two vi is not important here.
However, you may notice the indicator "current counter" in main1_vi.vi doesn't properly interpret the binary string from "invoke method: GET control
value", can someone shed some light on this, please?
Calv
Attachments:
main1_vi.vi 48 KB
sub1_vi.vi 13 KB -
Not alone with problems on "Mail" app server connection, iMap!!!! I believe Apple is strengthening their server farm. Has been out for over a week; they were wise to have the iCloud also in the cloud. Be patient!
Have you considered the possibility that the third party fan software might itself be implicated in the issue, theosib (or perhaps something else introduced at about that time?).
My inclination in a situation like this would be to back up your drive to an external, wipe the drive, and do a clean installation. At the very least I'd try an archive and install.
Do you have plenty of free space on the drive? Once you get things down below the last 10 to 20% things can get hairy at times, and may not be fixed as a result of simply freeing up some room, as free space fragmentation is likely to have set in.
As far as RAM goes, either "Rember" - http://www.kelleycomputing.net:16080/rember/ or, better still, but less user friendly, "memtest" - http://www.memtestosx.org/ does a much better job of checking your RAM than the AHT. Still takes a while to run for a thorough test, but much quicker than the approach you are planning on using.
You might also want to use "Activity Monitor" to check for any applications with progressive "memory leaks" or that are acting as CPU hogs, given your symptoms
Cheers
Rod -
SQL Server Connection over WAN Link
I am planning
to setup a BlackBerry server and connect to a remote SQL Server over a
WAN link with 150+ms ping time. Is there a known tolerance for
SQL server connection latency? For example, I have been told by
RIM that ping time for Exchange should be around 35ms so if it is
higher, a BES should be placed next to the Exchange server. Any reply would be greatly appreciated.There is no problem with slow connection :-)
You might get lots of waits in the SQL side (most likly there will be lots of
ASYNC_NETWORK_IO) which you can monitor using sys.dm_os_waiting_tasks and sys.dm_exec_requests. But if there is no disconnections then most small application will work OK
[Personal Site] [Blog] [Facebook] -
Error while creating a application server connection in jdeveloper 10.1.3.2
When I am trying to create a connection using the wizard with the following inputs
hostname as :- localhost
RMI Por as 22667
When I use the test conection receive the following error
racle.oc4j.admin.jmx.shared.exceptions.JMXRuntimeException: Error while getting remote MBeanServer for url: ormi://localhost:22667/default
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:502)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
at java.lang.Thread.run(Thread.java:613)
Caused by: javax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused] [Root exception is java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]]
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
... 14 more
Caused by: java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
... 20 more
Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
... 21 more
Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
... 26 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
... 28 more
---- Embedded exception
javax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused] [Root exception is java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]]
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
at java.lang.Thread.run(Thread.java:613)
Caused by: java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
... 20 more
Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
... 21 more
Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
... 26 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
... 28 more
---- Embedded exception
java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
at java.lang.Thread.run(Thread.java:613)
Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
... 21 more
Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
... 26 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
... 28 moreCaused by: java.net.ConnectException: Connection refused
Is the Oracle application server running?
Maybe you are looking for
-
I recently purchased iPad 4 and it is only one month old. I updated with iOS 7 and next day got problem with Skype and yahoo mails. People can't hear me on Skype though I can hear them clearly. I was replying yahoo mails quite nicely and now as I sta
-
How to deploy a Webapplication on WAS more than one times on same server?
Hi all, I 've a special problem: In our web-app (some DC's) also stored propertie-Files. Now we would to deploy this application more than one times at same server using different WebContentRoots. (f.e. http://server/app1 and http://server/app2 a.s.o
-
Goods receipt with blanket po's
Hi all, We have a scenario that results to a PR (originated from a SRM shopping Cart) with the item cat. B en AAC U. The AAC is changble to K and the best scenario would be that the item cat is also changeble, but that don't works. So item cat B it i
-
Multiple Logon Restriction in EP5.0 SP6
Hi, We are using the EP5.0 with SP6. BVackend CRM System. We have to restrict the users for single logon into the enterprise Portal. Can any one please let us know how to achieve this Single Logon. Its Very Urgent. WE are in Testing Phase and need to
-
My inbox/ view/ zoom in or out settings greyed out. Can't enlarge text! Thunderbird ver 31.4.0
The problem is simply, that the zoom setting is there, but greyed out and doesn't work for the inbox text. Once I open an e-mail, the zoom works fine. I'm using a large screen HD TV connected to the PC via HDMI with 1920X1080p resolution, which makes