Doorgaan naar hoofdcontent

Posts

Posts uit juni, 2011 tonen

Cordys: The value is not set for the parameter number

Today I ran into the following problem: <log4j:event logger="com.cordys.xds.internal.transaction.query.XQYQuery" timestamp="1308643015133" level="ERROR" thread="Monitor Stream Reader Thread"> <log4j:message><![CDATA[Failed to execute query. Error: + ' <error TYPE="Enumeration"> <elem>Error :com.microsoft.sqlserver.jdbc.SQLServerException: The value is not set for the parameter number 1.</elem> </error> ']]></log4j:message> <log4j:MDC><![CDATA[host=cvzlaca004 processid=1314]]></log4j:MDC> <log4j:throwable><![CDATA[com.cordys.xds.transaction.exception.DatabaseQueryException: Failed to execute query. Error: + ' <error TYPE="Enumeration"> <elem>Error :com.microsoft.sqlserver.jdbc.SQLServerException: The value is not set for the parameter number 1.</elem> </error> ' Trace: at com.cordys.xds.internal.transaction.query.X

Introduction to Cordys Cloud Provisioning

Introduction In my current Cordys project I am using the Cordys Cloud Provisioning (CCP) functionality of Cordys. I am very excited about this produkt and this blog item I will share my knowledge about it. First I will explain something about provisioning. What is Provisioning? Provisioning is the process of managing Organizations (also called Tenants) and Users to let them use Applications. It manages the usage of applications that can be used as SaaS applications by tenants. It can be used to create new business models. Cordys has made a separate package for this, on top of BOP4 called CCP. With CCP it is possible (among others): Managing Cordys-Applications and non-Cordys applications Managing of Tenants Managing of Users and Roles Keeping track of the usage of the Applications (Metering) Some Terminology The next picture shows the Cordys-ecosystem. A  Tenant  makes use of  SaaS  applications that are delivered by a  PaaS . These applications are developed by  Apps Pro

Address already in use error

During installation of Cordys BOP4 (CU17) we ran into the following problem. I tried to change the client connection point address of the WebGateway, but still no success. Eventually it appeared to be an Apache Config problem. In <Apache_Install_Dir>/conf/extra/httpd-mpm.conf there is a setting. # worker MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_worker_module>     ServerLimit           1     ThreadLimit         200     StartServers          1     MaxClients          200     MinSpareThreads      25     MaxSpareThreads     200      ThreadsPerChild     200     MaxRequestsPerChild