[ESBJAVA-3101] Local entry is not working when modifying it using source view Created: 19/Apr/14  Updated: 19/Apr/14

Status: Open
Project: WSO2 ESB
Component/s: Local Entries
Affects Version/s: 4.8.1
Fix Version/s: 4.9.0

Type: Bug Priority: High
Reporter: reka thirunavukkarasu Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   
The problem is when we create an local entry using UI, it will append a description tag to the local entry. So, in the source view, it will look like:

<localEntry key="test.app">test<description/>
</localEntry>

Then if we use source view and modify it, the actual element which paased to synapse is:
<localEntry key="test.app">test<description></description>\n
</localEntry>

When evaluating value by removing description tag:
<localEntry key="test.app">test\n
</localEntry>

Finally, "\n" is there in all the local entry values. So, the HTTP endpoint properties which uses this local entry got failed because of "\n" in the properties. Hence Malformed URL is generated as the URL is http://localhost\n:8280\n/services/test\n




[ESBJAVA-3100] Tenant domain has not been set in CarbonContext exception received when invoking a secured (Non-repudiation) proxy service in WSO2 ESB Created: 17/Apr/14  Updated: 18/Apr/14

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Shibu Gope Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Centos 6.3, java 7,

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   
Below is the proxy code:

<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="ApplicationProxy"
       transports="https"
       statistics="enable"
       trace="disable"
       startOnLoad="true">
   <target faultSequence="fault" endpoint="ApplicationServiceHttpEP">
      <inSequence>
         <sequence key="ApplicationProxyInFlow"/>
      </inSequence>
      <outSequence>
         <send/>
         <log level="full"/>
      </outSequence>
   </target>
   <publishWSDL uri="http://pregistry.skopos.me:9773/registry/resource/_system/governance/phases/design/wsdls/skopos/wsdl/application/Application.wsdl"/>
   <parameter name="disableREST">true</parameter>
   <enableSec/>
   <policy key="conf:/repository/axis2/service-groups/ApplicationProxy/services/ApplicationProxy/policies/SigOnly"/>
   <description/>
</proxy>

Below is the sequence called:

<sequence xmlns="http://ws.apache.org/ns/synapse" name="ApplicationProxyInFlow" onError="fault">
   <log level="full" separator=","></log>
   <validate>
      <schema key="gov:/schemas/skopos/bods/application/1.13.0/ApplicationBod.xsd"></schema>
      <resource location="../../resources/common/1.13.0/Components.xsd" key="gov:/schemas/skopos/resources/common/1.13.0/Components.xsd"></resource>
      <resource location="../dealer/1.13.0/Dealer.xsd" key="gov:/schemas/skopos/resources/nouns/dealer/1.13.0/Dealer.xsd"></resource>
      <resource location="./CodeLists.xsd" key="gov:/schemas/skopos/resources/common/1.13.0/CodeLists.xsd"></resource>
      <resource location="../../resources/nouns/decision/1.13.0/Decision.xsd" key="gov:/schemas/skopos/resources/nouns/decision/1.13.0/Decision.xsd"></resource>
      <resource location="../../resources/nouns/application/1.13.0/Application.xsd" key="gov:/schemas/skopos/resources/nouns/application/1.13.0/Application.xsd"></resource>
      <resource location="../borrower/1.13.0/Borrower.xsd" key="gov:/schemas/skopos/resources/nouns/borrower/1.13.0/Borrower.xsd"></resource>
      <resource location="../bank/1.13.0/Bank.xsd" key="gov:/schemas/skopos/resources/nouns/bank/1.13.0/Bank.xsd"></resource>
      <resource location="../vehicle/1.13.0/Vehicle.xsd" key="gov:/schemas/skopos/resources/nouns/vehicle/1.13.0/Vehicle.xsd"></resource>
      <resource location="../employee/1.13.0/Employee.xsd" key="gov:/schemas/skopos/resources/nouns/employee/1.13.0/Employee.xsd"></resource>
      <on-fail>
         <log level="custom" category="ERROR">
            <property xmlns:ns="http://org.apache.synapse/xsd" name="ERROR_CODE" expression="get-property('ERROR_CODE')"></property>
            <property xmlns:ns="http://org.apache.synapse/xsd" name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"></property>
            <property xmlns:app="http://skopos/resources/nouns/application" xmlns:ns="http://org.apache.synapse/xsd" xmlns:cmn="http://skopos/resources/common" name="ERROR_APP_ID" expression="//*/*/app:Application/cmn:ID[@Source='SKOPOS']"></property>
            <property xmlns:ns="http://org.apache.synapse/xsd" name="ERROR_XML" expression="/"></property>
         </log>
         <makefault version="soap11">
            <code xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/" value="soap11Env:Client"></code>
            <reason value="Request message is invalid"></reason>
            <role></role>
            <detail xmlns:ns="http://org.apache.synapse/xsd" expression="get-property('ERROR_MESSAGE')"></detail>
         </makefault>
         <property name="RESPONSE" value="true"></property>
         <header name="To" action="remove"></header>
      </on-fail>
   </validate>
</sequence>

Below is the exception stack trace:

Language="en_US">Acknowledged</Description></ResponseStatus></ApplicationArea></ns8:AcknowledgeApplication></soap:Body></soap:Envelope> Unexpected error sending message back
at org.apache.synapse.core.axis2.Axis2Sender.handleException(Axis2Sender.java:172)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:166)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:321)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:94)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:268)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:305)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.axis2.AxisFault: Error in getting password for user : "test"
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
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.send(AxisEngine.java:426)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:163)
... 14 more
Caused by: org.apache.rampart.RampartException: Error in getting password for user : "test"
at org.apache.rampart.builder.BindingBuilder.getSignatureBuilder(BindingBuilder.java:332)
at org.apache.rampart.builder.BindingBuilder.getSignatureBuilder(BindingBuilder.java:265)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:761)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:457)
at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
... 19 more
Caused by: javax.security.auth.callback.UnsupportedCallbackException: Tenant domain has not been set in CarbonContext
at org.wso2.carbon.security.util.ServicePasswordCallbackHandler.handle(ServicePasswordCallbackHandler.java:152)
at org.apache.rampart.builder.BindingBuilder.getSignatureBuilder(BindingBuilder.java:318)
... 25 more

 Comments   
Comment by Shibu Gope [ 18/Apr/14 ]
After turning on mediation tracer, we noticed that this exception is thrown after a message is received from the backend service in the OutSequence and about to leave the ESB. The client never receives the response message and times out.




[ESBJAVA-3099] ESB sample 60 is not working as expected Created: 17/Apr/14  Updated: 17/Apr/14  Resolved: 17/Apr/14

Status: Resolved
Project: WSO2 ESB
Component/s: Endpoints Management, Samples
Affects Version/s: 4.8.1
Fix Version/s: 4.9.0

Type: Bug Priority: Highest
Reporter: Malaka Silva Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   
I am running sample60, and using <recipientlist> inside the endpoint element. If I shutdown one of my endpoints, ESB throws an error.

[2014-04-17 13:27:55,625] ERROR - NativeWorkerPool Uncaught exception
java.lang.NullPointerException
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:114)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:321)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:94)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:85)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
at org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:640)
at org.apache.synapse.endpoints.AbstractEndpoint.informFailure(AbstractEndpoint.java:605)
at org.apache.synapse.endpoints.RecipientListEndpoint.onChildEndpointFail(RecipientListEndpoint.java:333)
at org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:638)
at org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:475)
at org.apache.synapse.endpoints.AddressEndpoint.onFault(AddressEndpoint.java:43)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:252)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
at org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:134)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


 Comments   
Comment by Malaka Silva [ 17/Apr/14 ]
https://github.com/wso2-dev/wso2-synapse/pull/10




[ESBJAVA-3098] WSO2 ESB unable to send a scheduled message to activemq broker Created: 17/Apr/14  Updated: 17/Apr/14

Status: Open
Project: WSO2 ESB
Component/s: Properties Management, Proxy Services Management
Affects Version/s: 4.7.0, 4.8.0 , 4.8.1
Fix Version/s: None

Type: Bug Priority: High
Reporter: faisal shaik Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB, passthru-transport
Remaining Estimate: 3 minutes
Time Spent: Not Specified
Original Estimate: 3 minutes
Environment: Ubuntu,wso2esb4.8.0,activemq5.8.0

Attachments: XML File JMSSCHEDULE.xml    
Severity: Critical
Estimated Complexity: Advanced
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: Yes
Affects Docs:
Yes

 Description   
Hi would like send a message to activemq based on schedule time like
below explanatiion
http://www.devteam.gr/blog/?p=265&lang=en
please go through that
 0 down vote favorite

I wish to raise a alert to user.User setting his ETA when he registered. so if he is unable to reach in time. i wish to raise a alert to user how would i achieve. for this i refereed TASK SCHEDULING in wso2esb but its static request and static time define but my time is different for every user how would i do it dynamic. Even i tried in ACTIVE MQ scheduling but no use any help for this.
for that i set a property like this

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="JMSSCHEDULE"
       transports="https http"
       startOnLoad="true"
       trace="disable">
   <description/>
   <target>
      <inSequence>
         <property name="OUT_ONLY" value="true"/>
         <log level="full"/>
         <property name="messageType" value="application/json" scope="axis2"/>
         <property name="OUT_ONLY" value="true"/>
         <property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
         <send>
            <endpoint>
               <address uri="jms:/JMSSCHEDULE?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://127.0.0.1:61616&amp;transport.jms.DestinationType=queue"/>
               <property name="AMQ_SCHEDULED_DELAY" value="30000000000" scope="transport"/>
            </endpoint>
         </send>
      </inSequence>
      <outSequence/>
   </target>
   <parameter name="AMQ_SCHEDULED_DELAY">300000</parameter>
</proxy

but no use message producing quickly happening
how would i achive this






[ESBJAVA-3097] WS-Addressing Not working properly when invoke RESTful Services Created: 16/Apr/14  Updated: 16/Apr/14

Status: Open
Project: WSO2 ESB
Component/s: Core Engine
Affects Version/s: 4.8.1
Fix Version/s: None

Type: New Feature Priority: Highest
Reporter: dushan abeyruwan Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: esb,
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Blocker
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: Yes

 Description   
When WS-Addressing is enabled, if no explicit action is defined in the WSDL, the client sends an implicit wsa:Action header using the following formats:

Input message action: targetNamespace/portTypeName/inputName

Output message action: targetNamespace/portTypeName/outputName

Fault message action: targetNamespace/portTypeName/operationName/Fault/FaultName

targetNamespace/portTypeName/[inputName | outputName]

Ideally, as describes above the when addressing enable and when publish WSDL enables, the response path should automatically maps the correlated Action headers.
  Currently this feature not possible with WSO2 ESB 4.8.1




[ESBJAVA-3096] Incorrect data displaying in API edit screen when modify multiple APIs within the same session Created: 16/Apr/14  Updated: 16/Apr/14

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Patch Priority: Normal
Reporter: Anusha Ruwanpathirana Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Estimated Complexity: Moderate
Test cases added: No

 Description   
Reproduce steps:

Go to a ESB API edit screen , then view source view, again go to API list without having any action, next go to another API edit screen, it displays correct request URL in address bar, but loads with the previous API data. As well as, endpoint displays previous API endpoint data.




Generated at Sun Apr 20 22:09:35 IST 2014 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.