标签: wso2-data-services-server

我正在使用wso2dss 3.0.0.我正在尝试执行postgresql查询,即

SELECT addressid, geocode
FROM maddress
WHERE geocode::point <@ circle '((18.9750,72.8258), 5)';

它在PostgreSQL中工作正常.当我在wso2dss中使用相同的查询时

SELECT addressid, geocode
FROM maddress
WHERE geocode::point <@ circle '((?,?), ?)';    

它给我的错误如下:

DS Fault Message: Error in 'SQLQuery.processNormalQuery'
DS Code: DATABASE_ERROR
Source Data Service:-
Name: Geofence_DataService
Location: /Geofence_DataService.dbs
Description: N/A
Default Namespace: http://ws.wso2.org/dataservice
Current Request Name: adding_geofence_op
Current Params: {longitude=72.8258, radius=4, latitude=18.9750}
Nested Exception:-
DS Fault Message: Error in 'createProcessedPreparedStatement'
DS Code: UNKNOWN_ERROR
Nested Exception:-
org.postgresql.util.PSQLException: The column index is out of range: 1, number of …

我想合并WSO2 ESB和Data Services Products以在一台服务器上执行它们.它们都基于Carbon框架,由一些OSGi包组成.有一个简单的方法来做到这一点.

最好的祝福.

--Seyyed Jamal

我正在使用wso2esb 4.7.0和wso2dss 3.0.0 ..我在wso2dss中编写了一个查询.它在dss中正常工作.另外,但是当我希望在序列介体中使用wso2esb时,它会显示如上所述的错误

 ERROR - RelayUtils Error while building Passthrough stream
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
    at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
    at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
    at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:154)
    at org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXSOAPModelBuilder(AbstractOMMetaFactory.java:73)
    at org.apache.axiom.om.impl.AbstractOMMetaFactory.createSOAPModelBuilder(AbstractOMMetaFactory.java:79)
    at org.apache.axiom.om.OMXMLBuilderFactory.createSOAPModelBuilder(OMXMLBuilderFactory.java:196)
    at org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:55)
    at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:118)
    at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:116)
    at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:91)
    at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:62)
    at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
    at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:232)
    at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:443)
    at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:166)
    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
    at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:222)
    at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:679)
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] …

我正在将WSO2 DSS 3.2.2服务器升级到3.5.0,但我最终收到此错误:

Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.tcp.TCPTransportSender cannot be found by axis2_1.6.1.wso2v15
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:195)
    at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
    at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:686)

这是配置问题还是我需要添加特定的JAR库？如果是的话,哪一个？

编辑:我刚刚发现axis2_1.6.1.wso2v10.jar有这个org.apache.axis2.transport.tcp.TCPTransportSender类,但是axis2_1.6.1.wso2v15.jar没有.

我尝试按照以下说明下载WSO2数据服务服务器(DSS)3.0.1:http: //docs.wso2.org/wiki/display/DSS301/Obtaining+the+Product

据说有用:

wget --user-agent="testuser" http://dist.wso2.org/products/data-services-server/3.0.1/wso2dss-3.0.1.zip

我用谷歌搜索并尝试了--user-agent ="Mozilla"和其他东西,但都没有用.我注册并尝试使用--user = user和--password = pass,但也没有运气.

我使用RedHat linux服务器.有没有人有类似的情况？

谢谢.

我试图在WSO2数据服务服务器中创建一个新的数据服务以连接SQL Server 2005.但是,每次我测试连接时,我收到错误消息"驱动程序类com.microsoft.jdbc.sqlserver.SQLServerDriver无法加载".

Data Source Type: RDBMS, Non-XA-DataSource
Database Engine: Microsoft SQL Server
Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver 
...

我不相信我的连接字符串或凭据是一个问题,因为它加载驱动程序失败.

我在这个过程中缺少的步骤是什么？

当我尝试运行WSO2 Dataservices或其他WSO2 Carbon服务器时,我收到以下错误:

$ sudo sh /opt/wso2dataservices-2.6.3/bin/wso2server.sh start
Error: JAVA_HOME is not defined correctly.:
CARBON cannot execute java

然后我检查JAVA_HOME变量:

$ echo $JAVA_HOME
/usr/lib/jvm/jdk1.6.0_35

这是正确的道路.该机器已安装64位64位Oracle Java JDK 1.6和64位Ubuntu Server 12.04.

我非常感谢你的回答.谢谢!

从我的dss服务请求json响应时出现以下错误.

{"Fault":{"faultcode":"soapenv:Server","faultstring":"Error while writing to the output stream using JsonWriter","detail":""}}

我通过的卷曲请求

curl -X GET -H "Accept:application/json" -H "Content-Type:application/json" http://localhost:9764/services/userdetails/test

如果我删除接受标头,我得到正确的xml响应.

奇怪的是,如果我从我的同事的笔记本电脑运行相同的dss服务,即时通过上面的curl命令获得正确的json响应.我的电脑有些配置发生了变化,因为我的电脑出现了这个错误.

我无法找到我的电脑中发生了什么变化,因为我收到了这个错误.

我一直在尝试在WSO2 DSS中使用参数化CQL查询.不幸的是我没有成功.当我遇到紧急事件时,请尽快感谢您的帮助.

以下是DBS文件内容

<data name="CassParamTest">
   <config id="CassDs">
      <property name="org.wso2.ws.dataservice.protocol">jdbc:cassandra://localhost:9161/oneDataAux</property>
      <property name="org.wso2.ws.dataservice.driver">org.apache.cassandra.cql.jdbc.CassandraDriver</property>
   </config>
   <query id="getEmps" useConfig="CassDs">
      <sql>select employeeNumber from EMPLOYEES where employeeNumber = :employeeNumber</sql>
      <param name="employeeNumber" sqlType="STRING" />
   </query>
   <operation name="getEmps">
      <call-query href="getEmps">
         <with-param name="employeeNumber" query-param="employeeNumber" />
      </call-query>
   </operation>
</data>

实际上,参数employeeNumber是一个数字.但我不断收到错误.所以我尝试使用String也无济于事.我也试过了？而不是命名参数

这是我得到的错误.

当参数是String时,

<soapenv:Fault xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:axis2ns12="http://ws.wso2.org/dataservice">
   <soapenv:Code>
      <soapenv:Value>axis2ns12:DATABASE_ERROR</soapenv:Value>
   </soapenv:Code>
   <soapenv:Reason>
      <soapenv:Text xml:lang="en-US" xmlns:xml="http://www.w3.org/XML/1998/namespace">DS Fault Message: Error in DS non result invoke.
DS Code: DATABASE_ERROR
Nested Exception:-
javax.xml.stream.XMLStreamException: DS Fault Message: Error in 'SQLQuery.processNormalQuery'
DS Code: DATABASE_ERROR
Source Data Service:-
Name: CassParamTest …

我正在使用邮件传输,我已经完成了axis2文件的更改,我的esb毁了罚款邮件但我的问题是它不发送更合适的格式我希望发送正文但它只是发送"主题"我的配置像这样

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="StaticMail"
       transports="http"
       startOnLoad="true"
       trace="disable">
   <description/>
   <target>
      <inSequence>
         <property name="senderAddress"
                   expression="//mail/text()"
                   scope="default"/>
         <property name="Subject" value="Alert:Reading Out of Range" scope="transport"/>
         <property name="message" value="Response message" scope="transport"/>
         <property name="body" expression="//list/text()" scope="default"/>
         <header name="To"
                 expression="fn:concat('mailto:', get-property('senderAddress'))"/>
         <property name="OUT_ONLY" value="true"/>
         <log level="full">
            <property name="message" value="Response message"/>
            <property name="Sender Address" expression="get-property('senderAddress')"/>
         </log>
         <send/>
      </inSequence>
      <outSequence/>
   </target>
</proxy>

但它只发送这样的邮件格式

提醒:作为主题读取超出范围没有人用于邮件和一个带有"noname"的空附件我们如何发送带有正确身体的邮件请告诉我

我正在创建WSO2ESB代理服务，该服务从WSO2DSS服务器获取数据并对其进行迭代，然后将获取请求发送到WSO2DSS。

<iterate id="it"
        expression="//*[local-name()='data']"
        sequential="true">
  <target>
     <sequence>
        <call>
           <endpoint>
              <http method="GET"
                    uri-template="http://localhost:9766/services/TEST/test?testId={uri.var.testId}"/>
           </endpoint>
        </call>
        <send/>
     </sequence>
  </target>
</iterate>

但是DSS给出了此错误：

[] [2016-11-28 13：13：03,808]错误{org.wso2.carbon.dataservices.core.DBInOutMessageReceiver}-输入/输出消息接收器{org.wso2.carbon.dataservices.core.DBInOutMessageReceiver}错误代码：INCOMPATIBLE_PARAMETERS_ERROR嵌套的异常：-javax.xml.stream.XMLStreamException：DS错误消息：“ CallQuery.extractParams”中的错误，找不到类型为：query-param name：testId DS的参数代码：INCOMPATIBLE_PARAMETERS_ERROR源数据服务：-名称： DAKPR位置：/DAKPR.dbs说明：N / A缺省名称空间：http ://dss.example.com/TEST 当前请求名称：test当前参数：{}

在org.wso2上的org.wso2.carbon.dataservices.core.dispatch.DataServiceRequest.dispatch（DataServiceRequest.java:354）在org.wso2.carbon.dataservices.core.dispatch.SingleDataServiceRequest.processRequest（SingleDataServiceRequest.java:75） org.wso2.carbon.dataservices.core.DBInOutMessageReceiver.invokeBusinessLogic（DBInOutMessageReceiver.java:57）的.carbon.dataservices.core.DataServiceProcessor.dispatch（DataServiceProcessor.java:41）位于org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic （AbstractInOutSyncMessageReceiver.java:42）在org.apache.axis2.receivers.AbstractMessageReceiver.receive（AbstractMessageReceiver.java:110）在org.apache.axis2.engine.AxisEngine.receive（AxisEngine.java:180）在org.apache。机构中的axis2.transport.http.util.RESTUtil.invokeAxisEngine（RESTUtil.java:144）。org.apache.axis2.transport.http.AxisServlet $ RestRequestProcessor.processURLRequest（AxisServlet.java:843）处的apache.axis2.transport.http.util.RESTUtil.processURLRequest（RESTUtil.java:139）在org.wso2.carbon处。 org.wso2.carbon.core.transports.CarbonServlet.doGet（CarbonServlet.java:152）处的core.transports.CarbonServlet.handleRestRequest（CarbonServlet.java:303）在javax.servlet.http.HttpServlet.service（HttpServlet.java： 624），位于org.eclipse.equinox.http.servlet.internal.ServletRegistration.service（ServletRegistration.java:61），位于org.eclipse.equinox.http，位于javax.servlet.http.HttpServlet.service（HttpServlet.java:731） org.eclipse.equinox.http.servlet.internal.ProxyServlet.service（ProxyServlet.java:68）上的.servlet.internal.ProxyServlet.processAlias（ProxyServlet.java:128）在javax.servlet.http.HttpServlet上。org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service（DelegationServlet.java:68）处的服务（HttpServlet.java:731）org.apache.catalina.core.ApplicationFilterChain.internalDoFilter（ApplicationFilterChain.java:303）在org.apache.tomcat.websocket.server.WsFilter.doFilter（WsFilter.java:52）在org.apache.catalina.core.ApplicationFilterChain.doFilter（ApplicationFilterChain.java:208）在org.apache.catalina.core.ApplicationFilterChain org.apache.catalina.core.ApplicationFilterChain.doFilter（ApplicationFilterChain.java:208）的org.owasp.csrfguard.CsrfGuardFilter.doFilter（CsrfGuardFilter.java:72）的.internalDoFilter（ApplicationFilterChain.java:241）位于org.apache.catalina.core的catalina.core.ApplicationFilterChain.internalDoFilter（ApplicationFilterChain.java:241）。org.apache.catalina.core.ApplicationFilterChain.internalDoFilter（ApplicationFilterChain.java：org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter（CharacterSetFilter.java:61）的ApplicationFilterChain.doFilter（ApplicationFilterChain.java:208）： 241）在org.apache.catalina.doFilter（ApplicationFilterChain.java:208）在org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter（HttpHeaderSecurityFilter.java:120）在org.apache.catalina.core.ApplicationFilterChain org.org.apache.catalina.core的.internalDoFilter（ApplicationFilterChain.java:241）org.org的org.apache.catalina.core.StandardWrapperValve.invoke（StandardWrapperValve.java:218）的ApplicationFilterChain.doFilter（ApplicationFilterChain.java:208）。 apache.catalina.core.StandardContextValve.invoke（StandardContextValve。java：122）位于org.apache.catalina.authenticator.AuthenticatorBase.invoke（AuthenticatorBase.java:505）位于org.apache.catalina.core.StandardHostValve.invoke（StandardHostValve.java:169）位于org.apache.catalina.valves org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation（CompositeValve.java:99）上的.ErrorReportValve.invoke（ErrorReportValve.java:103），org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve $ 1。在org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves（TomcatValveContainer.java :)在org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke（TenantLazyLoaderValve.java:57）处调用（CarbonTomcatValve.java:47） 47）位于org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke（CompositeValve.java:62）位于org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve。在org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke（CarbonContextCreatorValve.invoke（CarbonContextCreatorValve.java:57）上在org.apache.catalina.valves.AccessLogValve.invoke（AccessLogValve.java:956）处调用（CarbonStuckThreadDetectionValve.java:159）在org.apache.catalina.connector.CoyoteAdapter.service（CoyoteAdapter.java:442）的org.apache.catalina.core.StandardEngineValve.invoke（StandardEngineValve.java:116）在org.apache.coyote.http11.AbstractHttp11Processor.process （AbstractHttp11Processor.java:1082）在org.apache.coyote.AbstractProtocol $ AbstractConnectionHandler.process（AbstractProtocol.java:623）在org.apache.tomcat.util.net.NioEndpoint $ SocketProcessor.doRun（NioEndpoint.java:1756）在org.apache.tomcat.util.net.NioEndpoint $ SocketProcessor.run（NioEndpoint.java:1715），位于java.util.concurrent.ThreadPoolExecutor。org.apache.tomcat.util.threads.TaskThread $ WrappingRunnable.run（Task.java:61）上的java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:617）上的runWorker（ThreadPoolExecutor.java:1142）在java.lang.Thread.run（Thread.java:745）

端点http：// localhost：9766 / services / TEST / test？testId = 1正常运行，但是当与WSO2ESB在迭代介体中一起使用时，它将无法正常运行。为什么？