[Dev] Fwd: LDAP socket closed error.
Hi Team, I have created cluster, IS as key manager (5.3.0) and API manager as Pub/Store/TM (2.1.0) by referring [1] document. Step 4 I have pointed out LDAP server port number into the APi Mananger as mentioned or document. I was able to up IS server without no issues. but When I up API manager bellow error message pop up *LDAPConnectionContext Error obtaining connection for the second timelocalhost:9443; socket closed* *Caused by: java.lang.reflect.InvocationTargetException* Please help to resolve this issue.. [1] - https://docs.wso2.com/display/AM210/Configuring+ WSO2+Identity+Server+as+a+Key+Manager#ConfiguringWSO2IdentityServera saKeyManager-Step5-ConfiguretheAPIManager Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Usage of "sticky cookie JSESSIONID" parameter.
Hi Team, I would like to know what is the usage of below parameter, in the NGINX configuring file which located on [1] document. sticky cookie JSESSIONID; I got following error message when restarts my NGINX service, but when I removed above parameter no issue came. -- Unit nginx.service has begun starting up. Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: [emerg] unknown directive "sticky" in /etc/nginx/conf.d/am.https.conf:2 Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: configuration file /etc/nginx/nginx.conf test failed Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: nginx.service: Control process exited, code=exited status=1 Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: Failed to start A high performance web server and a reverse proxy server. [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+the+Gateway#ClusteringtheGateway-Configuringtheloadbalancer Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: LDAP socket closed error.
Hi Godwin, I was able to figure out, why that error happened. It was happening because bellow parameter was not configured properly. ldap://localhost:10389 Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Thu, Nov 9, 2017 at 11:21 AM, Godwin Shrimal wrote: > Hi Senuwan, > > Can you attach the user-mgt.xml and wso2carbon.log in APIM node? > > > Thanks > Godwin > > On Thu, Nov 9, 2017 at 10:44 AM, Senuwan Withana wrote: > >> Hi Team, >> >> I have created cluster, IS as key manager (5.3.0) and API manager as >> Pub/Store/TM (2.1.0) by referring [1] document. Step 4 I have pointed out >> LDAP server port number into the APi Mananger as mentioned or document. I >> was able to up IS server without no issues. but When I up API manager >> >> bellow error message pop up >> >> *LDAPConnectionContext Error obtaining connection for the second >> timelocalhost:9443; socket closed* >> >> *Caused by: java.lang.reflect.InvocationTargetException* >> >> >> >> Please help to resolve this issue.. >> >> >> >> [1] - https://docs.wso2.com/display/AM210/Configuring+WSO2+Ident >> ity+Server+as+a+Key+Manager#ConfiguringWSO2IdentityServerasa >> KeyManager-Step5-ConfiguretheAPIManager >> >> >> Regards, >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Godwin Amila Shrimal* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94772264165* > linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/ > <https://www.linkedin.com/in/godwin-amila-2ba26844/>* > twitter: https://twitter.com/godwinamila > <http://wso2.com/signature> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Usage of "sticky cookie JSESSIONID" parameter.
Hi Team, I have added the documentation jira to update documentation. [1] - https://support.wso2.com/jira/browse/WSODOCINTERNAL-892 *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Thu, Nov 9, 2017 at 4:38 PM, Senuwan Withana wrote: > Hi Abimaran, > > No, I have not installed it. I just follow the documentation steps. > > *Senuwan Withana* > Software Engineer - Support Team | WSO2 > > Email : senu...@wso2.com > Mobile: 94773212853 > Web: http://www.wso2.com > > > > On Thu, Nov 9, 2017 at 4:34 PM, Abimaran Kugathasan > wrote: > >> Hi Senuwan, >> >> Have you installed sticky module on your Nginx? >> >> [1]: https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng/overview >> >> On Thu, Nov 9, 2017 at 2:29 PM, Senuwan Withana wrote: >> >>> Hi Team, >>> >>> I would like to know what is the usage of below parameter, in the NGINX >>> configuring file which located on [1] document. >>> >>> >>> sticky cookie JSESSIONID; >>> >>> >>> I got following error message when restarts my NGINX service, but when I >>> removed above parameter no issue came. >>> >>> >>> -- Unit nginx.service has begun starting up. >>> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: [emerg] unknown >>> directive "sticky" in /etc/nginx/conf.d/am.https.conf:2 >>> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: configuration file >>> /etc/nginx/nginx.conf test failed >>> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: nginx.service: Control >>> process exited, code=exited status=1 >>> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: Failed to start A high >>> performance web server and a reverse proxy server. >>> >>> >>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+the+ >>> Gateway#ClusteringtheGateway-Configuringtheloadbalancer >>> >>> Regards, >>> >>> *Senuwan Withana* >>> Software Engineer - Support Team | WSO2 >>> >>> Email : senu...@wso2.com >>> Mobile: 94773212853 >>> Web: http://www.wso2.com >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks >> Abimaran Kugathasan >> Senior Software Engineer - API Technologies >> >> Email : abima...@wso2.com >> Mobile : +94 773922820 <+94%2077%20392%202820> >> >> <http://stackoverflow.com/users/515034> >> <http://lk.linkedin.com/in/abimaran> >> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >> <https://twitter.com/abimaran> >> >> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB ]Error : AxisEngine InvalidSecurity popup.
Hi Team, When i tried to access secured back-end using the soap ui I got following error message on ESB management console. I would like to know, why is this error popups, [2017-11-09 16:04:58,032] ERROR - AxisEngine InvalidSecurity org.apache.axis2.AxisFault: InvalidSecurity at org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(PostDispatchVerificationHandler.java:164) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) [2017-11-09 16:04:58,037] ERROR - ClientWorker Fault processing response message through Axis2 org.apache.axis2.AxisFault: InvalidSecurity at org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(PostDispatchVerificationHandler.java:164) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: Accessing secured back-end using the WSO2 ESB API.
Hi Team, Today I have tested how to access secured back-end using the API which created from the WSO2 ESB. Basically, I have followed the steps,[1] document. I want to know how do I configure password using the Dev Studio. As per my research I found below [2] document related to creating password call back class. Is there any way to configure password without writing the callback class? [1] - https://docs.wso2.com/display/ESB500/Applying+ Security+to+a+Proxy+Service [2] - http://pathberiya.blogspot.com/2010/02/how-to-create- password-callback-class.html Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Usage of "sticky cookie JSESSIONID" parameter.
Hi Abimaran, No, I have not installed it. I just follow the documentation steps. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Thu, Nov 9, 2017 at 4:34 PM, Abimaran Kugathasan wrote: > Hi Senuwan, > > Have you installed sticky module on your Nginx? > > [1]: https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng/overview > > On Thu, Nov 9, 2017 at 2:29 PM, Senuwan Withana wrote: > >> Hi Team, >> >> I would like to know what is the usage of below parameter, in the NGINX >> configuring file which located on [1] document. >> >> >> sticky cookie JSESSIONID; >> >> >> I got following error message when restarts my NGINX service, but when I >> removed above parameter no issue came. >> >> >> -- Unit nginx.service has begun starting up. >> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: [emerg] unknown >> directive "sticky" in /etc/nginx/conf.d/am.https.conf:2 >> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: configuration file >> /etc/nginx/nginx.conf test failed >> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: nginx.service: Control >> process exited, code=exited status=1 >> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: Failed to start A high >> performance web server and a reverse proxy server. >> >> >> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+the+ >> Gateway#ClusteringtheGateway-Configuringtheloadbalancer >> >> Regards, >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanks > Abimaran Kugathasan > Senior Software Engineer - API Technologies > > Email : abima...@wso2.com > Mobile : +94 773922820 <+94%2077%20392%202820> > > <http://stackoverflow.com/users/515034> > <http://lk.linkedin.com/in/abimaran> > <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> > <https://twitter.com/abimaran> > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Usage of "sticky cookie JSESSIONID" parameter.
Hi Pubudu, Thanks for information, I will try out ip_hash; *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Fri, Nov 10, 2017 at 9:52 AM, Pubudu Gunatilaka wrote: > Hi Senuwan, > > For session persistence, you can use ip_hash instead of sticky sessions > [1]. Nginx community version does not support sticky sessions. > > [1] - https://docs.wso2.com/display/CLUSTER44x/Configuring+NGINX > > Thank you! > > On Thu, Nov 9, 2017 at 4:38 PM, Senuwan Withana wrote: > >> Hi Abimaran, >> >> No, I have not installed it. I just follow the documentation steps. >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> On Thu, Nov 9, 2017 at 4:34 PM, Abimaran Kugathasan >> wrote: >> >>> Hi Senuwan, >>> >>> Have you installed sticky module on your Nginx? >>> >>> [1]: https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng/overview >>> >>> On Thu, Nov 9, 2017 at 2:29 PM, Senuwan Withana >>> wrote: >>> >>>> Hi Team, >>>> >>>> I would like to know what is the usage of below parameter, in the NGINX >>>> configuring file which located on [1] document. >>>> >>>> >>>> sticky cookie JSESSIONID; >>>> >>>> >>>> I got following error message when restarts my NGINX service, but when >>>> I removed above parameter no issue came. >>>> >>>> >>>> -- Unit nginx.service has begun starting up. >>>> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: [emerg] unknown >>>> directive "sticky" in /etc/nginx/conf.d/am.https.conf:2 >>>> Nov 09 14:15:11 senuwan-ThinkPad nginx[3869]: nginx: configuration file >>>> /etc/nginx/nginx.conf test failed >>>> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: nginx.service: Control >>>> process exited, code=exited status=1 >>>> Nov 09 14:15:11 senuwan-ThinkPad systemd[1]: Failed to start A high >>>> performance web server and a reverse proxy server. >>>> >>>> >>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+the+ >>>> Gateway#ClusteringtheGateway-Configuringtheloadbalancer >>>> >>>> Regards, >>>> >>>> *Senuwan Withana* >>>> Software Engineer - Support Team | WSO2 >>>> >>>> Email : senu...@wso2.com >>>> Mobile: 94773212853 >>>> Web: http://www.wso2.com >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Thanks >>> Abimaran Kugathasan >>> Senior Software Engineer - API Technologies >>> >>> Email : abima...@wso2.com >>> Mobile : +94 773922820 <+94%2077%20392%202820> >>> >>> <http://stackoverflow.com/users/515034> >>> <http://lk.linkedin.com/in/abimaran> >>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>> <https://twitter.com/abimaran> >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Senior Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy
(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:120)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.synapse.SynapseException: Unknown mediator referenced
by configuration element : {http://ws.apache.org/ns/synapse}ldap
at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:219)
at
org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:46)
at
org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:70)
at
org.apache.synapse.config.xml.ProxyServiceFactory.createProxy(ProxyServiceFactory.java:165)
at
org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.addProxyService(ProxyServiceAdmin.java:257)
at
org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.addProxy(ProxyServiceAdmin.java:706)
... 139 more
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy
Hi Waruna, and Vijtha,
Thanks for help. After adding the LDAP Zip file, I could able to deploy the
proxy without any issue. Shall we update the documentation and ask to link
[1] page, as well.
[1] - https://docs.wso2.com/display/ESBCONNECTORS/LDAP+Connector
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Fri, Nov 10, 2017 at 10:32 PM, Vijitha Ekanayake
wrote:
> Hi Senuwan,
>
> As per the error, synapse doesn't recognize LDAP as synapse library. Have
> you installed the Idap connector properly, if so please check whether the
> connector is enabled?
>
> Thanks.
>
> On Fri, Nov 10, 2017 at 10:14 PM, Senuwan Withana
> wrote:
>
>> Hi Team,
>>
>> I have tried out CRUD Operations sample proxy give in [1] documentation
>> Once I tried to save it I got below exceptions into the management console,
>> I would like to know the reason of that error.
>>
>> [1] - https://docs.wso2.com/display/ESBCONNECTORS/Working+with+
>> CRUD+operations+in+LDAP
>>
>> *Error Message:-*
>>
>> [2017-11-10 22:05:10,728] ERROR - MediatorFactoryFinder Unknown mediator
>> referenced by configuration element : {http://ws.apache.org/ns/synap
>> se}ldap
>> [2017-11-10 22:05:10,730] ERROR - RPCMessageReceiver Unknown mediator
>> referenced by configuration element : {http://ws.apache.org/ns/synap
>> se}ldap
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
>> RPCUtil.java:212)
>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>> nessLogic(RPCMessageReceiver.java:117)
>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>> bstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:169)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:82)
>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>> (LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:430)
>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:225)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.addPro
>> xy(ProxyServiceAdminStub.java:1272)
>> at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient
>> .addProxy(ProxyServiceAdminClient.java:102)
>> at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_j
>> sp.java:147)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>> rvice(ContextPathServletAdaptor.java:37)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at o
[Dev] How to retrieve data from payload factory.
Hi Team, I have created the ESB API with some payload(s). Basically the api has [ Post, Put, Delete, Get] resources. I would like to know how to retrieve the data from the payload? Do i need to create a JSON file separately, in-order to get data? Waiting for a favorable reply Thanks *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to retrieve data from payload factory.
Hi Pubudu, I will try out your suggestion as well. Thanks for support. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Mon, Nov 13, 2017 at 4:44 PM, Pubudu Gunatilaka wrote: > Hi Senuwan, > > Please refer [1]. > > [1] - https://susankhanirmala.wordpress.com/2016/04/19/ > accessing-content-from-json-payloads-using-wso2-esb/ > > Thank you! > > On Mon, Nov 13, 2017 at 5:51 PM, Senuwan Withana wrote: > >> Hi Team, >> >> I have created the ESB API with some payload(s). Basically the api has >> [ Post, Put, Delete, Get] resources. I would like to know how to retrieve >> the data from the payload? >> >> Do i need to create a JSON file separately, in-order to get data? >> >> >> Waiting for a favorable reply >> >> Thanks >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Senior Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] REST Method based routing within a proxy
Hi Team, What is the best approach to mediate the logic based on the REST CRUD operations request within the ESB proxy ? Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] REST Method based routing within a proxy
Hi Dushantha, Thanks for the update. Is there any other mediators can we use instead of switch, Regards *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Nov 14, 2017 at 12:26 PM, Dushantha Batuwita wrote: > Hi Senuwan > > According to my understanding, we can use the switch mediator if you have > to route against many options oppose to filter mediator which lets you > choose one of the two paths. > Within the inSequence of the proxy, we can perform a method based routing > with a switch mediator as demonstrated. > There we check the HTTP method at the source attribute of the Switch > mediator and match against the regular expression to trap whatever the HTTP > method that we are interested in and proceed with the logic that you need > to perform. > > > > http://ws.apache.org/ns/synapse";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > regards > > > On Tue, Nov 14, 2017 at 12:10 PM, Senuwan Withana > wrote: > >> Hi Team, >> >> What is the best approach to mediate the logic based on the REST CRUD >> operations request within the ESB proxy ? >> >> Regards, >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Dushantha Nayanajith Chandima Batuwita* > Software Engineer Support | WSO2 > dushan...@wso2.com > mobile : 0094777453010 > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Passing payloads from API to ESB
Thank you Dushantha, It also works for me.
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Thu, Nov 16, 2017 at 11:21 AM, Dushantha Batuwita
wrote:
> Hi Buddhimala:
>
> my pleasure
>
> regards
>
> On Thu, Nov 16, 2017 at 10:40 AM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi Dushantha,
>>
>> Thank you for the explanation and the solution. It is working for me now.
>>
>> Regards,
>> Buddhimala
>>
>> On Wed, Nov 15, 2017 at 5:32 PM, Dushantha Batuwita
>> wrote:
>>
>>> Hi Priya
>>>
>>> please find the attached image which I was referring in the above answer.
>>> sorry for the mixup
>>> Regards
>>>
>>> On Wed, Nov 15, 2017 at 5:30 PM, Dushantha Batuwita
>>> wrote:
>>>
>>>> Hi Piriya
>>>>
>>>> Above approach, you can implement in the POST and PUT.
>>>> The resource type GET produces a request that does not have a body
>>>> (payload),
>>>> hence we set the required parameter as a query parameter when you set
>>>> the resource GET while creating the API in publisher. (please refer to the
>>>> attached image )
>>>> Then the request parameter is accessed within the payload mediator of
>>>> the proxy service ( within the element) in ESB as the following
>>>> example.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> http://service.samp
>>>> le.oasis.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>>>> xmlns:xsd="http://dto.service.sample.oasis.com/xsd";>
>>>> 1
>>>>
>>>>
>>>>
>>>> $1
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> http://org.apache.synapse/xsd"/>
>>>>
>>>>
>>>>
>>>>
>>>> please refer to the following link for better understanding of the REST
>>>> Parameters
>>>> https://www.soapui.org/rest-testing/understanding-rest-parameters.html
>>>>
>>>> many thanks
>>>>
>>>>
>>>> On Wed, Nov 15, 2017 at 5:19 PM, Piriya Sivalingam
>>>> wrote:
>>>>
>>>>> Hi Dushantha,
>>>>>
>>>>> Since I have GET, POST,PUT, DELETE methods in my proxy, do you say the
>>>>> above-suggested method will work for GET. I have tried it but could not
>>>>> achieve it.
>>>>> And if I am correct, your example is about POST or PUT method.
>>>>> Could you please let me know whether I can use the same way for all
>>>>> four methods or only specific to POST method.
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>> On Wed, Nov 15, 2017 at 3:10 PM, Dushantha Batuwita <
>>>>> dushan...@wso2.com> wrote:
>>>>>
>>>>>> please refer to the above answers
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> On Wed, Nov 15, 2017 at 2:35 PM, Dushantha Batuwita <
>>>>>> dushan...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Buddhimala
>>>>>>> Accessing the JSON payload parameters and retrieving those within
>>>>>>> the proxy service can be achieved with the element of the Payload
>>>>>>> factory mediator according to your scenario.
>>>>>>> Setting already retrieved parameters to the predefined soap
>>>>>>> structure is accomplished within the element.
>>>>>>>
>>>>>>> suppose that we need to access the following JSON structure
>>>>>>>
>>>>>>> {
>>>>>>> "orderLine": {
>>>>>>>
>>>>>>> "ordername": "Cooking Item",
>>>>>>> "orderid": "123456",
>>>>>>> "product": {
>>>>>>>
>>>>>>> "productname": "coconutoil",
>>>>>>>
[Dev] Pass user details into the out sequence.
Hi Team, I have created the below class mediator to call my JWTRoleReder, inSequence . However I could not able to pass above details into the outSequence . Kindly suggest solutions? Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pass user details into the out sequence.
Hi Guys, Thanks for the replies . I was able to take the user role from class mediator in the in sequence But I could not able to pass that value into the out sequence. Thanks, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Wed, Nov 22, 2017 at 10:51 AM, Himasha Guruge wrote: > Hi Senuwan, > > What is your requirement here? Could you post your complete synapse > configuration? > > Thanks, > Himasha > > On Wed, Nov 22, 2017 at 10:09 AM, Senuwan Withana > wrote: > >> Hi Team, >> >> >> I have created the below class mediator to call my JWTRoleReder, in >> Sequence . >> >> >> >> >> >> >> However I could not able to pass above details into the outSequence . >> Kindly suggest solutions? >> >> Thanks. >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Himasha Guruge > Senior Software Engineer > WS*O2* *Inc.* > Mobile: +94 777459299 <+94%2077%20745%209299> > himas...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pass user details into the out sequence.
Thank you Saneth, Regards. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Wed, Nov 22, 2017 at 2:28 PM, Saneth Dharmakeerthi wrote: > Hi Senuwan, > > If you set a value to a property in default context (Synapse), It > should be accessible throughout in and out sequence[1][2][3]. The behavior > might different if you set this value inside a Clone or Iterator? > > > > [1]https://docs.wso2.com/display/EI610/Property+Mediator > [2]http://soatutorials.blogspot.com/2014/03/wso2-esb-propert > ies-tutorial.html > [3] http://blog.facilelogin.com/2011/02/wso2-esb-property-me > diator-different.html > > Thanks and Best Regards, > > Saneth Dharmakeerthi > *Associate Technical Lead* > WSO2, Inc. > Mobile: +94772325511 <+94%2077%20232%205511> > > <http://wso2.com/signature> > > On Wed, Nov 22, 2017 at 11:13 AM, Senuwan Withana > wrote: > >> Hi Guys, >> >> Thanks for the replies . >> >> I was able to take the user role from class mediator in the in sequence >> But I could not able to pass that value into the out sequence. >> >> Thanks, >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> On Wed, Nov 22, 2017 at 10:51 AM, Himasha Guruge >> wrote: >> >>> Hi Senuwan, >>> >>> What is your requirement here? Could you post your complete synapse >>> configuration? >>> >>> Thanks, >>> Himasha >>> >>> On Wed, Nov 22, 2017 at 10:09 AM, Senuwan Withana >>> wrote: >>> >>>> Hi Team, >>>> >>>> >>>> I have created the below class mediator to call my JWTRoleReder, in >>>> Sequence . >>>> >>>> >>>> >>>> >>>> >>>> >>>> However I could not able to pass above details into the outSequence . >>>> Kindly suggest solutions? >>>> >>>> Thanks. >>>> *Senuwan Withana* >>>> Software Engineer - Support Team | WSO2 >>>> >>>> Email : senu...@wso2.com >>>> Mobile: 94773212853 >>>> Web: http://www.wso2.com >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Himasha Guruge >>> Senior Software Engineer >>> WS*O2* *Inc.* >>> Mobile: +94 777459299 <+94%2077%20745%209299> >>> himas...@wso2.com >>> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pass user details into the out sequence.
Thanks guys,
I was able to send user details into the out sequence successfully.
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Wed, Nov 22, 2017 at 11:21 AM, Buddhimala Ranasinghe wrote:
> Hi Senuwan,
>
> In order to pass the value of a property from insequence to outsequence,
> you can try with the property scope as "default/synapse".
>
> So that you can modify your insequence and outsequence as follows.
>
>
>
>
>
> name="Role"
> scope="transport"/>
> name="myPropertyInDefault"
> scope="default"/>
>
>
> name="myPropertyInTransport"
> scope="transport"/>
>
>
> So that you can use "get-property('transport','myPropertyInTransport')"
> to retrieve the value in outsequence.
>
> Please refer https://stackoverflow.com/a/13378163 for further convenience.
>
> Regards,
> Buddhimala
>
>
> On Wed, Nov 22, 2017 at 10:42 AM, Rukshan Premathunga
> wrote:
>
>> Hi Senuwan,
>>
>> You can add required property to message context inside the class
>> mediator. So that you can read them back in out-sequence.
>>
>> Thanks and Regards
>>
>> On Wed, Nov 22, 2017 at 10:09 AM, Senuwan Withana
>> wrote:
>>
>>> Hi Team,
>>>
>>>
>>> I have created the below class mediator to call my JWTRoleReder, in
>>> Sequence .
>>>
>>>
>>>
>>>
>>>
>>>
>>> However I could not able to pass above details into the outSequence .
>>> Kindly suggest solutions?
>>>
>>> Thanks.
>>> *Senuwan Withana*
>>> Software Engineer - Support Team | WSO2
>>>
>>> Email : senu...@wso2.com
>>> Mobile: 94773212853
>>> Web: http://www.wso2.com
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>> +94711822074 <+94%2071%20182%202074>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <+94%2077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] <https://wso2.com/signature>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] An error message(s) popup when testing on throttling.
FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-11-23 12:50:30,794] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"HTTP/1.1 200 OK[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Content-Type: application/json; charset=UTF-8[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Date: Thu, 23 Nov 2017 07:20:30 GMT[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Transfer-Encoding: chunked[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Connection: Keep-Alive[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"124[\r][\n]"
[2017-11-23 12:50:30,795] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"{"patient":{"patientFullName":"sfsdsdsfdsfds","patientId":"nuasda123","Medical":{"medical":{"@type":"ax225:Medical","condition":"better","treatment":"ECG"}},"patientContact":{"patientContact":{"@type":"ax225:PatientContact","address":"colombo
03","email":"d...@gmail.com","phone":12321321[\r][\n]"
[2017-11-23 12:50:30,796] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"0[\r][\n]"
[2017-11-23 12:50:30,796] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"[\r][\n]"
[2017-11-23 12:50:30,801] DEBUG - wire HTTPS-Listener I/O dispatcher-3 <<
"HTTP/1.1 200 OK[\r][\n]"
[2017-11-23 12:50:30,801] DEBUG - wire HTTPS-Listener I/O dispatcher-3 <<
"Access-Control-Allow-Origin: *[\r][\n]"
*Please suggest any suggestions or solutions to over come above mentioned
issue.*
Thanks,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] An error message(s) popup when testing on throttling.
Thanks Guys, I was able to fix above mentioned error. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Thu, Nov 23, 2017 at 4:23 PM, Saneth Dharmakeerthi wrote: > Hi Senuwan. > > Please check your configuration where the connections to TM node is > correct[1]. The same issue in [2] > > [1] https://docs.wso2.com/display/AM210/Distributed+Deployme > nt+of+API+Manager > [2]. [Dev] API with Ip based throttling gives an error > > Thanks and Best Regards, > > Saneth Dharmakeerthi > *Associate Technical Lead* > WSO2, Inc. > Mobile: +94772325511 <+94%2077%20232%205511> > > <http://wso2.com/signature> > > On Thu, Nov 23, 2017 at 12:56 PM, Senuwan Withana > wrote: > >> Hi Team, >> >> *I have added IP base throttling to my API Manager pack. * >> >> >> >> >> >> *When I tried throttling scenario Following error messages popup* >> >> [2017-11-23 12:50:30,421] INFO - DependencyTracker Local entry : >> gov:/apimgt/statistics/ga-config.xml was added to the Synapse >> configuration successfully >> [2017-11-23 12:50:30,484] INFO - JMSConnectionFactory JMS >> ConnectionFactory : jmsEventPublisher initialized >> [2017-11-23 12:50:30,514] INFO - AMQConnection Unable to connect to >> broker at tcp://localhost:5672 >> org.wso2.andes.transport.TransportException: Could not open connection >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I >> oConnectorCreator.connect(MinaNetworkTransport.java:216) >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.c >> onnect(MinaNetworkTransport.java:74) >> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo >> nnection(AMQConnectionDelegate_8_0.java:130) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) >> at java.security.AccessController.doPrivileged(Native Method) >> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ >> Connection.java:628) >> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:351) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:40) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSUt >> ils.createConnection(JMSUtils.java:387) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory.createConnection(JMSConnectionFactory.java:268) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory$PoolableJMSConnectionFactory.makeObject(JMSC >> onnectionFactory.java:356) >> at org.apache.commons.pool.impl.GenericObjectPool.borrowObject( >> GenericObjectPool.java:1181) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory.getConnectionFromPool(JMSConnectionFactory.java:286) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSMe >> ssageSender.send(JMSMessageSender.java:86) >> at org.wso2.carbon.event.output.adapter.jms.JMSEventAdapter$JMS >> Sender.run(JMSEventAdapter.java:284) >> at java.util.concurrent.Executors$RunnableAdapter.call(Executor >> s.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >> Executor.java:1142) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >> lExecutor.java:617) >> at java.lang.Thread.run(Thread.java:748) >> [2017-11-23 12:50:30,518] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "GET /services/AsiriPatientService/patient HTTP/1.1[\r][\n]" >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "Authorization: Basic YWRtaW46YWRtaW4=[\r][\n]" >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "Origin: https://10.100.7.13:9444[\r][\n]"; >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "X-JWT-Assertion: eyJ0eXAiOiJKV1QiLCJhbGciOiJub2 >> 5lIn0=.eyJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1zXC91c2VyaWQiOiIwM >> zY0MDVkMC03MDM4LTQxNmUtYTVmYy05M2QzZTc4OWEzZWQiLCJodHRwOlwvX >> C93c28yLm9yZ1wvY2xhaW1zXC91c2VybmFtZSI6InBhdGllbnQiLCJodHRwO >> lwvXC93c28yLm9yZ1wvY2xhaW1zXC9yb2xlIjpbIkFwcGxpY2F0aW9uXC9wY >> XRpZW50X3Nzc3NfUFJPRFVDVElPTiIsIkludGVybmFsXC9zdWJzY3JpYmVyI >> iwiSW50ZXJuY
Re: [Dev] An error message(s) popup when testing on throttling.
Thanks, Sam. I will check on it. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Thu, Nov 23, 2017 at 3:53 PM, Sam Sivayogam wrote: > Check /repository/conf/jndi.properties file located in your > admin portal, whether you have pointed it correctly to the TM Node. > > Thanks, > Sam > > On Thu, Nov 23, 2017 at 12:56 PM, Senuwan Withana > wrote: > >> Hi Team, >> >> *I have added IP base throttling to my API Manager pack. * >> >> >> >> >> >> *When I tried throttling scenario Following error messages popup* >> >> [2017-11-23 12:50:30,421] INFO - DependencyTracker Local entry : >> gov:/apimgt/statistics/ga-config.xml was added to the Synapse >> configuration successfully >> [2017-11-23 12:50:30,484] INFO - JMSConnectionFactory JMS >> ConnectionFactory : jmsEventPublisher initialized >> [2017-11-23 12:50:30,514] INFO - AMQConnection Unable to connect to >> broker at tcp://localhost:5672 >> org.wso2.andes.transport.TransportException: Could not open connection >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I >> oConnectorCreator.connect(MinaNetworkTransport.java:216) >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport. >> connect(MinaNetworkTransport.java:74) >> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo >> nnection(AMQConnectionDelegate_8_0.java:130) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) >> at java.security.AccessController.doPrivileged(Native Method) >> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ >> Connection.java:628) >> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:351) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:40) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSUt >> ils.createConnection(JMSUtils.java:387) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory.createConnection(JMSConnectionFactory.java:268) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory$PoolableJMSConnectionFactory.makeObject(JMSC >> onnectionFactory.java:356) >> at org.apache.commons.pool.impl.GenericObjectPool.borrowObject( >> GenericObjectPool.java:1181) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSCo >> nnectionFactory.getConnectionFromPool(JMSConnectionFactory.java:286) >> at org.wso2.carbon.event.output.adapter.jms.internal.util.JMSMe >> ssageSender.send(JMSMessageSender.java:86) >> at org.wso2.carbon.event.output.adapter.jms.JMSEventAdapter$JMS >> Sender.run(JMSEventAdapter.java:284) >> at java.util.concurrent.Executors$RunnableAdapter.call( >> Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >> Executor.java:1142) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >> lExecutor.java:617) >> at java.lang.Thread.run(Thread.java:748) >> [2017-11-23 12:50:30,518] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "GET /services/AsiriPatientService/patient HTTP/1.1[\r][\n]" >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "Authorization: Basic YWRtaW46YWRtaW4=[\r][\n]" >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "Origin: https://10.100.7.13:9444[\r][\n]"; >> [2017-11-23 12:50:30,519] DEBUG - wire HTTPS-Sender I/O dispatcher-2 << >> "X-JWT-Assertion: eyJ0eXAiOiJKV1QiLCJhbGciOiJub2 >> 5lIn0=.eyJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1zXC91c2VyaWQiOiIwM >> zY0MDVkMC03MDM4LTQxNmUtYTVmYy05M2QzZTc4OWEzZWQiLCJodHRwOlwvX >> C93c28yLm9yZ1wvY2xhaW1zXC91c2VybmFtZSI6InBhdGllbnQiLCJodHRwO >> lwvXC93c28yLm9yZ1wvY2xhaW1zXC9yb2xlIjpbIkFwcGxpY2F0aW9uXC9wY >> XRpZW50X3Nzc3NfUFJPRFVDVElPTiIsIkludGVybmFsXC9zdWJzY3JpYmVyI >> iwiSW50ZXJuYWxcL2NyZWF0b3IiLCJJbnRlcm5hbFwvcHVibGlzaGVyIiwiS >> W50ZXJuYWxcL2V2ZXJ5b25lIiwicGF0aWVudFJvbGUiXSwiaHR0cDpcL1wvd >> 3NvMi5vcmdcL2NsYWltc1wvYXBwbGljYXRpb250aWVyIjoiVW5saW1pdGVkI >> iwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wva2V5dHlwZSI6IlBST0RVQ >> 1RJT04iLCJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1zXC92ZXJzaW9uIjoid >> jEiLCJpc3MiOiJ3c28yLm9yZ1wvcHJ
Re: [Dev] nginx master_process on; (code=exited, status=1/FAILURE)
Hi Dushantha, Its seems your port is already used. Please check on it again Thanks, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Nov 28, 2017 at 5:09 PM, Dushantha Batuwita wrote: > Hi Dev > > I have installed the nginx and when I try starting the nginx, I > receive following error. > > sudo service nginx start > > Job for nginx.service failed because the control process exited with error > code. > See "systemctl status nginx.service" and "journalctl -xe" for details. > > > when I check the status it gives me. > > ● nginx.service - A high performance web server and a reverse proxy server >Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor > preset: enabled) >Active: failed (Result: exit-code) since Tue 2017-11-28 16:33:48 +0530; > 50s ago > Docs: man:nginx(8) > Process: 953 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; > master_process on; (code=exited, status=1/FAILURE) > > නෙවැ 28 16:44:57 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] bind() to [::]:80 failed (98: Address already in use) > නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] bind() to [::]:80 failed (98: Address already in use) > නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] bind() to [::]:80 failed (98: Address already in use) > නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx: > [emerg] still could not bind() > නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: > nginx.service: Control process exited, code=exited status=1 > නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: Failed to > start A high performance web server and a reverse proxy server. > නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: > nginx.service: Unit entered failed state. > නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: > nginx.service: Failed with result 'exit-code'. > > > > > Is there any possible solution to get rid of the error > regards > > > > > -- > *Dushantha Nayanajith Chandima Batuwita* > Software Engineer Support | WSO2 > dushan...@wso2.com > mobile : 0094777453010 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to validate email adddress
Hi Team,
Regular expression should be like below
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Tue, Nov 28, 2017 at 2:18 PM, Dilusha Alphonso wrote:
> Hi,
>
> Thank you for the response. I changed my configuration as mentioned above
> it's working.
>
> Thanks
> Dilusha
>
>
> On Mon, Nov 27, 2017 at 3:35 PM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Also you need to use the template with + sign since its value can contain
>> @
>>
>> uri-template="/{*+*id}"
>>
>> Regards
>> Senduran
>>
>>
>>
>>
>> On Mon, Nov 27, 2017 at 3:24 PM, Abimaran Kugathasan
>> wrote:
>>
>>> Hi Dilusha,
>>>
>>> Since you have defined is as path parameter in the template, you must
>>> use 'uri.var.id' instead of 'query.param.id' in the filter mediator
>>> like below.
>>>
>>> >> regex="/^([A-Za-z0-9_\-\.])+\@([A-Za-z0-9_\-\.])+\.([A-Za-z]{2,4})$/">
>>>
>>> On Sat, Nov 25, 2017 at 11:37 AM, Dilusha Alphonso
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Requirement: I need to check a condition " Patient ID is the email
>>>> address of given patient". When I give any string to the ID, it must be an
>>>> email address. I have to validate ID whether it is in email format. For
>>>> this, I used the filter mediator in ESB, But I noticed my request didn't go
>>>> through that filter mediator.
>>>>
>>>> I attached my API configuration in ESB. Please, anyone, help me to
>>>> validate the email address with ID.
>>>>
>>>> http://ws.apache.org/ns/synapse"; name="Durdan"
>>>> context="/test">
>>>>
>>>>
>>>>
>>>> >>> regex="/^([A-Za-z0-9_\-\.])+\@([A-Za-z0-9_\-\.])+\.([A-Za-z]{2,4})$/">
>>>>
>>>>
>>>>
>>>>
>>>> http://schemas.
>>>> xmlsoap.org/soap/envelope/">
>>>>
>>>>17
>>>>
>>>>
>>>>http://service.sample.durdans.com";>
>>>> $1
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>>> scope="transport"/>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>>> value="application/soap+xml" scope="axis2" type="STRING"/>
>>>>
>>>>
>>>>
>>>> >>> value="deef"/>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks
>>>> Dilusha
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> before loop back to out sequence whether the USER_NAME and PATIENT_ID
>>>> are equal.
>>>>
>>>> --
>>>>
>>>>
>>>> *Best Regards,Dilusha Alphonso*
>>>>
>>>> *Software Engineer - Support Team*
>>>>
>>>>
>>>> *WSO2*
>>>> *Mobile : *
>>>>
>>>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>>>> <http://wso2.com/signature>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>
>>> <http://stackoverflow.com/users/515034>
>>> <http://lk.linkedin.com/in/abimaran>
>>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank>
>>> <https://twitter.com/abimaran>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.; http://wso2.com/ <http://wso2.com/>
>> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>>
>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> <http://wso2.com/signature>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter
(ServiceRegistry.java:214) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) at org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81) at org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1269) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1182) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1072) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5368) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5660) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1571) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1561) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) [2017-12-05 09:14:25,437] INFO - AMQConnection Unable to connect to broker at tcp://10.100.7.13:5674 org.wso2.andes.transport.TransportException: Could not open connection at org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216) at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74) at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) at java.security.AccessController.doPrivileged(Native Method) at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628) at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40) at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186) at java.lang.Thread.run(Thread.java:748) org.wso2.andes.AMQConnectionFailureException: Could not open connection at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40) at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186) at java.lang.Thread.run(Thread.java:748) Caused by: org.wso2.andes.transport.TransportException: Could not open connection at org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216) at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74) at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) at java.security.AccessController.doPrivileged(Native Method) at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628) at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) ... 7 more [1] - https://docs.wso2.com/display/AM210/Distributed+Deployment+of+the+Gateway#5a69bb14f904452ab5c678035c21178e Any suggestion to over come the above issue. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error popup on API Manager Worker node.
Hi Team, When I up my API Manager worker node, I got below error. Is there any way to resolve the below error. I have followed up [1] document as reference. [1] - https://docs.wso2.com/display/AM210/Distributed+ Deployment+of+the+Gateway#5a69bb14f904452ab5c678035c21178e [2017-12-05 15:46:15,469] ERROR - KeyTemplateRetriever Exception when retrieving throttling data from remote endpoint java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:522) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:401) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:178) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever.retrieveKeyTemplateData(KeyTemplateRetriever.java:83) at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111) at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Exception in thread "Timer-5" java.lang.NullPointerException at java.util.Objects.requireNonNull(Objects.java:203) at java.util.Arrays$ArrayList.(Arrays.java:3813) at java.util.Arrays.asList(Arrays.java:3800) at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111) at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) [2017-12-05 15:57:04,008] INFO - AndesRecoveryTask Running DB sync task. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter
Hi Guys, Thanks for the update. I have double checked the mentioned steps. However still I could not able to find the root cause of this error. I have followed the document mentioned steps clearly. Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga wrote: > Hi Senuwan, > > Please check whether the connection configs to TM is correct, in > api-manager.xml under under > as in [1] under the section "Step 3.5 - > Configure the Gateway". > > [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+ > of+API+Manager#DistributedDeploymentofAPIManager-Step3.5- > ConfiguretheGateway > > Regards, > Samitha > > On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena > wrote: > >> Hi senuwan, >> >> Before you start server as gateway worker you need to do setup [1]. >> please check you did it correctly. >> >> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW >> >> Thanks, >> krishan. >> >> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana wrote: >> >>> Hi Team, >>> >>> I have created a Gateway Cluster following the document [1]. When I >>> started the server using ./wso2server.sh -Dprofile=gateway-worker command I >>> got below errors. Without -Dprofile server was up correctly. >>> >>> [2017-12-05 09:14:25,262] INFO - JMSTransportHandler Starting jms topic >>> consumer thread... >>> [2017-12-05 09:14:25,284] WARN - APIManagerComponent Exception occurred >>> while creating JMS Event Adapter. Request Blocking may not work properly >>> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException: >>> Output Event Adapter not created as no adapter factory is registered with >>> type jms >>> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut >>> putEventAdapterService.create(CarbonOutputEventAdapterService.java:89) >>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con >>> figureJMSPublisher(APIManagerComponent.java:574) >>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act >>> ivate(APIManagerComponent.java:221) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>> ssorImpl.java:62) >>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>> thodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ >>> ate(ServiceComponent.java:260) >>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a >>> ctivate(ServiceComponentProp.java:146) >>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b >>> uild(ServiceComponentProp.java:345) >>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone >>> nt(InstanceProcess.java:620) >>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone >>> nts(InstanceProcess.java:197) >>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve >>> r.java:343) >>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC >>> RManager.java:222) >>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis >>> tener.serviceChanged(FilteredServiceListener.java:107) >>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d >>> ispatchEvent(BundleContextImpl.java:861) >>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve >>> nt(EventManager.java:230) >>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv >>> entSynchronous(ListenerQueue.java:148) >>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu >>> blishServiceEventPrivileged(ServiceRegistry.java:819) >>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu >>> blishServiceEvent(ServiceRegistry.java:771) >>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio >>> nImpl.register(ServiceRegistrationImpl.java:130) >>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re >>> gisterService(ServiceRegistry.java:214) >>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r >>> egisterService(BundleContextImpl.java:433) >>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r >>> egisterSe
Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter
12-05 19:38:49,331] INFO - PassThroughListeningIOReactorManager Pass-through HTTPS Listener started on 0.0.0.0:8245 [2017-12-05 19:38:49,425] INFO - NioSelectorPool Using a shared selector for servlet write/read [2017-12-05 19:38:49,467] INFO - NioSelectorPool Using a shared selector for servlet write/read [2017-12-05 19:38:49,801] INFO - TaskServiceImpl Task service starting in STANDALONE mode... [2017-12-05 19:38:49,858] INFO - RegistryEventingServiceComponent Successfully Initialized Eventing on Registry [2017-12-05 19:38:49,956] INFO - JMXServerManager JMX Service URL : service:jmx:rmi://localhost:3/jndi/rmi://localhost:10001/jmxrmi [2017-12-05 19:38:49,957] INFO - StartupFinalizerServiceComponent Server : WSO2 API Manager-2.1.0 [2017-12-05 19:38:49,957] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 42 sec [2017-12-05 19:38:50,163] INFO - CarbonUIServiceComponent Mgt Console URL : https://172.16.2.39:443/carbon/ [2017-12-05 19:38:50,163] INFO - CarbonUIServiceComponent API Publisher Default Context : https://172.16.2.39:443/publisher [2017-12-05 19:38:50,163] INFO - CarbonUIServiceComponent API Store Default Context : https://172.16.2.39:443/store [2017-12-05 19:38:50,651] INFO - AMQConnection Unable to connect to broker at tcp://172.16.2.39:5674 org.wso2.andes.transport.TransportException: Could not open connection at org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216) at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74) at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) at java.security.AccessController.doPrivileged(Native Method) at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628) at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40) at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186) at java.lang.Thread.run(Thread.java:748) org.wso2.andes.AMQConnectionFailureException: Could not open connection at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351) at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40) at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79) at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186) at java.lang.Thread.run(Thread.java:748) Caused by: org.wso2.andes.transport.TransportException: Could not open connection at org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216) at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74) at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) at java.security.AccessController.doPrivileged(Native Method) at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628) at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) ... 7 more [2017-12-05 19:38:50,655] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now. [2017-12-05 19:38:50,655] ERROR - JMSListener Connection attempt : 2 for JMS Provider failed. Next retry in 40 seconds Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 5, 2017 at 6:56 PM, Harsha Kumara wrote: > Hi Mari, > > We need to update the latest docs as well. > > [1 ]https://docs.wso2.com/display/AM210/Product+Profiles#GWW > > Thanks, > Harsha > > On Tue, Dec 5, 2017 at 6:54 PM, Harsha Kumara wrote: > >> This is a known issue when you start with the profiles. Please comment >> out the JMSEventPublisherParameters section in the api-manager.xml. It&
Re: [Dev] Error popup on API Manager Worker node.
Hi Guys,
Thanks for replying. Well I have used below configuration to GW to
communicate with the KM
https:// :9443/services/
${admin.username}
${admin.password}
...
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Tue, Dec 5, 2017 at 5:02 PM, Pubudu Gunatilaka wrote:
> Hi Senuwan,
>
> Make sure you have configured APIKeyValidator in api-manager.xml pointing
> to APIM key manager. At the server startup, gateway nodes retrieve key
> templates from the KM.
>
> Thank you!
>
> On Tue, Dec 5, 2017 at 4:34 PM, Dinusha Dissanayake
> wrote:
>
>> Hi Senuwan,
>>
>> Could you please check if there is any port conflict? Looks like
>> connection has not been established.
>>
>> Thanks,
>> DinushaD.
>>
>> On Tue, Dec 5, 2017 at 4:09 PM, Senuwan Withana wrote:
>>
>>> Hi Team,
>>>
>>> When I up my API Manager worker node, I got below error. Is there any
>>> way to resolve the below error. I have followed up [1] document as
>>> reference.
>>>
>>> [1] - https://docs.wso2.com/display/AM210/Distributed+Deployment
>>> +of+the+Gateway#5a69bb14f904452ab5c678035c21178e
>>>
>>> [2017-12-05 15:46:15,469] ERROR - KeyTemplateRetriever Exception when
>>> retrieving throttling data from remote endpoint
>>> java.net.ConnectException: Connection refused (Connection refused)
>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSock
>>> etImpl.java:350)
>>> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPl
>>> ainSocketImpl.java:206)
>>> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocket
>>> Impl.java:188)
>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>> at java.net.Socket.connect(Socket.java:589)
>>> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>> ocketFactory.java:522)
>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>> ocketFactory.java:401)
>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
>>> enConnection(DefaultClientConnectionOperator.java:178)
>>> at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoo
>>> lEntry.java:144)
>>> at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(Abs
>>> tractPooledConnAdapter.java:131)
>>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>>> t(DefaultRequestDirector.java:610)
>>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>>> efaultRequestDirector.java:445)
>>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>>> tractHttpClient.java:863)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:82)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:106)
>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>> eableHttpClient.java:57)
>>> at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRe
>>> triever.retrieveKeyTemplateData(KeyTemplateRetriever.java:83)
>>> at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRe
>>> triever.loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111)
>>> at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRe
>>> triever.run(KeyTemplateRetriever.java:54)
>>> at java.util.TimerThread.mainLoop(Timer.java:555)
>>> at java.util.TimerThread.run(Timer.java:505)
>>> Exception in thread "Timer-5" java.lang.NullPointerException
>>> at java.util.Objects.requireNonNull(Objects.java:203)
>>> at java.util.Arrays$ArrayList.(Arrays.java:3813)
>>> at java.util.Arrays.asList(Arrays.java:3800)
>>> at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRe
>>> triever.loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111)
>>> at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRe
>>> triever.run(KeyTemplateRetriever.java:54)
>>> at java.util.TimerThread.mainLoop(Timer.java:555)
>>> at java.util.TimerThread.run(Timer.java:505)
>>> [2017-12-05 15:57:04,008] INFO - AndesRecoveryTask Running DB sync task.
>>>
>>> Regards,
>>>
>>> *Senuwan Withana*
>>> Software Engineer - Support Team
Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter
Yes *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 5, 2017 at 7:55 PM, Harsha Kumara wrote: > Is your TM running with port offset 2? > > On Tue, Dec 5, 2017 at 7:43 PM, Senuwan Withana wrote: > >> Hi Guys >> >> Again Thanks for quick responses. I have looked all the comments and done >> the relevant changes >> Eg: Comment out the JMSEventPublisherParameters section, Up the TM >> first. so on. However still i got below errors. >> >> >> [2017-12-05 19:38:30,393] INFO - JMSTransportHandler Starting jms topic >> consumer thread... >> [2017-12-05 19:38:30,443] INFO - APIManagerComponent JMS Publisher not >> enabled. >> [2017-12-05 19:38:30,632] INFO - AMQConnection Unable to connect to >> broker at tcp://172.16.2.39:5674 >> org.wso2.andes.transport.TransportException: Could not open connection >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I >> oConnectorCreator.connect(MinaNetworkTransport.java:216) >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport. >> connect(MinaNetworkTransport.java:74) >> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo >> nnection(AMQConnectionDelegate_8_0.java:130) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) >> at java.security.AccessController.doPrivileged(Native Method) >> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ >> Connection.java:628) >> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:351) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:40) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon >> nection(JMSUtils.java:387) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ >> MSConnection(JMSListener.java:137) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start( >> JMSListener.java:79) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run( >> JMSListener.java:186) >> at java.lang.Thread.run(Thread.java:748) >> org.wso2.andes.AMQConnectionFailureException: Could not open connection >> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:351) >> at org.wso2.andes.client.AMQConnectionFactory.createConnection( >> AMQConnectionFactory.java:40) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon >> nection(JMSUtils.java:387) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ >> MSConnection(JMSListener.java:137) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start( >> JMSListener.java:79) >> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run( >> JMSListener.java:186) >> at java.lang.Thread.run(Thread.java:748) >> Caused by: org.wso2.andes.transport.TransportException: Could not open >> connection >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I >> oConnectorCreator.connect(MinaNetworkTransport.java:216) >> at org.wso2.andes.transport.network.mina.MinaNetworkTransport. >> connect(MinaNetworkTransport.java:74) >> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo >> nnection(AMQConnectionDelegate_8_0.java:130) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631) >> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628) >> at java.security.AccessController.doPrivileged(Native Method) >> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ >> Connection.java:628) >> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409) >> ... 7 more >> [2017-12-05 19:38:30,641] ERROR - JMSListener Unable to continue server >> startup as it seems the JMS Provider is not yet started. Please start the >> JMS provider now. >> [2017-12-05 19:38:30,644] ERROR - JMSListener Connection attempt : 1 for >> JMS Provider failed. Next retry in 20 seconds >> [2017-12-05 19:38:30,733] INFO - TenantLoadingConfig Using tenant lazy >> loading policy... >> [2017-12-05 19:38:30,743] INFO - PermissionUpdater Permission cache >> updated for tenant -1234 >> [2017-12-05 19:38:31,031] INFO - UserStoreMgtDSComponent Claim manager >> set for class org.wso2.carbon.user.core.common.DefaultRealm >> [2017-12-05 19:38:31
[Dev] [ESB] Buttons missing on developer studio window.
Hi Team, I have tried to add sample proxy service using WSO2 developer studio. But I could not find the navigation buttons on the "Add new proxy" screen. Is there any way to continue without those buttons. Furthermore I faced issue with maximise and minimize window. Suddenly window got closed. Version : developer-studio-ei-eclipse-jee-mars-2-linux-gtk-x86_64-1.1.0 Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB] SourceHandler I/O error
Hi Team, I got below error in EI Console. I would like to know why this error is happened? [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error: Received fatal alert: certificate_unknown javax.net.ssl.SSLException: Received fatal alert: certificate_unknown at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634) at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800) at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083) at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781) at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOSession.java:245) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:280) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:410) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586) at java.lang.Thread.run(Thread.java:748) Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM] Error occurred while connecting to back end
idate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347) ... 95 more Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Jun 19 14:43:07 IST 2017 at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274) at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629) at sun.security.provider.certpath.BasicChecker.verifyTimestamp(BasicChecker.java:190) at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144) at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125) ... 100 more Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Error occurred while connecting to back end
Hi Abimaran, Well, I did not generate any certificate. What I did was, tried to create an API using WSO2 API Manager, Publisher. When I was adding Production Endpoint that mentioned error was popping up. Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan wrote: > Hi Senuwan, > > By checking your exception, it says, your certificate is expired. You have > to generate a new certificate. > > Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon > Jun 19 14:43:07 IST 2017 > > On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana wrote: > >> Hi Team, >> >> I got below error when I'm trying to connect my ESB proxy into the API >> Manager. Any suggestion to solve this error? >> >> >> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred >> while connecting to backend : https://localhost:8243/services/EmailSender, >> reason : sun.security.validator.ValidatorException: PKIX path validation >> failed: java.security.cert.CertPathValidatorException: timestamp check >> failed >> javax.net.ssl.SSLHandshakeException: >> sun.security.validator.ValidatorException: >> PKIX path validation failed: java.security.cert.CertPathValidatorException: >> timestamp check failed >> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) >> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) >> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) >> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) >> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa >> ndshaker.java:1514) >> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands >> haker.java:216) >> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026) >> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961) >> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) >> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo >> cketImpl.java:1375) >> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) >> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) >> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS >> ocketFactory.java:533) >> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS >> ocketFactory.java:401) >> at org.apache.http.impl.conn.DefaultClientConnectionOperator. >> openConnection(DefaultClientConnectionOperator.java:178) >> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M >> anagedClientConnectionImpl.java:304) >> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec >> t(DefaultRequestDirector.java:610) >> at org.apache.http.impl.client.DefaultRequestDirector.execute(D >> efaultRequestDirector.java:445) >> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs >> tractHttpClient.java:863) >> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >> eableHttpClient.java:82) >> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >> eableHttpClient.java:106) >> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >> eableHttpClient.java:57) >> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen >> dHttpHEADRequest(APIProviderHostObject.java:4781) >> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF >> unction_isURLValid(APIProviderHostObject.java:4173) >> at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source) >> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >> thodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:498) >> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) >> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386) >> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) >> at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_10 >> (/publisher/modules/api/add.jag:225) >> at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher >> /modules/api/add.jag) >> at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRunti >> me.java:2430) >> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269) >> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97) >> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42) >> at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_5( >> /
Re: [Dev] [APIM] Error occurred while connecting to back end
Thank Guys, I will look into it. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 12, 2017 at 7:23 PM, Godwin Shrimal wrote: > Hi Senuwan, > > Check the validity period of the certificate of the ESB. Maybe it's > expired. > > Thanks > Godwin > > On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana wrote: > >> Hi Abimaran, >> >> Well, I did not generate any certificate. What I did was, tried to create >> an API using WSO2 API Manager, Publisher. When I was adding Production >> Endpoint that mentioned error was popping up. >> >> Thanks. >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan >> wrote: >> >>> Hi Senuwan, >>> >>> By checking your exception, it says, your certificate is expired. You >>> have to generate a new certificate. >>> >>> Caused by: java.security.cert.CertificateExpiredException: NotAfter: >>> Mon Jun 19 14:43:07 IST 2017 >>> >>> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana >>> wrote: >>> >>>> Hi Team, >>>> >>>> I got below error when I'm trying to connect my ESB proxy into the API >>>> Manager. Any suggestion to solve this error? >>>> >>>> >>>> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error occurred >>>> while connecting to backend : https://localhost:8243/service >>>> s/EmailSender, reason : sun.security.validator.ValidatorException: >>>> PKIX path validation failed: java.security.cert.CertPathValidatorException: >>>> timestamp check failed >>>> javax.net.ssl.SSLHandshakeException: >>>> sun.security.validator.ValidatorException: >>>> PKIX path validation failed: java.security.cert.CertPathValidatorException: >>>> timestamp check failed >>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) >>>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) >>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) >>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) >>>> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa >>>> ndshaker.java:1514) >>>> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands >>>> haker.java:216) >>>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026) >>>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961) >>>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) >>>> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo >>>> cketImpl.java:1375) >>>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl. >>>> java:1403) >>>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl. >>>> java:1387) >>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS >>>> ocketFactory.java:533) >>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS >>>> ocketFactory.java:401) >>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op >>>> enConnection(DefaultClientConnectionOperator.java:178) >>>> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M >>>> anagedClientConnectionImpl.java:304) >>>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec >>>> t(DefaultRequestDirector.java:610) >>>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D >>>> efaultRequestDirector.java:445) >>>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs >>>> tractHttpClient.java:863) >>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >>>> eableHttpClient.java:82) >>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >>>> eableHttpClient.java:106) >>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos >>>> eableHttpClient.java:57) >>>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen >>>> dHttpHEADRequest(APIProviderHostObject.java:4781) >>>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF >>>> unction_isURLValid(APIProviderHostObject.
Re: [Dev] [ESB] SourceHandler I/O error
Thanks, I will check on it. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Tue, Dec 12, 2017 at 8:14 PM, Dinusha Dissanayake wrote: > Hi Senuwa, > > The reason for this is the certifiacte has not been approved from the > browser. So I think this could be fixed when certificate is accepted from > browser. Please check if logging to EI from a new tab and trust the cert > from the browser would solve this issue > > Thanks, > DinushaD. > > On Tue, Dec 12, 2017 at 5:33 PM, Dilusha Alphonso > wrote: > >> Hi Senuwan, >> >> This looks like certificate error.I think this exception is happening >> when invoking API in EI. Could you tell how to use curl command when >> invoking API? >> >> Thanks >> Dilusha >> >> On Tue, Dec 12, 2017 at 4:36 PM, Senuwan Withana >> wrote: >> >>> Hi Team, >>> >>> I got below error in EI Console. I would like to know why this error is >>> happened? >>> >>> >>> [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error: >>> Received fatal alert: certificate_unknown >>> javax.net.ssl.SSLException: Received fatal alert: certificate_unknown >>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) >>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666) >>> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634) >>> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800) >>> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083) >>> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907) >>> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781) >>> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) >>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS >>> ession.java:245) >>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL >>> IOSession.java:280) >>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady >>> (SSLIOSession.java:410) >>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea >>> dy(AbstractIODispatch.java:119) >>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base >>> IOReactor.java:159) >>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv >>> ent(AbstractIOReactor.java:338) >>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv >>> ents(AbstractIOReactor.java:316) >>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A >>> bstractIOReactor.java:277) >>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI >>> OReactor.java:105) >>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto >>> r$Worker.run(AbstractMultiworkerIOReactor.java:586) >>> at java.lang.Thread.run(Thread.java:748) >>> >>> >>> Regards, >>> >>> *Senuwan Withana* >>> Software Engineer - Support Team | WSO2 >>> >>> Email : senu...@wso2.com >>> Mobile: 94773212853 >>> Web: http://www.wso2.com >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> >> *Best Regards,Dilusha Alphonso* >> >> *Software Engineer - Support Team* >> >> >> *WSO2* >> *Mobile : * >> >> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature] >> <http://wso2.com/signature>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Dinusha Dissanayake > Software Engineer > WSO2 Inc > Mobile: +94712939439 <+94%2071%20293%209439> > <https://wso2.com/signature> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB -DSS] Issue on sending emails.
Hi Team, When the user adds some value(s) into the back end I want to send an email to some other users like managers etc. In order to do below scenario I have used WSO2 EI DSS service. I have tried out the scenario give on documentation [1], but email have not generated. Please give me suggestion to over come this issue. /AddDetails/ENGINE_CAPACITY<10 new_order mailto:x...@wso2.com mailto:m...@gmail.com [1] - https://docs.wso2.com/display/EI600/Receiving+Notifications+from+Data+Services Furthermore I wan to clarify my x path as well. Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB -DSS] Issue on sending emails.
Hi Guys, Thanks for respond. Well, I would able to send email correctly, after the selecting the "Event Trigger" option. Input Event Trigger --Select-- SendEmail Regards, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Fri, Dec 15, 2017 at 9:29 AM, Chanika Geeganage wrote: > According to the configuration the email is sent only if the value passed > for ENGINE_CAPACITY is less than 10. As Praminda said do you observe any > exceptions in logs? If so can you please post them., > > On Fri, Dec 15, 2017 at 9:25 AM, Praminda Jayawardana > wrote: > >> Hi Senuwan, >> >> Do you get any errors when trying to send an email? If you get >> authentication errors you should use app password [1] for the axis2 email >> configuration. >> >> [1]: https://security.google.com/settings/security/apppasswords >> >> Thanks, >> Praminda >> >> On Thu, Dec 14, 2017 at 9:26 PM, Senuwan Withana >> wrote: >> >>> Hi Team, >>> >>> When the user adds some value(s) into the back end I want to send an >>> email to some other users like managers etc. >>> >>> In order to do below scenario I have used WSO2 EI DSS service. I have >>> tried out the scenario give on documentation [1], but email have not >>> generated. >>> >>> >>> Please give me suggestion to over come this issue. >>> >>> >>> >>> /AddDetails/ENGINE_CAPACITY<10 >>> new_order >>> >>> mailto:x...@wso2.com >>> mailto:m...@gmail.com >>> >>> >>> >>> >>> >>> [1] - https://docs.wso2.com/display/EI600/Receiving+Notification >>> s+from+Data+Services >>> >>> >>> >>> Furthermore I wan to clarify my x path as well. >>> >>> >>> Thanks. >>> >>> *Senuwan Withana* >>> Software Engineer - Support Team | WSO2 >>> >>> Email : senu...@wso2.com >>> Mobile: 94773212853 >>> Web: http://www.wso2.com >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Praminda Jayawardana* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Best Regards.. > > Chanika Geeganage > +94773522586 <+94%2077%20352%202586> > WSO2, Inc.; http://wso2.com > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [EI-DSS] "Can not issue executeUpdate() or executeLargeUpdate() for SELECTs" error popup.
2-16 10:24:16,290] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "[\n]"
[2017-12-16 10:24:16,290] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 <<
"http://ws.wso2.org/dataservice";>{}CARAPPConnected
CAR app data service.
/CARAPP.dbs
http://ws.wso2.org/dataserviceDATABASE_ERRORjava.sql.SQLException:
Can not issue executeUpdate() or executeLargeUpdate() for
SELECTsGetLastRecord[\r][\n]"
[2017-12-16 10:24:16,290] [EI-Core] DEBUG - content << "[\r]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "[\n]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "0"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "[\r]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "[\n]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "[\r]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - content << "[\n]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - header << "[\r][\n]"
[2017-12-16 10:24:16,291] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "0[\r][\n]"
[2017-12-16 10:24:16,292] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "[\r][\n]"
Thanks,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [EI-DSS] "Can not issue executeUpdate() or executeLargeUpdate() for SELECTs" error popup.
/CARAPP.dbs
http://ws.wso2.org/dataserviceDATABASE_ERRORjava.sql.SQLException:
Can not issue executeUpdate() or executeLargeUpdate() for
SELECTsGetLastRecord[\r][\n]"
[2017-12-16 16:42:39,236] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "0[\r][\n]"
[2017-12-16 16:42:39,236] [EI-Core] DEBUG - wire HTTP-Listener I/O
dispatcher-1 << "[\r][\n]"
[2017-12-16 16:42:39,236] [EI-Core] DEBUG - header << "HTTP/1.1 500
Internal Server Error[\r][\n]"
[2017-12-16 16:42:39,240] [EI-Core] DEBUG - header << "HTTP/1.1 500
Internal Server Error[\r][\n]"
[2017-12-16 16:42:39,240] [EI-Core] DEBUG - header << "Content-Type:
application/soap+xml; charset=UTF-8; action="
http://www.w3.org/2005/08/addressing/soap/fault"[\r][\n]";
[2017-12-16 16:42:39,241] [EI-Core] DEBUG - header << "Date: Sat, 16 Dec
2017 11:12:39 GMT[\r][\n]"
[2017-12-16 16:42:39,241] [EI-Core] DEBUG - header << "Transfer-Encoding:
chunked[\r][\n]"
[2017-12-16 16:42:39,241] [EI-Core] DEBUG - header << "[\r][\n]"
[2017-12-16 16:42:39,241] [EI-Core] DEBUG - content << "e"
[2017-12-16 16:42:39,242] [EI-Core] DEBUG - content << "f"
[2017-12-16 16:42:39,242] [EI-Core] DEBUG - content << "8"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "[\r]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "<"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "?xm"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "l version='1.0'
encoding='UTF-8'?>http://www.w3.org/2003/05/soap-envelope";>http://ws.wso2.org/dataservice";>axis2ns13:DATABASE_ERRORDS Fault Message: Error in DS non result invoke.[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "DS Code:
DATABASE_ERROR[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "Nested
Exception:-[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content <<
"javax.xml.stream.XMLStreamException: DS Fault Message: Error in
'SQLQuery.processPreNormalQuery': Can not issue executeUpdate() or
executeLargeUpdate() for SELECTs[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "DS Code:
DATABASE_ERROR[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "Source Data
Service:-[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "Name: CARAPP[\n]"
[2017-12-16 16:42:39,248] [EI-Core] DEBUG - content << "Location:
/CARAPP.dbs[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "Description:
Connected CAR app data service.
[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "Default Namespace:
http://ws.wso2.org/dataservice[\n]";
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "Current Request
Name: GetLastRecord[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "Current Params:
{GetRow=10}[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "Nested
Exception:-[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content <<
"java.sql.SQLException: Can not issue executeUpdate() or
executeLargeUpdate() for SELECTs[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content << "[\n]"
[2017-12-16 16:42:39,249] [EI-Core] DEBUG - content <<
"http://ws.wso2.org/dataservice";>{GetRow=10}CARAPPConnected
CAR app data service.
Re: [Dev] [EI-DSS] "Can not issue executeUpdate() or executeLargeUpdate() for SELECTs" error popup.
Thanks guys, After added following, It works. without popup errors. Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Sun, Dec 17, 2017 at 6:14 AM, Shazni Nazeer wrote: > Hi Senuwan, > > What you need is something like below. As Nandika mentioned you need to > add a for output mapping. > > > SELECT MAX(RECORD_ID) FROM employee_id; > > xsdType="string"/> > > > > > > > On Sat, Dec 16, 2017 at 5:18 AM, Senuwan Withana wrote: > >> Thanks for the update. >> I added query parameter and tested, but still I got same error. >> >> >> >> SELECT MAX(RECORD_ID) FROM Customer >> >> >> >> >> >> >> >> >> >> --- >> >> >> [2017-12-16 16:42:39,216] [EI-Core] DEBUG - header >> "POST >> /services/CARAPP.SOAP12Endpoint/GetLastRecord HTTP/1.1[\r][\n]" >> [2017-12-16 16:42:39,218] [EI-Core] DEBUG - header >> "Content-Type: >> application/soap+xml; charset=UTF-8; action="urn:GetLastRecord"[\r][\n]" >> [2017-12-16 16:42:39,218] [EI-Core] DEBUG - header >> "Cookie: >> menuPanel=visible; menuPanelType=main; region1_configure_menu=none; >> region3_registry_menu=none; region4_monitor_menu=none; >> region5_tools_menu=none; MSG15129165207870.21963900039265616=true; >> MSG15130739092210.15348576819556436=true; >> MSG15130739810920.3014705142781514=true; >> MSG15130753418090.33963906683288003=true; >> MSG15130753619370.12255281154976705=true; >> MSG15130753917050.04244936775745323=true; >> MSG15131806233020.2276242035284045=true; >> MSG15131806273740.689304387480249=true; >> MSG15131806535940.4462982474705657=true; >> MSG15131806597420.8476406500277069=true; wso2.carbon.rememberme=admin-d >> 5d1272f-b4ee-4853-b741-e87f912b4f81; >> JSESSIONID=70A6660D04EE2F2B733478004E9E86E4; >> requestedURI=../../carbon/service-mgt/index.jsp; >> current-breadcrumb=%2523[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - header >> "User-Agent: >> Axis2[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - header >> "Host: >> senuwan-ThinkPad:8280[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - header >> "Transfer-Encoding: >> chunked[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - header >> "[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - content >> "12f[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "POST /services/CARAPP.SOAP12Endpoint/GetLastRecord >> HTTP/1.1[\r][\n]" >> [2017-12-16 16:42:39,219] [EI-Core] DEBUG - content >> "> version='1.0' encoding='UTF-8'?>http://www.w3.org/2003/05/soap-envelope";>> xmlns:p="http://ws.wso2.org/dataservice";>http://ws.wso2.org/dataservice";>10> GetLastRecord>" >> [2017-12-16 16:42:39,220] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Content-Type: application/soap+xml; charset=UTF-8; >> action="urn:GetLastRecord"[\r][\n]" >> [2017-12-16 16:42:39,220] [EI-Core] DEBUG - content >> "[\r][\n]" >> [2017-12-16 16:42:39,220] [EI-Core] DEBUG - content >> "0" >> [2017-12-16 16:42:39,220] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Cookie: menuPanel=visible; menuPanelType=main; >> region1_configure_menu=none; region3_registry_menu=none; >> region4_monitor_menu=none; region5_tools_menu=none; >> MSG15129165207870.21963900039265616=true; >> MSG15130739092210.15348576819556436=true; >> MSG15130739810920.3014705142781514=true; >> MSG15130753418090.33963906683288003=true; >> MSG15130753619370.12255281154976705=true; >> MSG15130753917050.04244936775745323=true; >> MSG15131806233020.2276242035284045=true; >> MSG15131806273740.689304387480249=true; >> MSG15131806535940.4462982474705657=true; >> MSG15131806597420.8476406500277069=true; >> wso2.carbon.rememberme=admin-d5d1272f-b4ee-4853-b741-e87f912b4f81; >> JSESSIONID=70A6660D04EE2F2B733478004E9E86E4; >> requestedURI=../../carbon/service-mgt/index.jsp; >> current-breadcrumb=%2523[\r][\n]" >> [2017-12-16 16:42:39,220] [EI-Core] DEBUG - content >>
[Dev] [DSS] Issue on email pattern validation.
USTOMER_EMAIL Field Value: senu...@wso2.com at org.wso2.carbon.dataservices.core.dispatch.SingleDataServiceRequest.processRequest(SingleDataServiceRequest.java:75) at org.wso2.carbon.dataservices.core.dispatch.DataServiceRequest.dispatch(DataServiceRequest.java:357) at org.wso2.carbon.dataservices.core.DataServiceProcessor.dispatch(DataServiceProcessor.java:41) at org.wso2.carbon.dataservices.core.DBInOutMessageReceiver.invokeBusinessLogic(DBInOutMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: javax.xml.stream.XMLStreamException: DS Code: VALIDATION_ERROR Source Data Service:- Name: CARAPP Location: /CARAPP.dbs Description: Connected CAR app data service. Thanks, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DSS] Issue on email pattern validation.
Hi Sashika,
Thanks for the update. Great, that validation pattern works fine.
Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2
Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
On Sat, Jan 6, 2018 at 11:43 AM, Sashika Wijesinghe
wrote:
> Hi Senuwan,
>
> I have tried with the regex pattern you provided and I'm getting the same
> validation error as above. However, if I execute the given regex pattern in
> Mysql it gives the correct result as below. The reason for this behaviour
> is due to the differences in the metacharacters used in MySQL regex and
> Javascript regex.
>
> mysql> SELECT * FROM `Employee` WHERE `email`REGEXP
> '^[A-Z0-9._%-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$';
> +---+--+---+-+--+--+
> | EmpID | LastName | FirstName | Address | City | email|
> +---+--+---+-+--+--+
> | 199 | DEDDEDE | abcname | testadd | citytest | sash...@wso2.com |
> +---+--+---+-+--+--+
> 1 row in set (0.00 sec)
>
>
> To validate the email address in DSS you can use
> *^([0-9a-zA-Z]([-.\w]*[0-9a-zA-Z])*@([0-9a-zA-Z][-\w]*[0-9a-zA-Z]\.)+[a-zA-Z]{2,9})$*
> regex pattern.
>
> Example:
>
>
> INSERT INTO Employee (EMpID,LastName,FirstName,Address,City,
> email) VALUES (:id,:Lname,:Fname,:Address,:city, :email);
>
>
>
>
>
>
>
>
>
>
> Could you please try using the given regex pattern to validate the email
> address in your data service?
>
> Regards,
> Sashika
>
> On Fri, Jan 5, 2018 at 10:50 PM, Senuwan Withana wrote:
>
>> Hi Team,
>>
>> I found an issue when validating the email id using the WSO2 DSS. I have
>> used below mentioned pattern.
>>
>>
>> When I executed my API I got error like following:
>>
>> Nested Exception:-
>> Pattern {^[A-Z0-9._%-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$} is expected
>> Field Name: CUSTOMER_EMAIL
>> Field Value: senu...@wso2.com
>>
>>
>> Kindly give the suggestion to over come the mentioned issue.
>>
>> *Full log attached below.*
>>
>>
>>
>> [2018-01-05 22:42:58,397] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "POST /carproduction HTTP/1.1[\r][\n]"
>> [2018-01-05 22:42:58,397] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "cache-control: no-cache[\r][\n]"
>> [2018-01-05 22:42:58,397] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Postman-Token: ee0d92e3-e410-4bb3-b0c2-434041
>> ff1029[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Content-Type: application/xml[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "User-Agent: PostmanRuntime/6.4.1[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Accept: */*[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Host: localhost:8280[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "accept-encoding: gzip, deflate[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "content-length: 810[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Connection: keep-alive[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "[\r][\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> " [\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Samantha123
>> Perera[\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "senu...@wso2.com
>> [\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "Alto[\n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> dispatcher-2 >> "blue[
>> \n]"
>> [2018-01-05 22:42:58,398] [EI-Core] DEBUG - wire HTTP-Listener I/O
>> d
[Dev] [EI] Correct Xpath expression to read database response.
Hi Team, In my Scenario, I want to get Email_ID and Record_ID from the database response. Response is correctly come to the wire-log. But I could not able to log the Email_ID and Record_ID. I have tried out following Xpath expressions but non of those give me the correct result. [1]. $body/m0:Entries/m0:Entry/m0:CUSTOMER_EMAIL/text() - Not work [2]. "//*[local-name()='CUSTOMER_EMAIL']"- Not work [3].$body /Entries/Entry/CUSTOMER_EMAIL/text()- Not work [4].//body/Entries/Entry/CUSTOMER_EMAIL/text()- Not work [5].$body - Works, but all the data log. [2018-01-06 15:08:24,160] [EI-Core] DEBUG - content << "?xm" [2018-01-06 15:08:24,160] [EI-Core] DEBUG - content << "l version='1.0' encoding='UTF-8'?>http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">138senu...@wso2.com Altoblue800YesYesNoNoApprovedPink5T" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "0" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" [2018-01-06 15:08:24,161] [EI-Core] DEBUG - header << "[\r][\n]" [2018-01-06 15:08:24,163] [EI-Core] INFO - LogMediator Body = http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">138senu...@wso2.com Altoblue800YesYesNoNoApprovedPink5T [2018-01-06 15:08:24,164] [EI-Core] INFO - LogMediator Email = [2018-01-06 15:08:24,186] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "HTTP/1.1 202 Accepted[\r][\n]" [2018-01-06 15:08:24,189] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Content-Type: text/xml; charset=UTF-8[\r][\n]" Any suggestion to for the correct Xpath Expression. Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [EI] Correct Xpath expression to read database response.
Hi Vijitha, Thanks for the support. First I have tried out the above scenario. it works fine and retrieved the Email_ID and Record_ID However when I applied to suggested Xpath configurations to my API, It not functioned. An empty value is returned. Could you tell me what is the reason for that. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Sat, Jan 6, 2018 at 6:20 PM, Vijitha Ekanayake wrote: > Hi Senuwan, > > I tried this in EI WUM updated pack with below API configurations and was > able to get CUSTOMER_EMAIL and RECORD_ID by defining data service namespace > inside property mediator. > > *API configurations* > > http://ws.apache.org/ns/synapse"; > name="ContextServiceAPI-2.0.0" context="/context-2.0.0"> > > > > >http://www.mocky.io/v2/ > 5a50c0d32ffc128d52ee"> > > 3 > discard > > > 0 > 1.0 > 0 > > > > > > http://ws.wso2.org/dataservice"; > name="EmailID" expression="//m0:CUSTOMER_EMAIL"/> > http://ws.wso2.org/dataservice"; > name="Record_ID" expression="//m0:RECORD_ID"/> > > > > > > > *Request* > > curl -v http://localhost:8280/context-2.0.0/abc > > *Output in the console* > > [2018-01-06 18:15:15,206] [EI-Core] INFO - LogMediator EmailID = > senu...@wso2.com, Record_ID = 138 > > Could you try your scenario with suggested Xpath configurations as above? > > Thanks, > Vijitha. > > > On Sat, Jan 6, 2018 at 3:34 PM, Senuwan Withana wrote: > >> Hi Team, >> >> In my Scenario, I want to get Email_ID and Record_ID from the database >> response. >> Response is correctly come to the wire-log. But I could not able to log >> the Email_ID and Record_ID. >> >> I have tried out following Xpath expressions but non of those give me >> the correct result. >> >> >> [1]. $body/m0:Entries/m0:Entry/m0:CUSTOMER_EMAIL/text() - Not work >> [2]. "//*[local-name()='CUSTOMER_EMAIL']"- Not work >> [3].$body /Entries/Entry/CUSTOMER_EMAIL/text()- Not work >> [4].//body/Entries/Entry/CUSTOMER_EMAIL/text()- Not work >> [5].$body - Works, but all the data log. >> >> >> >> [2018-01-06 15:08:24,160] [EI-Core] DEBUG - content << "?xm" >> [2018-01-06 15:08:24,160] [EI-Core] DEBUG - content << "l version='1.0' >> encoding='UTF-8'?>http://schemas. >> xmlsoap.org/soap/envelope/">http://ws.wso2.org/dataservice";> >> 138senu...@wso2.com> EMAIL>Altoblue> COLOR>800> MATERIAL>Yes< >> HEATED_LEATHER_SEATS>Yes> ON>NoNo> TAILGATE>ApprovedPink> INTERIOR_COLOR>5T> soapenv:Body>" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "0" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\r]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - content << "[\n]" >> [2018-01-06 15:08:24,161] [EI-Core] DEBUG - header << "[\r][\n]" >> [2018-01-06 15:08:24,163] [EI-Core] INFO - LogMediator Body >> = http://schemas.xmlsoap.org/soap/envelope/ >> ">http://ws.wso2.org/dataservice";> >> 138senu...@wso2.com> EMAIL>Altoblue> COLOR>800> MATERIAL/>Yes >> YesNo< >> AUTOMATIC_TAILGATE>No >> ApprovedPink< >> TIRE_SIZE>5T >> [2018-01-06 15:08:24,164] [EI-Core] INFO - LogMediator Email >> = >> [2018-01-06 15:08:24,186] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-3 << "HTTP/1.1 202 Accepted[\r][\n]" >> [2018-01-06 15:08:24,189] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-3 << "Content-Type: text/xml; charset=UTF-8[\r][\n]" >> >> >> >> >> Any suggestion to for the correct Xpath Expression. >> >> Thanks. >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Vijitha Ekanayake > Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/ > Mobile : +94 777 24 73 39 | +94 718 74 44 08 > lean.enterprise.middleware > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [EI] RabbitMQStore Store [RabbitMQ] cannot create connection to the broker.java.io.IOException
/MSMP.MSMPHttpSoap12Endpoint, WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:3e7c884c-a3aa-4219-944c-19c73d02fee1, Direction: request, Envelope: http://www.w3.org/2003/05/soap-envelope";> *[2018-01-07 20:35:11,678] [EI-Core] ERROR - RabbitMQStore Store [RabbitMQ] cannot create connection to the broker.java.io.IOException* [2018-01-07 20:35:11,679] [EI-Core] WARN - RabbitMQProducer [RabbitMQ-P-4]. Ignored MessageID : urn:uuid:d1ebee4e-7b73-4a47-bd20-fe2f6bdca3a6 [2018-01-07 20:35:11,680] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "HTTP/1.1 202 Accepted[\r][\n]" [2018-01-07 20:35:11,680] [EI-Core] DEBUG - header << "HTTP/1.1 202 Accepted[\r][\n]" [2018-01-07 20:35:11,681] [EI-Core] DEBUG - header << "HTTP/1.1 202 Accepted[\r][\n]" [2018-01-07 20:35:11,680] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "Date: Sun, 07 Jan 2018 15:05:11 GMT[\r][\n]" [2018-01-07 20:35:11,681] [EI-Core] DEBUG - header << "Date: Sun, 07 Jan 2018 15:05:11 GMT[\r][\n]" [2018-01-07 20:35:11,681] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "Transfer-Encoding: chunked[\r][\n]" [2018-01-07 20:35:11,682] [EI-Core] DEBUG - header << "Transfer-Encoding: chunked[\r][\n]" [2018-01-07 20:35:11,682] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "[\r][\n]" [2018-01-07 20:35:11,682] [EI-Core] DEBUG - header << "[\r][\n]" [2018-01-07 20:35:11,682] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "0[\r][\n]" [2018-01-07 20:35:11,683] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-2 << "[\r][\n]" [2018-01-07 20:35:11,683] [EI-Core] DEBUG - content << "0" [2018-01-07 20:35:11,683] [EI-Core] DEBUG - content << "[\r]" [2018-01-07 20:35:11,683] [EI-Core] DEBUG - content << "[\n]" [2018-01-07 20:35:11,684] [EI-Core] DEBUG - content << "[\r]" [2018-01-07 20:35:11,684] [EI-Core] DEBUG - content << "[\n]" [2018-01-07 20:35:11,684] [EI-Core] DEBUG - header << "[\r][\n]" http://ws.apache.org/ns/synapse"; name="MSMP" startOnLoad="true" statistics="disable" trace="disable" transports="http,https"> What is the reason for below error and why is the message processor always in deactivated mode *[2018-01-07 20:35:11,678] [EI-Core] ERROR - RabbitMQStore Store [RabbitMQ] cannot create connection to the broker.java.io.IOException* Waiting for favourable reply. Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [EI] RabbitMQStore Store [RabbitMQ] cannot create connection to the broker.java.io.IOException
-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "Transfer-Encoding: chunked[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - header << "Date: Sun, 07 Jan 2018 17:10:24 GMT[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - header << "Transfer-Encoding: chunked[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "0[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - header << "[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "[\r][\n]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - content << "0" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - content << "[\r]" [2018-01-07 22:40:24,284] [EI-Core] DEBUG - content << "[\n]" [2018-01-07 22:40:24,285] [EI-Core] DEBUG - content << "[\r]" [2018-01-07 22:40:24,285] [EI-Core] DEBUG - content << "[\n]" [2018-01-07 22:40:24,285] [EI-Core] DEBUG - header << "[\r][\n]" But Still RabbitMQ message store displayed as "Not Applicable". Status . Thanks. *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Sun, Jan 7, 2018 at 10:31 PM, Eranda Rajapakshe wrote: > Hi Senuwan, > > I think the port you have used to connect to the RabbitMQ server is > incorrect. Assuming that you have not changed the port of the RabbitMQ, it > should be *5672. *Update that in RabbitMQ Store configuration and see. > > 15672 is the port they use for Management Console. > > Thanks, > > On Sun, Jan 7, 2018 at 10:10 PM, Senuwan Withana wrote: > >> Hi Team, >> >> According to my scenario, I have installed RabbitMQ. I could able to log >> RabbitMQ management console successfully by using below url. >> >> [1]. http://localhost:15672/# >> >> *Message Store like below.* >> >> http://ws.apache.org/ns >> /synapse"> >>localhost >>15672 >>RabbitMS_Queue >>true> parameter> >>InMemoryStore >> >> >> >> *Message Processor like below.* >> >> http://ws.apache.org/ns >> /synapse"> >>localhost >>15672 >>RabbitMS_Queue >>true> parameter> >>InMemoryStore >> >> >> >> >> *Sample Proxy like below* >> >> >> http://ws.apache.org/ns/synapse"; >>name="MSMP" >>startOnLoad="true" >>statistics="disable" >>trace="disable" >>transports="http,https"> >> >> >> >> >> >> >> >> >> >> >> >> >> However created Message store is displayed like below; >> >> >> Sample Output : >> >> >> [2018-01-07 20:35:06,688] [EI-Core] DEBUG - header >> "POST >> /services/MSMP.MSMPHttpSoap12Endpoint HTTP/1.1[\r][\n]" >> [2018-01-07 20:35:06,691] [EI-Core] DEBUG - header >> "Content-Type: >> application/soap+xml; charset=UTF-8; action="urn:mediate"[\r][\n]" >> [2018-01-07 20:35:06,691] [EI-Core] DEBUG - header >> "Cookie: >> menuPanel=visible; menuPanelType=main; region1_configure_menu=none; >> region3_registry_menu=none; region4_monitor_menu=none; >> region5_tools_menu=none; wso2.carbon.rememberme=admin-0 >> fcf06d6-0bce-4889-bfa4-e90824857bc1; >> MSG15153308979020.44872799565610855=true; >> MSG15153309964540.9715582563145939=true; >> MSG15153310279120.5745849191246893=true; >> MSG15153310508710.7582163507024167=true; m=2258:Z3Vlc3Q6Z3Vlc3Q%253D; >> JSESSIONID=760A7D05AFD555FC5A904276E1B8731F; >> requestedURI="../../carbon/proxyservices/templates.jsp?regio >> n=region1&item=proxy_services_menu"; current-breadcrumb=manage_menu >> %252Cmediation_menu%252CmessageProcessor_menu%2523[\r][\n]" >> [2018-01-07 20:35:06,692] [EI-Core] DEBUG - header >> "User-Agent: >> Axis2[\r][\n]" >> [2018-01-07 20:35:06,693] [EI-Core] DEBUG - header >> "Host: >> senuwan-ThinkPad:8280[\r][\n]" >> [2018-01-07 20:35:06,694] [EI-Core] DEBUG - header >> "Transfer-Encoding: >> chunked[\r][\n]" >> [2018-01-07 20:35:06,694] [EI-Core] DEBUG - header >> "[\r][\n]" >> [2018-01-07 20:35:06,695] [EI-Core] DEBUG -
Re: [Dev] [EI] RabbitMQStore Store [RabbitMQ] cannot create connection to the broker.java.io.IOException
Yes It works fine thanks for help *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com On Sun, Jan 7, 2018 at 10:53 PM, Eranda Rajapakshe wrote: > It says not Not Applicable to the number of messages. I think that's > expected, as its an external message store. The message count should only > be applicable to the In-Memory Store. > > Deactivate the processor and see if the message is there in the store > after publishing, if so it works fine. > > Thanks, > > > On Sun, Jan 7, 2018 at 10:47 PM, Senuwan Withana wrote: > >> Hi Eranda, >> >> Well, I have changed to the port number in RabbitMQ Store configuration. >> >> *Message Processor like below.* >> >> http://ws.apache.org/ns >> /synapse"> >>127.0.0.1 >>5672 >>RabbitMS_Queue >>true >>InMemoryStore >> >> >> >> After that I got below response >> >> >> >> >> [2018-01-07 22:40:24,254] [EI-Core] DEBUG - header >> "POST >> /services/MSMP.MSMPHttpSoap12Endpoint HTTP/1.1[\r][\n]" >> [2018-01-07 22:40:24,255] [EI-Core] DEBUG - header >> "Content-Type: >> application/soap+xml; charset=UTF-8; action="urn:mediate"[\r][\n]" >> [2018-01-07 22:40:24,256] [EI-Core] DEBUG - header >> "Cookie: >> menuPanel=visible; menuPanelType=main; region1_configure_menu=none; >> region3_registry_menu=none; region4_monitor_menu=none; >> region5_tools_menu=none; wso2.carbon.rememberme=admin-0 >> fcf06d6-0bce-4889-bfa4-e90824857bc1; >> MSG15153308979020.44872799565610855=true; >> MSG15153309964540.9715582563145939=true; >> MSG15153310279120.5745849191246893=true; >> MSG15153310508710.7582163507024167=true; m=2258:Z3Vlc3Q6Z3Vlc3Q%253D; >> requestedURI=../../carbon/admin/index.jsp; >> JSESSIONID=B36674C95012F4620A4D327AFD764039; >> current-breadcrumb=manage_menu%252Cmediation_menu%252Cmessag >> eProcessor_menu%2523[\r][\n]" >> [2018-01-07 22:40:24,256] [EI-Core] DEBUG - header >> "User-Agent: >> Axis2[\r][\n]" >> [2018-01-07 22:40:24,256] [EI-Core] DEBUG - header >> "Host: >> senuwan-ThinkPad:8280[\r][\n]" >> [2018-01-07 22:40:24,257] [EI-Core] DEBUG - header >> "Transfer-Encoding: >> chunked[\r][\n]" >> [2018-01-07 22:40:24,257] [EI-Core] DEBUG - header >> "[\r][\n]" >> [2018-01-07 22:40:24,257] [EI-Core] DEBUG - content >> "92[\r][\n]" >> [2018-01-07 22:40:24,257] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "POST /services/MSMP.MSMPHttpSoap12Endpoint >> HTTP/1.1[\r][\n]" >> [2018-01-07 22:40:24,258] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Content-Type: application/soap+xml; charset=UTF-8; >> action="urn:mediate"[\r][\n]" >> [2018-01-07 22:40:24,258] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Cookie: menuPanel=visible; menuPanelType=main; >> region1_configure_menu=none; region3_registry_menu=none; >> region4_monitor_menu=none; region5_tools_menu=none; >> wso2.carbon.rememberme=admin-0fcf06d6-0bce-4889-bfa4-e90824857bc1; >> MSG15153308979020.44872799565610855=true; >> MSG15153309964540.9715582563145939=true; >> MSG15153310279120.5745849191246893=true; >> MSG15153310508710.7582163507024167=true; >> m=2258:Z3Vlc3Q6Z3Vlc3Q%253D; requestedURI=../../carbon/admin/index.jsp; >> JSESSIONID=B36674C95012F4620A4D327AFD764039; >> current-breadcrumb=manage_menu%252Cmediation_menu%252Cmessag >> eProcessor_menu%2523[\r][\n]" >> [2018-01-07 22:40:24,258] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "User-Agent: Axis2[\r][\n]" >> [2018-01-07 22:40:24,259] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Host: senuwan-ThinkPad:8280[\r][\n]" >> [2018-01-07 22:40:24,259] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "Transfer-Encoding: chunked[\r][\n]" >> [2018-01-07 22:40:24,259] [EI-Core] DEBUG - wire HTTP-Listener I/O >> dispatcher-1 >> "[\r][\n]" >> [2018-01-07 22:40:24,265] [EI-Core] DEBUG - content >> "> version='1.0' encoding='UTF-8'?>http://www.w3.org/2003/05/soap-envelope";>> penv:Body/>" >> [2018-01-07 22:40:24,266] [EI-Core] DEBUG - content >> "[\r][\n]" >> [2018-01-07 22:40:24,266] [EI-Core] DEBUG - content >> "0" >> [2018-01-07 22:40:24,266] [EI-Core] D
[Dev] [EI] Issue on send an email with the attachment.
DEBUG - wire HTTP-Listener I/O dispatcher-1 << "Date: Mon, 08 Jan 2018 12:43:17 GMT[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "Transfer-Encoding: chunked[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "Transfer-Encoding: chunked[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "Connection: Keep-Alive[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "2a7[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "Connection: Keep-Alive[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">162senu...@wso2.com Altoblue800LeatherNoYesYesNoApprovedPink5T[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "0[\r][\n]" [2018-01-08 18:13:17,446] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-3 >> "[\r][\n]" [2018-01-08 18:13:17,445] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "2a7[\r][\n]" [2018-01-08 18:13:17,447] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">162senu...@wso2.com Altoblue800LeatherNoYesYesNoApprovedPink5T[\r][\n]" [2018-01-08 18:13:17,447] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "0[\r][\n]" [2018-01-08 18:13:17,447] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 << "[\r][\n]" [2018-01-08 18:13:17,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "HTTP/1.1 200 OK[\r][\n]" [2018-01-08 18:13:17,448] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "HTTP/1.1 200 OK[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "Content-Type: text/xml; charset=UTF-8[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Content-Type: text/xml; charset=UTF-8[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "Date: Mon, 08 Jan 2018 12:43:17 GMT[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Date: Mon, 08 Jan 2018 12:43:17 GMT[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "Transfer-Encoding: chunked[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Transfer-Encoding: chunked[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "Connection: Keep-Alive[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Connection: Keep-Alive[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "2a7[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "2a7[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">162senu...@wso2.com Altoblue800LeatherNoYesYesNoApprovedPink5T[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">162senu...@wso2.com Altoblue800LeatherNoYesYesNoApprovedPink5T[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "0[\r][\n]" [2018-01-08 18:13:17,449] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "0[\r][\n]" [2018-01-08 18:13:17,451] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-4 << "[\r][\n]" [2018-01-08 18:13:17,451] [EI-Core] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "[\r][\n]" [2018-01-08 18:13:17,456] [EI-Core] INFO - LogMediator Email_ID* = senu...@wso2.com [2018-01-08 18:13:17,456] [EI-Core] INFO - LogMediator ID = 162 [2018-01-08 18:13:19,930] [EI-Core] INFO - LogMediator To: http://localhost:8280/services/CARAPP, WSAction: , SOAPAction: , MessageID: urn:uuid:97D93C935F63092C7B137578033092885155037474, Direction: request, Envelope: http://schemas.xmlsoap.org/soap/envelope/";>http://ws.wso2.org/dataservice ">162senu...@wso2.com Altoblue800LeatherNoYesYesNoApprovedPink5T [2018-01-08 18:13:22,447] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "HTTP/1.1 200 OK[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Subject: Approved the Order[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Content-Type: text/html; charset=UTF-8[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Date: Mon, 08 Jan 2018 12:43:22 GMT[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Transfer-Encoding: chunked[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "Connection: keep-alive[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "87[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "http://ws.apache.org/commons/ns/payload";>Hello,Thank You for using our service.Your Order 162 is approved.[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "0[\r][\n]" [2018-01-08 18:13:22,448] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-3 << "[\r][\n]" [2018-01-08 18:13:30,553] [EI-Core] INFO - LogMediator TestLog01* = 11 [2018-01-08 18:13:30,558] [EI-Core] INFO - LogMediator TestLog02* = 12 Waiting for appropriate suggestions Thanks, *Senuwan Withana* Software Engineer - Support Team | WSO2 Email : senu...@wso2.com Mobile: 94773212853 Web: http://www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
