jconsole and jhs can not run wd commands and I don't think problem is qt related or can be solved by qt.
I had tried commenting the line in jcs_lab.ijs 'must be < 20' assert y<20 also change 'e7' to 'e5' Then this sentence ran fine on linux64 jconsole intel core i-7 quad-core (hyperthread disabled) (qrun bind 99 99)^:10 '' Пт, 29 сен 2017, jprogramming написал(а): > > A solid accidental fix comes from changing echo: > > > echo_z_ =: (0 0 $1!:2&2)`(wd bind 'msgs' ] 0 0 $ 1!:2&2)@.IFQT > > the liberal amount of wd 'msgs' in qrun, seems to let the system (perhaps > down to zmq) catch up to the state it thinks it should be in. > ________________________________ > From: 'Pascal Jasmin' via Programming <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Friday, September 29, 2017 3:50 PM > Subject: Re: [Jprogramming] zmq - big step for J socket services > > > > > > changing the kill verb to: > > kill=: 3 : 0 > access=: su > runa'exit 0' > killp PORT NB. new line. > destroy'' > i.0 0 > ) > > > helps with the sockets command consistently returning empty, and in general > lengthens the test lifetime but > > qrun 11 11 will still fail within 3 "reruns" > > (qrun modified to use e6 instead of e7 for convenience) > > windows 10 > > > ________________________________ > From: Eric Iverson <[email protected]> > To: Programming forum <[email protected]> > Sent: Friday, September 29, 2017 9:59 AM > Subject: Re: [Jprogramming] zmq - big step for J socket services > > > > When you get a server error, lse__c gives you the J error message. I think > this is covered in the lab and in the help. > > kill and related things depend on host services and that code is still a > bit rough and naive. It will be cleaned bup with experience or more > rigorous study. Problems in this area are do not indicate zmq problems per > se. > > Tracking down qrun hang would be worthwhile. Again, I will bet it has to do > with starting/tracking/killing tasks and not directly a zmq problem. > > On Thu, Sep 28, 2017 at 7:14 PM, 'Pascal Jasmin' via Programming < > [email protected]> wrote: > > > its working pretty well, > > > > A suggestion for generic "server error" would be to return the J error > > from the J server instead. Useful for the examples you are showing now. > > (basically show lse__ as client response) > > > > > > > > The labs and examples do eventually hang if repeated enough though. > > A repeated crash on the zmq lab occurs after the lines > > > > kill__c '' > > kill__d '' > > > > servers_jcs_ '' still shows the c port open 65201 > > > > then "jcst port" hangs. > > > > killp_jcs_ 65201 removes it from servers > > the kill__c command later in the lab does not crash. > > > > > > if qrun is repeated enough times, it will also hang the j session. > > ________________________________ > > From: Eric Iverson <[email protected]> > > To: Programming forum <[email protected]> > > Sent: Thursday, September 28, 2017 1:04 PM > > Subject: [Jprogramming] zmq - big step for J socket services > > > > > > > > New addons net/zmq and net/jcs are available. They require 806. > > > > > > The zmq addon has bindings between J and the zmq shared library. > > > > > > The jcs addon has J client/server tools built on the zmq request/reply > > > > pattern. > > > > > > These addons make it much easier and with far less code to provide > > > > high-performance, robust, and scalable socket services. > > > > > > Start with 806-beta-6 installed from the latest zip packages. Then be sure > > > > you have the > > > > latest base library and the net/zmq and net/jcs addons installed. > > > > > > An easy way to get started is to run the jcs lab. > > > > > > start J > > > > load'labs/labs' > > > > lab'~addons/net/jcs/jcs_lab.ijs' > > > > step through the lab > > > > > > The lab will let you know if you need to install zmq and where to look for > > > > info. > > > > > > Sharing zmq install hints in the forum could save others some trouble. > > > > > > *** > > > > Among other things, jcs makes it easy to start other J tasks and to use > > > > them as servers. The lab includes a simple example of starting multiple J > > > > tasks to service a queue of jobs. > > > > > > *** from the jcs lab > > > > zmq is an api built on top of sockets > > > > > > it is available across platforms and removes almost all the mundane and > > > > critical chores in building a solid, high-performance, scalable server > > > > > > if unfamiliar with zmq, it worth looking at: www.zeromq.org > > > > get an overview with: zguide.zeromq.org/page:all > > > > if zmq is not installed, you'll have to look at: > > > > zeromq.org/intro:get-the-software > > > > ---------------------------------------------------------------------- > > > > For information about J forums see http://www.jsoftware.com/forums.htm > > > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
