date:20171006

[Dev] Carbon Mediation 4.6.6 build failure due to unsatisfied dependancy

2017-10-06 Thread Dinesh J Weerakkody

Hi,

I tried to build the carbon mediation branch 4.6.6 and I got below error.

[ERROR] Failed to execute goal on project org.wso2.carbon.inbound.endpoint:
Could not resolve dependencies for project org.wso2.carbon.mediation:org.w
so2.carbon.inbound.endpoint:bundle:4.6.7-SNAPSHOT: Failed to collect
dependencies at org.apache.synapse:synapse-nhttp-transport:jar:2.1.7-wso2v7
-> or
g.apache.synapse:synapse-commons:jar:2.1.7-wso2v7: Failed to read artifact
descriptor for org.apache.synapse:synapse-commons:jar:2.1.7-wso2v7: Failure
 to find org.apache.synapse:Apache-Synapse:pom:2.1.7-wso2v8-SNAPSHOT in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
loca
l repository, resolution will not be reattempted until the update interval
of wso2-nexus has elapsed or updates are forced -> [Help 1]


>From where I can find the
* org.apache.synapse:Apache-Synapse:pom:2.1.7-wso2v8-SNAPSHOT*

It is not there in the WSO2 Nexus repo and I'm wondering why this is
happening. This happens even we try to create a mediator project in dev
studio and use the synapse version as 2.1.7-wso2v7.

Thanks

*Dinesh J. Weerakkody*
Senior Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 710 868676 | E : dine...@wso2.com | W : www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS][XACML] Introducing a Custom functionId

2017-10-06 Thread Johann Nallathamby

Will someone be able to shed some light on this issue sooner than later,
because Isuranga is trying to contribute a useful feature to WSO2 IS, which
is discussed in [1].

[1] [IAM] Restful API to Evaluate Permission Tree in IS

Regards,
Johann.

On Thu, Oct 5, 2017 at 7:22 PM, Johann Nallathamby  wrote:

> *[+Asela, IAM Team]*
>
> On Thu, Oct 5, 2017 at 7:20 PM, Isuranga Perera  > wrote:
>
>> Hi All,
>>
>> I'm trying to introduce a new XACML function in IS 5.3. This is the
>> procedure I followed so far.
>>
>>- Create the new class by extending the *FunctionBase* abstract class.
>>- Created a jar file and copied it into
>>*/repository/components/lib* directory
>>- Created "balana-config.xml" file with the following content and
>>copied it into */repository/conf/security*
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> *> defaultAttributeFactory="attr" defaultCombiningAlgFactory="comb"
>> defaultFunctionFactory="func">  > class="org.wso2.balana.finder.impl.CurrentEnvModule"/>
>>  > class="org.wso2.balana.finder.impl.SelectorModule"/>  > name="attr" useStandardDatatypes="true"/> > useStandardFunctions="true">  > class="org.wso2.xacml.permissions.PermissionEvalFunction"/>
>>> useStandardAlgorithms="true" />*
>>
>>- Set property
>>
>>*PDP.Balana.Config.Enable=true *in
>>*/repository/conf/identity/entitlement.properties*
>>
>> But when I tried to use that functionId in a policy it throws an
>> Exception saying functionId doesn't exist. It seems even my config file is
>> not parsed.
>> Appreciate any help.
>>
>> Best Regards,
>> Isuranga Perera
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Senior Lead Solutions Engineer
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Backend Returning 503 HTTP Status Code

2017-10-06 Thread Chamalee De Silva

Hi Francisco,

I tested this scenario.
To direct this response to the fault-sequence,
You can filter the response from the out-sequence of your proxy service,
and call the fault-sequence you want to invoke inside the out-equence using
a filter mediator.

As a simple example it is like this.

Then you can modify the error message as you want in the fault sequence
using a payload factory mediator.

Thanks,
Chamalee

On Thu, Oct 5, 2017 at 11:51 PM, Júnior  wrote:

> Hi,
>
> I have a ESB Proxy that calls a DSS endpoint. This DSS endpoint is under a
> Load Balancer. When the DSS server is down, the Load Balancer returns a 503
> HTTP Error.
>
> It seems strange to me that the flow is going to the outSequence and not
> to the faultSequence.
>
> Is this the expected behavior?
>
> Is it possible to make such case goes to the faultSequence?
>
> The code to send the request is like below:
>
> 
> 
> 
>
> Thanks,
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 debugger is not working for me .Please guide.

2017-10-06 Thread Nandika Jayawardana

Hi Aditya,

Please follow the instructions from the page [1]

[1] https://docs.wso2.com/display/ESB500/Debugging+Mediation.

It seems you are passing the wrong argument -Desb.debug=super, which should
be -Desb.debug=true.

Regards
Nandika

On Fri, Oct 6, 2017 at 4:53 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> WSO2 debugger is not working for me .Please guide.
>
>
> Please find attchment . For issue with screenshots.
>
>
>
> Debugger Steps :
>
> Following below document : https://nuwanpallewela.
> wordpress.com/2016/06/11/how-to-connect-with-wso2-esb-
> server-in-debug-mode/
> This section of above document : Starting WSO2 ESB Server with from ESB
> Tool and Connect to Server in Debug Mode 1.   Added server in eclipse :
> 2)   Double clicked generic server New_configuration(1) is created. 3)Went
> to Arguments tab and added Program arguments “-Desb.debug=super”.
>
> Clicked on Apply and close.
>
>
>
> 4)  Right clicked on server and pressed start .(also tried clicking
> here debug but server did not  start after long time also with similar
> error in logs , so I sttoped it)
>
>
>
> I get below error in logs :
>
> [2017-10-06 15:28:41,013] ERROR - SynapseDebugInterface Failed create
> communication channels to the external debugger
>
> *java.net .SocketTimeoutException*: Accept timed out
>
>at java.net.TwoStacksPlainSocketImpl.socketAccept(*Native Method*)
>
>at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
>
>at java.net.PlainSocketImpl.accept(Unknown Source)
>
>at java.net.ServerSocket.implAccept(Unknown Source)
>
>at java.net.ServerSocket.accept(Unknown Source)
>
>at org.apache.synapse.debug.SynapseDebugInterface.
> createDebugChannels(*SynapseDebugInterface.java:81*)
>
>at org.apache.synapse.debug.SynapseDebugInterface$
> AsynchronousChannelCreator.run(*SynapseDebugInterface.java:155*)
>
>at java.lang.Thread.run(Unknown Source)
>
> [2017-10-06 15:28:41,018] ERROR - ServiceBusInitializer Error while
> creating Synapse debug environment
>
> *java.net .SocketTimeoutException*: Accept timed out
>
>at java.net.TwoStacksPlainSocketImpl.socketAccept(*Native Method*)
>
>at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
>
>at java.net.PlainSocketImpl.accept(Unknown Source)
>
>at java.net.ServerSocket.implAccept(Unknown Source)
>
>at java.net.ServerSocket.accept(Unknown Source)
>
>at org.apache.synapse.debug.SynapseDebugInterface.
> createDebugChannels(*SynapseDebugInterface.java:81*)
>
>at org.apache.synapse.debug.SynapseDebugInterface$
> AsynchronousChannelCreator.run(*SynapseDebugInterface.java:155*)
>
>at java.lang.Thread.run(Unknown Source)
>
>
>
> Although thereafter the server starts :
>
> [2017-10-06 15:29:03,891]  INFO - JMXServerManager JMX Service URL  :
> service:jmx:rmi://localhost:1/jndi/rmi://localhost:/jmxrmi
>
> [2017-10-06 15:29:03,894]  INFO - StartupFinalizerServiceComponent
> Server   :  WSO2 Enterprise Service Bus-5.0.0
>
> [2017-10-06 15:29:03,896]  INFO - StartupFinalizerServiceComponent WSO2
> Carbon started in 112 sec
>
> [2017-10-06 15:29:04,218]  INFO - CarbonUIServiceComponent Mgt Console
> URL  : https://169.254.184.14:9443/carbon/
>
>
>
> 5)  Then I deployed my flow using eclipse server console.
>
> 6)  My flow got deployed successfully , as could be seen on wso2 console.
>
> 7)  Then I added breakpoints .
>
> 8)   Then I tried to hit the service from postman , but it did not
> stop at any breakpoint.
>
>
>
> Using :
>
>
>
> 1.   *Eclipse* Java EE IDE for Web Developers. Version: *Mars.2
> Release (4.5.2)*.Build id: 20160218-0600
>
> *2.   **Developer Studio :*
>
>
>
> *3.   * *wso2esb-5.0.0 server.*
>
>
>
> With Regards,
>
> Aditya
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 debugger is not working for me .Please guide.

2017-10-06 Thread Heshitha Hettihewa

Hi Aditya,

I guess you have missed some steps when connecting the debugger. You should
create a server and add the -Desb.debug=super parameter as you did.  Then
you should add debug configuration for ESB mediation debugger too. For that
you should go to debug configurations (Run -> Debug Configurations) and
locate to ESB Mediation Debugger and create a new configuration from that.


.[image: Inline image 1]


Then you should start the ESB server as usual (Not in debug mode. Right
click on server and start). Then it pauses at a point logging this message

"SynapseDebugInterface Listen on ports : Command 9005 - Event 9006"

In this point you have to connect the ESB Mediation debugger. To do that go
to Run -> Debug Configurations -> select ESB Mediation Debugger config you
created(New_configuration) and press debug. This should be done within a
usual time span of 1 min  otherwise server will give the same error saying
that the debugger is not connected. If you start ESB Mediation Debugger
within that time the server will start as usual with the debug capability.
Please follow the above steps too and let us know whether it fixes the
error.

Thanks,
Heshitha.

On Fri, Oct 6, 2017 at 4:53 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> WSO2 debugger is not working for me .Please guide.
>
>
> Please find attchment . For issue with screenshots.
>
>
>
> Debugger Steps :
>
> Following below document : https://nuwanpallewela.
> wordpress.com/2016/06/11/how-to-connect-with-wso2-esb-
> server-in-debug-mode/
> This section of above document : Starting WSO2 ESB Server with from ESB
> Tool and Connect to Server in Debug Mode 1.   Added server in eclipse :
> 2)   Double clicked generic server New_configuration(1) is created. 3)Went
> to Arguments tab and added Program arguments “-Desb.debug=super”.
>
> Clicked on Apply and close.
>
>
>
> 4)  Right clicked on server and pressed start .(also tried clicking
> here debug but server did not  start after long time also with similar
> error in logs , so I sttoped it)
>
>
>
> I get below error in logs :
>
> [2017-10-06 15:28:41,013] ERROR - SynapseDebugInterface Failed create
> communication channels to the external debugger
>
> *java.net .SocketTimeoutException*: Accept timed out
>
>at java.net.TwoStacksPlainSocketImpl.socketAccept(*Native Method*)
>
>at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
>
>at java.net.PlainSocketImpl.accept(Unknown Source)
>
>at java.net.ServerSocket.implAccept(Unknown Source)
>
>at java.net.ServerSocket.accept(Unknown Source)
>
>at org.apache.synapse.debug.SynapseDebugInterface.
> createDebugChannels(*SynapseDebugInterface.java:81*)
>
>at org.apache.synapse.debug.SynapseDebugInterface$
> AsynchronousChannelCreator.run(*SynapseDebugInterface.java:155*)
>
>at java.lang.Thread.run(Unknown Source)
>
> [2017-10-06 15:28:41,018] ERROR - ServiceBusInitializer Error while
> creating Synapse debug environment
>
> *java.net .SocketTimeoutException*: Accept timed out
>
>at java.net.TwoStacksPlainSocketImpl.socketAccept(*Native Method*)
>
>at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
>
>at java.net.PlainSocketImpl.accept(Unknown Source)
>
>at java.net.ServerSocket.implAccept(Unknown Source)
>
>at java.net.ServerSocket.accept(Unknown Source)
>
>at org.apache.synapse.debug.SynapseDebugInterface.
> createDebugChannels(*SynapseDebugInterface.java:81*)
>
>at org.apache.synapse.debug.SynapseDebugInterface$
> AsynchronousChannelCreator.run(*SynapseDebugInterface.java:155*)
>
>at java.lang.Thread.run(Unknown Source)
>
>
>
> Although thereafter the server starts :
>
> [2017-10-06 15:29:03,891]  INFO - JMXServerManager JMX Service URL  :
> service:jmx:rmi://localhost:1/jndi/rmi://localhost:/jmxrmi
>
> [2017-10-06 15:29:03,894]  INFO - StartupFinalizerServiceComponent
> Server   :  WSO2 Enterprise Service Bus-5.0.0
>
> [2017-10-06 15:29:03,896]  INFO - StartupFinalizerServiceComponent WSO2
> Carbon started in 112 sec
>
> [2017-10-06 15:29:04,218]  INFO - CarbonUIServiceComponent Mgt Console
> URL  : https://169.254.184.14:9443/carbon/
>
>
>
> 5)  Then I deployed my flow using eclipse server console.
>
> 6)  My flow got deployed successfully , as could be seen on wso2 console.
>
> 7)  Then I added breakpoints .
>
> 8)   Then I tried to hit the service from postman , but it did not
> stop at any breakpoint.
>
>
>
> Using :
>
>
>
> 1.   *Eclipse* Java EE IDE for Web Developers. Version: *Mars.2
> Release (4.5.2)*.Build id: 20160218-0600
>
> *2.   **Developer Studio :*
>
>
>
> *3.   * *wso2esb-5.0.0 server.*
>
>
>
> With Regards,
>
> Aditya
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Heshitha Hettihewa
*Software Engineer*
Mobile :

[Dev] [MB] Memory Leak in Message Delivery Content Cache

2017-10-06 Thread Wishmitha Mendis

Opened a issue[1] regarding the $subject.
[1] https://github.com/wso2/carbon-business-messaging/issues/592

Best Regards,
-- 

*Wishmitha Mendis*

*Intern - Software Engineering*
*WSO2*

*Mobile : +94 777577706*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 IoT Server 3.1.0-UPDATE4 Released!

2017-10-06 Thread Ruwan Yatawara

WSO2 IoT Server 3.1.0-UPDATE4


We are pleased to announce the latest update to WSO2 IoT Server 3.1.0

WSO2 IoT Server is one of the most adaptive Apache licensed open source IoT
platforms available today. It provides best of breed technologies for
device manufacturers to develop connected products as well as rich
integration and smart analytics capabilities for system integrators to
adopt devices into systems they build.

These capabilities involve device management, smart analytics, API and app
management for devices, transport extensions for MQTT, XMPP and many more.
What's new in WSO2 IoTS 3.1.0 Update 4

Bug Fixes : A list of bug fixes shipped with this release can be found here

Documentation

Documentations: WSO2 IoT Server Documentation

Known Issues

The known set of issues in this version can be found here

Engaging with CommunityMailing Lists

Join our mailing list and correspondence with the developers directly.

Developer list: dev@wso2.org | Subscribe
 | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 IoT Server through WSO2 IoT GIT Issues
.
Discussion Forums

We encourage you to use stackoverflow

to
engage with developers as well as other users.

For more information about WSO2 IoT Server, please see
http://wso2.com/products/iot-server or visit the WSO2 Oxygen Tank
 developer portal for additional resources.

Thank you for your interest in WSO2 IoT Server.

*The WSO2 IoT Server Team*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon Mediation 4.6.6 build failure due to unsatisfied dependancy

Re: [Dev] [IS][XACML] Introducing a Custom functionId

Re: [Dev] WSO2 Backend Returning 503 HTTP Status Code

Re: [Dev] WSO2 debugger is not working for me .Please guide.

Re: [Dev] WSO2 debugger is not working for me .Please guide.

[Dev] [MB] Memory Leak in Message Delivery Content Cache

[Dev] WSO2 IoT Server 3.1.0-UPDATE4 Released!

7 matches

Site Navigation

Mail list logo

Footer information