cmdex | Find command examples

What you want is impossible; clearly the reason you want 'one command' is you want this operation to be instantaneous; that there is no time in between force-killing all open PSQL connections and running dropdb. That's not how it works, the shell just executes these commands one after another.

So.. do the same thing: First run the one command (Make a processbuilder as you are doing and run the command; you don't need cmd.exe /c for it either then), then wait for that to complete, then make another processbuilder and run the dropdb command.

Separately, you really don't need processbuilder at all for the first command; you can use JDBC to send that query too. You can also use JDBC to send a DROP DATABASE query, which is what the dropdb command does under the hood. Then there's no need for processbuilder whatsoever.

The problem is due to the usage of POST verb (in POST /v2/entities/lamp1/attrs?type=lamp) to send the command. POST has create semantics, so it will add the ping attribute to the entity instead of forwarding it to IOTA. Thus, the command never reaches the IOTA, so the IOTA never published in the MQTT broker. This is explained with more detail in the "Important Note" of this section of the documentation.

However, if you use PATCH instead POST (i.e.PATCH /v2/entities/lamp1/attrs?type=lamp) the forwarding takes place so IOTA receives the command and the IOTA will publish {"ping":"Ping Request"} in the /1234/id_lamp1/cmd topic in the MQTT broker.

If you already did POST /v2/entities/lamp1/attrs?type=lamp then first you have to fix the situation deleting the attribute with DELETE /v2/entities/lamp1/attrs/ping on the Orion Context Broker API. Otherwise the local ping attribute you created with POST will take preference over the ping registered attribute at IOTA when you do PATCH and forwarding will not take place.

Run as defines the proxy account to be used to run this step. Proxy accounts defines a security context in which this job step runs. Each proxy corresponds to a security credential. For example, if you try to execute a copy command with CmdExec type, you must use a credential (e.g. Windows user account) that has rights to read the source file and rights to write in the destination folder.

Job steps can be different types:

• Executable programs and operating system commands.

• Transact-SQL statements, including stored procedures and extended stored procedures.

• PowerShell scripts.

• Microsoft ActiveX scripts.

• Replication tasks.

• Analysis Services tasks.

• Integration Services packages.

Each type is executed differently. T-SQL scripts are sent to the database engine, executable programs (CmdExec) starts external programs (e.g. copy to copy files, or DTSRun to run a DTS package outside of SQL Server, as in your example), etc.

If the field is set to AutoIncrement on the table itself, just leave the field out of your Insert-Statement. The value is added by the database itself.

In the process that you are using, with inserting the database output into a php declaration, you need to escape the qoute until it reaches. it would be strange that the substitue string will work in the declaration since the other parts after the single quote would go into the php zone and cause some sort of syntax error. But if you need to do that code above, you would escape it with a backslash character \ as the single quote is converted.

so change this:

the TcpListener.AcceptTcpClient begin I/O request on socket file object. internally IRP allocated and associated with this file object.

the TcpListener.Stop close the socket file handle. when the last handle for a file is closed - the IRP_MJ_CLEANUP handler is called. DispatchCleanup routine cancel every IRPs (I/O requests) that associated with file object for which cleanup is called.

so usually exist only one file (socket) handle which you use in call AcceptTcpClient. and when Stop is called (before client connect) - it close this handle. if handle is single - this is last handle closed, as result all I/O request for it canceled and AcceptTcpClient finished with error (canceled).

but if handle to this socket will be duplicated - close not last handle in Stop not give effect, I/O will be not canceled.

how and why socket handle is duplicated ? by unknown reason all socket handles is inheritable by default. only begin from Windows 7 with SP1 added flag WSA_FLAG_NO_HANDLE_INHERIT which let create a socket that is non-inheritable.

until you not call CreateProcess with bInheritHandles set to true this not play role. but after such call - all inheritable handles (including all your socket handles) will be duplicated to child process.

the redirecting input stream implementation use inheritable named pipes for input/output/error stream. and started process with bInheritHandles set to true. this is have fatal effect for network code - listened socket handle is duplicated to child and Stop close not last socket handle (else one will be in child process - cmd in your case). as result AcceptTcpClient will be not finished.

the exception seems to never be thrown until the process is terminated.

of course. when child process is terminated - the last handle to your socket will be closed and AcceptTcpClient is finished.

what is solution ? on c++ begin from win7 sp1 - always create sockets with WSA_FLAG_NO_HANDLE_INHERIT. on early systems - call SetHandleInformation for remove HANDLE_FLAG_INHERIT.

also begin from vista, when we need start child process with some duplicated handles, instead set bInheritHandles to true, which duplicated all inheritable handle to child process we can explicit set array of handles to be inherited by the child process by using PROC_THREAD_ATTRIBUTE_HANDLE_LIST.

by switching to async methods which seem unaffected by all this

no. absolute does not matter synchronous or asynchronous I/O (socket handle) you use here. the I/O request anyway will be not canceled. simply when you use synchronous call - this is very visible - call not return. if you use asynchronous call and managed environment - here more problematic note this. if you use callback, which must be called when AcceptTcpClient finished - this callback will be not called. if you associate event with this io operation - event will be not set. etc.

The problem comes from how I create my device on my IoT Agent. I have to specify the transport field, which is MQTT. So to make it work, I have to create a device like this :