Recent posts
#71
Web Services / Re: Apache TimeOut and system ...
Last post by EVa - February 11, 2026, 04:22:27 AMThe PxPlus Apache interface runs the *plus/apache/pxp_cgi program which relies on the *SYSTEM SetTimer() function to force a timeout (https://manual.pvxplus.com/?utilities/SYSTEM%20Event%20Handling%20Object/Introduction.htm). I'm assuming that your web application is not resetting that timer as that would cause problems with the Apache timeout. Did you try to connect to these sessions using the 'dbg' console mode command to determine where in your application they are stuck (https://manual.pvxplus.com/?commands/dbg.htm) ?
#72
Web Services / Apache TimeOut and system (pxp...
Last post by yonman - February 04, 2026, 11:51:52 AMAs per documentation, we've a default timeout of 30 seconds for an Apache web service installation. It's not been overridden for years. Starting last year, we've noticed that pxplus sessions, periodically, do not terminate. They don't seem to use any pxplus web licenses while they are hanging there. But, it does slow down the performance hugely, however.
The hug sessions are a variety of web pages, not any one specific page.
Might be a port issue. But, I thought this might be an easy answer for the Pxplus Developers here.
Thank you for any suggestions!
(attached)
timeout= nn
Changes the default 30 second timeout for the maximum run time that a task can take. If a spawned task takes longer than the number of seconds in the timeout period, the system will terminate the task and report an error.
#73
Programming / Re: source code -> binary on l...
Last post by Mike King - February 01, 2026, 11:03:32 PMTake a look at the program "*asctoprg.cnv"
#74
Programming / source code -> binary on linux...
Last post by damonbrodie - January 31, 2026, 09:25:49 AMOn a Linix install, I have a source tree of .pxprg programs in a folder. I want to turn them into pxplus binaries in a sister directory. Basically similar to what would happen if I had an SVN checkout in Windows and I did a SVN UPDATE in the IDE. I assume there is a set of command line args I can use to accomplish this with the pxplus command?
Thanks,
Damon
Thanks,
Damon
#75
General Announcements / PVX Plus January 2026 Update
Last post by PxPlus - January 30, 2026, 02:25:02 PMKeep up to date with what's happening at PVX Plus. Please see our first newsletter of the year.
See details about our Developer's Licensing Program.
January 2026 Newsletter
See details about our Developer's Licensing Program.
January 2026 Newsletter
#76
Web Services / Re: how to send Array of (htm...
Last post by Devon Austen - January 30, 2026, 10:13:13 AMAre you input field in a form?
There are several ways to have a web server interact with PxPlus for a overview check out this: https://home.pvxplus.com/files/7068/2024_v21_-_PxPlus_Web_Tools_Overview.pdf
Webster+ may be a good fir or *Web/Merge.
There are several ways to have a web server interact with PxPlus for a overview check out this: https://home.pvxplus.com/files/7068/2024_v21_-_PxPlus_Web_Tools_Overview.pdf
Webster+ may be a good fir or *Web/Merge.
#77
Web Services / how to send Array of (html) I...
Last post by suriakumar - January 30, 2026, 12:29:05 AMI am having a web page in which i have Array of input text box (HTML). I want to pass these text box values from one to another using pxpluS.
<input name="PAYMENT[1] " type="text" >
<input name="PAYMENT[2]" type="text" >
..
..
..
I am unable to get this in action page. Is there any way to send it in pxplus ?
J.SURIAKUMAR
#78
Thin Client/WindX / Re: 2017v14, Couldn't agree a ...
Last post by cdmoore1972 - January 27, 2026, 11:44:20 PMThe software vendor has a license for the WindX 2017 client. I don't know that they have or are willing to license the newer client, which I'm sure will work.
I'm stuck with dumbing down the cryptography settings on the server until it will work with 2017.
I'm stuck with dumbing down the cryptography settings on the server until it will work with 2017.
#79
Thin Client/WindX / Re: 2017v14, Couldn't agree a ...
Last post by Devon Austen - January 27, 2026, 04:23:46 PMWindX SSH is handled via a included version of plink (putty command line).
It looks like putty got support for that cipher if the AI summary is to be believed in version 0.76. This is newer then your version of PxPlus so it explains the issue.
If you upgrade to the latest version of PxPlus it include plink 0.83 which would support the cipher.
TO find out what ciphers it does support you will have to look up putty documentation for the version of plink in your PxPlus install. It may or may not be possible to enable them on the server.
It looks like putty got support for that cipher if the AI summary is to be believed in version 0.76. This is newer then your version of PxPlus so it explains the issue.
If you upgrade to the latest version of PxPlus it include plink 0.83 which would support the cipher.
TO find out what ciphers it does support you will have to look up putty documentation for the version of plink in your PxPlus install. It may or may not be possible to enable them on the server.
#80
Thin Client/WindX / 2017v14, Couldn't agree a key ...
Last post by cdmoore1972 - January 26, 2026, 10:24:41 PMHello,
My client has 2017v14 licensed through a third party. They're upgrading to a new RedHat 9.x server.
The WindX PxPlus 2017 client works with the (much) older RedHat server, but is getting the following error on the new server just after entering the username into the terminal login prompt:
Couldn't agree a key exchange algorithm (available: curve25519-sha)
I'm assuming that the new server did not enable the KEx or SSH ciphers that come with 2017. Is there a list of those somewhere? I didn't see them in the support docs.
Or if it's something else and you know the fix, I'll take that, instead.
Thanks,
Chris
My client has 2017v14 licensed through a third party. They're upgrading to a new RedHat 9.x server.
The WindX PxPlus 2017 client works with the (much) older RedHat server, but is getting the following error on the new server just after entering the username into the terminal login prompt:
Couldn't agree a key exchange algorithm (available: curve25519-sha)
I'm assuming that the new server did not enable the KEx or SSH ciphers that come with 2017. Is there a list of those somewhere? I didn't see them in the support docs.
Or if it's something else and you know the fix, I'll take that, instead.
Thanks,
Chris