Error In Strategy 0015 Closed Server
Contents |
thousands of posts from hundreds of Genesys users, we hope you will have all of your Genesys-related questions answered as well as learn something genesys university new along the way. There is no membership required for posting and
Genesys Certification
you are welcome to ask as little questions or as much questions as you like. This community is supported by users like yourself, so if you can help with someone else's questions, it would be greatly appreciated!(Just in case you were wondering - No, Genesys Labs does not endorse this site) - Genesys CTI Team Home Help Search Login Register Genesys CTI User Forum » Genesys CTI User Forum » Genesys CTI Technical Discussion (Moderator: victor) » Configure URS to use Webservices « previous next » Send this topic Print Pages: [1] Go Down Author Topic: Configure URS to use Webservices (Read 2802 times) cavagnaro Administrator Hero Member Posts: 5583 Karma: 65526 Configure URS to use Webservices « on: March 25, 2010, 06:02:35 AM » Hi guys,I have created a section called "web" under URS Options tab and added the following options:Quote[web]http-port=9780http_log_file=webservices.loghttp_log_size=1024log_check_interval=60log_remove_old_files=offparser_log_file=parser.logsoap_conn_idle_timeout=15soap_recv_timeout=5soap_retry_attempts=2soap_retry_timeout=10soap_send_timeout=5verbose=6xml_log_file=xml.logHowever I can't make it work or at least see some XML or SOAP events...What I get is:Quote _I_I_007001ca17aa2a4b [14:33] strategy: *0x65*WebServiceSMS is attached to the call15:47:30.137 Int 20001 interaction 007001ca17aa2a4b is started _I_I_007001ca17aa2a4b [01:14] current call classification: media=voice(100), service=default(200), segment=default(300)15:47:30.137_I_I_007001ca17aa2a4b [09:06] >>>>>>>>>>>>start interpretator _I_I_007001ca17aa2a4b [09:04] ASSIGN: __Return(SCRIPT) <- STRING: _I_I_007001ca17aa2a4b [07:46] no error mode for this call _I_I_007001ca17aa2a4b [09:04] ASSIGN: __Return(SCRIPT) <- STRING: _I_I_007001ca17aa2a4b [09:04] ASSIGN: __DBReturn(SCRIPT) <- STRING: _I_I_007001ca17aa2a4b [09:04] ASSIGN: __DBStrReturn(SCRIPT) <- STRING: _I_I_007001ca17aa2a4b [09:04] ASSIGN: __TargetVar(SCRIPT) <- STRING: 15:47:30.137_I_I_007001ca17aa2a4b [07:39] HERE IS XDATA _I_E_007001ca17aa2a4b [09:04] error in strategy: 0015 Closed server _I_I_007001ca17aa2a4b [09:04] ASSIGN: __WEBReturn(SCRIPT) <- LIST: list Any idea what else am I missing?ThanksPD: already restarted URS Logged rpenney Jr. Member Posts: 64 Karma: 2 Re: Configure URS to use
Sign in Pricing Blog Support Search GitHub This repository Watch 258 Star 1,953 Fork 544 akkadotnet/akka.net Code Issues 173 Pull requests 22 Projects 2 Pulse Graphs New issue Disassociated error without any reason. #2141 Closed VitaliiPerederii opened this Issue Jul 6, 2016 · 4 comments Projects None yet Labels None yet Milestone 1.1.0 Assignees No one assigned 3 participants VitaliiPerederii commented Jul 6, 2016 • edited Hi all. I've encountered http://www.sggu.com/smf/index.php?topic=5434.0 problem with sudden disassociation when developing system using akka.net remote. Server actor system application is sending a lot of messages (10-20 k/sec )to remote actor. CPU utilization on the server machine is about 100%, thought heartbeat messages is delivered in time. After 3 minutes of working message flow is stopped by the disassociation error. Here is https://github.com/akkadotnet/akka.net/issues/2141 config: akka { stdout-loglevel = DEBUG loglevel = DEBUG actor { debug { receive = on autoreceive = on lifecycle = on event-stream = on unhandled = on fsm = on } serialize-creators = on akka.actor.guardian-supervisor-strategy = "Akka.Actor.SupervisorStrategy.StoppingStrategy" provider = "Akka.Remote.RemoteActorRefProvider, Akka.Remote" serializers { wire = "Akka.Serialization.WireSerializer, Akka.Serialization.Wire" } serialization-bindings { "System.Object" = wire } deployment { /CDRRouterActor/Actor0 { remote = "akka.tcp://DeployTarget@127.0.0.1:8090" } } } remote { helios.tcp { port = 0 hostname = 127.0.0.1 } watch-failure-detector { threshold = 100 acceptable-heartbeat-pause = 1000 s } transport-failure-detector { heartbeat-interval = 1 s # default 4s acceptable-heartbeat-pause = 1000 s # default 10s min-std-deviation = 12 s } } } The log is pretty the same on both nodes: [DEBUG][7/6/2016 2:26:43 PM][Thread 0014][[akka://Reconcilation/system/remote-watcher]] Sending Heartbeat to [akka.tcp://DeployTarget@127.0.0.1:8090] [DEBUG][7/6/2016 2:26:44 PM][Thread 0016][[akka://Reconcilation/system/remote-watcher]] Sending Heartbeat to [akka.tcp://DeployTarget@127.0.0.1:8090] [DEBUG][7/6/2016 2:26:45 PM][Thread 0016][[akka://Reconcilation/system/remote-watcher]] Sending Heartbeat to [akka.tcp://DeployTarget@127.0.0.1:8090] [DEBUG][7/6/2016 2:26:45 PM][Thread 0015][[akka://Reconcilation/system/remote-watcher]] Received heartbeat rsp from [akka.tcp://DeployTarget@127.0.0.1:8090] [DEBUG][7/6/2016 2:26:45 PM][Thread 0017][[akka://Reconcilation/system/remote-watcher]] Received heartbeat rsp from [akka.tcp://DeployTarget@127.0.0.1:8090] [DEBUG][7/6/2016 2:26:45 PM][Thread 0017][[akka://Reconcilation/system/remote-
An error in strategy Error Has Occurred! Sorry Guest, you are banned from using this forum!IP addresses in this netblock create multiple accounts per day.This ban is not set to expire. Back SMF 2.0.9 | SMF © 2014, Simple Machines XHTML WAP2
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 07:16:45 GMT by s_ac4 (squid/3.5.20)