[ESBJAVA-4774] Sequence name text doesn't prevent of performing an XSS attack Created: 20/Jul/16  Updated: 20/Jul/16

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

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

It is able to create a sequence named

<script>alert(123)</script>






[ESBJAVA-4779] [Data Mapper][Mediation Debugger] Property operator does not take updated value of property when value changed while debugging Created: 04/Jul/16  Updated: 22/Jul/16

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

Type: Bug Priority: Highest
Reporter: Chathurika De Silva Assignee: Nuwan Pallewela
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Ubuntu 14.04
JDK: Oracle 1.8.0
Pack: Pre-RC2 (23.06.2016)


Attachments: File PRERCCAR_1_1.0.0.car     PNG File PropertyDebugger_2.png     PNG File PropertyDebugger_3.png     PNG File PropertyDebugger_4.png     PNG File PropertyDebugging_1.png     PNG File PropertyMediationDebugging.png    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

I have the following property configured in the sequence

 <property description="" name="test_property" scope="default" type="STRING" value="true"/>

While debugging I am changing the value to false as shown in the attached image. Even-though the value is changed, after being processed by data mapper the mapped value is shown as true (please see the image)

Wire logs

[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Host: 172.17.0.1:8280[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Connection: keep-alive[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Content-Length: 162[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Cache-Control: no-cache[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Content-Type: application/json[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Postman-Token: b9fc61eb-4e6f-76d2-043b-3750858f094b[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Accept: */*[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Accept-Encoding: gzip, deflate[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "Accept-Language: en-US,en;q=0.8[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "[\r][\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "{[\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "  "patientDetails": {[\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "    "patient": {[\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "      "name": "test",[\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "      "address": "test",[\n]"
[2016-07-04 13:54:56,105] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "      "dateOfBirth": "test",[\n]"
[2016-07-04 13:54:56,106] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "      "age": 0,[\n]"
[2016-07-04 13:54:56,106] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "      "opd": true[\n]"
[2016-07-04 13:54:56,106] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "    }[\n]"
[2016-07-04 13:54:56,106] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "  }[\n]"
[2016-07-04 13:54:56,106] DEBUG - wire HTTP-Listener I/O dispatcher-9 >> "}"
[2016-07-04 13:54:56,106] DEBUG - wire source request wire Log added to the log holder, phase - SOURCE_REQUEST_READY
[2016-07-04 13:54:56,108] DEBUG - headers http-incoming-1 >> POST /prercapi2 HTTP/1.1
[2016-07-04 13:54:56,108] DEBUG - headers http-incoming-1 >> Host: 172.17.0.1:8280
[2016-07-04 13:54:56,108] DEBUG - headers http-incoming-1 >> Connection: keep-alive
[2016-07-04 13:54:56,108] DEBUG - headers http-incoming-1 >> Content-Length: 162
[2016-07-04 13:54:56,108] DEBUG - headers http-incoming-1 >> Cache-Control: no-cache
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Content-Type: application/json
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Postman-Token: b9fc61eb-4e6f-76d2-043b-3750858f094b
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Accept: */*
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Accept-Encoding: gzip, deflate
[2016-07-04 13:54:56,109] DEBUG - headers http-incoming-1 >> Accept-Language: en-US,en;q=0.8
[2016-07-04 13:55:40,258]  INFO - LogMediator To: /prercapi2, MessageID: urn:uuid:9e142874-d48a-4a16-aa93-0cc3c575c028, Direction: request, Payload: {
  "patientDetails": {
    "patient": {
      "name": "test",
      "address": "test",
      "dateOfBirth": "test",
      "age": 0,
      "opd": true
    }
  }
}
[2016-07-04 13:56:28,934]  INFO - LogMediator To: /prercapi2, MessageID: urn:uuid:9e142874-d48a-4a16-aa93-0cc3c575c028, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><patientDetails><patient><age>0</age><dateOfBirth>test</dateOfBirth><address>test</address><name>test</name><opd>true</opd></patient></patientDetails></soapenv:Body></soapenv:Envelope>
[2016-07-04 13:56:33,914] DEBUG - headers http-incoming-1 << HTTP/1.1 200 OK
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Accept: */*
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Cache-Control: no-cache
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Host: 172.17.0.1:8280
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Postman-Token: b9fc61eb-4e6f-76d2-043b-3750858f094b
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Accept-Encoding: gzip, deflate
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Accept-Language: en-US,en;q=0.8
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Content-Type: application/xml; charset=UTF-8
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Date: Mon, 04 Jul 2016 08:26:33 GMT
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Transfer-Encoding: chunked
[2016-07-04 13:56:33,915] DEBUG - headers http-incoming-1 << Connection: keep-alive
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "HTTP/1.1 200 OK[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Accept: */*[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Cache-Control: no-cache[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Host: 172.17.0.1:8280[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Postman-Token: b9fc61eb-4e6f-76d2-043b-3750858f094b[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Accept-Encoding: gzip, deflate[\r][\n]"
[2016-07-04 13:56:33,919] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Accept-Language: en-US,en;q=0.8[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Date: Mon, 04 Jul 2016 08:26:33 GMT[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Transfer-Encoding: chunked[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "Connection: keep-alive[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "96[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "<patientDetails><patient><age>0</age><dateOfBirth>test</dateOfBirth><address>test</address><name>test</name><opd>true</opd></patient></patientDetails>[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "0[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire HTTP-Listener I/O dispatcher-9 << "[\r][\n]"
[2016-07-04 13:56:33,920] DEBUG - wire source response wire Log added to the log holder, phase - SOURCE_RESPONSE_READY


 Comments   
Comment by Nuwan Pallewela [ 04/Jul/16 ]

Hi Chathurika,

Can you please describe the steps you exactly did to reproduce this and artifacts files and car file used?

Thanks,
Nuwan

Comment by Chathurika De Silva [ 04/Jul/16 ]

Hi Nuwan

Exact steps are similar to what I have given before. To elaborate, I change the property value while debugging using the variable view in Debugging mode. So when the data mapper is reached, the value of the property is actually false, but the outcome of the datamapper is true (which is the original value). Please have a look at the attached images that illustrate the process.

CAR attached as requested: relevant sequence: data_map_seq_8 and API: PRERCAPI2

Best Regards
Erandi





[ESBJAVA-4784] Event publisher and CSRF warnings observed at server startup in Windows Created: 23/Jul/16  Updated: 24/Jul/16

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

Type: Bug Priority: Highest
Reporter: Chathurika De Silva Assignee: Buddhima Wijeweera
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS:Windows 10
JDK: Oracle 1.8.0


Attachments: Text File wso2carbon.log    
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   

Errors related to EventPublisher and CSRF were observed in Windows at server startup and first login respectively. Carbon log attached herewith

At server startup

TID: [-1234] [] [2016-07-23 22:13:41,073] ERROR {org.wso2.carbon.event.publisher.core.EventPublisherDeployer} -  Error, Event Publisher not deployed and in inactive state, Error while deleting the Event Publisher : Illegal char <:> at index 2: /E:/erandi/erandi/wso2esb-5.0.0-BETA2/bin/../repository/deployment/server/\eventpublishers {org.wso2.carbon.event.publisher.core.EventPublisherDeployer}
org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException: Error while deleting the Event Publisher : Illegal char <:> at index 2: /E:/erandi/erandi/wso2esb-5.0.0-BETA2/bin/../repository/deployment/server/\eventpublishers
	at org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
	at org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
	at org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
	at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
	at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
	at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
	at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
	at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
	at org.apache.synapse.Axis2SynapseController.deployMediatorExtensions(Axis2SynapseController.java:743)
	at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:388)
	at org.apache.synapse.ServerManager.start(ServerManager.java:183)
	at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:452)
	at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:196)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)

At login

TID: [-1234] [] [2016-07-23 22:22:44,501]  WARN {org.owasp.csrfguard.log.JavaLogger} -  potential cross-site request forgery (CSRF) attack thwarted (user:<anonymous>, ip:192.168.1.3, method:HEAD, uri:/carbon/admin/login.jsp, error:required token is missing from the request) {org.owasp.csrfguard.log.JavaLogger}


 Comments   
Comment by Buddhima Wijeweera [ 23/Jul/16 ]

Hi,

Seems this is fixed through : https://github.com/wso2/carbon-analytics-common/commit/7e9525881afcb4778b6f1cbb60af1181d6a5da45

So need to upgrade carbon-analytics-common dependency to obtain the change.

Thanks,
Buddhima





[ESBJAVA-4760] When response has 204 status code with disable chunking false, the response gets dropped Created: 15/Jul/16  Updated: 25/Jul/16

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

Type: Bug Priority: Highest
Reporter: viraj senevirathne Assignee: Rajith Vitharana
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   

We can oberve the following error message in the console log.
TID: [0] [ESB] [2016-07-11 13:48:25,968] ERROR

{org.apache.synapse.transport.passthru.SourceHandler} - Content-Length header already present {org.apache.synapse.transport.passthru.SourceHandler}

350865 org.apache.http.ProtocolException: Content-Length header already present
350866 at org.apache.http.protocol.ResponseContent.process(ResponseContent.java:102)
350867 at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:117)
350868 at org.apache.synapse.transport.passthru.SourceResponse.start(SourceResponse.java:182)
350869 at org.apache.synapse.transport.passthru.SourceHandler.responseReady(SourceHandler.java:195)
350870 at org.apache.http.impl.nio.DefaultNHttpServerConnection.produceOutput(DefaultNHttpServerConnection.java:247)
350871 at org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.produceOutput(LoggingNHttpServerConnection.java:114)
350872 at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:87)
350873 at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:39)
350874 at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:148)
350875 at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:181)
350876 at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:346)
350877 at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
350878 at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
350879 at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
350880 at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
350881 at java.lang.Thread.run(Thread.java:745)






[ESBJAVA-4789] Iterator Mediator hangs if the expression has 0 elements to iterate Created: 26/Jul/16  Updated: 26/Jul/16

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

Type: Bug Priority: Highest
Reporter: dushan abeyruwan Assignee: Rajith Vitharana
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   

Payload

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:getQuotes>
         
      </ser:getQuotes>
   </soapenv:Body>
</soapenv:Envelope>
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="IteratorProxy"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <log level="full">
            <property name="Start Iterating" value="so#######"/>
         </log>
         <iterate xmlns:m1="http://services.samples"
                  xmlns:m2="http://services.samples/xsd"
                  id="buildQuintSource_iterator"
                  expression="//m1:getQuotes/m1:getQuote"
                  sequential="true">
            <target>
               <sequence>
                  <log level="custom">
                     <property name="buildQuintSource.iterate" value="START#######"/>
                     <property name="transactionID" expression="get-property('transactionID')"/>
                     <property name="sourceMessageID" expression="get-property('sourceMessageID')"/>
                     <property name="proxyMessageID" expression="get-property('proxyMessageID')"/>
                  </log>
                  <loopback/>
               </sequence>
            </target>
         </iterate>
         <log level="custom">
            <property name="we are here then right" value="so#######"/>
         </log>
      </inSequence>
      <outSequence>
         <property name="outMessageID"
                   expression="get-property('MessageID')"
                   scope="default"/>
         <log level="full">
            <property name="buildQuintSource" value="out"/>
            <property name="transactionID" expression="get-property('transactionID')"/>
            <property name="sourceMessageID" expression="get-property('sourceMessageID')"/>
            <property name="proxyMessageID" expression="get-property('proxyMessageID')"/>
            <property name="outMessageID" expression="get-property('outMessageID')"/>
         </log>
         <property name="channel" scope="default">
            <channel xmlns=""/>
         </property>
         <aggregate id="buildQuintSource_iterator">
            <completeCondition timeout="10">
               <messageCount min="-1" max="-1"/>
            </completeCondition>
            <onComplete xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                        xmlns:ns="http://org.apache.synapse/xsd"
                        xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                        expression="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"
                        enclosingElementProperty="channel">
               <property name="aggregatorID"
                         expression="get-property('MessageID')"
                         scope="default"/>
               <log level="custom">
                  <property name="buildQuintSource" value="AGGREGATE"/>
                  <property name="transactionID" expression="get-property('transactionID')"/>
                  <property name="sourceMessageID" expression="get-property('sourceMessageID')"/>
                  <property name="proxyMessageID" expression="get-property('proxyMessageID')"/>
                  <property name="outMessageID" expression="get-property('outMessageID')"/>
                  <property name="aggregatorID" expression="get-property('aggregatorID')"/>
               </log>
               <payloadFactory media-type="xml">
                  <format>
                     <rss xmlns="">$1</rss>
                  </format>
                  <args>
                     <arg evaluator="xml" expression="$body/channel"/>
                  </args>
               </payloadFactory>
               <log level="custom">
                  <property name="buildQuintSource" value="END"/>
                  <property name="transactionID" expression="get-property('transactionID')"/>
                  <property name="sourceMessageID" expression="get-property('sourceMessageID')"/>
                  <property name="proxyMessageID" expression="get-property('proxyMessageID')"/>
                  <property name="outMessageID" expression="get-property('outMessageID')"/>
                  <property name="aggregatorID" expression="get-property('aggregatorID')"/>
               </log>
               <send/>
            </onComplete>
         </aggregate>
         <log level="custom">
            <property name="buildQuintSource" value="drop-called"/>
         </log>
         <drop/>
      </outSequence>
      <faultSequence>
         <log level="full" category="ERROR">
            <property name="buildQuintSource" value="FAULT"/>
            <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
            <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
            <property name="ERROR_DETAIL" expression="get-property('ERROR_DETAIL')"/>
            <property name="ERROR_EXCEPTION" expression="get-property('ERROR_EXCEPTION')"/>
            <property name="transactionID" expression="get-property('transactionID')"/>
            <property name="sourceMessageID" expression="get-property('sourceMessageID')"/>
            <property name="proxyMessageID" expression="get-property('proxyMessageID')"/>
         </log>
         <payloadFactory media-type="xml">
            <format>
               <rss xmlns="" version="2.0">
                  <channel/>
               </rss>
            </format>
            <args/>
         </payloadFactory>
         <property name="HTTP_SC" value="500" scope="axis2"/>
         <send/>
      </faultSequence>
   </target>
   <description/>
</proxy>





[ESBJAVA-4790] Send Mediator behavior incorrect (Please see config given below) Created: 26/Jul/16  Updated: 26/Jul/16

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

Type: Bug Priority: Highest
Reporter: dushan abeyruwan 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   
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="Foo"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <log level="full">
            <property name="MESSAGE" value="#11111"/>
            <property name="11 Header" expression="$ctx:To"/>
         </log>
         <call>
            <endpoint>
               <http uri-template="http://localhost:8080/foo">
                  <timeout>
                     <duration>40000</duration>
                     <responseAction>fault</responseAction>
                  </timeout>
                  <suspendOnFailure>
                     <errorCodes>-1</errorCodes>
                     <progressionFactor>1.0</progressionFactor>
                  </suspendOnFailure>
                  <markForSuspension>
                     <errorCodes>-1</errorCodes>
                  </markForSuspension>
               </http>
            </endpoint>
         </call>
         <log level="full">
            <property name="MESSAGE" value="#2222222"/>
            <property name="To Header" expression="$ctx:To"/>
         </log>
         <send/>
      </inSequence>
   </target>
   <description/>
</proxy>

When putting "send" mediator, it seems the behavior is exactly as "respond" but that shouldn't be correct.

In addition to that , above config leads to unwanted timeout handler error, please review the behavior of above flow and correct the logic at "Send" mediator






[ESBJAVA-4778] CXF orbit bundle import conflicts Created: 22/Jul/16  Updated: 26/Jul/16  Due: 21/Jul/16

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

Type: Bug Priority: Highest
Reporter: prabath ariyarathna Assignee: Jagath Ariyarathne
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File client.xml     XML File testProxy.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

We planned to release RM-connector with the ESB 5.0 GA release. I got following exception while RM-Connector testing with the latest ESB pack.

[2016-07-21 14:03:29,854] ERROR - NativeWorkerPool Uncaught exception

java.lang.LinkageError: javax/xml/bind/attachment/AttachmentMarshaller

at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.startDocument(XMLSerializer.java:818)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.prewrite(MarshallerImpl.java:344)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:307)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:163)

at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder.java:615)

at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:248)

at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:237)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.writeSoapEnvelopeStart(SoapOutInterceptor.java:169)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage(SoapOutInterceptor.java:87)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage(SoapOutInterceptor.java:67)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

at org.apache.cxf.ws.rm.Proxy.invoke(Proxy.java:313)

at org.apache.cxf.ws.rm.Proxy.createSequence(Proxy.java:199)

at org.apache.cxf.ws.rm.RMManager.getSequence(RMManager.java:472)

at org.apache.cxf.ws.rm.RMCaptureOutInterceptor.handle(RMCaptureOutInterceptor.java:156)

at org.apache.cxf.ws.rm.AbstractRMInterceptor.handleMessage(AbstractRMInterceptor.java:83)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)

at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:314)

at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:327)

at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:246)

at org.wso2.carbon.connector.rm.ReliableMessage.invokeBackendRMService(ReliableMessage.java:118)

at org.wso2.carbon.connector.rm.ReliableMessage.connect(ReliableMessage.java:58)

at org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)

at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:84)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:94)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:56)

at org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:104)

at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:148)

at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:84)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:94)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:56)

at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)

at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:210)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)

at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:398)

at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:145)

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:745)

Steps to reproduce the issue.

1. Install CXF feature to the latest ESB pack. Since we haven't release p2 repo yet for the ESB 5.0 . We need to manually install the CXF feature to the pack.

https://github.com/wso2/carbon-mediation/tree/master/features/inbound-endpoints/org.wso2.carbon.inbound.endpoints.ext.wsrm.feature

2. Need to install RM-Connector (Since we haven't released it yet. You have to build connector from the code)

https://github.com/prabathariyaratna/esb-connectors/tree/master/reliablemessage/reliablemessage-connector/reliablemessage-connector-1.0.0

3. You can use existing service as the backend service (https://github.com/prabathariyaratna/esb-connectors/tree/master/reliablemessage/reliablemessage-connector/reliablemessage-connector-1.0.0/org.wso2.carbon.connector/src/test/resources/rmserver)

5. Please refer following document for other configurations (https://docs.wso2.com/pages/viewpage.action?title=Working%2Bwith%2Bthe%2BRM%2BConnector&spaceKey=CONNECTORS)

Note:- Once I have removed the javax.xml.bind.attachment;resolution:=optional entry from the import section of the orbit bundle. Then it was worked fine. We need to check the RM-Inbound also with this change since we are sharing cxf bundle among the RM inbound and outbound.

https://github.com/wso2/orbit/blob/master/cxf/3.0.5.wso2v2/pom.xml






[ESBJAVA-2867] Inconsistency in filter mediator Created: 06/Jan/14  Updated: 09/Jul/15

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

Type: Bug Priority: High
Reporter: Chandana Napagoda Assignee: Jagath Ariyarathne
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.xml    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Filter mediator shows an inconsistent behavior after messages passed via message store processor. Please refer below synapse config. With out store processor it prints below log[1] and with store processor it prints log[2]

[1]. RESULT = Found a SOAP fault, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>java.io.IOException Message being parsed: </faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>

[2]. RESULT = All is well, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>java.io.IOException Message being parsed: </faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>



 Comments   
Comment by Kasun Indrasiri [ 23/Jan/14 ]

Lowering the priority as this is not a L1.





[ESBJAVA-3007] Unable to install Single "Sign On(SAML2)", "Application Management" & "Miscellaneous" features to ESB 4.8.1 Created: 14/Feb/14  Updated: 09/Jul/15

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

Type: Bug Priority: High
Reporter: Suminda Chamara Silva Assignee: Ravi Undupitiya
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Single Sign On(SAML2) feature not compatible with ESB 4.8.1.

Steps to reproduce.
1. Add turing P2 repo to the ESB 4.8.1 (http://dist.wso2.org/p2/carbon/releases/turing/)
2. Install Single sign, Application Management or Application Management on features
3. Below error popup when clicking install button

Cannot complete the install because of a conflicting dependency. Software being installed: SAML2 based Single Sign-On authenticator Feature 4.2.2 (org.wso2.carbon.identity.authenticator.saml2.sso.feature.group 4.2.2) Software currently installed: SAML2 based authenticator UI Feature 4.2.1 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.1) Only one of the following can be installed at once: SAML2 based authenticator UI Feature 4.2.2 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.2) SAML2 based authenticator UI Feature 4.2.1 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.1) SAML2 based authenticator UI Feature 4.2.0 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.0) Cannot satisfy dependency: From: SAML2 based Single Sign-On authenticator Feature 4.2.2 (org.wso2.carbon.identity.authenticator.saml2.sso.feature.group 4.2.2) To: org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group [4.2.2] Cannot satisfy dependency: From: SAML2 based authenticator UI Feature 4.2.1 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.1) To: org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar [4.2.1] Cannot satisfy dependency: From: SAML2 based authenticator UI Feature 4.2.2 (org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.2) To: org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar [4.2.2]






[ESBJAVA-2467] [MSMP] Add JMS Message Store Username / Passwords Plain text ? Created: 20/Sep/13  Updated: 09/Jul/15  Due: 20/Sep/13

Status: Open
Project: WSO2 ESB
Component/s: Message Stores
Affects Version/s: 4.8.0 M2
Fix Version/s: None

Type: Improvement Priority: High
Reporter: dushan abeyruwan Assignee: shafreen anfar
Resolution: Unresolved Votes: 0
Labels: None
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   

need expressions thus we can use mediation security component to secure passwords






[ESBJAVA-2441] Unable to enable custom module in proxy configuration Created: 10/Sep/13  Updated: 20/Jul/15

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.5.1, 4.6.0, 4.7.0
Fix Version/s: None

Type: Improvement Priority: High
Reporter: Thijs Volders Assignee: Isuru Udana Loku Narangoda
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 synapse proxy configuration does not allow to specify which custom modules should be engaged upon deployment.

This introduces several challenges:
1) One cannot change the synapse configuration or a deploy a proxy service through the filesystem without manually engaging the module on the proxy through the admin-console.
2) When a CAR (with proxy service) is (re-)deployed manual actions are necessary through the console to engage the module on the proxy(ies).
3) When Carbon decides to undeploy a service and redeploy it later then the engaged module is no longer engaged thus messages are no longer properly processed. Again manual engagement is necessary.

This latter issue is rather problematic as I have seen situations where Carbon decided to undeploy the proxy under high load en redeploy it moments later. Unfortunately the module was gone after this redeployment thus causing invalid messages to go through as the module did not stop them...






[ESBJAVA-2753] [EntitlementMediator] Once did some change in esb side, it took nearly 15min to update and execute the correct result for a XACML policy Created: 26/Nov/13  Updated: 25/Jul/15

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

Type: Improvement Priority: High
Reporter: Suneth Ranasinghe Assignee: madhuranga bandara
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: No

 Description   

I have changed the XACML policy (role) and try to invoke the given service which should not be permitted for the given user. But its allowing the user to access the service for nearly like 15mins.






[ESBJAVA-3835] Message tracing publisher sets fault "payload_status" Created: 09/Jun/15  Updated: 22/Jun/15

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

Type: Bug Priority: High
Reporter: Vijayaratha Vijayasingam Assignee: Isuru Udana Loku Narangoda
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
Test cases added: Yes

 Description   

When there is a soap error occurs at ESB due to wrong endpoint configuration,
ESB generates '500' http status error.
But, Message tracer publishes the status as "SUCCESS".(wrong value!)

If we explicitly set the status code to 500, then the payload status is recorded as 'fault'.
Sample proxy;

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="HorribleFaultProxy1"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log>
<property name="HorribleFaultProxy" value=" === In HorribleFault Proxy ==="/>
</log>
<send>
<endpoint>
<address uri="http://abc.com"/>
</endpoint>
</send>
</inSequence>
<outSequence/>
<faultSequence>
<log>
<property name="HorribleFaultProxy" value=" === In fault handler==="/>
</log>
<makefault version="soap11">
<code xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/"
value="soap11Env:Server"/>
<reason value="Deliberate horrible fault here"/>
<detail>DeliberateException</detail>
</makefault>
<send/>
</faultSequence>
</target>
<description/>
</proxy>



 Comments   
Comment by Gihan Anuruddha [ 22/Jun/15 ]

In the Message tracer level, we are using below code snippet to get status. So it seems to be in a wrong endpoint configuration scenario, ESB sent those responses through an OUT_FLOW not in an OUT_FAULT_FLOW

private String getStatus(MessageContext messageContext) {
String status = MessageTracerConstants.STATUS_SUCCESS;
if (MessageContext.OUT_FLOW == messageContext.getFLOW()) {
Object httpSC = messageContext.getProperty(HTTP_SC);
if (httpSC != null) {
int statusCode = Integer.parseInt(httpSC.toString());
if (statusCode == 200 || statusCode == 202)

{ status = MessageTracerConstants.STATUS_SUCCESS; }

else

{ status = MessageTracerConstants.STATUS_FAULT; }

} else

{ status = MessageTracerConstants.STATUS_SUCCESS; }

} else if (MessageContext.OUT_FAULT_FLOW == messageContext.getFLOW())

{ status = MessageTracerConstants.STATUS_FAULT; }

return status;
}

Comment by Isuru Udana Loku Narangoda [ 22/Jun/15 ]

Can you please explain what is meant by "wrong endpoint configuration" ?

Comment by Vijayaratha Vijayasingam [ 22/Jun/15 ]

I provided sample proxy conf. I do not see any wrong there.

Comment by Isuru Udana Loku Narangoda [ 22/Jun/15 ]

What I asked was to clarify what is meant by "wrong endpoint configuration"





[ESBJAVA-3719] Issue in STSClient while requesting token from MS ADFS Created: 27/May/15  Updated: 21/Sep/15

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

Type: Bug Priority: High
Reporter: Dilfuruz TORLAK 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   

Hi,
We have started to WSO2 ESB project in our company.
We are implementing security part of the project.
Our backend services require SAML authentication through Microsoft ADFS.
Currently, we use WSO2 ESB 4.8.1, rampart-1.6.2 and addressing-1.6.2 modules and ADFS 2.0.
While requesting token from ADFS, I'm getting below exception on ESB:

ERROR - STSClient errorInObtainingToken
org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:348)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:165)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:182)
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:766)
at org.apache.rampart.util.RampartUtil.getIssuedToken(RampartUtil.java:675)
at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:379)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:420)
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)
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.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-04-10 10:41:38,607] ERROR - Axis2Sender Unexpected error during sending message out org.apache.axis2.AxisFault: Error in obtaining a token
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.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: Error in obtaining a token
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:779)
at org.apache.rampart.util.RampartUtil.getIssuedToken(RampartUtil.java:675)
at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:379)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:420)
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)
... 24 more
Caused by: org.apache.rahas.TrustException: Error in obtaining token from : "https://XXXX:443/adfs/services/trust/13/usernamemixed"
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:174)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:182)
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:766)
... 30 more
Caused by: org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:348)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:165)
-----------------------------------------------------------------------------------------------------

When I investigated I noticed that WS-Addressing and WS-Trust namespaces at the token request prepared by apache rampart are different than expectation of ADFS.

The addressing module (addressing-1.6.2) supports the WS-Addressing Submission version (2004/08).
The apache rampart module(rampart-1.6.2) supports WS-Trust version 1.2.
ADFS has 2 kinds of endpoint; version 1.3 and version 2005.
I have tried both of them as endpoint while requesting SAML token from ADFS.
Although the ADFS endpoint with version 2005 supports WS-Trust version 1.2, still needed to change WS-Addressing namespace as "Final".

When I change below items in apache rampart, I'm able to obtain a token from ADFS..

  • Version of WS-Trust from 1.2 to 1.3
  • WS-Addressing namespace from Submission to Final

Is it a known bug?
Are there a version of apache rampart/rahas which is compatible with MS ADFS?
Thanks a lot.



 Comments   
Comment by Asela Pathberiya [ 21/Sep/15 ]

Hi Dilfuruz,

Rampart/Rahas supports up to WS-Trust 1.4 as STS (Security Token Service).

But; STSClient (just client side implementation which can use to generate RST and validates them) of the rahas is only supported to generate RST which is compatible with WS-Trust 1.2 version. It does not support for 1.3/1.4. Therefore it is addressing header is set for submission version.

According to the WS-Trust 1.2 specification, It must be the submission version

 wsa  : http://schemas.xmlsoap.org/ws/2004/08/addressing 

Therefore we do not see any bug in this. So; Please correct us, if we have missed something.

Yes. We agree that it is better to update the STS client RST version to 1.3 and addressing version to Final. We can do this improvement for future release. If you like to contribute, it is highly appreciated. Please attach the source diff in to this ticket. Then team can verify and fix it for future release.

[1] http://specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf

Thanks,
Asela.





[ESBJAVA-3329] Mediation Stat Data Publisher configuration details not get updated properly and no user message returns Created: 29/Jul/14  Updated: 26/Sep/14

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

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

ESB 481
BAM 242 27thJuly Build -Standalone server
Java version 1.7


Attachments: Text File BAM-1726.patch    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps:
1. Start a fresh BAM server
2. Start a ESB 481 server
3. Go to the Mediation Data Publisher configuration page on ESB and fill the required fields and click the update button
4. Now invoke a ESB proxy service and check whether mediation data available on the BAM server side
5. Go back to the ESB and change the "Stream Name" on the Mediation Data Publisher configuration page
6. Click Update button and check whether user notification message displaying
7. Publish data to the BAM server and check whether new column family created with newly defined Stream Name

Issue:
ESB not displaying any user message at step 6 and ESB has failed to create a new column family on BAM server side.

When Publishing data at step7 following exception can be found on the ESB stack-trace
[2014-07-29 17:10:14,515] ERROR - AsyncDataPublisher Not Supported stream definition type
[2014-07-29 17:10:14,515] ERROR - AsyncDataPublisher
java.lang.NullPointerException
at org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher$DataPublishWorker.run(AsyncDataPublisher.java:700)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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)
[2014-07-29 17:10:14,517] ERROR - AsyncDataPublisher Not Supported stream definition type
[2014-07-29 17:10:14,518] ERROR - AsyncDataPublisher
java.lang.NullPointerException
at org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher$DataPublishWorker.run(AsyncDataPublisher.java:700)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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)



 Comments   
Comment by Malith Dhanushka [ 26/Sep/14 ]

Attaching the patch to resolve this. Please add this to git by moving org.wso2.carbon.bam.mediationstats.data.publisher to git repo under ESB components.

Patch is taken from,

https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/data-agents/org.wso2.carbon.bam.mediationstats.data.publisher/4.2.1

p.s - Please not that this wont fix any UI related issues. If you click on update button there wont be any messages displayed but configuration gets updated.





[ESBJAVA-4254] NPE when shutting down server. Created: 06/Oct/15  Updated: 06/Oct/15

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

Type: Bug Priority: High
Reporter: Ajith Vitharana 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   

1. I had deployed the sample[i] with 1s trigger interval in message injector.

2. Observed the following error at the sever shutdown.

[i] https://docs.wso2.com/display/IntegrationPatterns/Test+Message

[2015-10-05 23:59:32,962] ERROR - SequenceMediator Runtime error occurred while mediating the message
java.lang.NullPointerException
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:343)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:214)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274)
at org.apache.synapse.startup.tasks.MessageInjector.execute(MessageInjector.java:319)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-10-05 23:59:32,974] ERROR - TaskQuartzJobAdapter Error in executing task: Runtime error occurred while mediating the message
org.apache.synapse.SynapseException: Runtime error occurred while mediating the message
at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:325)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:93)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:214)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274)
at org.apache.synapse.startup.tasks.MessageInjector.execute(MessageInjector.java:319)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:343)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
... 19 more
[2015-10-05 23:59:33,961] ERROR - SequenceMediator Runtime error occurred while mediating the message
java.lang.NullPointerException
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:343)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:214)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274)
at org.apache.synapse.startup.tasks.MessageInjector.execute(MessageInjector.java:319)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-10-05 23:59:33,964] ERROR - TaskQuartzJobAdapter Error in executing task: Runtime error occurred while mediating the message
org.apache.synapse.SynapseException: Runtime error occurred while mediating the message
at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:325)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:93)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:214)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274)
at org.apache.synapse.startup.tasks.MessageInjector.execute(MessageInjector.java:319)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:343)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
... 19 more
[2015-10-05 23:59:34,873] INFO - CarbonTomcatServiceComponent Stopping the carbon web-app registered under : /
[2015-10-05 23:59:36,013] INFO - CarbonServerManager Shutdown complete
[2015-10-05 23:59:36,013] INFO - CarbonServerManager Halting JVM






[ESBJAVA-4293] Exception is thrown when you create a topic without configuring topic name in jndi.properties in Inbound Endpoints Created: 29/Oct/15  Updated: 29/Oct/15

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

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

OS: Ubuntu 14.04
JDK: 1.7.0_79
Database : H2
Browser : Firefox 40.0
Setup : Standalone


Attachments: PNG File Screenshot from 2015-10-29 17-08-13.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

This issue is observed when you try to create a JMS topic subscriber with Inbound Endpoints integrated with MB 3.0.0 Beta.

Steps to recreate
------------------------------------------------------------------------------------------------------------
1. Create an inbound endpoint for the a topic with configurations are shown in the screen shot.
2. Configure the jndi.properties file as follows.

connectionfactory.QueueConnectionFactory = amqp://admin:admin@carbon/carbon?brokerlist='tcp://localhost:5673'

connectionfactory.TopicConnectionFactory = amqp://admin:admin@carbon/carbon?brokerlist='tcp://localhost:5673'

# register some queues in JNDI using the form
# queue.[jndiName] = [physicalName]
queue.MyQueue = MyQueue

# register some topics in JNDI using the form
# topic.[jndiName] = [physicalName]
topic.MyTopic222 = MyTopic222

Note: The destination "MyTopic" is not configured in the jndi.properties file

Issue
--------------------------------------------------------------------------------------------------------------
Exception is thrown as follows and a topic will not be created with the given name.

[2015-10-29 16:58:29,339] ERROR - JMSConnectionFactory JMS Exception while creating consumer. Object org.wso2.andes.client.AMQSession_0_8@4b317eca has been closed
[2015-10-29 16:58:29,339] ERROR - JMSPollingConsumer Error while receiving JMS message. null
java.lang.NullPointerException
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.receiveMessage(JMSPollingConsumer.java:247)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.poll(JMSPollingConsumer.java:135)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.execute(JMSPollingConsumer.java:98)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSTask.taskExecute(JMSTask.java:45)
	at org.wso2.carbon.inbound.endpoint.common.InboundTask.execute(InboundTask.java:44)
	at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
	at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

But, when you try to create a queue, you can give any name regardless of the queue name configured in the jndi.properties file and a queue will be created. So, there is a conflict in the behavior for queues and topics.






[ESBJAVA-4324] Missing wsse:Security header in request" while invoking a secured proxy in ESB 4.9.0 Created: 20/Nov/15  Updated: 20/Nov/15

Status: Open
Project: WSO2 ESB
Component/s: Endpoints Management, Registry, Transport
Affects Version/s: 4.9.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Kranthi Bandaru Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WSO2 ESB 4.9.0


Attachments: Text File wso2carbon_wsse_error.log    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Hello WSO2 Team,
I downloaded the ESB 4.9.0 and added the security policies to the registry and deployed the car file. When I try to invoke the proxy, I get this error.
"Missing wsse:Security header in request wso2"
Attached is the wire log.
Please let me know if a patch is available for this issue.
Note: Will send the artifacts once some one responds back to this ticket.
Thanks
Kranthi






[ESBJAVA-4308] ESB sometimes sends empty, cut or combined messages. Created: 11/Nov/15  Updated: 11/Nov/15

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

Type: Bug Priority: High
Reporter: Łukasz Andrzejak Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Enterprise Linux Server release 7.1


Attachments: PNG File image.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

I use a clusterization. Steps to reproduce.

1. Create FailoverEndpoint 'CheckTokenEndpoint'.
2. Create FailoverEndpoint 'WSTestEndpoint'.
3. Create ServiceProxy 'CheckTokenService' with FailoverEndpoint 'CheckTokenEndpoint'.
4. Create ServiceProxy 'WSTestService' with FailoverEndpoint 'WSTestEndpoint'.
5. Create mediator 'CheckTokenMediator', which connect via ServiceProxy 'CheckTokenService'. There, I use AxisClient.
6. Add mediator 'CheckTokenMediator' to sequence ServiceProxy 'WSTestService'.
7. Connect via ServiceProxy 'WSTestService'.

Most of messages are send correct, but some messages are empty or cut like this:

  • "errorMsg xsi:nil=\"true\"></ax2330:errorMsg><ax2330:expiryTime>315</ax2330:expiryTime><ax2330:scope></ax2330:scope><ax2330:valid>true</ax2330:valid></ns:return></ns:validateResponse></soapenv:Body></soapenv:Envelope>",
  • "orMsg xsi:nil=\"true\"></ax2330:errorMsg><ax2330:expiryTime>3599</ax2330:expiryTime><ax2330:scope></ax2330:scope><ax2330:valid>true</ax2330:valid></ns:return></ns:validateResponse></soapenv:Body></soapenv:Envelope>".

Combined messages look like:
"<Response from CheckTokenService> + many empty space + <Proper request message>"

Size of "<Response from WSTestService> + many empty space" is nearly 16KB.
I guess it involves parameter "io_buffer_size=16384" in file "passthru-http.properties".
Maybe this will help.






[ESBJAVA-4307] Endpoint test throw error when backend is TLS v2 Created: 09/Nov/15  Updated: 10/Nov/15

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

Type: Bug Priority: High
Reporter: Udara Liyanage 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   

Following error is shown in UI when testing a backend which supports only TLS v2.
"Unable to validate SSL Certificate"






[ESBJAVA-4240] Update jsch version to newest (0.1.53) version Created: 29/Sep/15  Updated: 29/Sep/15

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

Type: Bug Priority: High
Reporter: viraj senevirathne Assignee: viraj senevirathne
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   

In ESB 4.5.1 when some files are not properly copied when using sftp protocol.
The error happens as the transfer process fails before the rename of the file.
Caused by: org.apache.commons.vfs2.FileSystemException: Could not connect to SFTP server at "sftp://usrname:***@hshs.local/".
.....
Caused by: com.jcraft.jsch.JSchException: verify: false
Seems to be a problem in the JSch library (which is the library used by WSO2ESB for SFTP connection management):
http://www.mail-archive.com/jsch-users@lists.sourceforge.net/msg01677.html
http://stackoverflow.com/questions/12279836/ssh-using-jschexception-verify-false-sometimes-fails
https://issues.apache.org/jira/browse/IVY-1374
Also it is fixed in 0.1.50, see http://www.jcraft.com/jsch/ChangeLog.
But the version of WSO2ESB currently installed includes this jar:
/home/wso2esb/software/wso2esb/repository/components/plugins/jsch_0.1.41.wso2v1.jar
Still in ESB 4.9.0 version used is 0.1.49






[ESBJAVA-4155] Fault sequence not invoked in tenant mode Created: 03/Sep/15  Updated: 03/Sep/15

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

Type: Bug Priority: High
Reporter: Jason De Silva Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : wso2esb-4.9.0-RC2.zip
Message broker - Apache activemq 5.12.0
OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: XML File activemq.xml     XML File api.xml     XML File store.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Create a user in activemq with read / write permissions ( this user does not have admin permission(queue creation) in activemq)
2. Disable anonymous access in activemq
3. Add the activemq jars to esb and create jms message store by giving credentials of the user created in step 1.
4. Create a Tenant and login to esb from that tenant
4. Create a simple api with "post" method and set the in sequence to the message store and set the fault sequence to the default fault sequence.
5. When the api is called the below exception is thrown which is correct but the fault sequence is not called.

In super tenant mode the exact scenario will invoke the fault sequence correctly.

[2015-09-03 18:59:57,743] ERROR - JmsStore Could not create a Message Producer for Store [NewRC1]. Error:User jason is not authorized to create: queue://idntink
javax.jms.JMSSecurityException: User jason is not authorized to create: queue://idntink
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
	at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1398)
	at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2085)
	at org.apache.activemq.ActiveMQMessageProducer.<init>(ActiveMQMessageProducer.java:124)
	at org.apache.activemq.ActiveMQSession.createProducer(ActiveMQSession.java:1116)
	at org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:361)
	at org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:140)
	at org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:119)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
	at org.apache.synapse.rest.Resource.process(Resource.java:297)
	at org.apache.synapse.rest.API.process(API.java:378)
	at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
	at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:65)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
	at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRESTRequest(MultitenantMessageReceiver.java:611)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doNhttpREST(MultitenantMessageReceiver.java:555)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doREST(MultitenantMessageReceiver.java:366)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRequest(MultitenantMessageReceiver.java:224)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:78)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: User jason is not authorized to create: queue://idntink
	at org.apache.activemq.security.AuthorizationBroker.addDestination(AuthorizationBroker.java:115)
	at org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBrokerFilter.java:177)
	at org.apache.activemq.broker.region.RegionBroker.addProducer(RegionBroker.java:398)
	at org.apache.activemq.broker.jmx.ManagedRegionBroker.addProducer(ManagedRegionBroker.java:267)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.advisory.AdvisoryBroker.addProducer(AdvisoryBroker.java:188)
	at org.apache.activemq.broker.CompositeDestinationBroker.addProducer(CompositeDestinationBroker.java:56)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.security.AuthorizationBroker.addProducer(AuthorizationBroker.java:201)
	at org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:112)
	at org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:618)
	at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:108)
	at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
	at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
	at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
	at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
	at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
	... 1 more
[2015-09-03 18:59:57,746]  WARN - JmsProducer [NewRC1-P-2]. Ignored MessageID : urn:uuid:3b254fc3-8979-4829-85e9-05b7383ff84d
[2015-09-03 18:59:57,746] ERROR - MessageStoreMediator Failed to store message [urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c] in store [NewRC1].
[2015-09-03 18:59:57,746] ERROR - bbb Failed to store message [urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c] in store [NewRC1].
[2015-09-03 18:59:57,747]  INFO - LogMediator To: local://axis2services/aaa, MessageID: urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">abdef</text></soapenv:Body></soapenv:Envelope>
[2015-09-03 19:02:57,929]  WARN - SourceHandler Connection time out after request is read: http-incoming-3


 Comments   
Comment by Jason De Silva [ 03/Sep/15 ]

Attached the activemq.xml xml (broker user configuration) and the ESB api and store configurations.





[ESBJAVA-4140] NullPointerException seen when server is kept idle (Ghost Deployer is enabled). Created: 01/Sep/15  Updated: 01/Sep/15

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

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

Pack : ESB 4.9.0 RC1 (standalone)
Java version : jdk1.7.0_79


Severity: Critical
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

Occurs during tenant loading as well.

[2015-09-01 12:38:07,247]  INFO - ServiceUnloader Unloading actual Service Group : Echo and adding a Ghost Service Group. Tenant Domain: carbon.super
[2015-09-01 12:38:07,249]  INFO - DeploymentInterceptor Removing Axis2 Service: echo {super-tenant}
[2015-09-01 12:38:07,465] ERROR - CGAgentAdminService Could not retrieve the service publish flag for service 'echo'
java.lang.NullPointerException
	at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.getServiceStatus(CGAgentAdminService.java:365)
	at org.wso2.carbon.cloud.gateway.agent.observer.CGServiceObserver.serviceUpdate(CGServiceObserver.java:52)
	at org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:666)
	at org.apache.axis2.engine.AxisConfiguration.removeServiceGroup(AxisConfiguration.java:530)
	at org.wso2.carbon.service.mgt.multitenancy.ServiceUnloader.unloadInactiveServices(ServiceUnloader.java:117)
	at org.wso2.carbon.service.mgt.multitenancy.ServiceUnloader.unload(ServiceUnloader.java:71)
	at org.wso2.carbon.core.multitenancy.GenericArtifactUnloader.run(GenericArtifactUnloader.java:44)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2015-09-01 12:38:07,467] ERROR - CGServiceObserver Error while updating the service event for the service 'echo'
[2015-09-01 12:38:07,469]  INFO - GhostDeployerUtils Deploying Ghost Axis2 Service: echo
[2015-09-01 12:38:07,470] ERROR - CGAgentAdminService Could not retrieve the service publish flag for service 'echo'
java.lang.NullPointerException
	at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.getServiceStatus(CGAgentAdminService.java:365)
	at org.wso2.carbon.cloud.gateway.agent.observer.CGServiceObserver.serviceUpdate(CGServiceObserver.java:52)
	at org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:666)
	at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:420)
	at org.wso2.carbon.service.mgt.multitenancy.ServiceUnloader.unloadInactiveServices(ServiceUnloader.java:131)
	at org.wso2.carbon.service.mgt.multitenancy.ServiceUnloader.unload(ServiceUnloader.java:71)
	at org.wso2.carbon.core.multitenancy.GenericArtifactUnloader.run(GenericArtifactUnloader.java:44)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2015-09-01 12:38:07,471] ERROR - CGServiceObserver Error while updating the service event for the service 'echo'
[2015-09-01 12:59:04,738]  INFO - TenantAxisUtils Starting to clean tenant : moon.com
[2015-09-01 12:59:04,948]  INFO - TenantServiceBusInitializer Shutting down the persistence manager for the tenant: moon.com
[2015-09-01 12:59:04,953]  INFO - TenantAxisUtils Cleaned up tenant moon.com





[ESBJAVA-4139] Allows to delete proxy services that are deployed via a CApp. For other artifacts 'delete' is disabled. Created: 01/Sep/15  Updated: 23/Sep/15

Status: In Progress
Project: WSO2 ESB
Component/s: Carbon Applications, Proxy Services Management
Affects Version/s: 4.9.0 - RC1
Fix Version/s: None

Type: Bug Priority: High
Reporter: Sandapa Handakumbura Assignee: vanii thiyagarajah
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : ESB 4.9.0 RC1 (standalone)
Java version : jdk1.7.0_79


Severity: Critical
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Comments   
Comment by vanii thiyagarajah [ 23/Sep/15 ]

Please Find the pull requests.[1] [2]
[1] https://github.com/wso2/carbon-deployment/pull/175
[2] https://github.com/wso2/carbon-mediation/pull/453

Comment by Malaka Silva [ 23/Sep/15 ]

Reopening the issue since pr is not merged





[ESBJAVA-4200] FORCE_SC_ACCEPTED not working as expected when ESB cannot connect to the backend IP. Created: 08/Sep/15  Updated: 08/Sep/15

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

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

Pack : WSO2 ESB-4.9.0-RC4 (standalone)
Java version : jdk1.8.0_45


Severity: Critical
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

When we invoke this proxy we do not get the 202 Accepted. This occurs only when the log mediator is present. When we remove the log mediator we get the 202 Accepted as expected.

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="mypx"
transports="http https"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<property name="OUT_ONLY" value="true" scope="default" type="STRING"/>
<property name="FORCE_SC_ACCEPTED"
value="true"
scope="axis2"
type="STRING"/>
<log>
<property name="**** IN ******" value="AAAAAAAAAAAAA"/>
</log>
<send>
<endpoint>
<address uri="http://10.10.10.10:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
</target>
</proxy>






[ESBJAVA-4199] zookeeper.session.timeout.ms and zookeeper.connection.timeout.ms parameters in kafka inbound endpoint are not working properly Created: 08/Sep/15  Updated: 08/Sep/15

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

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

Pack : wso2esb-4.9.0-RC4
Java version : Oracle jdk 1.7.0
DB Version : embedded H2
OS : Ubuntu 14.04 LTS


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

 Description   

Create a kafka inbound endpoint and give values for zookeeper.session.timeout.ms and zookeeper.connection.timeout.ms parameters.

Timeouts are not performing within the given time durations.






[ESBJAVA-4125] Creating a secondary ldap user store in read only mode fails to authenticate users Created: 27/Aug/15  Updated: 04/Sep/15

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

Type: Bug Priority: High
Reporter: Jason De Silva Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : wso2esb-4.9.0-RC1.zip
ldap : default wso2is-5.0.0 with sp
OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: XML File recreate.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Started WSO2 IS500 with SP with port off set to use as the ldap user store
2. Created secondary read only ldap user store in esb by filling mandatory fields pointing to IS ldap
3. The secondary user store was created successfully and the ldap users were shown.
4. Login to ESB with the a secondary user store user after applying login and home page permission for the internal/everyone user role

Issue - invalid user name / password popup is shown

Enabled debug log and found the below exception

javax.naming.directory.InvalidSearchFilterException: Unbalanced parenthesis; remaining name 'ou=Users,dc=WSO2,dc=ORG'
	at com.sun.jndi.ldap.Filter.findRightParen(Filter.java:694)
	at com.sun.jndi.ldap.Filter.encodeFilterList(Filter.java:733)
	at com.sun.jndi.ldap.Filter.encodeComplexFilter(Filter.java:657)
	at com.sun.jndi.ldap.Filter.encodeFilter(Filter.java:104)
	at com.sun.jndi.ldap.Filter.encodeFilterString(Filter.java:74)
	at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:547)
	at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
	at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
	at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
	at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386)
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356)
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:339)
	at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.getNameInSpaceForUserName(ReadOnlyLDAPUserStoreManager.java:2047)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.getNameInSpaceForUserName(ReadOnlyLDAPUserStoreManager.java:2015)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.doAuthenticate(ReadOnlyLDAPUserStoreManager.java:409)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:419)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:375)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:358)
	at org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:100)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
	at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
	at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.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(OutInAxisOperation.java:430)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
	at org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
	at org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
	at org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
	at org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:83)
	at org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:377)
	at org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:244)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	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.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:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	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:950)
	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:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)
TID: [-1234] [] [2015-08-27 14:56:20,018] DEBUG {org.wso2.carbon.user.core.common.AbstractUserStoreManager} -  Authentication failure. Wrong username or password is provided. {org.wso2.carbon.user.core.common.AbstractUserStoreManager}



 Comments   
Comment by Jason De Silva [ 27/Aug/15 ]

Uploaded the config file(recreate.xml) created for the secondary user store and observed that below elements have an "amp" removing that and restated the server led ldap users also to successfully login

<Property name="UserNameSearchFilter">(&amp;amp;(objectClass=person)(uid=?))</Property>
<Property name="GroupNameSearchFilter">(&amp;amp;(objectClass=groupOfNames)(cn=?))</Property>




[ESBJAVA-4186] [Message Processors] Message processor synapse configs differ from main source view to processors' local source view Created: 07/Sep/15  Updated: 07/Sep/15

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

Type: Bug Priority: High
Reporter: Yasassri Rathnayake Assignee: Ravindra Ranwala
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : wso2esb-4.9.0-RC4-SNAPSHOT.zip
Java Version : Java 1.8
Setup : Standalone
Browser : Chrome Version 43.0.2357.130 (64-bit) | FireFox 38.0
DB : MYSQL


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

 Description   

Create a message processor, now compare the synapse configs relevent to the created processor from the main source view against the processors' local source view. These two are different, the main source view has many parameters that are not even available.

Main Source View

<messageProcessor class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor" messageStore="Test" name="Processor_ActiveMQ_03" targetEndpoint="MESSAGE_EP">
        <parameter name="message.processor.deactivate.sequence">DeactivateSEQ</parameter>
        <parameter name="message.processor.reply.sequence">On_REPLY</parameter>
        <parameter name="max.delivery.drop">Enabled</parameter>
        <parameter name="client.retry.interval">5000</parameter>
        <parameter name="max.delivery.attempts">1</parameter>
        <parameter name="interval">3000</parameter>
        <parameter name="member.count">1</parameter>
        <parameter name="throttle">false</parameter>
        <parameter name="target.endpoint">MESSAGE_EP</parameter>
        <parameter name="message.processor.fault.sequence">MyFAULT</parameter>
        <parameter name="is.active">false</parameter>
        <parameter name="message.target.store.name">null</parameter>
    </messageProcessor>

Local source view

<messageProcessor name="Processor_ActiveMQ_03" class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor" targetEndpoint="MESSAGE_EP" messageStore="Test" xmlns="http://ws.apache.org/ns/synapse">
   <parameter name="interval">3000</parameter>
   <parameter name="client.retry.interval">5000</parameter>
   <parameter name="max.delivery.attempts">1</parameter>
   <parameter name="message.processor.reply.sequence">On_REPLY</parameter>
   <parameter name="message.processor.fault.sequence">MyFAULT</parameter>
   <parameter name="message.processor.deactivate.sequence">DeactivateSEQ</parameter>
   <parameter name="is.active">false</parameter>
   <parameter name="max.delivery.drop">Enabled</parameter>
   <parameter name="member.count">1</parameter>
</messageProcessor>


 Comments   
Comment by Nadeeshaan Gunasinghe [ 07/Sep/15 ]

After going through the source, following observations found as the main reasons for the issue
1. In the master source view, message processor parameters are being read from the message context
2. In the message processor's local source view parameters are read from the html table content which list the parameters for editing.

Due to this reason some of the parameters are not shown in the message processor's local source view





[ESBJAVA-4176] API invocation sends "202 Accepted" as the response if the HTTP method is not allowed Created: 06/Sep/15  Updated: 07/Sep/15

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

Type: Bug Priority: High
Reporter: Yasassri Rathnayake Assignee: Kevin Ratnasekera
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : wso2esb-4.9.0-RC4-SNAPSHOT.zip
Java Version : Java 1.8
Setup : Cluster 3 Node
Browser : Chrome Version 43.0.2357.130 (64-bit) | FireFox 38.0
DB : MYSQL


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

 Description   

Steps to reproduce

1. Create the following API.

<api xmlns="http://ws.apache.org/ns/synapse" name="api02" context="/api02">
   <resource methods="POST">
      <inSequence>
         <send>
            <endpoint>
               <address uri="http://10.100.5.112:8080/getesb"/>
            </endpoint>
         </send>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </resource>
</api>

2. Now send a request other than a POST.

Issue : ESB will send a 202 Accepted as the response. The ESB should send error code "405- Method Not allowed" if the HTTP verb cannot be found.






[ESBJAVA-4234] The Throttle Mediator doesn't work correctly when using Respond Mediator without sending message out to an endpoint Created: 24/Sep/15  Updated: 24/Sep/15

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

Type: Bug Priority: High
Reporter: shmily wen Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: 8 hours
Time Spent: Not Specified
Original Estimate: 8 hours
Environment:

windows7 64bit, Developer Studio 3.7.1, JDK 8


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

 Description   

The Throttle Mediator doesn't treats the Respond Mediator as a response, so that the count for concurrent access number is not increase after Respond Mediator send message back to client. When digging into the code, I found ThrottleMediator.java has decrease the rest count for concurrent access number in line 129,
if (concurrentAccessController != null)

{ canAccess = doThrottleByConcurrency(isResponse, synLog); }

and only when SynapseCallbackReceiver.java line 501 is called,
int available = concurrentAccessController.incrementAndGet();
the number will be added back.

But when I use Respond Mediator, it doesn't involve SynapseCallbackReceiver since it doesn't send request to real service, so it doesn't add the number back. After a few invocation, all my request will fail.






[ESBJAVA-3837] RequestSecurityTokenTemplate from IssuedToken policy isn't used Created: 22/Jun/15  Updated: 22/Jun/15

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

Type: Bug Priority: High
Reporter: Alexey Smirnov Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB, IS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RedHat Linux


Attachments: File STS.rar     XML File STSPolicy.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

We use STS in WSO2 IS to secure echo service on WSO2ESB. We use non-secure NewTestSTS proxy (attached in archive STS.rar) to access this secured service. STSPolicy.xml (attached) is used to secure echo service. It's stored in configuration registry (or can be stored in governance registry).
First attempt of service call works fine, STS is being got from WSO2IS and is sent to echo service. But all the following attempts end with error "Requested KeyType is missing" on the IS side.
In debug log of ESB we see this message:
[2015-06-22 17:02:12,051] DEBUG - Using RSTTemplate: <spn:RequestSecurityTokenTemplate xmlns:spn="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust">

</spn:RequestSecurityTokenTemplate>

{org.apache.rahas.client.STSClient}

After re-saving of policy, service call can be performed again






[ESBJAVA-3896] Sample 657 of distributed transaction management is not working properly Created: 13/Jul/15  Updated: 15/Jul/15

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

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

Pack : wso2esb-4.9.0-ALPHA3 - 22.06.2015 pack
Java version : Oracle jdk 1.7.0
DB Version : embedded H2
OS : Ubuntu 14.04 LTS


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

 Description   

Steps to recreate :

1.Create two data sources using management console.
2.Create two derby databases.
3.Insert values into tables as transaction mediator example.(https://docs.wso2.com/display/ESB490/Transaction+Mediator+Example)

4.Since there was no 657 synapse config file, copy the given synapse config to synapse.xml file in ESB_HOME/repository/samples/ location.

5.Invoke the clients as stated in document.

But when we invoke client using commands stated in document, nothing happening to values of database tables as stated.

The successful scenario and failure scenario are not effecting to any of the database table values we have created.






[ESBJAVA-4369] Cannot save template endpoints with parameterized values Created: 21/Dec/15  Updated: 21/Dec/15

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

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

Attachments: XML File HTTP_DYNAMIC_EP_TEMPLATE.xml     XML File TemplateEndpointProxy.xml    
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: No

 Description   

We can use endpoint templates to get rid of repetition of codes when developing ESB configurations. We can parameterize the following attributes of an endpoint template

1) format
2) name
3) uri
4) method (HTTP)
5) timeout
6) error codes
7) regression factor
8) responseAction

But when we create and save a template endpoint, it will save the correct values. If we reopen the template using management console or from developer studio, it will remove the following attributes

format
method
timeout
responseAction

Above parameters are getting removed. Here (attached) is a sample configuration which works perfectly fine unless we edit from management console (or developer studio). The functionality is working properly, but we cannot edit/save.



 Comments   
Comment by Chanaka Fernando [ 21/Dec/15 ]

Attached the endpoint template and a sample proxy configuration which uses the template.





[ESBJAVA-2830] Mutual (SSL) authentication with proxy backend not possible. Created: 09/Dec/13  Updated: 30/Dec/15

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

Type: Improvement Priority: High
Reporter: Janis Jansons Assignee: Jagath Ariyarathne
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day

Severity: Major
Estimated Complexity: Advanced
Test cases added: No

 Description   

There have been a couple discussions about this problem but seems like that some WSO2 developers just do not understand what people are trying to say.

It seems like it is NOT possible to use a client certificate wtih ESB to connect to a backend server.
(Yes, seems like you can enable client authentication for the ESB proxy itself (when a client with a certificate connects to ESB) but that is something else.)

Please see this thread: http://stackoverflow.com/questions/20215809/wso2-esb-proxy-backend-with-mutual-authentication/20217063?noredirect=1#comment30467962_20217063



 Comments   
Comment by Jagath Ariyarathne [ 19/Jul/15 ]

Mutual SSL implemented in WSO2 ESB is working fine with backend service. It uses certificates in both ESB and backend service to be validated each other at SSL handshake.

But the functionality mentioned in this issue is currently not supported. It requires to use the client's certificate to be validated at backend service as the ESB's certificates. Therefore it avoids use of ESB's default certificate and requires to use client's certificate instead.

Since it is an improvement to be done, type is changed as improvement and will be taken into consideration in a future release.

Current implementation and workarounds can be done are mentioned in stackoverflow thread mentioned in the issue.

Comment by Gabriel Vince [ 30/Dec/15 ]

Mutual SSL with backend service mostly works using the customSSLProfiles (see http://nadeeshaan.blogspot.be/2014/03/enabling-custom-ssl-in-wso2-esb-4.html)

still seems there's an unresolved issue https://wso2.org/jira/browse/CARBON-11041 where the client certificate is requested during renegotiation and then it hangs.. (tested with WSO2 ESB 4.8.1)





[ESBJAVA-4589] Incoperate thread pool to Kafka Inbound Created: 03/May/16  Updated: 03/May/16

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

Type: Improvement Priority: High
Reporter: viraj senevirathne Assignee: Kathees Rajendram
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   

Introducing thread pool for Kafka Inbound. Currently, Kafka inbound only uses one stream when it provided List of streams to consume from [1]. But in this Kafka page [2] it has thread pool implementation for Kafka to read from multiple streams it passes on the list. In my opinion, if we use thread pool like this we can give users to fine tune Kafka inbound as they want. It says that "The first thing to know about using a High Level Consumer is that it can (and should!) be a multi-threaded application.".

[1] https://github.com/wso2/carbon-mediation/blob/8f66d42c1a0fed945fc8fc6046e7ecb86a5a5366/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint/src/main/java/org/wso2/carbon/inbound/endpoint/protocol/kafka/KAFKAMessageListener.java#L145

[2] https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Example



 Comments   
Comment by viraj senevirathne [ 03/May/16 ]

Related to https://wso2.org/jira/browse/ESBJAVA-4520





[ESBJAVA-3361] Inconsistence fault handling for users and tenants Created: 30/Oct/12  Updated: 24/May/16

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

Type: Bug Priority: High
Reporter: Nuwan Wimalasekara Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File soap11_fault_code_Server_synapse.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

same fault handling synapse configuration behave differently for users and tenant.

attached soap11_fault_code_Server_synapse.xml configuration make different fault messages for receiver. It works fine for users, but tenants It sees not.

Same configuration send fault message for users
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/">soap11Env:Server</faultcode>
<faultstring>Soap11FaultCodeServerTestCase</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

for tenants
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Connection refused or failed for : localhost/127.0.0.1:9020, IO Exception occured : Connection refused</faultstring>
<detail>Connection refused or failed for : localhost/127.0.0.1:9020, IO Exception occured : Connection refused</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>



 Comments   
Comment by Kasun Indrasiri [ 09/Dec/12 ]

This is not a blocker, hence lowering the priority.





[ESBJAVA-2914] wso2ESB 4.8.0 not working for transactions Created: 16/Jan/14  Updated: 24/May/16

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

Type: Bug Priority: High
Reporter: faisal shaik Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu,wso2dss3.0.1 ,wso2esb4.8.0


Attachments: File Transaction.dbs     XML File TransactionProxy.xml     PNG File ibx4q.png    
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
Affects Docs:
Yes

 Description   

Hi
I am using wso2esb4.8.0 and wso2dss3.0.1.My issue is i wish to insert the data into 2 tables its working nicely but i wish to applay transaction for my tables both table exist in same DB.If my 2nd table going fail on any moment that time my 1 st table should be rollback for that my DSS data source configuration is
and my dataservice is like this and i enabled boxcar for transaction

<data disableStreaming="true" enableBoxcarring="true" name="Transaction" serviceNamespace="http://ws.wso2.org/dataservice">
<config id="default">
<property name="carbon_datasource_name">USCProduction</property>
</config>
<query id="insertinto_mclient" useConfig="default">
<sql>insert into mclient(clientcode,clientname,createdbyid,modifiedbyid) values(?,?,?,?)</sql>
<param name="clientcode" ordinal="1" sqlType="STRING"/>
<param name="clientname" ordinal="2" sqlType="STRING"/>
<param name="createdbyid" ordinal="3" sqlType="BIGINT"/>
<param name="modifiedbyid" ordinal="4" sqlType="BIGINT"/>
</query>
<query id="insertinto_mcompany" useConfig="default">
<sql>insert into mcompany(companycode,companyname,createdbyid,modifiedbyid,clientid) values(?,?,?,?,?)</sql>
<param name="companycode" ordinal="1" sqlType="STRING"/>
<param name="comapnyname" ordinal="2" sqlType="STRING"/>
<param name="createdbyid" ordinal="3" sqlType="BIGINT"/>
<param name="modifiedbyid" ordinal="4" sqlType="BIGINT"/>
<param name="clientid" ordinal="5" sqlType="BIGINT"/>
</query>
<operation disableStreaming="true" name="insertinto_mclient_OP" returnRequestStatus="true">
<call-query href="insertinto_mclient">
<with-param name="clientcode" query-param="clientcode"/>
<with-param name="clientname" query-param="clientname"/>
<with-param name="createdbyid" query-param="createdbyid"/>
<with-param name="modifiedbyid" query-param="modifiedbyid"/>
</call-query>
</operation>
<operation disableStreaming="true" name="insertinto_mcompany_OP" returnRequestStatus="true">
<call-query href="insertinto_mcompany">
<with-param name="companycode" query-param="companycode"/>
<with-param name="comapnyname" query-param="comapnyname"/>
<with-param name="createdbyid" query-param="createdbyid"/>
<with-param name="modifiedbyid" query-param="modifiedbyid"/>
<with-param name="clientid" query-param="clientid"/>
</call-query>
</operation>
</data>
and my proxy service is
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="TransactionProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="full">
<property name="M1" value="************HITTING Transaction PROXY************"/>
</log>
<property name="OUT_ONLY" value="true"/>
<property name="companycode" expression="//companycode/text()"/>
<property name="companyname" expression="//companyname/text()"/>
<property name="clientcode" expression="//clientcode/text()"/>
<property name="clientname" expression="//clientname/text()"/>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M2" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:begin_boxcar"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/begin_boxcar"
action="urn:begin_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<p:insertinto_mclient_OP xmlns="http://ws.wso2.org/dataservice">
<xs:clientcode xmlns:xs="http://ws.wso2.org/dataservice">$1</xs:clientcode>
<xs:clientname xmlns:xs="http://ws.wso2.org/dataservice">$2</xs:clientname>
<xs:createdbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:createdbyid>
<xs:modifiedbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:modifiedbyid>
</p:insertinto_mclient_OP>
</format>
<args>
<arg evaluator="xml" expression="get-property('clientcode')"/>
<arg evaluator="xml" expression="get-property('clientname')"/>
</args>
</payloadFactory>
<header name="Action" value="urn:insertinto_mclient_OP"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/"
action="urn:insertinto_mclient_OP">
<source xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<p:insertinto_mcompany_OP xmlns="http://ws.wso2.org/dataservice">
<xs:companycode xmlns:xs="http://ws.wso2.org/dataservice">$1</xs:companycode>
<xs:comapnyname xmlns:xs="http://ws.wso2.org/dataservice">$2</xs:comapnyname>
<xs:createdbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:createdbyid>
<xs:modifiedbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:modifiedbyid>
<xs:clientid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:clientid>
</p:insertinto_mcompany_OP>
</format>
<args>
<arg evaluator="xml" expression="get-property('companycode')"/>
<arg evaluator="xml" expression="get-property('companyname')"/>
</args>
</payloadFactory>
<log level="full">
<property name="M5" value="*************hitting2nd dss****"/>
</log>
<header name="Action" value="urn:insertinto_mcompany_OP"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/"
action="urn:insertinto_mcompany_OP">
<source xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M3" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:end_boxcar"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/end_boxcar"
action="urn:end_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<log level="full">
<property name="M4" value="************HITTING Transaction PROXY************"/>
</log>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<description/>
</proxy>
box_carying is working in wso2dss but not in wso2esb is there any session management is there
i started with begin_boxcar and end with end_boxcar.BUt while i am doing this with dss if i start with begin_boxcar then 1st insert after that i checked the table but ther is no data insertion if i insert into 2nd table and end with end_boxcar then only data inserting into 2 tables.Where as i checked with proxy service configuration like above strted with begin_boxcar and inserted 1st table and checked the table dat is there means with out end_boxcar also data inserted properly
and
how can i get DSS session into proxy.what is this JSESSIONID



 Comments   
Comment by faisal shaik [ 17/Jan/14 ]

how to get the boxcarying session id in to proxy?

Comment by faisal shaik [ 20/Jan/14 ]

wso2esb support for transactions are not.

<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M2" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:begin_boxcar"/>
<property name="setCookieHeader"
expression="$trp:Set-Cookie"
scope="default"
type="STRING"/>
<callout serviceURL="http://1localhost:9764/services/Transaction/begin_boxcar"
action="urn:begin_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<property name="setCookieHeader5" expression="$trp:JSESSIONID"/>
<log level="full">
<property name="JSession" expression="get-property('setCookieHeader')"/>
</log>

how to get dss JSESSIONID in to wso2esb proxy





[ESBJAVA-4283] wso2esb is unable to create xa datasource for postgressql Created: 22/Jan/14  Updated: 24/May/16

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

Type: Bug Priority: High
Reporter: faisal shaik Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu,wso2esb4.8.0


Attachments: XML File master-datasources.xml    
Severity: Critical
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
Affects Docs:
Yes

 Description   

Hi
I am working with wso2esb 4.8.0 and postgressql9.1
I wish to do a simple transaction based insert in wso2esb .If we want to do a transaction need to use xa data source but wso2esb and dss default using non xa data source.So i created a xa data source but its showing errors even i tried wso2dss box carring but no result we are unable maintain a same JSESSONID in to proxy so now i am trying with DBLOOKUP and DB REPORT for that i am trying create xa datasource using below
configuration in repository/config/master-datasource.xmll
<datasource>
<name>DS2</name>
<jndiConfig>
<name>DS2</name>
</jndiConfig>
<definition type="RDBMS">
<configuration>
<dataSourceClassName>com.atomikos.jdbc.AtomikosDataSourceBean</dataSourceClassName>
<dataSourceProps>
<property name="xaDataSourceClassName">org.postgresql.xa.PGXADataSource</property>
<property name="uniqueResourceName">TXUSCProduction</property>
<property name="xaProperties.user">youtilitydba</property>
<property name="xaProperties.password">Youtility11</property>
<property name="xaProperties.URL">jdbc:postgresql://localhost:5432/USCProduction</property>
<property name="poolSize">10</property>
</dataSourceProps>
</configuration>
</definition>
</datasource>
its creating and showing in UI also when i am trying with DBREPORT giving pool errors are AtomikosDataSourceBean errors
really fed up with wso2 no proper docs are no proper example even no reply for any question



 Comments   
Comment by faisal shaik [ 20/Feb/14 ]

is it bug in wso2.

Comment by dushan abeyruwan [ 27/Jun/14 ]

This should be a bug related to carbon components.





[ESBJAVA-2247] Incorrect host name displayed as 'API Invocation URL' in worker manager separated setup Created: 28/Jun/13  Updated: 24/May/16

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

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

Packs : 20130624-wso2esb-4.7.0.zip


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

 Description   

In a worker manager separated setup I created an API but the given URL is incorrect. The URL contains the management host name and not the worker host name.

http://mgt.esb.qa.com:8280/t/thika.com/thikaapi2






[ESBJAVA-3688] Clean up Enrich Mediator Created: 08/May/15  Updated: 24/May/16

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

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

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

I think we can get rid of most of the redundant attributes and support them through xpath only. For instance most of the operations that you do with enrich can be done using xpath attribute in both source and target. So, we will fully verify and fix these use cases while keeping support for existing syntax for backward compatibility.

<!--payload to property -->
<enrich>
<source xpath="//m0:getQuote/m0:request/m0:symbol/text()"
xmlns:m0="http://services.samples"/>
<target xpath="$ctx:PropName"/>
</enrich>

<!-- property to payload -->
<enrich>
<source xpath="$ctx:PropName"
xmlns:m0="http://services.samples"/>
<target xpath="//m0:Foo/"/>
</enrich>

See the thread "ESB Feedback: Improve Payload Factory and Improving Enrich" at arch@ for more info/






[ESBJAVA-4271] [MB] ESB becomes inaccessible when a user tries to subscribe to a queue without permission Created: 16/Oct/15  Updated: 30/May/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.9.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Dilini Gunatilake Assignee: Dilini Gunatilake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Ubuntu 14.04
JDK: 1.7.0_79
Database : H2
Browser : Firefox 40.0
Setup : Standalone


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

 Description   

Steps to reproduce
--------------------------------------------------------------------------------------------------------
1. Login as the admin user (admin/admin)
2. Create a queue - test
3. Create another user in MB with only login, queue and topic permissions.
4. Create a JMS Proxy to consume messages from test queue by the user created at step 3

Issue
--------------------------------------------------------------------------------------------------------
Exception is logged continuously as follows mentioning permission is denied. Also, Management console will not be accessible and need to restart ESB to work again.

[2015-10-16 11:10:18,256]  INFO - ProxyService Successfully created the Axis2 service for Proxy service : SimpleStockTopicSub2
[2015-10-16 11:10:20,772]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:20,773]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:20,773]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:21,212]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:21,214]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-32
[2015-10-16 11:10:21,214] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:21,217]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:25,775] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:26,218]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:26,218]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:26,219]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:26,571]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:26,572]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-36
[2015-10-16 11:10:26,572] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:26,573] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:26,574] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:26,573] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:26,575]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:31,220] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:31,576]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:31,577]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:31,577]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:31,821]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:31,822]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-40
[2015-10-16 11:10:31,823] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:31,825]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:36,579] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:36,827]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:36,827]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:36,828]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:37,116]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:37,117]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-37
[2015-10-16 11:10:37,118] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:37,118] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]

[2015-10-16 11:11:18,960] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:11:18,959] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:11:18,961]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:11:23,676] ERROR - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2 failed. Next retry in 40 seconds
[2015-10-16 11:11:23,962]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:11:23,963]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:11:23,963]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:11:24,405]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:11:24,406]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-33
[2015-10-16 11:11:24,406] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:11:24,407] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:11:24,407] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:11:24,408] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:11:24,408]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:11:28,965] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:11:29,410]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:11:29,411]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:11:29,411]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:11:34,412] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:11:37,623]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:42,764]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:48,053]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:48,966]  INFO - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2
[2015-10-16 11:11:53,324]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:54,413]  INFO - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2
[2015-10-16 11:11:58,611]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:58,840]  INFO - DeploymentInterceptor Removing Axis2 Service: SimpleStockTopicSub2 {super-tenant}
[2015-10-16 11:11:59,422]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:0
Current Retry:0
Current Broker:0
>tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:11:59,426]  INFO - FailoverRoundRobinServers Delay between connect retries:10
[2015-10-16 11:12:03,677]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2

[2015-10-16 11:12:29,448]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2015-10-16 11:12:29,451]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:12:29,451]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:5
Current Retry:0
Current Broker:1
tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
>tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers Trying tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers Delay between connect retries:10
[2015-10-16 11:12:59,475]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2015-10-16 11:12:59,478]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:12:59,479]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:5
Current Retry:1
Current Broker:1
tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
>tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:12:59,480]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:12:59,480]  INFO - FailoverRoundRobinServers Trying tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
[2015-10-16 11:12:59,481]  INFO - FailoverRoundRobinServers Delay between connect retries:10


 Comments   
Comment by Ravindra Ranwala [ 30/May/16 ]

The given information is not cleat for us to reproduce the issue. Please clearly state the necessary steps to reproduce the issue. If you are sharing the user store etc please state those specific information that will facilitate us to replicate the issue here.





[ESBJAVA-4102] Message processor allows duplicate names when creating message processors Created: 24/Aug/15  Updated: 30/May/16

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

Type: Bug Priority: High
Reporter: viraj senevirathne Assignee: Ravindra Ranwala
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   

Prints error message in console about duplicate message processors but don't show warning in the UI

[2015-08-24 12:33:59,014] ERROR - SynapseConfiguration Duplicate Message Processor sdsd
[2015-08-24 12:33:59,014] ERROR - RPCInOnlyMessageReceiver Duplicate Message Processor sdsd
org.apache.synapse.SynapseException: Duplicate Message Processor sdsd
at org.apache.synapse.config.SynapseConfiguration.handleException(SynapseConfiguration.java:1588)
at org.apache.synapse.config.SynapseConfiguration.addMessageProcessor(SynapseConfiguration.java:1767)
at org.wso2.carbon.message.processor.service.MessageProcessorAdminService.addMessageProcessor(MessageProcessorAdminService.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.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.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.wso2.carbon.message.processor.stub.MessageProcessorAdminServiceStub.addMessageProcessor(MessageProcessorAdminServiceStub.java:417)
at org.wso2.carbon.message.processor.ui.MessageProcessorAdminServiceClient.addMessageProcessor(MessageProcessorAdminServiceClient.java:66)
at org.apache.jsp.message_005fprocessor.ServiceCaller_jsp._jspService(ServiceCaller_jsp.java:276)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
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:727)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
at org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_005finsertAttribute_005f7(template_jsp.java:640)
at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:356)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
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:727)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
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.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
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.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:504)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
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:950)
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:421)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)






[ESBJAVA-4355] Required Transaction support for the RabbitMQ transport Created: 08/Dec/15  Updated: 10/Jun/16

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

Type: New Feature Priority: High
Reporter: Krishan Malan Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB, RabbitMQ, Transaction
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

In JMS, it is possible to do transactions with the following parameters, but in Rabbitmq transport couldn't find anything similar to this.
<parameter name="transport.jms.SessionTransacted">true</parameter>
<parameter name="transport.jms.SessionAcknowledgement" locked="true">CLIENT_ACKNOWLEDGE</parameter>

Also couldn't find any OOTB solution to do transaction sessions.

Please consider this in future development.






[ESBJAVA-4398] When seperate listener is used in endpoint, the request is not sent to the endpoint Created: 01/Feb/16  Updated: 13/Jun/16

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

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

OS: Ubuntu 14.04
JDK; 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   

Steps

1. Create WSDL endpoint
2. Enable WS-Addressing with separate listener

When the above endpoint is invoked, the request fails with the following

[2016-02-01 15:15:04,041] ERROR - SourceHandler Unexpected I/O error: java.nio.channels.ClosedChannelException
java.nio.channels.ClosedChannelException
	at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
	at org.apache.http.impl.nio.reactor.SessionOutputBufferImpl.flush(SessionOutputBufferImpl.java:167)
	at org.apache.http.impl.nio.DefaultNHttpServerConnection.produceOutput(DefaultNHttpServerConnection.java:315)
	at org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.produceOutput(LoggingNHttpServerConnection.java:114)
	at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:87)
	at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:39)
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:143)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:180)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
	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:744)
[2016-02-01 15:15:04,043] ERROR - AxisEngine The endpoint reference (EPR) for the Operation not found is http://erandi-Latitude-E6540:8280/services/__ADDR_ONLY__ and the WSA Action = urn:greetResponse. If this EPR was previously reachable, please contact the server administrator.
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://erandi-Latitude-E6540:8280/services/__ADDR_ONLY__ and the WSA Action = urn:greetResponse. If this EPR was previously reachable, please contact the server administrator.
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
	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.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
[2016-02-01 15:15:04,043] ERROR - ServerWorker Error processing POST request for : /services/__ADDR_ONLY__
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://erandi-Latitude-E6540:8280/services/__ADDR_ONLY__ and the WSA Action = urn:greetResponse. If this EPR was previously reachable, please contact the server administrator.
	at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
	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.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
[2016-02-01 15:15:04,045] ERROR - PassThroughHttpSender Cannot send message to http://www.w3.org/2005/08/addressing/none

But when the "separate listener" option is ticked on, the request is successful






[ESBJAVA-4391] ERROR - SourceHandler Unexpected I/O error: java.nio.channels.ClosedChannelException Created: 22/Jan/16  Updated: 13/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.9.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Pedro Díaz Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CarbonCoreActivator Operating System : Linux 2.6.32-504.8.1.el6.x86_64, amd64
CarbonCoreActivator Java Home : /opt/soa/jdk1.7.0_51/jre
CarbonCoreActivator Java Version : 1.7.0_51
CarbonCoreActivator Java VM : Java HotSpot(TM) 64-Bit Server VM 24.51-b03,Oracle Corporation
CarbonCoreActivator Carbon Home : /opt/soa/wso2esb-4.9.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   

We have a lot of these errors in wso2-esb-errors.log file

2016-01-21 02:36:12,203 [-] [HTTPS-Listener I/O dispatcher-2] WARN SourceHandler Trying to write response body while the handler is in an inconsistent state REQUEST_READY
2016-01-21 02:36:12,201 [-] [PassThroughMessageProcessor-133] ERROR NativeWorkerPool Uncaught exception
java.nio.BufferOverflowException
at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:183)
at org.apache.http.nio.util.SimpleOutputBuffer.write(SimpleOutputBuffer.java:76)
at org.apache.http.nio.entity.ContentOutputStream.write(ContentOutputStream.java:72)
at org.wso2.carbon.mediation.transport.handlers.PassThroughNHttpGetProcessor.generateServicesList(PassThroughNHttpGetProcessor.java:367)
at org.wso2.carbon.mediation.transport.handlers.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:257)
at org.apache.synapse.transport.passthru.ServerWorker.processHttpRequestUri(ServerWorker.java:688)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:129)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2016-01-21 02:36:12,204 [-] [HTTPS-Listener I/O dispatcher-2] ERROR SourceHandler Unexpected I/O error: java.nio.channels.ClosedChannelException
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
at org.apache.http.nio.reactor.ssl.SSLIOSession.sendEncryptedData(SSLIOSession.java:343)
at org.apache.http.nio.reactor.ssl.SSLIOSession.outboundTransport(SSLIOSession.java:431)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:152)
at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
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:744)
2016-01-21 03:15:06,282 [-] [HTTPS-Listener I/O dispatcher-1] WARN SourceHandler Illegal incoming connection state: REQUEST_READY . Possibly two send backs are happening for the same request
2016-01-21 03:15:06,283 [-] [HTTPS-Listener I/O dispatcher-1] WARN SourceHandler Trying to write response body while the handler is in an inconsistent state REQUEST_READY
2016-01-21 03:15:06,283 [-] [HTTPS-Listener I/O dispatcher-1] ERROR SourceHandler Unexpected I/O error: java.nio.channels.ClosedChannelException
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
at org.apache.http.nio.reactor.ssl.SSLIOSession.sendEncryptedData(SSLIOSession.java:343)
at org.apache.http.nio.reactor.ssl.SSLIOSession.outboundTransport(SSLIOSession.java:431)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:152)
at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
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:744)
2016-01-21 06:26:14,628 [-] [HTTPS-Listener I/O dispatcher-1] WARN SourceHandler Illegal incoming connection state: REQUEST_READY . Possibly two send backs are happening for the same request
2016-01-21 06:26:14,628 [-] [HTTPS-Listener I/O dispatcher-1] WARN SourceHandler Trying to write response body while the handler is in an inconsistent state REQUEST_READY
2016-01-21 06:26:14,629 [-] [HTTPS-Listener I/O dispatcher-1] ERROR SourceHandler Unexpected I/O error: java.nio.channels.ClosedChannelException
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
at org.apache.http.nio.reactor.ssl.SSLIOSession.sendEncryptedData(SSLIOSession.java:343)
at org.apache.http.nio.reactor.ssl.SSLIOSession.outboundTransport(SSLIOSession.java:431)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:152)
at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
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:744)



 Comments   
Comment by Kasun Senevirathne [ 15/Mar/16 ]

In my case i have using wso2esb-4.9.0 ESB version in cent OS 7 & Java version jdk1.7.0_55 but similar closed channel issues are promote.

TID: [-1] [] [2016-03-01 11:37:14,317] ERROR

{org.apache.synapse.transport.passthru.SourceHandler} - Unexpected I/O error: java.nio.channels.ClosedChannelException {org.apache.synapse.transport.passthru.SourceHandler}

java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
at org.apache.http.impl.nio.reactor.SessionOutputBufferImpl.flush(SessionOutputBufferImpl.java:167)
at org.apache.http.impl.nio.DefaultNHttpServerConnection.produceOutput(DefaultNHttpServerConnection.java:315)
at org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.produceOutput(LoggingNHttpServerConnection.java:114)
at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:87)
at org.apache.synapse.transport.passthru.ServerIODispatch.onOutputReady(ServerIODispatch.java:39)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:143)
at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
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:745)

Comment by Isuru Udana Loku Narangoda [ 13/Jun/16 ]

This usually happens while sending a response back to the client if the connection (channel) has already closed.





[ESBJAVA-4447] Throttle mediator deny rule for IP range does not work when the client is in a seperate network Created: 26/Feb/16  Updated: 13/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0-M2
Fix Version/s: None

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

Server OS; Ubuntu 14.04
Server JDK: 1.8.0
Client 1 OS: Ubuntu 14.04
Client 1 JDK: 1.8.0
Client 2 OS: Windows Server 2012 R2
Client 2 JDK: 1.8.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   

I configured the following proxy for throttling deny rule

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="ThrottleProxy9"
       transports="http,https"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <throttle id="throt9">
            <policy>
               <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
                           xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
                           xmlns:throttle="http://www.wso2.org/products/wso2commons/throttle"
                           wsu:Id="WSO2MediatorThrottlingPolicy">
                  <throttle:MediatorThrottleAssertion>
                     <wsp:Policy>
                        <throttle:ID throttle:type="IP">10.100.5.30-10.100.5.200</throttle:ID>
                        <wsp:Policy>
                           <throttle:Deny/>
                        </wsp:Policy>
                     </wsp:Policy>
                     <wsp:Policy>
                        <throttle:ID throttle:type="IP">192.168.48.145-192.168.48.155</throttle:ID>
                        <wsp:Policy>
                           <throttle:Deny/>
                        </wsp:Policy>
                     </wsp:Policy>
                  </throttle:MediatorThrottleAssertion>
               </wsp:Policy>
            </policy>
            <onReject>
               <makefault version="soap12">
                  <code xmlns:soap12Env="http://www.w3.org/2003/05/soap-envelope"
                        value="soap12Env:Receiver"/>
                  <reason value="Access Denied"/>
                  <node/>
                  <role/>
               </makefault>
            </onReject>
            <onAccept>
               <send>
                  <endpoint>
                     <address uri="http://192.168.48.146:9793/services/InfoParser"/>
                  </endpoint>
               </send>
            </onAccept>
         </throttle>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </target>
   <publishWSDL uri="http://192.168.48.146:9793/services/InfoParser?wsdl"/>
   <description/>
</proxy>
                                

Please note between the given IP ranges, connections can be established

The server is hosted in the range 10.100.5.30-10.100.5.200 and Client 1 resides in the same range. Then it works as expected.

But when invoked from client 2 who resides in 192.168.48.145-192.168.48.155 it doesn't work as expected. The requests are not denied.

But when the client IP is used for deny rule it works as expected.

To isolate i hosted ESB server in 192.168.48.145-192.168.48.155 and invoked from client 2 who resides in the same range. Then it worked as expected.



 Comments   
Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

I am just wondering whether you have used private IPs of the other network here.

"But when the client IP is used for deny rule it works as expected"
Can you please mention the IP you have used in the above success case.

Comment by Chathurika De Silva [ 08/Jun/16 ]

Hi Isuru

The success case is IPs of WSO2 network, while the other set is of internal testing instances.

Thank You
Erandi

Comment by Isuru Udana Loku Narangoda [ 13/Jun/16 ]

Hi Chathurika,

Sorry I didn't get the above response, can you please explain.
Can you ping from machine which has the ESB instance to client IPs falling within the specified range ?

Comment by Chathurika De Silva [ 13/Jun/16 ]

Hi Isuru

Yes, I can. The ping worked from the failed range to the range where the server is hosted.

Thank you
Erandi

Comment by Isuru Udana Loku Narangoda [ 13/Jun/16 ]

Hi Chathurika,

I am interested in the reverse.
Can you ping from machine which has the ESB instance to client IPs falling within the specified range ?

Comment by Chathurika De Silva [ 13/Jun/16 ]

Hi Isuru

I am sorry for not providing the information before.
Yes from the range the server is hosted, I can ping to the other range

Thank You
Erandi





[ESBJAVA-4167] [IBM JDK][Cent-OS] Cannot gracefully/forcefully shutdown the server Created: 05/Sep/15  Updated: 13/Jun/16

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

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

JAVA Version
======
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470_27sr1-20140411_01(SR1))
IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20140410_195893 (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR1_20140410_1931_B195893
JIT - tr.r13.java_20140410_61421
GC - R27_Java727_SR1_20140410_1931_B195893_CMPRSS
J9CL - 20140410_195893)
JCL - 20140409_01 based on Oracle 7u55-b13
======

OS

========
Linux host-192-168-48-48 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
========

Pack : wso2esb-4.9.0-RC4-SNAPSHOT.zip
Clustered Setup with 3 Nodes


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

 Description   

Cannot gracefully/forcefully shutdown the server, the server hangs after the following log. Then need to kill the process from OS level.

Note : This was observed on IBM JDK running on Cent-OS

[2015-09-05 03:56:44,943]  INFO - PassThroughHttpSSLListener Destroying PassThroughHttpListener

The complete logs after the shutdown is triggered.

[2015-09-05 03:54:43,741]  INFO - CarbonAuthenticationUtil 'admin@carbon.super [-1234]' logged in at [2015-09-05 03:54:43,739+0000]
[2015-09-05 03:56:43,146]  INFO - CarbonServerManager Gracefully shutting down WSO2 Enterprise Service Bus...
[2015-09-05 03:56:43,149]  INFO - ServerManagement Starting to switch to maintenance mode...
[2015-09-05 03:56:43,149]  INFO - VFSTransportListener VFS Listener Shutdown
[2015-09-05 03:56:43,149]  INFO - PassThroughHttpListener Stopping Pass-through HTTP Listener..
[2015-09-05 03:56:43,150]  INFO - PassThroughListeningIOReactorManager Shutting down IO Reactor bind for port 8280
[2015-09-05 03:56:43,152]  INFO - PassThroughListeningIOReactorManager HTTP-Listener I/O dispatcher Listener shutdown.
[2015-09-05 03:56:43,152]  INFO - PassThroughHttpSSLListener Stopping Pass-through HTTPS Listener..
[2015-09-05 03:56:43,152]  INFO - PassThroughListeningIOReactorManager Shutting down IO Reactor bind for port 8243
[2015-09-05 03:56:43,154]  INFO - PassThroughListeningIOReactorManager HTTPS-Listener I/O dispatcher Listener shutdown.
[2015-09-05 03:56:43,155]  INFO - ServerManagement Stopped all transport listeners
[2015-09-05 03:56:43,155]  INFO - ServerManagement Waiting for request service completion...
[2015-09-05 03:56:43,159]  INFO - ServerManagement All requests have been served.
[2015-09-05 03:56:43,159]  INFO - ServerManagement Waiting for deployment completion...
[2015-09-05 03:56:43,166]  INFO - ServerManagement All deployment tasks have been completed.
[2015-09-05 03:56:43,166]  INFO - ServerManagement Waiting for server task completion...
[2015-09-05 03:56:44,748]  INFO - SolrClient Default Embedded Solr Server Initialized
[2015-09-05 03:56:44,749]  INFO - ServerManagement All server tasks have been completed.
[2015-09-05 03:56:44,749]  INFO - CarbonServerManager Shutting down WSO2 Enterprise Service Bus...
[2015-09-05 03:56:44,749]  INFO - CarbonServerManager Shutting down OSGi framework...
[2015-09-05 03:56:44,836]  INFO - SynapseTaskManager Shutting down the task manager
[2015-09-05 03:56:44,941]  INFO - CarbonServerManager Stopping CarbonServerManager...
[2015-09-05 03:56:44,941]  INFO - VFSTransportSender VFS Sender Shutdown
[2015-09-05 03:56:44,942]  INFO - PassThroughHttpSender HTTP Sender shutdown
[2015-09-05 03:56:44,943]  INFO - PassThroughHttpSSLSender HTTPS Sender shutdown
[2015-09-05 03:56:44,943]  INFO - PassThroughHttpListener Destroying PassThroughHttpListener
[2015-09-05 03:56:44,943]  INFO - PassThroughHttpSSLListener Destroying PassThroughHttpListener





[ESBJAVA-4696] Given sample in documentation for XSLT mediator resources is not working Created: 21/Jun/16  Updated: 21/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0-Pre-RC
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:

OS: Ubuntu 14.04
JDK: 1.8.0
Pack: Pre-RC (09.06.2016)


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: Not-applicable
Affects Docs:
Yes

 Description   

Tried Example 3 - Adding XSLT imports as resources in [1]. Failed with the following error

Request in [1] is wrong. Gave the following request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> 
    <soapenv:Header/> 
    <soapenv:Body> 
        <people> 
            <person> 
                <firstname>Isuru</firstname> 
                <lastname>Udana</lastname> 
                <gender>Male</gender> 
                <age>26</age> 
                <country>SriLanka</country> 
            </person> 
            <person> 
                <firstname>Ishan</firstname> 
                <lastname>Jayawardena</lastname> 
                <gender>Male</gender> 
                <age>26</age> 
                <country>SriLanka</country> 
            </person> 
        </people> 
    </soapenv:Body> 
</soapenv:Envelope>
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "POST /services/DocSample.DocSampleHttpSoap11Endpoint HTTP/1.1[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "Accept-Encoding: gzip,deflate[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "SOAPAction: "urn:mediate"[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "Content-Length: 704[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "Host: erandi-Latitude-E6540:8280[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "Connection: Keep-Alive[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "[\r][\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> [\n]"
[2016-06-21 17:33:11,678] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "    <soapenv:Header/> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "    <soapenv:Body> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "        <people> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "            <person> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <firstname>Isuru</firstname> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <lastname>Udana</lastname> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <gender>Male</gender> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <age>26</age> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <country>SriLanka</country> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "            </person> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "            <person> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <firstname>Ishan</firstname> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <lastname>Jayawardena</lastname> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <gender>Male</gender> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <age>26</age> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "                <country>SriLanka</country> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "            </person> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "        </people> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "    </soapenv:Body> [\n]"
[2016-06-21 17:33:11,679] DEBUG - wire HTTP-Listener I/O dispatcher-16 >> "</soapenv:Envelope>"
[2016-06-21 17:33:11,679] DEBUG - headers http-incoming-8 >> POST /services/DocSample.DocSampleHttpSoap11Endpoint HTTP/1.1
[2016-06-21 17:33:11,679] DEBUG - headers http-incoming-8 >> Accept-Encoding: gzip,deflate
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> Content-Type: text/xml;charset=UTF-8
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> SOAPAction: "urn:mediate"
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> Content-Length: 704
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> Host: erandi-Latitude-E6540:8280
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> Connection: Keep-Alive
[2016-06-21 17:33:11,680] DEBUG - headers http-incoming-8 >> User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
[2016-06-21 17:33:11,684]  WARN - SynapseConfigUtils Cannot convert null to a StreamSource
[2016-06-21 17:33:11,684] ERROR - XSLTMediator Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:/xslt2.xslt'}
org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
	at org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:580)
	at org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:81)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:394)
	at org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator.java:243)
	at org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.java:202)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:200)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:398)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:145)
	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:745)
[2016-06-21 17:33:11,688] ERROR - XSLTMediator Unable to perform XSLT transformation using : Value {name ='null', keyValue ='conf:/xslt2.xslt'} against source XPath : s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1] reason : Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:/xslt2.xslt'}
org.apache.synapse.SynapseException: Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:/xslt2.xslt'}
	at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:365)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:404)
	at org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator.java:243)
	at org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.java:202)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:200)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:398)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:145)
	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:745)
Caused by: org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
	at org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:580)
	at org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:81)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:394)
	... 13 more
[2016-06-21 17:33:11,690]  INFO - LogMediator To: /services/DocSample.DocSampleHttpSoap11Endpoint, WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:c2bd78b2-cdde-487b-9cb6-94fd8bb15e54, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Unable to perform XSLT transformation using : Value {name ='null', keyValue ='conf:/xslt2.xslt'} against source XPath : s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1] reason : Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:/xslt2.xslt'}, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body> 
        <people> 
            <person> 
                <firstname>Isuru</firstname> 
                <lastname>Udana</lastname> 
                <gender>Male</gender> 
                <age>26</age> 
                <country>SriLanka</country> 
            </person> 
            <person> 
                <firstname>Ishan</firstname> 
                <lastname>Jayawardena</lastname> 
                <gender>Male</gender> 
                <age>26</age> 
                <country>SriLanka</country> 
            </person> 
        </people> 
    </soapenv:Body></soapenv:Envelope>
[2016-06-21 17:33:11,691] DEBUG - headers http-incoming-8 << HTTP/1.1 202 Accepted
[2016-06-21 17:33:11,691] DEBUG - headers http-incoming-8 << Date: Tue, 21 Jun 2016 12:03:11 GMT
[2016-06-21 17:33:11,691] DEBUG - headers http-incoming-8 << Transfer-Encoding: chunked
[2016-06-21 17:33:11,691] DEBUG - headers http-incoming-8 << Connection: Keep-Alive
[2016-06-21 17:33:11,691] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "HTTP/1.1 202 Accepted[\r][\n]"
[2016-06-21 17:33:11,694] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "Date: Tue, 21 Jun 2016 12:03:11 GMT[\r][\n]"
[2016-06-21 17:33:11,694] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "Transfer-Encoding: chunked[\r][\n]"
[2016-06-21 17:33:11,695] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "Connection: Keep-Alive[\r][\n]"
[2016-06-21 17:33:11,695] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "[\r][\n]"
[2016-06-21 17:33:11,695] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "0[\r][\n]"
[2016-06-21 17:33:11,695] DEBUG - wire HTTP-Listener I/O dispatcher-16 << "[\r][\n]"

[1] https://docs.wso2.com/display/ESB500/XSLT+Mediator






[ESBJAVA-4697] Tibco EMS Connection creation Ends with Null pointer Exception Created: 21/Jun/16  Updated: 21/Jun/16

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

Type: Bug Priority: High
Reporter: Nadeeshaan Gunasinghe Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Tibco_ems_error.log    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

I am following https://docs.wso2.com/display/ESB490/Configure+with+Tibco+EMS and after go through the configurations, it throws the ClassNotFound exception, failing to create the ems server connectivity. I have attached the particular log herewith.






[ESBJAVA-4700] Enrich mediator related artifact is not working when deployed through dev studio Created: 22/Jun/16  Updated: 22/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 5.0.0-Pre-RC
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:

OS: Ubuntu 14.04
JDK: 1.8.0
Pack: Pre-RC (09.06.2016)


Attachments: XML File SampleProxy1.xml     File TestCaseCAR_2_1.0.0.car     XML File sample_seq_1.xml    
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: Not-applicable

 Description   

The attached CAR related artifact is not working. Where as the same configuration made through management console is working.

Request
Content-Type: application/json
Payload
{

"welcomePerson":

{ "name":"WSO2", "address":"test", "age":"21" }

}






[ESBJAVA-4429] When trying to use xpath expression with xml to text using csv parser in smooks, error is thrown Created: 19/Feb/16  Updated: 07/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0-M3
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:

OS: Ubuntu 14.04
JDK: 1.8.0


Attachments: XML File Smooks5.xml     XML File data.xml     XML File smooks_config_xmlselection.xml    
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   

I have used a xml input and tried to convert part of that xml to text using the csv parser (configs attached)

Resulted in the following error


[2016-02-19 15:53:38,139] ERROR - SmooksMediator Specified node by xpath cannot be found.
[2016-02-19 15:53:38,143] ERROR - SequenceMediator null 'source' arg in method call.
java.lang.IllegalArgumentException: null 'source' arg in method call.
	at org.milyn.assertion.AssertArgument.isNotNull(AssertArgument.java:42)
	at org.milyn.Smooks.filterSource(Smooks.java:470)
	at org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:140)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328)
	at org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:753)
	at org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:407)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:177)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:124)
	at org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
	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:745)
[2016-02-19 15:53:38,143]  INFO - LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:6BD779DD445AE1EC8B1455877418153, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = null 'source' arg in method call., Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">&lt;?xml version="1.0" encoding="UTF-8"?>
&lt;companies>
   &lt;wso2employees>
      &lt;employee1>001,aparna,QA&lt;/employee1>
      &lt;employee>002,sashika,QA&lt;/employee>
      &lt;employee>002,ushani,QA&lt;/employee>
      &lt;employee>002,nuwan,QA&lt;/employee>
   &lt;/wso2employees>
   &lt;abcemployees>
      &lt;employee>001,nihal,QA&lt;/employee>
      &lt;employee>002,tiran,QA&lt;/employee>
      &lt;employee>002,jerad,QA&lt;/employee>
      &lt;employee>002,riyana,QA&lt;/employee>
   &lt;/abcemployees>
&lt;/companies>
</text></soapenv:Body></soapenv:Envelope>

Reference: http://vvratha.blogspot.com/2014/02/xml-to-text-transformation-using-smooks.html






[ESBJAVA-4632] [ESB 500][JMS] Missing messages when using "transport.Transactionality" parameter Created: 25/May/16  Updated: 08/Jun/16

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

Type: Bug Priority: High
Reporter: Dilshani Subasinghe Assignee: Nuwan Wimalasekara
Resolution: Unresolved 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: ActiveMQ (5.11.1)


Attachments: PNG File inboundResult.png     PNG File proxyResult.png    
Severity: Critical
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   

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

  • JMS receiver
  <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</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.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="default" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</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.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>
    </transportReceiver>
  • JMS sender
  <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
           <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</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.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>
     </transportSender>

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

 <proxy name="QueueProxy" startOnLoad="true" transports="https http jms">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <log level="full"/>
                <send>
                    <endpoint>
                        <address uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=failover:tcp://localhost:61616&amp;transport.jms.DestinationType=queue&amp;transport.jms.SessionTransacted=true&amp;transport.Transactionality=local"/>
                    </endpoint>
                </send>
            </inSequence>
        </target>
        <parameter name="transport.jms.ConnectionFactory">myQueueConnectionFactory</parameter>
        <parameter name="transport.jms.DestinationType">queue</parameter>
        <parameter name="transport.jms.Destination">QueueProxy</parameter>
    </proxy>

2. Publish messages to queue "QueueProxy"

Expected result:

  • All messages should be send to other queue "MyQueue"

Actual Result:

  • Messages will be missing.

Note: Refer attachments. When testing same scenario with inbound endpoints, it may work properly.



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

Hi Dilshani,
I could not observed this behaviour on ESB 5.0.0-BETA. Can you please test this issue on 5.0.0-BETA and verify

Thanks,
Nuwanw

Comment by Dilshani Subasinghe [ 27/May/16 ]

Hi Nuwan,
I can reproduce the issue with Beta pack.

Regards,
Dilshani

Comment by Nuwan Wimalasekara [ 01/Jun/16 ]

This issue can not be reproduced with ActiveMQ client 5.8 versions. only reproduced with ActiveMQ client 5.9 or later versions

Even if the 5.9 version, when we send the messages with DeliveryMode.PERSISTENT, all the messages are consumed by ESB properly.

producer.setDeliveryMode(DeliveryMode.PERSISTENT)

Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Hi,

Is this only happening when transport.Transactionality is set ?

Comment by Dilshani Subasinghe [ 08/Jun/16 ]

Hi,

Yes, It is.

Regards,
Dilshani





[ESBJAVA-4606] JMS Sender level cache is not working properly with the stale connections. Created: 09/May/16  Updated: 08/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0, 5.0.0-M1
Fix Version/s: None

Type: Bug Priority: High
Reporter: prabath ariyarathna 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   

JMS Sender level cache is not working properly with the stale connections.
We need to check this for the session and producer cache levels.
We can reproduce this issue easily with setup JMS broker as the backend and send some requests to fill the JMS connection factory. Then need to restart the JMS broker. You can see the failures in the next subsequent requests.






[ESBJAVA-4552] Call mediator does not return the body for 202 response Created: 10/Apr/16  Updated: 08/Jun/16

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

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

OS: Ubuntu 14.04; JDK 1.7.0_51


Attachments: XML File MyMockProxy.xml     XML File test4.xml    
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   

Call mediator (Non blocking) is not sending the response body to the client when the backend sends a 202 response with body. Attached the two proxy services, test4 proxy (In ESB instance with offset 0) is called by the client and MyMockProxy (in ESB instance with offset 1) is the backend which returns 202 with response.

[2016-04-08 10:52:41,048] DEBUG - wire >> "POST /services/test4 HTTP/1.1[\r][\n]"
[2016-04-08 10:52:41,048] DEBUG - wire >> "User-Agent: curl/7.35.0[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Host: localhost:8243[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Content-Type: application/xml[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Content-Length: 12[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "<x>hello</x>"
[2016-04-08 10:52:41,051]  INFO - LogMediator To: /services/test4, MessageID: urn:uuid:3ab84305-2bda-465d-b60d-2cf13fa54e51, Direction: request
[2016-04-08 10:52:41,054] DEBUG - wire << "POST /services/MyMockProxy HTTP/1.1[\r][\n]"
[2016-04-08 10:52:41,054] DEBUG - wire << "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "c[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "<x>hello</x>[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "0[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "HTTP/1.1 202 Accepted[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Date: Fri, 08 Apr 2016 05:22:41 GMT[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "10[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "<hello>s</hello>[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "0[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,062]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:6514f496-88f6-4ca2-bd38-9ad8b22f236f, Direction: request, HTTP_Status = 202, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope>
[2016-04-08 10:52:41,064] DEBUG - wire << "HTTP/1.1 202 Accepted[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Content-Type: application/xml; charset=UTF-8; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "Date: Fri, 08 Apr 2016 05:22:41 GMT[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "0[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "[\r][\n]"


 Comments   
Comment by prabath ariyarathna [ 10/Apr/16 ]

According to my observations, This only happens when we have content aware mediators in our sequence. Inside the RelayUtils we are checking status code equal to the 202[1] and ignore build the response body. So we need to verify this behaviour.

[1] https://github.com/wso2/wso2-synapse/blob/Apache-Synapse-2.1.3-wso2v11/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/util/RelayUtils.java#L92-L96





[ESBJAVA-4460] Incorrect behavior of json-eval() Created: 02/Mar/16  Updated: 08/Jun/16

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

Type: Bug Priority: High
Reporter: Rajkumar Rajaratnam 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
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   

Lets say we have following JSON payload

{
"objectIdFieldName":"OBJECTID",
"globalIdFieldName":"",
"fields":[

{ "name":"OBJECTID", "alias":"OBJECTID", "type":"esriFieldTypeOID" }

],
"features":[
{
"attributes":

{ "OBJECTID":2445710 }

}
]
}

Now, "json-eval($.features[0].attributes.OBJECTID)" correctly returns 2445710.

But when the features array is empty like below, the above JSON Path returns "[]" which is an incorrect behavior. IMO, it should return null or undefined.

{
"objectIdFieldName":"OBJECTID",
"globalIdFieldName":"",
"fields":[

{ "name":"OBJECTID", "alias":"OBJECTID", "type":"esriFieldTypeOID" }

],
"features":[
]
}






[ESBJAVA-4428] XML to XML transformation results in error, expected output is not given Created: 19/Feb/16  Updated: 08/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0-M3, 5.0.0-Beta
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:

OS: Ubuntu 14.04
JDK: 1.8


Attachments: XML File InXml.xml     XML File Smooks4.xml     XML File smooks_xml_config.xml    
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   

Using the attached configs, performed a XML to XML transformation.
Resulted in the following error


[2016-02-19 14:51:33,736] ERROR - SmooksMediator Failed to filter source.
org.milyn.SmooksException: Failed to filter source.
	at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:97)
	at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:64)
	at org.milyn.Smooks._filter(Smooks.java:526)
	at org.milyn.Smooks.filterSource(Smooks.java:482)
	at org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:140)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328)
	at org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:753)
	at org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:407)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:177)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:124)
	at org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
	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:745)
Caused by: java.lang.NullPointerException
	at org.codehaus.stax2.ri.Stax2EventWriterImpl.add(Stax2EventWriterImpl.java:97)
	at org.wso2.carbon.mediator.transform.stream.IOElementPipe.populateEvents(IOElementPipe.java:91)
	at org.wso2.carbon.mediator.transform.stream.IOElementPipe.getData(IOElementPipe.java:68)
	at org.wso2.carbon.mediator.transform.stream.ElementInputStream.read(ElementInputStream.java:61)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
	at java.io.InputStreamReader.read(InputStreamReader.java:184)
	at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
	at org.apache.xerces.impl.XMLEntityScanner.skipString(Unknown Source)
	at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.milyn.delivery.sax.SAXParser.parse(SAXParser.java:76)
	at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:86)
	... 19 more
[2016-02-19 14:51:33,738] ERROR - SequenceMediator Failed to filter source. Caused by Failed to filter source.
org.wso2.carbon.mediator.service.MediatorException: Failed to filter source. Caused by Failed to filter source.
	at org.wso2.carbon.mediator.transform.SmooksMediator.handleException(SmooksMediator.java:265)
	at org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:160)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328)
	at org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:753)
	at org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:407)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:177)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:124)
	at org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
	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:745)
[2016-02-19 14:51:33,740]  INFO - LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:6BD779DD445AE1EC8B1455873693690, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Failed to filter source. Caused by Failed to filter source., Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">&lt;?xml version="1.0" encoding="UTF-8"?>
&lt;order id="332">
    &lt;header>
        &lt;customer number="123">Joe&lt;/customer>
    &lt;/header>
    &lt;order-items>
        &lt;order-item id="1">
            &lt;product>1&lt;/product>
            &lt;quantity>2&lt;/quantity>
            &lt;price>8.80&lt;/price>
        &lt;/order-item>
        &lt;!-- etc etc -->
    &lt;/order-items>
&lt;/order>
</text></soapenv:Body></soapenv:Envelope>



 Comments   
Comment by Chaminda Jayawardena [ 08/Jun/16 ]

Same getting when transform xml to text as well.





[ESBJAVA-4374] "Missing wsse:Security header in request" while invoking a secured proxy in ESB 4.9.0 Created: 18/Nov/15  Updated: 08/Jun/16

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

Type: Bug Priority: High
Reporter: Kranthi Bandaru Assignee: Sameera Madushan Jayasoma
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WSO2 ESB 4.9.0


Attachments: Text File wso2carbon_wsse_error.log    
Severity: Critical
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   

Hello WSO2 Team,

I downloaded the ESB 4.9.0 and added the security policies to the registry and deployed the car file. When I try to invoke the proxy, I get this error.

"Missing wsse:Security header in request wso2"

Attached is the wire log.

Please let me know if a patch is available for this issue.

Note: Will send the artifacts once some one responds back to this ticket.
Thanks
Kranthi



 Comments   
Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Hi Kranthi,

Reason for this error is follows.

From ESB to backend request is secured with UT.

<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1"><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Timestamp-1"><wsu:Created>2015-11-17T19:13:01.667Z</wsu:Created><wsu:Expires>2015-11-17T19:18:01.667Z</wsu:Expires></wsu:Timestamp><wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-2"><wsse:Username>SRAPIDIR1</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">A87368</wsse:Password></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><get:getID xmlns:get="https://mais.he.umich.edu/schemas/getID.v1"><get:fieldname>campus_id</get:fieldname><get:fieldvalue>dcp</get:fieldvalue></get:getID></soapenv:Body></soapenv:Envelope>

But the response we get for that from backend does not contain security headers.

<?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><getIDResponse xmlns="http://mais.he.umich.edu/schemas/getIDResponse.v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://mais.he.umich.edu/schemas/getIDResponse.v1 http://csdev9ib.dsc.umich.edu/PSIGW/PeopleSoftServiceListeningConnector/getIDResponse.v1.xsd"><Emplid>80723686</Emplid><Campus_id>DCP</Campus_id></getIDResponse></soapenv:Body> </soapenv:Envelope>

To fix the issue, either backend should send security headers or else we need to disable security from the endpoint level.





[ESBJAVA-4435] Unable to execute EDI to database insertion with smooks mediator Created: 23/Feb/16  Updated: 09/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0-M2
Fix Version/s: None

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

OS: Ubuntu 14.04
JDK: 1.8.0


Attachments: XML File Smooks6.xml     File edi.edi     XML File edimapping.xml     XML File smooks_edi_db_config.xml    
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   

Using the given configuration files, and using [1] as the guide line i have tried in executing this using WSO2 ESB, but failed with the following error

[2016-02-23 18:14:50,191] ERROR - SequenceMediator Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'.
org.milyn.cdr.SmooksConfigurationException: Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'.
	at org.milyn.cdr.annotation.Configurator.applyConfigParam(Configurator.java:336)
	at org.milyn.cdr.annotation.Configurator.processFieldConfigParamAnnotations(Configurator.java:146)
	at org.milyn.cdr.annotation.Configurator.processFieldConfigAnnotations(Configurator.java:126)
	at org.milyn.cdr.annotation.Configurator.configure(Configurator.java:82)
	at org.milyn.cdr.annotation.Configurator.configure(Configurator.java:66)
	at org.milyn.delivery.JavaContentHandlerFactory.create(JavaContentHandlerFactory.java:69)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.addCDU(ContentDeliveryConfigBuilder.java:642)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.applyCDUStrategy(ContentDeliveryConfigBuilder.java:568)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.applyStrategy(ContentDeliveryConfigBuilder.java:556)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$SmooksResourceConfigurationTableIterator.iterate(ContentDeliveryConfigBuilder.java:730)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$SmooksResourceConfigurationTableIterator.access$300(ContentDeliveryConfigBuilder.java:709)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.extractContentHandlers(ContentDeliveryConfigBuilder.java:494)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.load(ContentDeliveryConfigBuilder.java:356)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.getConfig(ContentDeliveryConfigBuilder.java:147)
	at org.milyn.container.standalone.StandaloneExecutionContext.<init>(StandaloneExecutionContext.java:91)
	at org.milyn.container.standalone.StandaloneExecutionContext.<init>(StandaloneExecutionContext.java:65)
	at org.milyn.Smooks.createExecutionContext(Smooks.java:418)
	at org.milyn.Smooks.createExecutionContext(Smooks.java:376)
	at org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:115)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328)
	at org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:753)
	at org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:407)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:177)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:124)
	at org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
	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:745)
Caused by: org.milyn.javabean.DataDecodeException: Failed to decode 'com.mysql.jdbc.Driver' as a Java Class.
	at org.milyn.javabean.decoders.ClassDecoder.decode(ClassDecoder.java:36)
	at org.milyn.cdr.annotation.Configurator.applyConfigParam(Configurator.java:334)
	... 33 more
Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)
	at org.milyn.util.ClassUtil.forName(ClassUtil.java:95)
	at org.milyn.javabean.decoders.ClassDecoder.decode(ClassDecoder.java:34)
	... 34 more
[2016-02-23 18:14:50,208]  INFO - LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:66E5DBEE35D675C51B1456231489841, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'., Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">MLS*Wed Nov 15 13:45:28 EST 2006
HDR*1*0*59.97*64.92*4.95
CUS*user1*Harry^Fletcher*SD
ORD*1*1*364*HarryPorter*28.98
ORD*2*1*299*Pulp Fiction*30.99
HDR*2*0*81.30*91.06*9.76
CUS*user2*George^Hook*SD
ORD*3*2*983*Gone with The Wind*25.80
ORD*4*3*299*Lethal Weapon 2*55.50
</text></soapenv:Body></soapenv:Envelope>

Followed [2] to get the namespaces for smooks 1.5.

[1] https://github.com/smooks/smooks/blob/v1.5.1/smooks-examples/db-extract-transform-load/smooks-configs/datasources.xml
[2] http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide_c6_c11



 Comments   
Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Can you please explain the issue in detail.

From the error log it seems it fails to find mysql driver.

Comment by Chathurika De Silva [ 08/Jun/16 ]

Hi Isuru

I have the mysql connector in <Product_Home>/repository/components/lib. There is no WSO2 ESB documentation to follow in this as well.
If you have such a sample documented, please be kind enough to point it to me, so I can verify my configs.

Thank You
Erandi





[ESBJAVA-4686] [ESB][JMS][IBM MQ] ESB do not reconnect IBM MQ after broken connection Created: 17/Jun/16  Updated: 17/Jun/16

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

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

Operating System : Windows server-2012-R2
Java Version : Oracle JDK1.8
Packs : ESB 5.0.0 Beta
ESB Setup: Standalone
JMS Broker: IBM MQ (8.0.0.2)


Attachments: Text File wso2carbon(1).log    
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   

Preconditions:
1. ESB should be configured with IBM MQ.
Sample Axis2.xml config:

<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
  <parameter name="default" locked="false">
 <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myQueueConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
  </parameter>

  <parameter name="myQueueConnectionFactory1" locked="false">
    <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myQueueConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
	 </parameter>
	
	<parameter name="myTopicConnectionFactory1" locked="false">
    <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myTopicConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
	<parameter name="transport.jms.DestinationType" locked="false">topic</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
  </parameter>
</transportReceiver>

2. IBM MQ should be up and running
3.ESB should be up and running

Steps to reproduce:
1. Created a proxy which will subscribe to a JMS topic
Sample Configuration:

  <proxy name="ListenerProxy" startOnLoad="true" transports="jms http https">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <property expression="get-property('SYSTEM_TIME')"
                    name="startTime" scope="default" type="STRING"/>
                <property expression="//senderInfo/common:messageId"
                    name="messagId" scope="axis2" type="STRING"/>
                <property name="messageType" scope="axis2" value="application/sampleFormatReceive"/>
                <property name="FORCE_SC_ACCEPTED" scope="axis2" value="true"/>
                <property name="JMS_IBM_PutApplType" scope="transport"
                    type="INTEGER" value="2"/>
                <property name="JMS_IBM_Encoding" scope="transport"
                    type="INTEGER" value="785"/>
                <property name="JMS_IBM_Character_Set" scope="transport"
                    type="INTEGER" value="37"/>
                <property name="JMS_IBM_MsgType" scope="transport"
                    type="INTEGER" value="8"/>
                <property action="remove" name="Accept-Encoding" scope="transport"/>
                <property action="remove" name="Content-Length" scope="transport"/>
                <property action="remove" name="User-Agent" scope="transport"/>
                <property action="remove" name="JMS_REDELIVERED" scope="transport"/>
                <property action="remove" name="JMS_DESTINATION" scope="transport"/>
                <property action="remove" name="JMS_TYPE" scope="transport"/>
                <property action="remove" name="JMS_REPLY_TO" scope="transport"/>
                <property action="remove" name="Content-Type" scope="transport"/>
                <log level="full"/>
                <store messageStore="messagestore1"/>
            </inSequence>
        </target>
        <parameter name="transport.jms.Destination">jmsTopic</parameter>
        <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory1</parameter>
    </proxy>

2. Stop IBM MQ queue manger
3. Restart IBM MQ queue manger

Expected Result:

  • Create connection again with IBM MQ.

Actual Result:

  • Continuously printing error message without creating connection.

Sample Error:

TID: [-1234] [] [2016-06-17 11:57:38,095] ERROR {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} -  Error while receiving JMS message. JMSWMQ2002: Failed to get a message from destination 'jms'. {org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer}
com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2002: Failed to get a message from destination 'jms'.
WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error.
Use the linked exception to determine the cause of this error.
	at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:578)
	at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
	at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:129)
	at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQConsumerShadow.java:1810)
	at com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receiveInternal(WMQSyncConsumerShadow.java:230)
	at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.receive(WMQConsumerShadow.java:1446)
	at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.receive(WMQMessageConsumer.java:533)
	at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:1015)
	at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:652)
	at com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:209)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.receiveMessage(JMSPollingConsumer.java:258)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.poll(JMSPollingConsumer.java:146)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer.execute(JMSPollingConsumer.java:100)
	at org.wso2.carbon.inbound.endpoint.protocol.jms.JMSTask.taskExecute(JMSTask.java:47)
	at org.wso2.carbon.inbound.endpoint.common.InboundTask.execute(InboundTask.java:45)
	at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:98)
	at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
	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(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
	at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)
	... 21 more

Note: Attached carbon log.






[ESBJAVA-4729] [ESB / Properties] When HTTP_SC property is set in super tenant mode HTTP Status message is not updated as per the http status code in super tenant Created: 06/Jul/16  Updated: 06/Jul/16

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

Type: Bug Priority: High
Reporter: Pubudu D.P Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack - wso2esb-5.0.0-pre-RC2.zip
JDK - IBM 1.8
DB- MySql 5.7


Attachments: JPEG File Selection_003.jpg     JPEG File Selection_004.jpg    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When HTTP_SC property is set within a proxy, in super tenant mode it returns a wrong Status message. But in tenant mode, the response is returned with the correct response. Please invoke the below proxy using super tenant and tenant mode. Please check attached screenshots for more information.


<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="TenantMode304Test"
       transports="http,https"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <send>
            <endpoint>
               <address uri="http://www.mocky.io/v2/577ca011100000c2284c2352"/>
            </endpoint>
         </send>
         <log level="custom">
            <property name="MESSAGE" value="++++++++++++++++Hit the end of In Seq"/>
         </log>
      </inSequence>
      <outSequence>
         <log level="custom">
            <property name="MESSAGE"
                      value="+++++++++++++++++++++++++++++++++++++++++++++++++++++++ Hit Out Sequence STATUS 304 +++++++++++++++++++++++++++++++++++++++++++"/>
            <property xmlns:ns="http://org.apache.synapse/xsd"
                      name="Status"
                      expression="get-property('axis2', 'HTTP_SC')"/>
         </log>
         <property name="HTTP_SC" value="200" scope="axis2"/>
         <log level="custom">
            <property name="MESSAGE"
                      value="+++++++++++++++++++++++++++++++++++++++++++++++++++++++ AFTER CHANGING STATUS to 200 +++++++++++++++++++++++++++++++++++++++++++"/>
            <property xmlns:ns="http://org.apache.synapse/xsd"
                      name="Status"
                      expression="get-property('axis2', 'HTTP_SC')"/>
         </log>
         <payloadFactory media-type="json">
            <format>{
 "Response Returned with Status Code": "$1"
}</format>
            <args>
               <arg evaluator="xml" expression="get-property('axis2', 'HTTP_SC')"/>
            </args>
         </payloadFactory>
         <respond/>
      </outSequence>
   </target>
   <description/>
</proxy>
                                

Expected Results:-

  • Super tenant mode should return the correct status message when HTTP_SC property is set

Actual Results:-

  • The status message is not updated when HTTP_SC property is set in super tenant mode. But this works fine in tenant mode





[ESBJAVA-4734] Update to VFS 2.1 Created: 06/Jul/16  Updated: 06/Jul/16

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

Type: Improvement Priority: High
Reporter: Philipp Bruegger Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, transport, vfs
Remaining Estimate: 4 hours
Time Spent: Not Specified
Original Estimate: 4 hours
Environment:

-


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   

Finally after several years, the Apache VFS library has been update to the version 2.1.

This version contains a whole bunch of bugfixes which are very important.

Please update the VFS library with the new release of the ESB.
Thanks



 Comments   
Comment by Philipp Bruegger [ 06/Jul/16 ]

https://commons.apache.org/proper/commons-vfs/download.html

Also update to the most recent versions of JCIFS and JSCH





[ESBJAVA-4744] [Data Mapper] Handle the NullPointer when wrong input type and output type is used Created: 04/Jul/16  Updated: 08/Jul/16

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

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

OS: Ubuntu 14.04
JDK: Oracle 1.8.0
Pack: Pre-Rc2 (23.06.2016)


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   

Tried to map a json to xml with mediator configuration given as xml to xml. There following error was observed at console

[2016-07-04 11:58:55,370] ERROR - SequenceMediator Runtime error occurred while mediating the message
java.lang.NullPointerException
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLInputReader.getElementType(XMLInputReader.java:329)
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLInputReader.XMLTraverse(XMLInputReader.java:162)
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLInputReader.XMLTraverse(XMLInputReader.java:221)
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLInputReader.read(XMLInputReader.java:117)
	at org.wso2.carbon.mediator.datamapper.engine.input.InputBuilder.buildInputModel(InputBuilder.java:59)
	at org.wso2.carbon.mediator.datamapper.engine.core.mapper.MappingHandler.doMap(MappingHandler.java:67)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.transform(DataMapperMediator.java:289)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.mediate(DataMapperMediator.java:255)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:215)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.rest.Resource.process(Resource.java:325)
	at org.apache.synapse.rest.API.process(API.java:399)
	at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:125)
	at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
	at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:69)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:300)
	at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:75)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:320)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:366)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:145)
	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:745)

Please handle this to show an ERROR in the console






[ESBJAVA-4763] NullPointerException while sending IDOC to SAP Created: 16/Jul/16  Updated: 21/Jul/16

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

Type: Bug Priority: High
Reporter: Muralidharan Balanandan Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File DebuggingWithWSO2SuggestedParameters_sapDebugEnabled.txt     Text File Test_SAP_XSLT.txt     XML File idocTestXSLT.xslt     File sapdelts.dest     Text File test_sap.txt    
Severity: Blocker
Estimated Complexity: Advanced
Test cases added: No

 Description   

Facing the following error while sending the IDOC to SAP.

Transport configurations are fine (Even BAPI message to SAP is successful)

TID: [0] [ESB] [2016-07-12 13:50:39,213] ERROR

{org.wso2.carbon.transports.sap.SAPTransportSender} - Error while sending an IDoc to the EPR : idoc:/sapdelts {org.wso2.carbon.transports.sap.SAPTransportSender}

java.lang.NullPointerException
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.closeStream(DefaultIDocXMLMapper.java:68)
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.getDocumentList(DefaultIDocXMLMapper.java:59)
at org.wso2.carbon.transports.sap.SAPTransportSender.getIDocs(SAPTransportSender.java:163)
at org.wso2.carbon.transports.sap.SAPTransportSender.sendMessage(SAPTransportSender.java:103)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:114)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
TID: [0] [ESB] [2016-07-12 13:50:39,215] ERROR

{org.apache.synapse.core.axis2.Axis2Sender} - Unexpected error during sending message out {org.apache.synapse.core.axis2.Axis2Sender}

org.apache.axis2.AxisFault: Error while sending an IDoc to the EPR : idoc:/sapdelts
at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:226)
at org.wso2.carbon.transports.sap.SAPTransportSender.sendMessage(SAPTransportSender.java:136)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:114)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)



 Comments   
Comment by Muralidharan Balanandan [ 19/Jul/16 ]

Proxy used to send IDOC to SAP

Comment by Muralidharan Balanandan [ 19/Jul/16 ]

the .dest file used to connect to SAP

Comment by Chanaka Fernando [ 20/Jul/16 ]

This looks like an issue with the connectivity from the ESB to SAP over IDOC transport or an error with the IDOC message. Could you please enable the error handler with the following parameters for this proxy and attach the resulting log.

<parameter name="transport.sap.enableTIDHandler">enabled</parameter>
<parameter name="transport.sap.enableErrorListener">enabled</parameter>

Another thing you can do is to check the validity of the IDOC message which you are sending to the SAP system from ESB. If the message is not formatted properly, you will get this kind of error.

Comment by Chanaka Fernando [ 20/Jul/16 ]

Reducing the priority since this looks like a configuration issue.

Comment by Muralidharan Balanandan [ 20/Jul/16 ]

Thanks Chanaka Fernando.. Can you please share some reference to valid IDOC message or message content. It would be very helpful.

Comment by Muralidharan Balanandan [ 21/Jul/16 ]

We validated the IDOC message and its fine. As you suggested, added the above parameters and tried. Attaching the latest proxy. XSLT used and the logs.
Kindly have a look and let us know your findings.





[ESBJAVA-4747] Unable to use sftpPathFromRoot parameter in File Inbound. Created: 11/Jul/16  Updated: 15/Jul/16

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

Type: Bug Priority: High
Reporter: Kesavan Yogarajah 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   

We can add "sftpPathFromRoot" parameter to VFS FileURI as [1] to get absolute path access. It worked for vfs transport. But It doesn't work for file inbound endpoint.

[1] - <parameter name="transport.vfs.FileURI">sftp://[ username[: password]@] hostname[: port][ absolute-path]?sftpPathFromRoot=true</parameter>






[ESBJAVA-4769] JMS message publishing fails after encryptiing JMS credentials in the axis2.xml Created: 18/Jul/16  Updated: 18/Jul/16

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

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

ActiveMQ
ESB 4.8.1


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

 Description   

Enable user validation on the broker and encrypt the following JMS credentials in axis2.xml sender configuration and try to publish a message.

<parameter name="java.naming.security.credentials" svns:secretAlias="Axis2.Jndi.Parameter.Password">password</parameter>
<parameter name="transport.jms.Password" svns:secretAlias="Axis2.Jms.Parameter.Password">password</parameter>

The following exception occurs.
The value being passed as the password after encrypting the credentials is actually the value in the axis2.xml (i.,e the value 'password'). The encrypted value of the password is not considered here.

[2016-07-14 01:02:59,557] ERROR - JMSConnectionFactory Error creating JMS session from JMS CF : default
javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more
[2016-07-14 01:02:59,566] ERROR - Axis2Sender Unexpected error during sending message out
org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS session from JMS CF : default
at org.apache.axis2.transport.jms.JMSConnectionFactory.handleException(JMSConnectionFactory.java:248)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:350)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
... 24 more
Caused by: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more
[2016-07-14 01:02:59,570] WARN - FaultHandler ERROR_CODE : 0
[2016-07-14 01:02:59,570] WARN - FaultHandler ERROR_MESSAGE : Unexpected error during sending message out
[2016-07-14 01:02:59,571] WARN - FaultHandler ERROR_DETAIL : org.apache.synapse.SynapseException: Unexpected error during sending message out
at org.apache.synapse.core.axis2.Axis2Sender.handleException(Axis2Sender.java:172)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:71)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
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.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS session from JMS CF : default
at org.apache.axis2.transport.jms.JMSConnectionFactory.handleException(JMSConnectionFactory.java:248)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:350)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
... 15 more
Caused by: javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
... 24 more
Caused by: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more

[2016-07-14 01:02:59,571] WARN - FaultHandler ERROR_EXCEPTION : org.apache.synapse.SynapseException: Unexpected error during sending message out
[2016-07-14 01:02:59,572] WARN - FaultHandler FaultHandler : AnonymousEndpoint
[2016-07-14 01:02:59,572] WARN - EndpointContext Endpoint : AnonymousEndpoint will be marked SUSPENDED as it failed
[2016-07-14 01:02:59,572] WARN - EndpointContext Suspending endpoint : AnonymousEndpoint - last suspend duration was : 30000ms and current suspend duration is : 30000ms - Next retry after : Thu Jul 14 01:03:29 IST 2016






[ESBJAVA-4740] [IBM JDK 8 / MsSql ] An exception triggered when starting ESB pack with IBM JDK 8 and MSSql Created: 08/Jul/16  Updated: 18/Jul/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 5.0.0-Pre-Beta2
Fix Version/s: None

Type: Bug Priority: High
Reporter: Pubudu D.P Assignee: Balasubramaniyam Senduran
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack:- wso2esb-5.0.0-pre-RC2.zip
JDK:-
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)
DB:- MSSql 2012
DB Driver:- sqljdbc4.jar


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

 Description   

Pre-Conditions:-

  • Point the db to MSSQL database
  • Mount the registry
  • Set the JDK as IBM jdk8

1. Go to [$ESB_HOME]/bin
2. Start the server and observe

Expected Results:-

  • ESB server should be started successfully

Actual Results:-

  • Server is not started successfully
  • Following exception is triggered on startup

[2016-07-08 12:46:47,928] ERROR - DatabaseUtil Database Error - The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 SSLContext not available.
com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 SSLContext not available.
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSChannel.throwSSLConnectionFailed(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
	at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278)
	at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
	at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127)
	at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:158)
	at org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:448)
	at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:124)
	at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:263)
	at org.wso2.carbon.user.core.common.DefaultRealmService.<init>(DefaultRealmService.java:100)
	at org.wso2.carbon.user.core.common.DefaultRealmService.<init>(DefaultRealmService.java:113)
	at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:68)
	at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(AccessController.java:650)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2016-07-08 12:46:47,942] ERROR - Activator Cannot start User Manager Core bundle
org.wso2.carbon.user.core.UserStoreException: Cannot initialize the realm.
	at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:273)
	at org.wso2.carbon.user.core.common.DefaultRealmService.<init>(DefaultRealmService.java:100)
	at org.wso2.carbon.user.core.common.DefaultRealmService.<init>(DefaultRealmService.java:113)
	at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:68)
	at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(AccessController.java:650)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: org.wso2.carbon.user.core.UserStoreException: Database Error - The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 SSLContext not available.
	at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:168)
	at org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:448)
	at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:124)
	at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:263)
	... 19 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 SSLContext not available.
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSChannel.throwSSLConnectionFailed(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
	at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278)
	at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
	at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
	at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127)
	at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:158)
	... 22 more
[2016-07-08 12:47:01,734]  INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined

Note:-

  • The same pack is successfully started with Oracle JDK 8
  • Fresh pack is started successfully on top of IBM JDK 8 without any errors
  • Similar issue found for MySQL (ESBJAVA-4739)


 Comments   
Comment by Buddhima Wijeweera [ 15/Jul/16 ]

Hi,
This seems like a driver issue that you use.

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 SSLContext not available.

Thanks,
Buddhima

Comment by Pubudu D.P [ 18/Jul/16 ]

Hi Buddhima,
Tested with a fresh pack for Beta2 release without pointing to a DB. I'm getting the below error only by pointing to the IBM JDK 8. Please let me know if you require any further information on this.

[2016-07-18 11:56:23,146]  INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2016-07-18 11:56:32,756]  INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined
[2016-07-18 11:56:32,908] ERROR - StandardContext Exception sending context initialized event to listener instance of class org.owasp.csrfguard.CsrfGuardServletContextListener
java.lang.RuntimeException: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:34)
	at org.owasp.csrfguard.config.overlay.ConfigurationAutodetectProviderFactory.retrieveConfiguration(ConfigurationAutodetectProviderFactory.java:73)
	at org.owasp.csrfguard.CsrfGuard.retrieveNewConfig(CsrfGuard.java:112)
	at org.owasp.csrfguard.CsrfGuard.config(CsrfGuard.java:86)
	at org.owasp.csrfguard.CsrfGuard.isPrintConfig(CsrfGuard.java:685)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.printConfigIfConfigured(CsrfGuardServletContextListener.java:97)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.contextInitialized(CsrfGuardServletContextListener.java:86)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
	at java.util.concurrent.FutureTask.run(FutureTask.java:277)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.lang.Thread.run(Thread.java:785)
Caused by: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:234)
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:32)
	... 15 more
Caused by: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at sun.security.jca.GetInstance.getService(GetInstance.java:99)
	at sun.security.jca.GetInstance.getInstance(GetInstance.java:218)
	at java.security.SecureRandom.getInstance(SecureRandom.java:342)
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:121)
	... 16 more
[2016-07-18 11:56:32,910] ERROR - StandardContext One or more listeners failed to start. Full details will be found in the appropriate container log file
[2016-07-18 11:56:32,915] ERROR - StandardContext Context [/] startup failed due to previous errors


Comment by Buddhima Wijeweera [ 18/Jul/16 ]

Hi Pubudu,
For me, last error seems not relevant to the initial issue reported. could you please open a new ticket to report this behavior?
Thanks,
Buddhima

Comment by Pubudu D.P [ 18/Jul/16 ]

Created: ESBJAVA-4772





[ESBJAVA-3354] Editing Streams should not be allowed in BAM mediator Created: 30/Oct/12  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Maninda Edirisooriya Assignee: Vijitha Ekanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

BAM 2.0.2 with ESB 4.5.1


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   

In BAM config UI, editing Stream information should not be allowed as edited streams are not supported. Only inserting and deleting should be possible.






[ESBJAVA-3475] SOAP Faults are not properly decrypted when sending through to a secured endpoint through secured ESB proxy (Both endpoint and proxy are secured with an encryption mechanism) Created: 02/Sep/11  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Johann Nallathamby Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu, Linux


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   

Following are the steps to reproduce.
1. Create a service in WSAS
2. Secure WSAS service using security scenario 5 (Sign and Encrypt)
3. Create an ESB proxy and an ESB endpoint
4. Also secure ESB proxy service using security scenario 5 (Sign and Encrypt)
5. Send an invalid message to endpoint through ESB proxy so that endpoint will send a soap fault
6. Client will not receive the soap fault instead it will print a message similar to following,

2011-08-25 14:55:44,799 [-] [main] ERROR AxisEngine The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
org.apache.axis2.AxisFault: The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:259)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:165)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:556)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:532)
at org.wso2.identity.esb.kerberos.KerberosClient.main(Unknown Source)
Caused by: org.apache.ws.security.WSSecurityException: The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:250)
at org.apache.ws.security.processor.EncryptedKeyProcessor.decryptDataRef(EncryptedKeyProcessor.java:443)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:381)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:104)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleToken(EncryptedKeyProcessor.java:84)
at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:333)
at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:250)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:171)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 10 more
Caused by: org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.xml.security.encryption.XMLCipher$Serializer.deserialize(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.decryptElement(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.decryptElementContent(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.doFinal(Unknown Source)
at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:248)
... 18 more

Further this issue only occurs when we applied encryption to both client -> ESB and ESB -> WSAS flows.

On ESB side before encrypting message it will get a message similar to following,

<?xml version="1.0" encoding="UTF-8"?>
<fragment
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<faultcode xmlns:axis2ns34="">soapenv:Server</faultcode>
<faultstring xmlns:axis2ns35="">For input string: "1er"</faultstring>
<detail xmlns:axis2ns36=""></detail>
</soapenv:Fault>
</fragment>






[ESBJAVA-1503] New edit options (Source View / Design View) in service list are visible even when proxy services are Inactive. Created: 22/Aug/12  Updated: 25/Jul/15

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.5.0 M5
Fix Version/s: None

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

Pack : WSO2 ESB 4.5.0 - 20th August 2012


Attachments: PNG File screenshot1.png     PNG File screenshot2.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

When proxy services are inactive, 'WSDL' and 'Try it' options are not visible in service list(as expected), but new edit options (Source View / Design View)are visible. And if you try to edit inactive proxy services using those options, An error is thrown. Error given on UI doesn't even give the reason.

[2012-08-22 10:07:06,034] ERROR - ProxyServiceAdmin Invalid proxy service definition :: The system is attempting to access an inactive service: InOnlyProxy
org.apache.axis2.AxisFault: The system is attempting to access an inactive service: InOnlyProxy
at org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:1033)
at org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.modifyProxyService(ProxyServiceAdmin.java:321)
at org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.modifyProxy(ProxyServiceAdmin.java:702)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
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:619)
[2012-08-22 10:07:06,059] ERROR - ProxyServiceAdminClient Unable to modify proxy service: InOnlyProxy
org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminProxyAdminException: ProxyServiceAdminProxyAdminException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.modifyProxy(ProxyServiceAdminStub.java:1573)
at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient.modifyProxy(ProxyServiceAdminClient.java:112)
at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_jsp.java:107)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:690)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:599)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:536)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:265)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:643)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:637)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_insertAttribute_7(template_jsp.java:539)
at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:290)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:690)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:477)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:258)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
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:619)



 Comments   
Comment by Sandapa Handakumbura [ 22/Aug/12 ]

At least the Error message given on UI should be meaningful.





[ESBJAVA-2213] Callout mediator improvement to get NTLM working Created: 02/May/12  Updated: 20/Jul/15

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

Type: Improvement Priority: Normal
Reporter: Nandika Jayawardana Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any


Attachments: Text File callout-mediator-update.patch     Text File callout-mediator.patch    
Severity: Major
Estimated Complexity: Moderate

 Description   

With this fix, it is possible to reuse the existing Axis2 client options available in the Synapse message context when invoking the external service through the Callout mediator. This can be enabled by setting the property initAxis2ClientOptions to "false". By default, it's value is "true", so that this new addition does not affect any of the its current usages.



 Comments   
Comment by Nandika Jayawardana [ 02/May/12 ]

patch committed to trunk

Comment by Rajika Kumarasiri [ 10/Jul/12 ]

Does this patches made up their ways to Synapse ?

Rajika





[ESBJAVA-3477] Policies loaded using Local Entries should be able to use the default password call back handler. Created: 17/May/12  Updated: 03/Jan/15

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

Type: Bug Priority: Normal
Reporter: Suresh Attanayake Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WSO2 ESB 4.0.3


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   

Policies loaded using the Local Entries in the ESB must be able to use the default password call back handler. ESB throws following error at the current implementation when try to use the default password callback handler.

org.apache.axis2.AxisFault: General security error (WSSecurityEngine: Callback supplied no password for: wso2carbon)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)






[ESBJAVA-3349] BAM Mediator does not store field "meta_host" in Casandra when Internet is not available Created: 24/Sep/12  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Maninda Edirisooriya Assignee: Vijitha Ekanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

BAM 2.0 and ESB 4.5.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: Not-applicable

 Description   

BAM mediator throws an exception while mediating and "meta_host" field seems empty in Cassandra database when Internet is not available. i.e. when IP address is set to 127.0.0.1.






[ESBJAVA-1564] Gracefully Restart server does not wait until server to persist synapse configuration in to file system. Created: 03/Sep/12  Updated: 07/Oct/12

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

Type: Bug Priority: Normal
Reporter: Nuwan Wimalasekara Assignee: Isuru Udana Loku Narangoda
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   

I upload a synapse configuration which has one proxy service which use groovy script. after test Groovy.jar is removed from class path and upload a new synapse configuration which has not that proxy service. I let 5 sec to deploy new synapse and restart serve gracefully.
when restarting server i got following error and server does not responding any more even if it says carbon server started.
the problem is that proxy service does not delete from file system. when ESB deploying proxy service again error occurred because of no grrovy.jar in classpath.

if we make a much delay scenario get passed. restarting server does not wait server to delete proxy from file system.

Refer Test case:
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/esb/4.5.0/modules/integration/tests/src/test/java/org/wso2/carbon/esb/mediator/test/script/GroovySupportWithinProxyTestCase.java

ERROR

[2012-09-03 12:05:19,629] INFO - Axis2SynapseController Loading mediator extensions...
[2012-09-03 12:05:19,633] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,633] INFO - CarbonSynapseController Loading the mediation configuration from the file system
[2012-09-03 12:05:19,635] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:19,635] INFO - MultiXMLConfigurationBuilder Building synapse configuration from the synapse artifact repository at : ././repository/deployment/server/synapse-configs/default
[2012-09-03 12:05:19,636] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,636] INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
[2012-09-03 12:05:19,720] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:19,719] FATAL - ServiceBusInitializer Failed to initialize ESB due to a fatal error
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - java.lang.NoClassDefFoundError: groovy/lang/MissingMethodException
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at com.sun.script.groovy.GroovyScriptEngineFactory.getScriptEngine(GroovyScriptEngineFactory.java:90)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at javax.script.ScriptEngineManager.getEngineByExtension(ScriptEngineManager.java:256)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.mediators.bsf.ScriptMediator.initScriptEngine(ScriptMediator.java:452)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:315)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.mediators.bsf.ScriptMediator.<init>(ScriptMediator.java:134)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.mediators.bsf.ScriptMediatorFactory.createSpecificMediator(ScriptMediatorFactory.java:102)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:192)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:69)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.ProxyServiceFactory.createProxy(ProxyServiceFactory.java:172)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.defineProxy(SynapseXMLConfigurationFactory.java:142)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.createProxyServices(MultiXMLConfigurationBuilder.java:225)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.getConfiguration(MultiXMLConfigurationBuilder.java:130)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.SynapseConfigurationBuilder.getConfiguration(SynapseConfigurationBuilder.java:100)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.Axis2SynapseController.createSynapseConfiguration(Axis2SynapseController.java:443)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.mediation.initializer.CarbonSynapseController.createSynapseConfiguration(CarbonSynapseController.java:167)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.ServerManager.start(ServerManager.java:177)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:412)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:172)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at java.lang.reflect.Method.invoke(Method.java:597)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.event.core.internal.builder.EventBrokerHandler.startEventBroker(EventBrokerHandler.java:57)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS.activate(EventBrokerBuilderDS.java:72)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at java.lang.reflect.Method.invoke(Method.java:597)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:503)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:289)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- Caused by: java.lang.ClassNotFoundException: groovy.lang.MissingMethodException
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- ... 70 more
[2012-09-03 12:05:19,727] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,727] INFO - RuleEngineConfigDS Successfully registered the Rule Config service
[2012-09-03 12:05:20,490] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:20,490] INFO - CarbonUIServiceComponent Mgt Console URL : https://10.100.3.190:9443/carbon/
[2012-09-03 12:05:23,053] INFO

{org.wso2.carbon.automation.core.utils.ClientConnectionUtil} - Waiting until server starts on port 9443
[2012-09-03 12:05:24,054] INFO {org.wso2.carbon.automation.core.utils.ClientConnectionUtil}

- Waiting until server starts on port 9443






[ESBJAVA-1555] Invalid schemaLocation appears in WSDL when proxy service endpoints are customized with ServiceURI parameter. Created: 30/Aug/12  Updated: 07/Oct/12

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

Type: Bug Priority: Normal
Reporter: Ramith Jayasinghe Assignee: Isuru Udana Loku Narangoda
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   

How to reproduce:

1. Get a wsdl with schema imports.
2. Save them (wsdl and xsd files) in a embedded registry (either config registry or governance)
3. Define a proxy service using this wsdl.
4. customize the endpoint of the proxy service using ServiceURI
5. Load the WSDL of the proxy service from SOAP UI and notice SOAP UI complains that it can create the project.
Also notice that 'try it' UI seems to work.

for example:
with following proxy definition:

<proxy name="CustProxy" transports="http" startOnLoad="true" trace="disable">
<target>
<endpoint>
<address uri="http://localhost:8280/services/calculatorImportSchema"/>
</endpoint>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL key="conf:/trunk/calculatorImportSchema.wsdl">
<resource location="SCHEMA_LOCATION" key="conf:/trunk/calculator.xsd"/>
</publishWSDL>
<parameter name="ServiceURI">/test/custom</parameter>
</proxy

WSDL of proxy service will incorrectly point to:
http://localhost:8280/test/custom/CustProxy?xsd=calculator.xsd






[ESBJAVA-1754] Iterate Mediator operation scope not functioning properly with high concurrency Created: 10/Jan/13  Updated: 23/May/13

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

Type: Bug Priority: Normal
Reporter: Kasun Indrasiri 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   

Can reproduce with the following configuration:

<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
<parameter name="cachableDuration">15000</parameter>
</registry>
<proxy name="aggregateMediatorTestProxy" transports="https http" startOnLoad="true" trace="disable">
<description/>
<target>
<inSequence>
<property name="counter" value="0" scope="operation"/>
<iterate xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns3="http://org.apache.synapse/xsd" xmlns:m0="http://services.samples" id="iterate1" preservePayload="true" attachPath="//m0:getQuotes" expression="//m0:getQuotes/m0:getQuote"
sequential="true">
<target>
<sequence>

<log level="full">

<property name="target1" value="***********After 1st Iterate before 2nd Iterate************"/>
</log>
<iterate id="iterate2" preservePayload="true" attachPath="//m0:getQuote" expression="//m0:getQuotes/m0:getQuote/m0:request">
<target sequence="anon">
<sequence>
<property name="counter" expression="get-property('operation','counter') + 1" scope="operation"/>
<log level="custom">
<property name="printingCount" expression="get-property('operation','counter')"/>
</log>
<payloadFactory>
<format>
<m0:getQuote>
<m0:request>
<m0:symbol>WSO2 $1</m0:symbol>
</m0:request>
</m0:getQuote>
</format>
<args>
<arg expression="get-property('operation','counter')"/>
</args>
</payloadFactory>
<log level="full" category="DEBUG">
<property name="target1" value="***********after payload factory************"/>
</log>
<send>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</sequence>
</target>
</iterate>
</sequence>
</target>
</iterate>
</inSequence>
<outSequence>
<aggregate id="iterate2">
<completeCondition>
<messageCount min="-1" max="-1"/>
</completeCondition>
<onComplete xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns3="http://org.apache.synapse/xsd" xmlns:m0="http://services.samples" expression="//m0:getQuoteResponse">
<log level="custom">
<property name="messageLog" value="****Aggregating****"/>
</log>
<send/>
</onComplete>
</aggregate>
</outSequence>
</target>
</proxy>
<sequence name="fault">
<log level="full">
<property name="MESSAGE" value="Executing default 'fault' sequence"/>
<property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
<property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
</log>
<drop/>
</sequence>
<sequence name="main">
<in>
<sequence key="IterateMediatorSequence"/>
</in>
<out>
<sequence key="IteratorAggregateSequence"/>
</out>
</sequence>
</definitions>






[ESBJAVA-2894] MTOM attachments transferring is not working between 2 ESBs Created: 08/Jan/14  Updated: 28/Jul/15

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

Type: Bug Priority: Normal
Reporter: Irosha Sooriyawansha Assignee: Bhanuka Dissanayake
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   

MTOM attachments transferring is not working between 2 ESBs. There is an issue in identifying boundaries (Mime parts not found), when transferring files from 1st esb to 2nd esb. This is working for small files. But for large files its not working.






[ESBJAVA-2848] OSGi container at server start up is only initializing the first bundle it came across Created: 19/Dec/13  Updated: 25/Jul/15

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

Type: Bug Priority: Normal
Reporter: Chris Riley Assignee: shafreen anfar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Development


Attachments: File AIA_Test_Lab_Spring_Mediator_Issues.rtf     Zip Archive esb-security2.zip     Zip Archive uw_esb_security_mediator.zip    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

At design time of inSequence, when trying to add a Spring Extension, we encounter an exception stating that certain namespace handlers are unavailable. We have verified that the required jars are in the repository/components/lib directory.

The error occurs when WSO2 ESB tries to load the Spring configuration file.

I have included a text file with log entries and other specific configuration details. I have also included Maven projects for both our custom security jar(which is runnable in test mode without our database), and the current state of our Spring mediator project.



 Comments   
Comment by Chris Riley [ 19/Dec/13 ]

I discovered that when WSO2 ESB/Synapse was converting the spring-jdbc, spring-tx, etc. jars into OSGi bundles, it was not assigning a valid Bundle-SymbolicName and Bundle-Version for each converted jar. It was assigning them all the same values for these properties in the MANIFEST.MF files. Basically the OSGi container at server start up was only initializing the first bundle it came across which was spring-jdbc.

I went to the Spring bundle repository and fetched the 3.1.0.RELEASE OSGi bundles. Once I restarted synapse, the OSGi console reported that all of the spring modules were active.

Comment by Chris Riley [ 19/Dec/13 ]

Error originally received.

Comment by Chris Riley [ 19/Dec/13 ]

mediator definition.

Comment by Chris Riley [ 11/Mar/14 ]

Just wanted to see if this issue has been examined and if not when we could get some feedback on the issue.





[ESBJAVA-3484] Limiting Threads used by a single cron job/scheduled task Created: 28/Mar/14  Updated: 20/Jul/15

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

Type: Task Priority: Normal
Reporter: Shivam Sharma Assignee: prabath ariyarathna
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate

 Description   

Hi,

I am facing an issue where all the scheduler threads are being used by a single cron job, and that is causing other shceduled tasks to not run consistently and on time. I am wondering what the best way to deal with this is? I am looking to have a setting which basically says "allow one thread per cron job, and if a cron job is running and has one thread, dont let another one kick off." Can this be done through some sort of quartz setting? Or any other config?

Thanks



 Comments   
Comment by Shivam Sharma [ 03/Apr/14 ]

Any recommendations for this?

Appreciate your help.

Thanks
Shivam





[ESBJAVA-2905] [ Intermitant ] on some occasions HL7TransportSender Error while processing the response HL7 message java.lang.UnsupportedOperationException: Not yet implemented is thorwn Created: 10/Jan/14  Updated: 27/Jan/14

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

Type: Bug Priority: Normal
Reporter: Shavantha Weerasinghe Assignee: Ravi Undupitiya
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux
Java Version/Java VM :jdk1.6.0
Packs : wso2esb-4.8.1
DBMS: mysql
User Store:OpenLDAP
Browser : Firefox
Set up :proxy services


Attachments: XML File SFTPToHL7.xml     File bigmessage4.hl7    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

on some occasions HL7TransportSender Error while processing the response HL7 message java.lang.UnsupportedOperationException: Not yet implemented is thrown

steps
1.add a file to the ftp location
2.check the logs once the proxy reads the file

urn:uuid:CF2E261F366585B44C1389336245242, Direction: request, Envelope: <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><hl7:message xmlns:hl7="http://wso2.org/hl7"><ADT_A01 xmlns="urn:hl7-org:v2xml">
<MSH>
<MSH.1>|</MSH.1>
<MSH.2>^~\&</MSH.2>
<MSH.3>
<HD.1>EPIC</HD.1>
</MSH.3>
<MSH.4>
<HD.1>EPICADT</HD.1>
</MSH.4>
<MSH.5>
<HD.1>SMS</HD.1>
</MSH.5>
<MSH.6>
<HD.1>SMSADT</HD.1>
</MSH.6>
<MSH.7>
<TS.1>199912271408</TS.1>
</MSH.7>
<MSH.8>CHARRIS</MSH.8>
<MSH.9>
<MSG.1>ADT</MSG.1>
<MSG.2>A04</MSG.2>
</MSH.9>
<MSH.10>1817457</MSH.10>
<MSH.11>
<PT.1>D</PT.1>
</MSH.11>
<MSH.12>
<VID.1>2.5</VID.1>
</MSH.12>
</MSH>
<PID>
<PID.2>
<CX.1>0493575</CX.1>
<CX.4>
<HD.1>2</HD.1>
</CX.4>
<CX.5>ID 1</CX.5>
</PID.2>
<PID.3>
<CX.1>454721</CX.1>
</PID.3>
<PID.5>
<XPN.1>
<FN.1>DOE</FN.1>
</XPN.1>
<XPN.2>JOHN</XPN.2>
</PID.5>
<PID.6>
<XPN.1>
<FN.1>DOE</FN.1>
</XPN.1>
<XPN.2>JOHN</XPN.2>
</PID.6>
<PID.7>
<TS.1>19480203</TS.1>
</PID.7>
<PID.8>M</PID.8>
<PID.10>
<CE.1>B</CE.1>
</PID.10>
<PID.11>
<XAD.1>
<SAD.1>254 MYSTREET AVE</SAD.1>
</XAD.1>
<XAD.3>MYTOWN</XAD.3>
<XAD.4>OH</XAD.4>
<XAD.5>44123</XAD.5>
<XAD.6>USA</XAD.6>
</PID.11>
<PID.13>
<XTN.1>(216)123-4567</XTN.1>
</PID.13>
<PID.16>
<CE.1>M</CE.1>
</PID.16>
<PID.17>
<CE.1>NON</CE.1>
</PID.17>
<PID.18>
<CX.1>400003403</CX.1>
</PID.18>
<PID.18>
<CX.1>1129086</CX.1>
</PID.18>
</PID>
<NK1>
<NK1.2>
<XPN.1>
<FN.1>ROE</FN.1>
</XPN.1>
<XPN.2>MARIE</XPN.2>
</NK1.2>
<NK1.3>
<CE.1>SPO</CE.1>
</NK1.3>
<NK1.5>
<XTN.1>(216)123-4567</XTN.1>
</NK1.5>
<NK1.7>
<CE.1>EC</CE.1>
</NK1.7>
</NK1>
<PV1>
<PV1.2>O</PV1.2>
<PV1.3>
<PL.1>168 </PL.1>
</PV1.3>
<PV1.3>
<PL.1>219</PL.1>
</PV1.3>
<PV1.3>
<PL.1>C</PL.1>
</PV1.3>
<PV1.3>
<PL.1>PMA</PL.1>
</PV1.3>
<PV1.7>
<XCN.1>277</XCN.1>
<XCN.2>
<FN.1>ALLEN MYLASTNAME</FN.1>
</XCN.2>
<XCN.3>BONNIE</XCN.3>
</PV1.7>
<PV1.19>
<CX.1>2688684</CX.1>
</PV1.19>
<PV1.44>
<TS.1>199912271408</TS.1>
</PV1.44>
<PV1.50>
<CX.1>002376853</CX.1>
</PV1.50>
</PV1>
</ADT_A01></hl7:message></soapenv:Body></soapenv:Envelope>
[2014-01-10 12:14:05,355] INFO - TimeoutHandler This engine will expire all callbacks after : 120 seconds, irrespective of the timeout action, after the specified or optional timeout
[2014-01-10 12:14:05,405] ERROR - HL7TransportSender Error while processing the response HL7 message
java.lang.UnsupportedOperationException: Not yet implemented
at org.apache.axis2.description.OutOnlyAxisOperation.getMessage(OutOnlyAxisOperation.java:124)
at org.apache.axis2.transport.base.AbstractTransportSender.createResponseMessageContext(AbstractTransportSender.java:193)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.processResponse(HL7TransportSender.java:77)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.sendUsingEPR(HL7TransportSender.java:167)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.sendMessage(HL7TransportSender.java:67)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:626)
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)
[2014-01-10 12:14:05,407] INFO - AxisEngine [MessageContext: logID=24d6197df22ab61931c3d5412f5f3e384358ceec390ba5bf] Error while processing the response HL7 message
[2014-01-10 12:14:05,407] ERROR - AsyncCallback Error while processing the response HL7 message
org.apache.axis2.AxisFault: Error while processing the response HL7 message
at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:226)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.processResponse(HL7TransportSender.java:82)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.sendUsingEPR(HL7TransportSender.java:167)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.sendMessage(HL7TransportSender.java:67)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:626)
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)
Caused by: java.lang.UnsupportedOperationException: Not yet implemented
at org.apache.axis2.description.OutOnlyAxisOperation.getMessage(OutOnlyAxisOperation.java:124)
at org.apache.axis2.transport.base.AbstractTransportSender.createResponseMessageContext(AbstractTransportSender.java:193)
at org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender.processResponse(HL7TransportSender.java:77)
... 7 more






[ESBJAVA-2953] Error handling of Sequence (OnError) not working when using Sampling Message Processor Created: 24/Jan/14  Updated: 26/Jul/15

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

Type: Improvement Priority: Normal
Reporter: Wenod Pathirana Assignee: Priyadarssini Kishokumar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 4.5.1


Attachments: File SamplingJob.diff    
Severity: Major
Estimated Complexity: Moderate

 Description   

Error handling of Sequence mediator (OnError) not working when using Sampling Message Processor to send messages to the particular sequence.
Steps to reproduce:
1. Create a Sampling Message processor pointing to a sequence which has callout mediator.
2. Add onError sequence to the pointed sequence
3. Use the callout mediator inside the sequence and test the flow when the endpoint is unavailable.

Exception:

java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
at org.apache.synapse.mediators.builtin.CalloutMediator.mediate(CalloutMediator.java:155)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at org.apache.synapse.message.processors.sampler.SamplingJob$1.run(SamplingJob.java:80)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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)
TID: [0] [ESB] [2014-01-21 09:56:13,971] ERROR

{org.apache.synapse.message.processors.sampler.SamplingJob} - Error occurred while executing the message {org.apache.synapse.message.processors.sampler.SamplingJob}

org.apache.synapse.SynapseException: Error while performing the callout operation
at org.apache.synapse.mediators.builtin.CalloutMediator.handleFault(CalloutMediator.java:229)
at org.apache.synapse.mediators.builtin.CalloutMediator.mediate(CalloutMediator.java:157)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at org.apache.synapse.message.processors.sampler.SamplingJob$1.run(SamplingJob.java:80)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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: Connection refused
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
at org.apache.synapse.mediators.builtin.CalloutMediator.mediate(CalloutMediator.java:155)
... 9 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
... 19 more






[ESBJAVA-3020] ESB does not stop properly if dependent systems are not running Created: 25/Feb/14  Updated: 25/Feb/14

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

Type: Bug Priority: Normal
Reporter: Isabelle Mauny 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: No

 Description   

ESB depends on ActiveMQ / MB , which are not running, since I am shutting down. Note that the error message talks about server startup although I am shutting down. The retry time is multiplied by 2 each time... and there does not seem to be any exit , give-up at any point.

[2014-02-24 20:04:38,395] INFO - ServerManagement All deployment tasks have been completed.
[2014-02-24 20:04:38,395] INFO - ServerManagement Waiting for server task completion...
[2014-02-24 20:04:38,395] INFO - ServerManagement All server tasks have been completed.
[2014-02-24 20:04:38,395] INFO - CarbonServerManager Shutting down WSO2 Enterprise Service Bus...
[2014-02-24 20:04:38,397] INFO - CarbonServerManager Shutting down OSGi framework...
[2014-02-24 20:04:56,477] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now.
[2014-02-24 20:04:56,478] ERROR - JMSListener Connection attempt : 3 for JMS Provider failed. Next retry in 80 seconds

[2014-02-24 20:06:16,480] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now.
[2014-02-24 20:06:16,481] ERROR - JMSListener Connection attempt : 4 for JMS Provider failed. Next retry in 160 seconds
[2014-02-24 20:08:56,484] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now.
[2014-02-24 20:08:56,485] ERROR - JMSListener Connection attempt : 5 for JMS Provider failed. Next retry in 320 seconds






[ESBJAVA-2384] Error in building Passthrough stream when Entitlement Mediator is configured Created: 02/Aug/13  Updated: 25/Jul/15

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

Type: Bug Priority: Normal
Reporter: Pushpalanka Jayawardhana Assignee: madhuranga bandara
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WSO2 ESB 4.7.0
WSO2 IS 4.5.0
WSO2 AS 5.1.0
Ubuntu 12.04


Attachments: Zip Archive Resources_for_the_sample.zip    
Severity: Minor
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
Affects Docs:
Yes

 Description   

The scenario is as described in the article [1] . When the sample client is run following error is printed in ESB server side though the expected results are presented.

[2013-08-02 12:53:43,991] INFO - LogMediator LOG = ===================================In Sequence ============================
[2013-08-02 12:53:43,991] INFO - LogMediator Entitlement Phase = Before the entitlement phase
[2013-08-02 12:53:44,217] INFO - LogMediator Entitlement Phase = After the entitlement mediator
[2013-08-02 12:53:44,222] INFO - LogMediator LOG = ===================================Out Sequence ============================
[2013-08-02 12:53:44,222] ERROR - RelayUtils Error while building Passthrough stream
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col

{unknown-source}]: [1,0]
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129)
at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:116)
at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:91)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:302)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:92)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:71)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:239)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:443)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:222)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}

]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2116)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2022)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1114)
at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 19 more
[2013-08-02 12:53:44,224] ERROR - RelayUtils Error while building Passthrough stream
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col

{unknown-source}]: [1,0]
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129)
at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:116)
at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:91)
at org.apache.synapse.transport.passthru.util.RelaySecuirtyMessageBuilderDispatchandler.build(RelaySecuirtyMessageBuilderDispatchandler.java:165)
at org.apache.synapse.transport.passthru.util.RelaySecuirtyMessageBuilderDispatchandler.invoke(RelaySecuirtyMessageBuilderDispatchandler.java:101)
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:161)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:308)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:92)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:71)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:239)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:443)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:222)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}

]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2116)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2022)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1114)
at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 26 more
[2013-08-02 12:53:44,250] INFO - LogMediator LOG = ===================================In Sequence ============================
[2013-08-02 12:53:44,250] INFO - LogMediator Entitlement Phase = Before the entitlement phase
[2013-08-02 12:53:44,277] INFO - LogMediator Entitlement Phase = After the entitlement mediator
[2013-08-02 12:53:44,280] INFO - LogMediator LOG = ===================================Out Sequence ============================
[2013-08-02 12:53:44,301] INFO - LogMediator LOG = ===================================In Sequence ============================
[2013-08-02 12:53:44,302] INFO - LogMediator Entitlement Phase = Before the entitlement phase
[2013-08-02 12:53:44,326] ERROR - EntitlementMediator org.apache.synapse.SynapseException: User is not authorized to perform the action

The sample client, used entitlement policy and proxy configuration at ESB are attached here with.

[1] - http://wso2.com/library/articles/2011/08/finegrained-authorization-restful-services-xacml






[ESBJAVA-2507] NPE at EnterpriseBeanstalkManager.destroy in repository/components/default/configuration logs Created: 28/Sep/13  Updated: 21/Jul/15

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

Type: Bug Priority: Normal
Reporter: Isuru Perera Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 13.04, Java 6


Attachments: Text File 1379661276735.log    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

I noticed some errors inside configuration logs.

$ESB_HOME/repository/components/default/configuration/



 Comments   
Comment by Kasun Indrasiri [ 20/Jul/15 ]

Can you please provide more information on reproducing this issue. The provided information is incomplete.

Comment by Isuru Perera [ 20/Jul/15 ]

Hi Kasun,

AFAIR, there were no specific steps to reproduce this issue. But could you please check the logs in $ESB_HOME/repository/components/default/configuration/ and see whether there are any errors?

Comment by Isuru Perera [ 21/Jul/15 ]

I'm still seeing this issue in ESB 4.9.0-ALPHA5. Please start the ESB and stop. Then you will see the mentioned NPE in the log.

I downloaded wso2esb-4.9.0-ALPHA5.zip from [1].

[1] https://svn.wso2.org/repos/wso2/scratch/ESB/packs/21072015/





[ESBJAVA-2808] Reducing of free thread count when communicating with a JMS Queue Created: 29/Nov/13  Updated: 25/Jul/15

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

Type: Improvement Priority: Normal
Reporter: Irosha Sooriyawansha Assignee: shafreen anfar
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: No

 Description   

Passthrough sender thread is not notified, if a jms endpoint is getting a readtimeout from the response queue. In this case, the sender thread never getting finished and the calling client receive a timeout for this operation.






[ESBJAVA-3485] Add integration tests to verify MTOM use cases Created: 16/Oct/13  Updated: 28/Jul/15

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

Type: Improvement Priority: Normal
Reporter: Charitha Kankanamge Assignee: Bhanuka Dissanayake
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   

I think we have no tests to cover MTOM test scenarios in ESB. Please add automated tests






[ESBJAVA-2831] Unable to specify proxy to use with specific backend Created: 09/Dec/13  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Janis Jansons Assignee: Balasubramaniyam Senduran
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 6 hours
Time Spent: Not Specified
Original Estimate: 6 hours

Severity: Minor
Estimated Complexity: Moderate
Test cases added: No

 Description   

It seems like it's possible to specify HTTP proxy for the whole ESB to use but it is not possible to do it for each backend.



 Comments   
Comment by Kasun Indrasiri [ 20/Jul/15 ]

@Senduran : Is this supported with proxy profiles? Is that added to 4.9?





[ESBJAVA-2627] MTOM enabled in side ESB not propery building multipart/related header for back end message Created: 06/Nov/13  Updated: 28/Jul/15

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

Type: Bug Priority: Normal
Reporter: jayalal kahandawa Assignee: Bhanuka Dissanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 4 hours
Time Spent: Not Specified
Original Estimate: 4 hours
Environment:

Linux,Windows


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

 Description   

ESB not converting "text/xml" content type to "multipart/related" before sending the request to the backend server , when the client send the POST request to the ESB and inside the ESB proxy do Enable MTOM .






[ESBJAVA-2607] [ESB4.8] - Connection error for message store configured for Weblogic 10.3.4 Created: 01/Nov/13  Updated: 09/Jul/15

Status: Open
Project: WSO2 ESB
Component/s: Message Stores
Affects Version/s: 4.8.0 M4
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Iranga Muthuthanthri Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux
Java Version/Java VM :1.6.0_29
Packs : M5 Packs(01-11)
Weblogic :10.3.4
DBMS: H2
Browser : Firefox
Setup : Local


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

 Description   

Steps to reproduce
-----------------------
Source:http://docs.wso2.org/display/ESB480/Configure+with+WebLogic

Steps to reproduce
----------------------
1.) Create Message Store configured as follows

<messageStore class="org.apache.synapse.message.store.impl.jms.JmsStore"
name="SWISMS">
<parameter name="vender.class.loader.enabled">false</parameter>
<parameter name="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</parameter>
<parameter name="store.jms.cache.connection">false</parameter>
<parameter name="store.jms.password">admin123</parameter>
<parameter name="java.naming.provider.url">t3://localhost:7001</parameter>
<parameter name="store.jms.ConsumerReceiveTimeOut">300</parameter>
<parameter name="store.jms.connection.factory">jms/ConnectionFactory</parameter>
<parameter name="store.jms.username">weblogic</parameter>
<parameter name="store.jms.JMSSpecVersion">1.1</parameter>
<parameter name="store.jms.destination">jms/testQueue</parameter>
</messageStore>

Following Exception Noted:
----------------------------------------
3-11-01 11:09:39,411] INFO - CarbonAuthenticationUtil 'admin@carbon.super [-1234]' logged in at [2013-11-01 11:09:39,410+0530]
[2013-11-01 11:14:46,026] INFO - MessageStoreFactory Successfully created Message Store: SWISMS
[2013-11-01 11:14:46,236] ERROR - JmsStore Store [SWISMS] cannot create connection to the broker. Error:Authentication failure due to LoginException
[2013-11-01 11:14:46,236] WARN - JmsStore Store [SWISMS]. Starting with a faulty connection to the broker.
[2013-11-01 11:14:46,236] INFO - JmsStore Initialized Store [SWISMS]...



 Comments   
Comment by Miyuru Daminda [ 19/Nov/13 ]

Just to clear
does weblogic,admin123 valid username and password for broker?

Comment by Iranga Muthuthanthri [ 19/Nov/13 ]

Yes, otherwise believe that the Weblogic MQ Authentication would fail at server startup.





[ESBJAVA-2372] File Encoding problem in Sequence Mediator ( UTF-8 Conversion error in windows env ) Created: 25/Jul/13  Updated: 25/Jul/13

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

Type: Bug Priority: Normal
Reporter: jayalal kahandawa Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7


Attachments: Text File RefProxyFile_SequenceMediator_Error.log     XML File wronginput_002_GPV.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

We have a proxy configuration which reads a file and then calls a webservice. The following configuration shows only the relevant parts for the description of the problem:

<proxy xmlns="http://ws.apache.org/ns/synapse" name="RefProxyFile" transports="vfs" statistics="enable" trace="enable" startOnLoad="true">
<target>
<inSequence>
<log category="INFO" level="full" separator="," />
<send>
...
</send>
</inSequence>
<outSequence>
...
</outSequence>
<faultSequence>
...
</faultSequence>
</target>
<parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
<parameter name="transport.PollInterval">10</parameter>
<parameter name="transport.vfs.FileURI">file:///C:/temp/in&lt;/parameter>
<parameter name="transport.vfs.MoveAfterProcess">file:///C:/temp/processing&lt;/parameter>
<parameter name="transport.vfs.FailedRecordNextRetryDuration">1000</parameter>
<parameter name="transport.vfs.MoveAfterFailure">file:///C:/temp/failed_io&lt;/parameter>
<parameter name="transport.vfs.Locking">true</parameter>
<parameter name="transport.vfs.FileNamePattern">*.xml</parameter>
<parameter name="transport.vfs.ContentType">application/xml;charset="UTF-8"</parameter>
<parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
<parameter name="transport.vfs.MaxRetryCount">2</parameter>
</proxy>

In the normal case, if the encoding of the input file is wrong, then the vfs-listener catches the exception and moves the file (transport.vfs.MoveAfterFailure).
In some cases, the vfs-listener can read the input file, but the SequenceMediator crashes because of a wrong encoding. This is the case with the attached xml-file "wronginput_002_GPV.xml".
Exception:
ERROR - SequenceMediator Error while building message
[com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 start byte 0xfc (at char #136, byte #127)
at com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)

The complete Stacktrace is in attached File "RefProxyFile_SequenceMediator_Error.log".

If this error happens, the inSequence or faultSequence is not called, so in the proxy configuration it is not possible to react on it.
The expected behavior is, that all encoding problems with input files are detected by the vfs-listener and the action "transport.vfs.MoveAfterFailure" processed.
Is this a bug in the vfs-listener?






[ESBJAVA-4115] WSO2 Identity Management mail sender doesn't work with Amazon Simple Email Service Created: 02/Jul/13  Updated: 25/Aug/15

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

Type: Bug Priority: Normal
Reporter: Suresh Attanayake 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   

org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager}
TID: [0] [IS] [2013-06-27 20:51:13,392] DEBUG

{org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager} - Searching for (&(objectClass=person)(mail=admin@example.com)) {org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager}

TID: [0] [IS] [2013-06-27 20:51:13,399] DEBUG

{org.wso2.carbon.identity.mgt.util.Utils} - Password is updated for user: mhs_bob@example.com {org.wso2.carbon.identity.mgt.util.Utils}

TID: [0] [IS] [2013-06-27 20:51:13,834] ERROR

{org.apache.axis2.transport.mail.MailTransportSender} - Error creating mail message or sending it to the configured server {org.apache.axis2.transport.mail.MailTransportSender}

com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal header 'SOAPAction'.

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1215)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:586)
at javax.mail.Transport.send0(Transport.java:169)
at javax.mail.Transport.send(Transport.java:98)
at org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:489)
at org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
at org.wso2.carbon.identity.mgt.mail.DefaultEmailSendingModule.sendEmail(DefaultEmailSendingModule.java:95)
at org.wso2.carbon.identity.mgt.mail.AbstractEmailSendingModule.notifyUser(AbstractEmailSendingModule.java:81)
at org.wso2.carbon.identity.mgt.NotificationSendingModule.run(NotificationSendingModule.java:16)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [IS] [2013-06-27 20:51:13,834] ERROR

{org.apache.axis2.transport.mail.MailTransportSender} - Error creating mail message or sending it to the configured server {org.apache.axis2.transport.mail.MailTransportSender}

com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal header 'SOAPAction'.

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1215)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:586)
at javax.mail.Transport.send0(Transport.java:169)
at javax.mail.Transport.send(Transport.java:98)
at org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:489)
at org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
at org.wso2.carbon.identity.mgt.mail.DefaultEmailSendingModule.sendEmail(DefaultEmailSendingModule.java:95)
at org.wso2.carbon.identity.mgt.mail.AbstractEmailSendingModule.notifyUser(AbstractEmailSendingModule.java:81)
at org.wso2.carbon.identity.mgt.NotificationSendingModule.run(NotificationSendingModule.java:16)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [IS] [2013-06-27 20:51:13,841] ERROR

{org.apache.axis2.transport.mail.MailTransportSender} - Error generating mail message {org.apache.axis2.transport.mail.MailTransportSender}

org.apache.axis2.AxisFault: Error creating mail message or sending it to the configured server
at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:226)
at org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:500)
at org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
at org.wso2.carbon.identity.mgt.mail.DefaultEmailSendingModule.sendEmail(DefaultEmailSendingModule.java:95)
at org.wso2.carbon.identity.mgt.mail.AbstractEmailSendingModule.notifyUser(AbstractEmailSendingModule.java:81)
at org.wso2.carbon.identity.mgt.NotificationSendingModule.run(NotificationSendingModule.java:16)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal header 'SOAPAction'.

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1215)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:586)
at javax.mail.Transport.send0(Transport.java:169)
at javax.mail.Transport.send(Transport.java:98)
at org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:489)
... 16 more
TID: [0] [IS] [2013-06-27 20:51:13,841] ERROR

{org.apache.axis2.transport.mail.MailTransportSender} - Error generating mail message