[ESBJAVA-4629] If back end service goes down during ESB sends the request, flow will get dropped Created: 23/May/16  Updated: 24/May/16

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

Type: Bug Priority: Normal
Reporter: Rajith Vitharana Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File errorHandling.diff    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

If back end service goes down while ESB send a message to back end(that is when back end goes down while ESB flow is in TargetHandler connected method) then that message flow will behave in unpredictable way.



 Comments   
Comment by Rajith Vitharana [ 23/May/16 ]

Fix is attached herewith

Comment by Rajith Vitharana [ 24/May/16 ]

pull request for the fix - https://github.com/wso2/wso2-synapse/pull/557





[ESBJAVA-4628] Log Messages when they have Special Characters Created: 23/May/16  Updated: 23/May/16

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

Type: Improvement Priority: Normal
Reporter: Nadeeshaan Gunasinghe Assignee: Chanaka Fernando
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   

When we try to log a full message when there are special characters in the message, ESB throws the following exception

ERROR - LogMediator Could not build full log message: Can not serialize OM Element Envelope






[ESBJAVA-4627] if deploy the capp which refer unavaliable jar throw the exception. Created: 20/May/16  Updated: 20/May/16

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

Type: Bug Priority: Normal
Reporter: Srisunmugaraja Paraparan Assignee: Chanaka Fernando
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   

If a proxy service using groovy library and the library is not in the server, then this throw the exception in the capp deployment time and servere bacame hang.



 Comments   
Comment by Krishan Malan [ 20/May/16 ]

The similar issue occurs for the following use case.

1) First place a cApp which uses a class mediator by it's synapse artifacts at the deployment/server/carbonapps folder.
2) Start the ESB server.
3) If the Synapse artifacts deployer unable to resolve the class, then ESB hangs without any ERROR. Even we cannot access the management console.

You can reproduce this scenario easily by removing the class mediator from the ESB and deploy the cApp which having synapse artifacts like proxy which use the relevant class mediator.





[ESBJAVA-4626] Should # be encoded as a special character with REST_URL_POSTFIX Created: 19/May/16  Updated: 19/May/16

Status: Open
Project: WSO2 ESB
Component/s: Properties Management
Affects Version/s: 5.0.0 - Alpha
Fix Version/s: None

Type: Bug Priority: High
Reporter: Chathurika De Silva Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

pack: Alpha 19.05.2016
OS: Ubuntu 14.04


Severity: Major
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   

Sequence

<sequence name="my_seq_1" xmlns="http://ws.apache.org/ns/synapse">
    <property name="REST_URL_POSTFIX" scope="axis2" type="STRING" value="/users name/test new#"/>
    <send>
        <endpoint>
            <http uri-template="http://192.168.1.5:9793/SampleRestService/restservice/TestUserService"/>
        </endpoint>
    </send>
    <log level="full"/>
</sequence>

Output when executed

wire HTTP-Sender I/O dispatcher-6 << "GET /SampleRestService/restservice/TestUserService/users%20name/test%20new%23 HTTP/1.1[\r][\n]"
[2016-05-19 16:44:08,597] DEBUG - wire HTTP-Sender I/O dispatcher-6 << "Content-Type: application/xml[\r][\n]"
[2016-05-19 16:44:08,597] DEBUG - wire HTTP-Sender I/O dispatcher-6 << "Host: 192.168.1.5:9793[\r][\n]"
[2016-05-19 16:44:08,597] DEBUG - wire HTTP-Sender I/O dispatcher-6 << "Connection: Keep-Alive[\r][\n]"
[2016-05-19 16:44:08,598] DEBUG - wire HTTP-Sender I/O dispatcher-6 << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"

The test new# is encoded as test%20new%23. But when tested with http://www.example.com/test%20new# is given, here the # is not encoded. With ESB encoding this, is it the correct behavior?






[ESBJAVA-4625] [ESB500][JMS] Logs show incorrect value Created: 19/May/16  Updated: 19/May/16  Resolved: 19/May/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 5.0.0 - Alpha
Fix Version/s: 5.0.0-Beta

Type: Bug Priority: High
Reporter: Dilshani Subasinghe Assignee: Nuwan Wimalasekara
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.7
Packs : ESB 5.0.0 Alpha
ESB Setup: Standalone
JMS Broker: MB (3.1.0)


Severity: Major
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   

Preconditions:
1. ESB should be configured with MB.
Configure JMS parameters as follows in axis2.xml

  <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
 <parameter name="myTopicConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter>
 <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
<parameter name ="transport.jms.DestinationType" locked="false">topic</parameter>
<parameter name ="transport.jms.InitialReconnectDuration" locked="false">10000</parameter>
<parameter name ="transport.jms.MaxReconnectDuration" locked="false">30000</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter>
 <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
<parameter name ="transport.jms.InitialReconnectDuration" locked="false">10000</parameter>
<parameter name ="transport.jms.MaxReconnectDuration" locked="false">30000</parameter>
        </parameter>

        <parameter name="default" locked="false">
<parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter>
 <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
<parameter name ="transport.jms.DestinationType" locked="false">topic</parameter>
<parameter name ="transport.jms.InitialReconnectDuration" locked="false">10000</parameter>
<parameter name ="transport.jms.MaxReconnectDuration" locked="false">30000</parameter>
        </parameter>

    </transportReceiver>

2. MB should be up and running
3.ESB should be up and running

Steps to reproduce:
1. Create ESB proxy with jms transport.

<proxy name="TopicProxy" startOnLoad="true" transports="https http jms">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <send>
                    <endpoint>
                        <address uri="jms:/MyTopic?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory&amp;java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&amp;java.naming.provider.url=repository/conf/jndi.properties&amp;transport.jms.DestinationType=topic"/>
                    </endpoint>
                </send>
            </inSequence>
        </target>
    </proxy>

2. Shut down jms broker

Expected result:

  • Reconnection time duration only increase upto "MaxReconnectDuration"

Actual result:

  • Logs will indicate increasing of reconnection time duration.

Note: Refer mail thread "[Dev][ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor" "



 Comments   
Comment by Nuwan Wimalasekara [ 19/May/16 ]

Fixed in https://github.com/wso2/wso2-axis2-transports/pull/79





[ESBJAVA-4624] 'Enable/Disable Statistics and tracing options are not there for endpoints and sequences that are saved in registry. Created: 18/May/16  Updated: 20/May/16

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

Type: Improvement Priority: High
Reporter: sewmini jayaweera Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Packs:

  • wso2esb-5.0.0-SNAPSHOT.zip build#1051
  • wso2analytics-esb-1.0.0-SNAPSHOT build #88
    Browser: chrome 50.0.2661.94 (64-bit)
    OS: version 10.11.3
    Database: H2
    JDK: "1.7.0_71"
    Other configurations: Statistics and tracing related configs

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

 Description   

Observation

  • Endpoints saved in registry doesn't contain a UI level configuration to enable/disabled statistics where endpoints saved as a synapse configuration doesn't.
  • Sequence saved in Registry doesn't contain UI configurations to enable/disable statistics nor tracing where as the sequences saved as synapse configs has.





[ESBJAVA-4623] Kerberos security doesn't work when applied the policy via source view Created: 18/May/16  Updated: 18/May/16  Resolved: 18/May/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: FUTURE, 4.9.0

Type: Bug Priority: Normal
Reporter: Balasubramaniyam Senduran Assignee: Balasubramaniyam Senduran
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   

Since the password is taken from the service meta file and when applying the policy via source view, there is no way to enter the password.



 Comments   
Comment by Balasubramaniyam Senduran [ 18/May/16 ]

Since the proxy can be secured only via developer studio in ESB version 490 or above. the password is stored in the policy file itself.





[ESBJAVA-4622] Session ID is getting printed in 'INFO' logs every time when user logs into analytics dashboard Created: 18/May/16  Updated: 18/May/16  Resolved: 18/May/16

Status: Resolved
Project: WSO2 ESB
Component/s: Analytics
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: sewmini jayaweera Assignee: Chanaka Fernando
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Packs:

  • wso2esb-5.0.0-SNAPSHOT.zip build#1051
  • wso2analytics-esb-1.0.0-SNAPSHOT build #88
    Browser: chrome 50.0.2661.94 (64-bit)
    OS: version 10.11.3
    Database: H2
    JDK: "1.7.0_71"
    Other configurations: Statistics and tracing related configs

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

 Description   

Observation

Every time when user logs into analytics dashboard session ID gets printed in INFO log [1] of Analytics server log.

Expected result

1. Isn't there a security threat (hijacking) by printing the session ID in the log?
2. This should get removed from the INFO level

[1]. Log

INFO {JAGGERY.modules.api:js} -  Session cookie JSESSIONID=F28D6CBEFF42EDFA1F34F3D8749F1DE4; Path=/; Secure=null; HttpOnly=null


 Comments   
Comment by sewmini jayaweera [ 18/May/16 ]

Created the Jira in ESB analytics project
https://wso2.org/jira/browse/ANLYESB-80





[ESBJAVA-4621] "Transport error: 401 Error: Unauthorized" error when saving username password with non blocking local transport enabled Created: 17/May/16  Updated: 19/May/16

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

Type: Bug Priority: Normal
Reporter: Viraj Rajaguru Assignee: Viraj Rajaguru
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
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

 Description   

Reproduce the issue in a fresh ESB pack 4.8.1 using the below steps.

1) Modified the cipher-text.properties and commented all the records.
2) Run the sh ciphertool.sh -Dconfigure
3) Then went to Secure Vault Tool -> Manage Passwords and checked whether working fine.
4) Then enabled the non blocking local transport using [1].
5) Went to Secure Vault Tool -> Manage Passwords and added a username and password - when saving got the
"Transport error: 401 Error: Unauthorized".

[1] https://docs.wso2.com/display/ESB481/Local+Transport






Generated at Tue May 24 11:30:06 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.