Re: [Dev] Error while Building Project for Microservice-GW
On Fri, Jun 29, 2018 at 8:33 PM, Bhashinee Nirmali wrote: > Hi Dushan, > > We have experienced a similar issue with an older java version. If your > java version is less than 8u60, can you try upgrading the java version. > Please refer mail thread [1]. If that is the case, you should get the same > issue, when you try the following command [2]. > > [1] PKCS12 requires JDK 8u60 or above version > [2] keytool -list -keystore -v > Yes that did the trick thanks Bhashinee!!! > > Thanks, > Bhashinee > > On Sat, Jun 30, 2018 at 8:15 AM Rukshan Premathunga > wrote: > >> Hi Dushan, >> >> We released Micro Gateway Toolkit 2.5.0-Beta2[1] yesterday. Can you >> please download and check on that and let us know. >> >> [1] WSO2 API Manager Micro Gateway Toolkit 2.5.0-Beta2 Released! >> >> Thanks and Regards >> >> On Fri, Jun 29, 2018 at 11:14 PM, Dushan Abeyruwan >> wrote: >> >>> >>> >>> On Fri, Jun 29, 2018 at 10:41 AM, Dushan Abeyruwan >>> wrote: >>> >>>> Folks, >>>> This is what I have tried with wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT >>>> >>>> w-toolkit-2.5.0-SNAPSHOT/lib/platform >>>> MICROGW_TOOLKIT_HOME environment variable is set to >>>> /Users/xx/xx/wso2/dev/xxx/wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT >>>> Enter Username: >>>> admin >>>> Enter Password for admin: >>>> >>>> Enter APIM base URL [https://localhost:9443/]: >>>> >>>> Enter Trust store location: [lib/platform/bre/security/ >>>> ballerinaTruststore.p12] >>>> >>>> Enter Trust store password: [ use default? ] >>>> >>>> micro-gw: Internal error occurred while executing command. >>>> xx-xx-Pro-3:APIM250 dushan$ >>>> >>>> The error. >>>> >>>> Caused by: java.net.SocketException: >>>> java.security.NoSuchAlgorithmException: >>>> Error constructing implementation (algorithm: Default, provider: SunJSSE, >>>> class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) >>>> at javax.net.ssl.DefaultSSLSocketFactory.throwException( >>>> SSLSocketFactory.java:248) >>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory. >>>> java:255) >>>> at sun.net.www.protocol.https.HttpsClient.createSocket( >>>> HttpsClient.java:409) >>>> at sun.net.NetworkClient.doConnect(NetworkClient.java:162) >>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) >>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) >>>> at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:275) >>>> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) >>>> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnec >>>> tion.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) >>>> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0( >>>> HttpURLConnection.java:1104) >>>> at sun.net.www.protocol.http.HttpURLConnection.plainConnect( >>>> HttpURLConnection.java:998) >>>> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnec >>>> tion.connect(AbstractDelegateHttpsURLConnection.java:177) >>>> at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0( >>>> HttpURLConnection.java:1282) >>>> at sun.net.www.protocol.http.HttpURLConnection.getOutputStream( >>>> HttpURLConnection.java:1257) >>>> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream( >>>> HttpsURLConnectionImpl.java:250) >>>> at org.wso2.apimgt.gateway.cli.oauth.OAuthServiceImpl. >>>> generateClientIdAndSecret(OAuthServiceImpl.java:103) >>>> ... 4 more >>>> Caused by: java.security.NoSuchAlgorithmException: Error constructing >>>> implementation (algorithm: Default, provider: SunJSSE, class: >>>> sun.security.ssl.SSLContextImpl$DefaultSSLContext) >>>> at java.security.Provider$Service.newInstance(Provider.java:1617) >>>> at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) >>>> at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) >>>> at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) >>>> at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) >>>> at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:122) >>>> at javax.net.ssl.HttpsURLConnection.getDefaul
Re: [Dev] Error while Building Project for Microservice-GW
On Fri, Jun 29, 2018 at 10:41 AM, Dushan Abeyruwan wrote: > Folks, > This is what I have tried with wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT > > w-toolkit-2.5.0-SNAPSHOT/lib/platform > MICROGW_TOOLKIT_HOME environment variable is set to > /Users/xx/xx/wso2/dev/xxx/wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT > Enter Username: > admin > Enter Password for admin: > > Enter APIM base URL [https://localhost:9443/]: > > Enter Trust store location: [lib/platform/bre/security/bal > lerinaTruststore.p12] > > Enter Trust store password: [ use default? ] > > micro-gw: Internal error occurred while executing command. > xx-xx-Pro-3:APIM250 dushan$ > > The error. > > Caused by: java.net.SocketException: java.security.NoSuchAlgorithmException: > Error constructing implementation (algorithm: Default, provider: SunJSSE, > class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) > at javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSock > etFactory.java:248) > at javax.net.ssl.DefaultSSLSocketFactory.createSocket( > SSLSocketFactory.java:255) > at sun.net.www.protocol.https.HttpsClient.createSocket(HttpsCli > ent.java:409) > at sun.net.NetworkClient.doConnect(NetworkClient.java:162) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) > at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:275) > at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnectio > n.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Ht > tpURLConnection.java:1104) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Htt > pURLConnection.java:998) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnectio > n.connect(AbstractDelegateHttpsURLConnection.java:177) > at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0 > (HttpURLConnection.java:1282) > at sun.net.www.protocol.http.HttpURLConnection.getOutputStream( > HttpURLConnection.java:1257) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputS > tream(HttpsURLConnectionImpl.java:250) > at org.wso2.apimgt.gateway.cli.oauth.OAuthServiceImpl.generateC > lientIdAndSecret(OAuthServiceImpl.java:103) > ... 4 more > Caused by: java.security.NoSuchAlgorithmException: Error constructing > implementation (algorithm: Default, provider: SunJSSE, class: > sun.security.ssl.SSLContextImpl$DefaultSSLContext) > at java.security.Provider$Service.newInstance(Provider.java:1617) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) > at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) > at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) > at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:122) > at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory( > HttpsURLConnection.java:332) > at javax.net.ssl.HttpsURLConnection.(HttpsURLConnection.java:289) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.(Htt > psURLConnectionImpl.java:85) > at sun.net.www.protocol.https.Handler.openConnection(Handler.java:62) > at sun.net.www.protocol.https.Handler.openConnection(Handler.java:57) > at java.net.URL.openConnection(URL.java:972) > at org.wso2.apimgt.gateway.cli.oauth.OAuthServiceImpl.generateC > lientIdAndSecret(OAuthServiceImpl.java:94) > ... 4 more > Caused by: java.io.IOException: Invalid keystore format > at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) > at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) > at java.security.KeyStore.load(KeyStore.java:1445) > at sun.security.ssl.TrustManagerFactoryImpl.getCacertsKeyStore( > TrustManagerFactoryImpl.java:226) > at sun.security.ssl.SSLContextImpl$DefaultSSLContext.getDefault > TrustManager(SSLContextImpl.java:767) > at sun.security.ssl.SSLContextImpl$DefaultSSLContext.(SSL > ContextImpl.java:733) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native > ConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De > legatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at java.security.Provider$Service.newInstance(Provider.java:1595) > ... 16 more > > > [+add dev] > > -- > Dushan Abeyruwan | Architect > Technical Support,MV > PMC Member Apache Synpase > WSO2 Inc. http://wso2.com/ > Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* > Li
[Carbon-dev] Error while Building Project for Microservice-GW
Folks, This is what I have tried with wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT w-toolkit-2.5.0-SNAPSHOT/lib/platform MICROGW_TOOLKIT_HOME environment variable is set to /Users/xx/xx/wso2/dev/xxx/wso2am-micro-gw-toolkit-2.5.0-SNAPSHOT Enter Username: admin Enter Password for admin: Enter APIM base URL [https://localhost:9443/]: Enter Trust store location: [lib/platform/bre/security/ ballerinaTruststore.p12] Enter Trust store password: [ use default? ] micro-gw: Internal error occurred while executing command. xx-xx-Pro-3:APIM250 dushan$ The error. Caused by: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) at javax.net.ssl.DefaultSSLSocketFactory.throwException( SSLSocketFactory.java:248) at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory. java:255) at sun.net.www.protocol.https.HttpsClient.createSocket(HttpsClient.java:409) at sun.net.NetworkClient.doConnect(NetworkClient.java:162) at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:275) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnec tion.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0( HttpURLConnection.java:1104) at sun.net.www.protocol.http.HttpURLConnection.plainConnect( HttpURLConnection.java:998) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect( AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0( HttpURLConnection.java:1282) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream( HttpURLConnection.java:1257) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream( HttpsURLConnectionImpl.java:250) at org.wso2.apimgt.gateway.cli.oauth.OAuthServiceImpl. generateClientIdAndSecret(OAuthServiceImpl.java:103) ... 4 more Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) at java.security.Provider$Service.newInstance(Provider.java:1617) at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:122) at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory( HttpsURLConnection.java:332) at javax.net.ssl.HttpsURLConnection.(HttpsURLConnection.java:289) at sun.net.www.protocol.https.HttpsURLConnectionImpl.( HttpsURLConnectionImpl.java:85) at sun.net.www.protocol.https.Handler.openConnection(Handler.java:62) at sun.net.www.protocol.https.Handler.openConnection(Handler.java:57) at java.net.URL.openConnection(URL.java:972) at org.wso2.apimgt.gateway.cli.oauth.OAuthServiceImpl. generateClientIdAndSecret(OAuthServiceImpl.java:94) ... 4 more Caused by: java.io.IOException: Invalid keystore format at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) at java.security.KeyStore.load(KeyStore.java:1445) at sun.security.ssl.TrustManagerFactoryImpl.getCacertsKeyStore( TrustManagerFactoryImpl.java:226) at sun.security.ssl.SSLContextImpl$DefaultSSLContext.getDefaultTrustManager( SSLContextImpl.java:767) at sun.security.ssl.SSLContextImpl$DefaultSSLContext.( SSLContextImpl.java:733) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance( NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.security.Provider$Service.newInstance(Provider.java:1595) ... 16 more -- Dushan Abeyruwan | Architect Technical Support,MV PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-987-1348 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Dev] [EMM] Value too long for column "DEVICE_MODEL VARCHAR(45) DEFAULT NULL": "'Google Nexus 6 - 5.0.0 - API 21 - 1440x2560_1-2'
[2017-04-29 10:08:16,113] [IoT-Core] ERROR - DeviceTypePluginDAO Error occurred while adding the device '000' to the AD_DEVICE db. org.h2.jdbc.JdbcSQLException: Value too long for column "DEVICE_MODEL VARCHAR(45) DEFAULT NULL": "'Google Nexus 6 - 5.0.0 - API 21 - 1440x2560_1-2' (47)"; SQL statement: INSERT INTO AD_DEVICE(DEVICE_ID , GCM_TOKEN, DEVICE_INFO, IMEI, IMSI, OS_VERSION, DEVICE_MODEL, VENDOR, LATITUDE, LONGITUDE, SERIAL, MAC_ADDRESS, DEVICE_NAME, OS_BUILD_DATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-175] at org.h2.message.DbException.getJdbcSQLException(DbException.java:332) at org.h2.message.DbException.get(DbException.java:172) at org.h2.table.Column.validateConvertUpdateSequence(Column.java:317) at org.h2.table.Table.validateConvertUpdate -- Dushan Abeyruwan | Senior Technical Lead Technical Support,MV PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
hings and it >>>>>>>>>>> led me >>>>>>>>>>> to select and find more about this project. I was an intern at WSO2 >>>>>>>>>>> and I >>>>>>>>>>> have a keen knowledge about WSO2ESB, inbound endpoints and >>>>>>>>>>> transports since >>>>>>>>>>> my internship project was related to them. >>>>>>>>>>> >>>>>>>>>>> Regarding this project, I have already started to follow the >>>>>>>>>>> WSO2 doc about current implementation of WSO2 ESB for IBM >>>>>>>>>>> WebSphere MQ >>>>>>>>>>> through JMS transport. I would be grateful if you can give me some >>>>>>>>>>> suggestions and materials to understand the project more. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> -- >>>>>>>>>>> Chanaka Balasooriya >>>>>>>>>>> Undergraduate >>>>>>>>>>> Department of Computer Science and Engineering >>>>>>>>>>> University of Moratuwa >>>>>>>>>>> +9471 294 7898 <071%20294%207898> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> >>>>>>>>>> Malaka Silva >>>>>>>>>> Associate Director / Architect >>>>>>>>>> M: +94 777 219 791 <+94%2077%20721%209791> >>>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>>> Fax :94 11 2145300 <011%202%20145300> >>>>>>>>>> Skype : malaka.sampath.silva >>>>>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>>>>>>>> Blog : http://mrmalakasilva.blogspot.com/ >>>>>>>>>> >>>>>>>>>> WSO2, Inc. >>>>>>>>>> lean . enterprise . middleware >>>>>>>>>> https://wso2.com/signature >>>>>>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>>>>>> https://store.wso2.com/store/ >>>>>>>>>> >>>>>>>>>> Don't make Trees rare, we should keep them with care >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Chanaka Balasooriya >>>>>>>>> Undergraduate >>>>>>>>> Department of Computer Science and Engineering >>>>>>>>> University of Moratuwa >>>>>>>>> +9471 294 7898 <071%20294%207898> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Malaka Silva >>>>>>>> Associate Director / Architect >>>>>>>> M: +94 777 219 791 <+94%2077%20721%209791> >>>>>>>> Tel : 94 11 214 5345 >>>>>>>> Fax :94 11 2145300 <011%202%20145300> >>>>>>>> Skype : malaka.sampath.silva >>>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>>>>>> Blog : http://mrmalakasilva.blogspot.com/ >>>>>>>> >>>>>>>> WSO2, Inc. >>>>>>>> lean . enterprise . middleware >>>>>>>> https://wso2.com/signature >>>>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>>>> https://store.wso2.com/store/ >>>>>>>> >>>>>>>> Don't make Trees rare, we should keep them with care >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Chanaka Balasooriya >>>>>>> Undergraduate >>>>>>> Department of Computer Science and Engineering >>>>>>> University of Moratuwa >>>>>>> +9471 294 7898 <071%20294%207898> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Malaka Silva >>>>>> Associate Director / Architect >>>>>> M: +94 777 219 791 <+94%2077%20721%209791> >>>>>> Tel : 94 11 214 5345 >>>>>> Fax :94 11 2145300 <011%202%20145300> >>>>>> Skype : malaka.sampath.silva >>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>>>> Blog : http://mrmalakasilva.blogspot.com/ >>>>>> >>>>>> WSO2, Inc. >>>>>> lean . enterprise . middleware >>>>>> https://wso2.com/signature >>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>> https://store.wso2.com/store/ >>>>>> >>>>>> Don't make Trees rare, we should keep them with care >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Chanaka Balasooriya >>>>> Undergraduate >>>>> Department of Computer Science and Engineering >>>>> University of Moratuwa >>>>> +9471 294 7898 <071%20294%207898> >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Associate Director / Architect >>>> M: +94 777 219 791 <+94%2077%20721%209791> >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 <011%202%20145300> >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> https://wso2.com/signature >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Don't make Trees rare, we should keep them with care >>>> >>> >>> >>> >>> -- >>> Chanaka Balasooriya >>> Undergraduate >>> Department of Computer Science and Engineering >>> University of Moratuwa >>> +9471 294 7898 <071%20294%207898> >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Associate Director / Architect >> M: +94 777 219 791 <+94%2077%20721%209791> >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> https://wso2.com/signature >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> > > > > -- > Chanaka Balasooriya > Undergraduate > Department of Computer Science and Engineering > University of Moratuwa > +9471 294 7898 <+94%2071%20294%207898> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dushan Abeyruwan | Senior Technical Lead Technical Support,MV PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IOT] [wso2iots-1.0.0-alpha] Continues errors getting print after sometimes without valid reason
Hi Devs, $subject [2016-06-08 11:55:49,431] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:49,431] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:49,443] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:49,457] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:49,458] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:49,893] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:49,900] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:49,900] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:49,917] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:49,924] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:49,924] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:50,031] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:50,041] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:50,041] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:50,058] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:50,068] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:50,069] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:50,395] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:50,403] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense [2016-06-08 11:55:50,403] WARN - ProtocolProcessor MQTTAuthorizationSubject for client ID -9708-6bd5--99d603a9:android_sense is not removed since the entry does not exist [2016-06-08 11:55:50,411] WARN - ProtocolProcessor Andes does not support last will operation [2016-06-08 11:55:50,419] INFO - ProtocolProcessor Lost connection with client -9708-6bd5--99d603a9:android_sense https://github.com/wso2/product-iots/releases/tag/v1.0.0-alpha -- Dushan Abeyruwan | Senior Technical Lead Technical Support,MV PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while running APIM profiles
Hi
Issue was resolved, thanks Chamila !
Cheers,
Dushan
On Sun, May 22, 2016 at 7:44 PM, Dushan Abeyruwan <dus...@wso2.com> wrote:
> I'm sorry which file [1] you mean?
> in documentation it does not say which file i need to do these changes and
> common.yaml has this AFAIU
>
> For instance gateway-worker only has
>
> # Copyright (c) 2016, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
> #
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
>
> ---
> wso2::mgt_hostname: mgt.gw.dev.wso2.org
> wso2::hostname: gw.dev.wso2.org
>
> wso2::clustering:
> enabled: true
> domain: gw.am.wso2.domain
> sub_domain: worker
> local_member_host: "%{::ipaddress}"
> local_member_port: 4000
> membership_scheme: wka
> wka:
> members:
> -
> hostname: 192.168.100.5
> port: 4000
> -
> hostname: 192.168.100.6
> port: 4000
>
> wso2::dep_sync:
> enabled: true
> auto_checkout: true
> auto_commit: false
> repository_type: svn
> svn:
> url: http://svn.gw.am.dev.wso2.org/gateway-artifacts
> user: svnuser
> password: password
> append_tenant_id: true
>
> wso2::registry_mounts:
> wso2_config_db:
>path: /_system/config
>target_path: /_system/config/apim-gw
>read_only: true
>registry_root: /
>enable_cache: true
>
> wso2_gov_db:
>path: /_system/governance
>target_path: /_system/governance
>read_only: true
>registry_root: /
>enable_cache: true
>
> [1] https://github.com/wso2/puppet-modules/tree/master/modules/wso2am
>
> On Sun, May 22, 2016 at 6:23 PM, Chamila De Alwis <chami...@wso2.com>
> wrote:
>
>> Hi Dushan,
>>
>> It seems you have not enabled the data sources needed to configure the
>> registry mounting. Please refer the module README. It lists which entries
>> should be uncommented and changed in order to configure distributed
>> profiles.
>>
>> [1] - https://github.com/wso2/puppet-modules/tree/master/modules/wso2am
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Mon, May 23, 2016 at 2:11 AM, Dushan Abeyruwan <dus...@wso2.com>
>> wrote:
>>
>>> compelete error log
>>>
>>> root@dushan-b:/opt# ./setup.sh
>>> #
>>>Starting cleanup
>>> #
>>> #
>>>Setting up environment
>>> #
>>> reading
>>> product_name=wso2am product_version=1.10.0 product_profile=gateway-worker
>>> reading end
>>> #
>>> Installing
>>> #
>>> Info: Retrieving plugin
>>> Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
>>> Info: Loading facts in /var/lib/puppet/lib/facter/service_provider.rb
>>> Info: Loading facts in /var/lib/puppet/lib/facter/package_provider.rb
>>> Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
>>> Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
>>> Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
>>> Error: Could not retrieve catalog from remote server: Error 400 on
>>> SERVER: Failed to parse template
>>> wso2am/1.10.0/repository/conf/registry.xml.erb:
>>> Filepath:
>>> /etc/puppet/modules/wso2am/templates/1.10.0/repository/conf/registry.xml.erb
>>> Line: 37
>>> Detail: undefined method `[]' for nil:NilClass
>>> at /etc/puppet/modules/wso2base/manifests/push_templates.pp:23 on node
>>> dushan-b.openstacklocal
>>> Warning: Not using cache on failed catalog
>>> Error: Could not retrieve
Re: [Dev] Error while running APIM profiles
I'm sorry which file [1] you mean?
in documentation it does not say which file i need to do these changes and
common.yaml has this AFAIU
For instance gateway-worker only has
# Copyright (c) 2016, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
---
wso2::mgt_hostname: mgt.gw.dev.wso2.org
wso2::hostname: gw.dev.wso2.org
wso2::clustering:
enabled: true
domain: gw.am.wso2.domain
sub_domain: worker
local_member_host: "%{::ipaddress}"
local_member_port: 4000
membership_scheme: wka
wka:
members:
-
hostname: 192.168.100.5
port: 4000
-
hostname: 192.168.100.6
port: 4000
wso2::dep_sync:
enabled: true
auto_checkout: true
auto_commit: false
repository_type: svn
svn:
url: http://svn.gw.am.dev.wso2.org/gateway-artifacts
user: svnuser
password: password
append_tenant_id: true
wso2::registry_mounts:
wso2_config_db:
path: /_system/config
target_path: /_system/config/apim-gw
read_only: true
registry_root: /
enable_cache: true
wso2_gov_db:
path: /_system/governance
target_path: /_system/governance
read_only: true
registry_root: /
enable_cache: true
[1] https://github.com/wso2/puppet-modules/tree/master/modules/wso2am
On Sun, May 22, 2016 at 6:23 PM, Chamila De Alwis <chami...@wso2.com> wrote:
> Hi Dushan,
>
> It seems you have not enabled the data sources needed to configure the
> registry mounting. Please refer the module README. It lists which entries
> should be uncommented and changed in order to configure distributed
> profiles.
>
> [1] - https://github.com/wso2/puppet-modules/tree/master/modules/wso2am
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Mon, May 23, 2016 at 2:11 AM, Dushan Abeyruwan <dus...@wso2.com> wrote:
>
>> compelete error log
>>
>> root@dushan-b:/opt# ./setup.sh
>> #
>>Starting cleanup
>> #
>> #
>>Setting up environment
>> #
>> reading
>> product_name=wso2am product_version=1.10.0 product_profile=gateway-worker
>> reading end
>> #
>> Installing
>> #
>> Info: Retrieving plugin
>> Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/service_provider.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/package_provider.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
>> Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Failed to parse template
>> wso2am/1.10.0/repository/conf/registry.xml.erb:
>> Filepath:
>> /etc/puppet/modules/wso2am/templates/1.10.0/repository/conf/registry.xml.erb
>> Line: 37
>> Detail: undefined method `[]' for nil:NilClass
>> at /etc/puppet/modules/wso2base/manifests/push_templates.pp:23 on node
>> dushan-b.openstacklocal
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>> root@dushan-b:/opt# exit
>> exit
>> ubuntu@dushan-b:~$ exit
>>
>> On Sun, May 22, 2016 at 12:49 PM, Dushan Abeyruwan <dus...@wso2.com>
>> wrote:
>>
>>> Hi Devs,
>>> Getting following error while running profiles other than the default,
>>> what could be the reason here?
>>>
>>> I'm using following script [1], as I mentioned default profile seems
>>> working fine.
>>>
>>> *Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb*
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Error: Could not retrie
Re: [Dev] Error while running APIM profiles
compelete error log root@dushan-b:/opt# ./setup.sh # Starting cleanup # # Setting up environment # reading product_name=wso2am product_version=1.10.0 product_profile=gateway-worker reading end # Installing # Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/service_provider.rb Info: Loading facts in /var/lib/puppet/lib/facter/package_provider.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template wso2am/1.10.0/repository/conf/registry.xml.erb: Filepath: /etc/puppet/modules/wso2am/templates/1.10.0/repository/conf/registry.xml.erb Line: 37 Detail: undefined method `[]' for nil:NilClass at /etc/puppet/modules/wso2base/manifests/push_templates.pp:23 on node dushan-b.openstacklocal Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run root@dushan-b:/opt# exit exit ubuntu@dushan-b:~$ exit On Sun, May 22, 2016 at 12:49 PM, Dushan Abeyruwan <dus...@wso2.com> wrote: > Hi Devs, > Getting following error while running profiles other than the default, > what could be the reason here? > > I'm using following script [1], as I mentioned default profile seems > working fine. > > *Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb* > > > > > > > *Error: Could not retrieve catalog from remote server: Error 400 on > SERVER: Failed to parse template > wso2am/1.10.0/repository/conf/registry.xml.erb: Filepath: > /etc/puppet/modules/wso2am/templates/1.10.0/repository/conf/registry.xml.erb > Line: > 37 Detail: undefined method `[]' for nil:NilClassat > /etc/puppet/modules/wso2base/manifests/push_templates.pp:23 on node > dushan-b.openstacklocalWarning: Not using cache on failed catalogError: > Could not retrieve catalog; skipping run* > > [1]https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2%2Fpuppet-modules%2Freleases%2Ftag%2Fv2.0.0-rc1=D=1=AFQjCNHA0b950X7MovnpUcIVqXTHQUfaaQ> > > -- > Dushan Abeyruwan | Technical Lead > > PMC Member Apache Synpase > WSO2 Inc. http://wso2.com/ > Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* > LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan > <https://www.linkedin.com/in/dushanabeyruwan>* > Mobile:(001)408-791-9312 > > -- Dushan Abeyruwan | Technical Lead PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while running APIM profiles
Hi Devs, Getting following error while running profiles other than the default, what could be the reason here? I'm using following script [1], as I mentioned default profile seems working fine. *Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb* *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template wso2am/1.10.0/repository/conf/registry.xml.erb: Filepath: /etc/puppet/modules/wso2am/templates/1.10.0/repository/conf/registry.xml.erb Line: 37 Detail: undefined method `[]' for nil:NilClassat /etc/puppet/modules/wso2base/manifests/push_templates.pp:23 on node dushan-b.openstacklocalWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run* [1]https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1 <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fwso2%2Fpuppet-modules%2Freleases%2Ftag%2Fv2.0.0-rc1=D=1=AFQjCNHA0b950X7MovnpUcIVqXTHQUfaaQ> -- Dushan Abeyruwan | Technical Lead PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [DEV][ESB]Access URI, Headers and Query params in Java script
Hi The $subject, I guess this can be a valid use case, anyway, it seems [1] having setProperty, but ideally, that should have improved to select whichever property according to developer preferred scope. Can we consider this in our roadmap? [1] https://github.com/wso2/wso2-synapse/blob/master/modules/extensions/src/main/java/org/apache/synapse/mediators/bsf/ScriptMessageContext.java -- Dushan Abeyruwan | Technical Lead PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* LinkedIn:*https://www.linkedin.com/in/dushanabeyruwan <https://www.linkedin.com/in/dushanabeyruwan>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 ESB 5.0.0 - Milestone 2 Released!
Hi Have seen mediation debugging feature in docs (others audience: please note, doc are still at a draft stage so not visible to public) anyway, is there correspondent DevS version available? On Mon, Feb 15, 2016 at 4:09 AM, Vijitha Ekanayake <vijit...@wso2.com> wrote: > *WSO2 ESB 5.0.0-Milestone 2 Released* > > ESB Team is pleased to announce the WSO2 ESB 5.0.0 - Milestone 2 Release. > It contains following improvement and bug fixes. > > Bug > >- [ESBJAVA-4416 <https://wso2.org/jira/browse/ESBJAVA-4416>] - ESB >Management console shows Invalid product version. >- [ESBJAVA-4417 <https://wso2.org/jira/browse/ESBJAVA-4415>] - ESB >server terminal shows Invalid product version. > > Improvement > >- [ESBJAVA-4415 <https://wso2.org/jira/browse/ESBJAVA-4415>] - SSL >support for MQTT inbound. > > > > The distribution is available to download at [1]. > > [1] > https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/ > > - WSO2 ESB Team - > > -- > Vijitha Ekanayake > Software Engineer*, *WSO2, Inc.; http://wso2.com/ > Mobile : +94 777 24 73 39 | +94 718 74 44 08 > lean.enterprise.middleware > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dushan Abeyruwan | Technical Lead PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SSL configuration of the Websphere MQ Java client need certificate of the CA.
-- >> 11/21/2015 09:59:32 - Process(6000.4) User(MUSR_MQADMIN) >> Program(amqrmppa.exe) >> Host(KASUN-PC) Installation(Installation1) >> VRMF(7.5.0.2) QMgr(SSLQM) >> >> AMQ9492: The TCP/IP responder program encountered an error. >> >> EXPLANATION: >> The responder program was started but detected an error. >> >> The host name was 'kasun-PC (127.0.0.1)'; in some cases the host name >> cannot be >> determined and so is shown as ''. >> ACTION: >> Look at previous error messages in the error files to determine the error >> encountered by the responder program. >> - amqrmrsa.c : 889 >> >> >> >> >> >> -- >> Thanks & Regards, >> Kirishanthy >> Associate Software Engineer >> Mobile : +94 778333939 >> kirishan...@wso2.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Dinithi De Silva* > Associate Software Engineer, WSO2 Inc. > m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com > | a: #20, Palm Grove, Colombo 03 > -- Dushan Abeyruwan | Technical Lead PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* Mobile:(001)408-791-9312 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [BAM 2.5.0] BAM error when wifi connected (seems IPV6 issue)
Hi
Any idea how to resolve this, as soon as wi-fi stopped its working, don't
have control to disable IPV6 in my local PC
I mean how we could instruct HBase not to look up IPV6 address?
r of reduce tasks not specified. Estimated from input data size: 1
In order to change the average load for a reducer (in bytes):
set hive.exec.reducers.bytes.per.reducer=
In order to limit the maximum number of reducers:
set hive.exec.reducers.max=
In order to set a constant number of reducers:
set mapred.reduce.tasks=
log4j:WARN No appenders could be found for logger
(org.apache.axiom.util.stax.dialect.StAXDialectDetector).
log4j:WARN Please initialize the log4j system properly.
Execution log at:
/Users/xx/workspace/xxx/APIM/APIM19BAM/wso2bam-2.5.0/repository/logs//wso2carbon.log
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:199)
at
org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:168)
at
org.apache.hadoop.security.UserGroupInformation.isSecurityEnabled(UserGroupInformation.java:227)
at
org.apache.hadoop.security.UserGroupInformation.getLoginUser(UserGroupInformation.java:453)
at
org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:431)
at org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:1420)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1319)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
at org.apache.hadoop.fs.FileSystem.getLocal(FileSystem.java:197)
at org.apache.hadoop.hive.ql.exec.ExecDriver.main(ExecDriver.java:692)
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.hadoop.util.RunJar.main(RunJar.java:156)*
*Caused by: java.lang.NumberFormatException: For input string:
"558:feed::1"*
* at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)*
* at java.lang.Integer.parseInt(Integer.java:492)*
* at java.lang.Integer.parseInt(Integer.java:527)*
* at com.sun.jndi.dns.DnsClient.(DnsClient.java:125)*
* at com.sun.jndi.dns.Resolver.(Resolver.java:61)*
* at com.sun.jndi.dns.DnsContext.getResolver(DnsContext.java:570)*
* at com.sun.jndi.dns.DnsContext.c_getAttributes(DnsContext.java:430)*
* at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirC*
ontext.java:231)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:139)
at
com.sun.jndi.toolkit.url.GenericURLDirContext.getAttributes(GenericURLDirContext.java:103)
at
sun.security.krb5.KrbServiceLocator.getKerberosService(KrbServiceLocator.java:87)
at sun.security.krb5.Config.checkRealm(Config.java:1295)
at sun.security.krb5.Config.getRealmFromDNS(Config.java:1268)
at sun.security.krb5.Config.getDefaultRealm(Config.java:1162)
at org.apache.hadoop.security.KerberosName.(KerberosName.java:81)
... 15 more
Execution failed with exit status: 1
[2015-11-11 14:58:27,674] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
Execution failed with exit status: 1
Obtaining error information
[2015-11-11 14:58:27,675] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
Obtaining error information
Task failed!
Task ID:
Stage-0
Logs:
--
Dushan Abeyruwan | Technical Lead
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>*
Mobile:(001)408-791-9312
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BAM 2.5.0] BAM error when wifi connected (seems IPV6 issue)
Already reported issue [1]
JDK bug seems.
I did start BAM 2.5.0 with JDK8v65 [2], then issue resolved, but we never
recommend CARBON 4.2.0 to start on JDK 8
[1] https://issues.apache.org/jira/browse/HADOOP-11582
[2] http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8086893
On Wed, Nov 11, 2015 at 3:06 PM, Dushan Abeyruwan <dus...@wso2.com> wrote:
> Hi
> Any idea how to resolve this, as soon as wi-fi stopped its working,
> don't have control to disable IPV6 in my local PC
>
> I mean how we could instruct HBase not to look up IPV6 address?
>
> r of reduce tasks not specified. Estimated from input data size: 1
> In order to change the average load for a reducer (in bytes):
> set hive.exec.reducers.bytes.per.reducer=
> In order to limit the maximum number of reducers:
> set hive.exec.reducers.max=
> In order to set a constant number of reducers:
> set mapred.reduce.tasks=
> log4j:WARN No appenders could be found for logger
> (org.apache.axiom.util.stax.dialect.StAXDialectDetector).
> log4j:WARN Please initialize the log4j system properly.
> Execution log at:
> /Users/xx/workspace/xxx/APIM/APIM19BAM/wso2bam-2.5.0/repository/logs//wso2carbon.log
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:199)
> at
> org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:168)
> at
> org.apache.hadoop.security.UserGroupInformation.isSecurityEnabled(UserGroupInformation.java:227)
> at
> org.apache.hadoop.security.UserGroupInformation.getLoginUser(UserGroupInformation.java:453)
> at
> org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:431)
> at org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:1420)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1319)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at org.apache.hadoop.fs.FileSystem.getLocal(FileSystem.java:197)
> at org.apache.hadoop.hive.ql.exec.ExecDriver.main(ExecDriver.java:692)
> 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.hadoop.util.RunJar.main(RunJar.java:156)*
> *Caused by: java.lang.NumberFormatException: For input string:
> "558:feed::1"*
> * at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)*
> * at java.lang.Integer.parseInt(Integer.java:492)*
> * at java.lang.Integer.parseInt(Integer.java:527)*
> * at com.sun.jndi.dns.DnsClient.(DnsClient.java:125)*
> * at com.sun.jndi.dns.Resolver.(Resolver.java:61)*
> * at com.sun.jndi.dns.DnsContext.getResolver(DnsContext.java:570)*
> * at com.sun.jndi.dns.DnsContext.c_getAttributes(DnsContext.java:430)*
> * at
> com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirC*
> ontext.java:231)
> at
> com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:139)
> at
> com.sun.jndi.toolkit.url.GenericURLDirContext.getAttributes(GenericURLDirContext.java:103)
> at
> sun.security.krb5.KrbServiceLocator.getKerberosService(KrbServiceLocator.java:87)
> at sun.security.krb5.Config.checkRealm(Config.java:1295)
> at sun.security.krb5.Config.getRealmFromDNS(Config.java:1268)
> at sun.security.krb5.Config.getDefaultRealm(Config.java:1162)
> at org.apache.hadoop.security.KerberosName.(KerberosName.java:81)
> ... 15 more
> Execution failed with exit status: 1
> [2015-11-11 14:58:27,674] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
> Execution failed with exit status: 1
> Obtaining error information
> [2015-11-11 14:58:27,675] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
> Obtaining error information
>
> Task failed!
> Task ID:
> Stage-0
>
> Logs:
>
> --
> Dushan Abeyruwan | Technical Lead
>
> PMC Member Apache Synpase
> WSO2 Inc. http://wso2.com/
> Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>*
> Mobile:(001)408-791-9312
>
>
--
Dushan Abeyruwan | Technical Lead
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>*
Mobile:(001)408-791-9312
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Connectors] Storing connector endpoint in registry
Hi Why you need like that ? SF connector we have uses initial service URL at init [1] and upon successfully authenticate all the other operations other than salesforce.init will use dynamic url return from authenticate requests (extracting from response payload).[2] init property expression=//ns:loginResponse/ns:result/ns:serverUrl/text() name=salesforce.serviceUrl scope=operation type=STRING xmlns:ns=urn:partner.soap.sforce.com / property name=salesforce.login.done scope=operation type=STRING value=true / [1] https://login.salesforce.com/services/Soap/u/27.0 [2] https://github.com/wso2-dev/esb-connectors/blob/master/salesforce/1.0.0/src/main/resources/salesforce/init.xml Cheers, Dushan On Mon, Aug 24, 2015 at 4:12 PM, Bhathiya Jayasekara bhath...@wso2.com wrote: Hi all, Is there a way to store Salesforce endpoint in registry, and refer to that in init block of connector? Thanks, -- *Bhathiya Jayasekara* *Senior Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185 %2B94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* *Blog: http://movingaheadblog.blogspot.com http://movingaheadblog.blogspot.com/* -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ http://www.dushantech.com/* Mobile:(001)812-391-7441 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while using EJB mediator
Hi Dinusha, Yeah, you could create public JIRA for the improvement also document it. @adding 'Shadsha' as she was struggling to get it connect FYI: Shadsha please communicate with Dinusha to get more details if you still can't connect On Fri, Aug 14, 2015 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Dushan, I was running JBoss with port offset. Reverting back to default port solved the issue. There should be some client property in ESB side to tell the remote connection port of JBoss server. Not sure what it is though. Regards, Dinusha. On Fri, Aug 14, 2015 at 5:45 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Dinusha, There has been lot's of class loader issues when comes to EJBMediator connection to JBoss, have shared the artifacts archived [1], we have to have jboss client (osgied) to be placed in ESB, anyway did you check by writing a simple JAVA client to invoke those services ? if with ESB we still getting above mentioned issue, we could try to add following parameter to synapse.properties under bean you have defined synapse.beanstalks.jack.jboss.naming.client.ejb.context=true anyway, shall we first check the java client ? [1] https://drive.google.com/drive/u/0/folders/0BxjKaX2u7UlUZXRaVURnWkxMcHc [2] http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling On Fri, Aug 14, 2015 at 7:50 AM, Dinusha Senanayaka dinu...@wso2.com wrote: Forgot to send the exception org.apache.synapse.SynapseException: Error while invoking 'getClosestStore' method via reflection. at org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:79) at org.apache.synapse.mediators.bean.enterprise.EJBMediator.mediate(EJBMediator.java:132) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException 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.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:74) ... 12 more Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:EJBDemo,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@5d5f1834 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy17.getClosestStore(Unknown Source) On Fri, Aug 14, 2015 at 5:14 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi, I'm trying EJB sample given in [1], [2]. But getting following exception while invoking the proxy. Found this [3] which is reported earlier, but for me issue comes continuously not intermittent. Also [4] seems to be related. but not sure how to set this property with ESB. Appreciate any help to sort this. [1] http://wso2.com/library/articles/2012/06/ejb-mediator-action-wso2-esb-450/ [2] http://www.dushantech.com/2012/06/syntaxhighlighter.html [3] https://wso2.org/jira/browse/ESBJAVA-1487 [4] http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling Regards, Dinusha. -- Dinusha Dilrukshi Associate Technical Lead WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Dinusha Dilrukshi Associate Technical Lead WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Dushan Abeyruwan | Technical Lead
Re: [Dev] Error while using EJB mediator
Hi Dinusha, There has been lot's of class loader issues when comes to EJBMediator connection to JBoss, have shared the artifacts archived [1], we have to have jboss client (osgied) to be placed in ESB, anyway did you check by writing a simple JAVA client to invoke those services ? if with ESB we still getting above mentioned issue, we could try to add following parameter to synapse.properties under bean you have defined synapse.beanstalks.jack.jboss.naming.client.ejb.context=true anyway, shall we first check the java client ? [1] https://drive.google.com/drive/u/0/folders/0BxjKaX2u7UlUZXRaVURnWkxMcHc [2] http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling On Fri, Aug 14, 2015 at 7:50 AM, Dinusha Senanayaka dinu...@wso2.com wrote: Forgot to send the exception org.apache.synapse.SynapseException: Error while invoking 'getClosestStore' method via reflection. at org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:79) at org.apache.synapse.mediators.bean.enterprise.EJBMediator.mediate(EJBMediator.java:132) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException 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.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:74) ... 12 more Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:EJBDemo,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@5d5f1834 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy17.getClosestStore(Unknown Source) On Fri, Aug 14, 2015 at 5:14 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi, I'm trying EJB sample given in [1], [2]. But getting following exception while invoking the proxy. Found this [3] which is reported earlier, but for me issue comes continuously not intermittent. Also [4] seems to be related. but not sure how to set this property with ESB. Appreciate any help to sort this. [1] http://wso2.com/library/articles/2012/06/ejb-mediator-action-wso2-esb-450/ [2] http://www.dushantech.com/2012/06/syntaxhighlighter.html [3] https://wso2.org/jira/browse/ESBJAVA-1487 [4] http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling Regards, Dinusha. -- Dinusha Dilrukshi Associate Technical Lead WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Dinusha Dilrukshi Associate Technical Lead WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ http://www.dushantech.com/* Mobile:(001)812-391-7441 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Deploying an ESB Connector with a cApp?
On Tue, Jul 7, 2015 at 8:07 AM, Jasintha Dasanayake jasin...@wso2.com wrote: @viraj Shall we enable this in ESB project level , since there is a option already in ESB project , that we can improve to pack connector into capp when adding the ESB project into Capp ? +1 this should be feasible with ESB Project level as its already there in DevS Shashika, could please provide more detail (design and implementation detail/changes you have done) how you planned to integrate this ? however, please note that we need manage depdenencies correctly CAR -- upload -- deploy connector/s --- [[*critical:* monitor the status of connector deployment]] -- if success --- execute connector-meta-import -- if success -- then deploy other synapse-artifacts *guess, the difficulty can be holding synapse artifact deployment till connector's uploaded successfully and import connector meta data, have found solution for this ?* Thanks and Regards /Jasintha On Tue, Jul 7, 2015 at 4:33 PM, Shakila Sivagnanarajah shak...@wso2.com wrote: Hi Kasun, Since there is no feature in developer studio to import connector zip into the CApp, I have manually added the zip in to car. Now I am debugging and modifying the code [1]. I think I am going well with the task. [1] https://github.com/wso2/carbon-mediation/blob/master/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java Thank you. On Tue, Jul 7, 2015 at 4:22 PM, Kasun Indrasiri ka...@wso2.com wrote: Any progress on this task? On Thu, Jul 2, 2015 at 11:09 PM, Malaka Silva mal...@wso2.com wrote: Hi All, Shakila will be starting to implement this functionality from ESB side. @Shakila - Any blockers user this mail thread to discuss. On Tue, Jun 30, 2015 at 5:57 PM, Jasintha Dasanayake jasin...@wso2.com wrote: From tooling perspective, this is similar to class mediator deployment using Capp , Since Capp class mediator deployment now working fine with Capp so this can be done , However this is also kind of sever extension so we have to educate the users to use this properly. Thanks and Regards /Jasintha On Tue, Jun 30, 2015 at 5:11 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi, AFAIR, this was discussed several times. But in the context of ESB as a service, I think this will be quite useful. I don't think we have any technical difficulty in doing this. Use case : - We want to invoke a twitter operation. - Import the twitter connector from connector-store( into DevS) and use the twitter connector operation in our mediation logic. - Now we want to deploy the artifact into ESB but it is required to deploy/enable the connector beforehand. (If the connector is not deployed in the ESB instance, this config deployment will fail.) - If we can include the connector as part of the cApp, then the connector deployment is completely transparent to the users. WDYT? -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean . enterprise . middleware* *mobile :- 0711368118 0711368118* -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean . enterprise . middleware* *mobile :- 0711368118* ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ http://www.dushantech.com/* Mobile:(001)812-391-7441 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error when trying out playground app included in wso2 IS 5.0.0 with tomcat 7
Hi Folks, I could observe the same error, can't test https://docs.wso2.com/display/IS500/OAuth+2.0+Grant+Types+with+WSO2+API+Manager+Implicit please ACK asap for resolution Cheers, Dushan On Wed, Apr 22, 2015 at 1:44 AM, Hasitha Amal De Silva hasit...@wso2.com wrote: Hi all, I'm facing the below exception from the apache tomcat7 server when trying out the playground oauth sample with wso2 IS 5.0.0 and APIM 1.8.0 (Using a common Service Provider) : java.lang.NoSuchMethodError: org.wso2.carbon.identity.oauth.cache.SessionDataCacheEntry.setParamMap(Ljava/util/Map;)V org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleOAuthAuthorizationRequest(OAuth2AuthzEndpoint.java:517) org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.authorize(OAuth2AuthzEndpoint.java:146) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) It seems that the proper jar is not loaded when deploying the webapp. The previous versions of this class had a different method signature. Have any of you come across a similar issue ? p:s: I noted that theres a way to check the classes / jars loaded into tomcat runtime on startup, but not clear on how to do it. This way I can confirm if the proper jar is loaded. Thanks, Hasitha Amal De Silva Software Engineer Mobile : 0772037426 Blog: http://devnutshell.tumblr.com/ WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. ) ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ http://www.dushantech.com/* Mobile:(001)812-391-7441 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 Message Broker 3.0.0 Milestone 7 Released !
Hi Something wrong with milestone release note, should include Improvements done, bug fixes inline rather providing link, please go with standard template we have Please refer other product's milestone releases. Cheers, Dushan On Wed, Apr 22, 2015 at 4:30 AM, Pumudu Ruhunage pum...@wso2.com wrote: *WSO2 Message Broker 3.0.0 Milestone 7 Released !* The WSO2 Message Broker team is pleased to announce the 7th milestone release of WSO2 Message Broker (MB) 3.0.0. WSO2 Message Broker (WSO2 MB) 3.0.0 is designed to be a fast, lightweight and user friendly open source distributed message brokering system under the Apache Software License v2.0 http://www.apache.org/licenses/LICENSE-2.0.html. It primarily allows system administrators and developers to easily configure JMS queues and topics which could be used for message routing, message stores and message processors. WSO2 MB is compliant with Advanced Message Queuing Protocol Version 0-9-1, Java Message Service Specification version 1.1 and MQTT protocol version 3.1. WSO2 MB 3.0.0 is developed on top of the revolutionary WSO2 Carbon platform http://wso2.org/projects/carbon (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via modularization. This release also contains many other new features and a range of optional components (add-ons) that can be installed to customize the behavior of the MB. Further, any existing features of the MB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In a nutshell, WSO2 MB can be fully customized and tailored to meet your exact SOA needs. You can download this distribution from [1]. Release notes for this milestone can be found at [2]. Known issues are listed at [3]. This milestone has mainly focused on bug fixes and performance improvements. How You Can Contribute:Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : dev@wso2.org | Subscribe | Mail Archive http://wso2.org/mailarchive/carbon-dev/ - User List : StackOverflow.com http://stackoverflow.com/questions/tagged/wso2 Reporting Issues WSO2 encourages you to report issues and your enhancement requests for the WSO2 MB using the public JIRA https://wso2.org/jira/browse/MB. You can also watch how they are resolved, and comment on the progress.. [1] https://svn.wso2.org/repos/wso2/scratch/MB/3.0.0/M7/wso2mb-3.0.0-SNAPSHOT-m7.zip https://www.google.com/url?q=https%3A%2F%2Fsvn.wso2.org%2Frepos%2Fwso2%2Fscratch%2FMB%2F3.0.0%2FM7%2Fwso2mb-3.0.0-SNAPSHOT-m7.zipsa=Dsntz=1usg=AFQjCNEj-PKEn-9ZHW0HM2CzMwsR_IyzhQ [2] https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11766 https://www.google.com/url?q=https%3A%2F%2Fwso2.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D10200%26version%3D11766sa=Dsntz=1usg=AFQjCNH50zjXZAR9qR6UZm5RIphFHqD15A [3] https://wso2.org/jira/browse/MB#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(001)812-391-7441 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Converting JSON to SOAP and vise versa in ESB
) at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138) at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214) ... 25 more 23:24:39,141 SequenceMediator Error while building message org.apache.axis2.AxisFault: Error while building Passthrough stream at org.apache.synapse.transport.passthru.util.RelayUtils.handleException(RelayUtils.java:236) at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:111) at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:82) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68) 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.rest.Resource.process(Resource.java:297) at org.apache.synapse.rest.API.process(API.java:298) at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76) at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:50) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Premature end of file. at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:154) at org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXSOAPModelBuilder(AbstractOMMetaFactory.java:73) at org.apache.axiom.om.impl.AbstractOMMetaFactory.createSOAPModelBuilder(AbstractOMMetaFactory.java:79) at org.apache.axiom.om.OMXMLBuilderFactory.createSOAPModelBuilder(OMXMLBuilderFactory.java:196) at org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:55) at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:118) at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107) ... 17 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Premature end of file. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:594) 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.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138) at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214) ... 25 more On 6 February 2015 at 22:50, Dushan Abeyruwan dus...@wso2.com wrote: Your API should be as. api xmlns=http://ws.apache.org/ns/synapse; name=tempAPI context=/temp resource methods=POST GET inSequence log level=custom property name=IN_MESSAGE value=IN_MESSAGE/property /log property name=messageType value=application/xml scope=axis2/property * property name=FORCE_HTTP_1.0 value=true scope=axis2/property* * property name=DISABLE_CHUNKING value=true scope=axis2/property* payloadFactory media-type=xml format soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; xmlns:web= http://www.w3schools.com/webservices/; soapenv:Header/soapenv:Header soapenv:Body
Re: [Dev] Converting JSON to SOAP and vise versa in ESB
) 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.rest.Resource.process(Resource.java:297) at org.apache.synapse.rest.API.process(API.java:341) at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76) at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:63) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220) at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:344) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:385) 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$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1937) at org.apache.axis2.builder.XFormURLEncodedBuilder.extractParametersFromRequest(XFormURLEncodedBuilder.java:174) at org.apache.axis2.builder.XFormURLEncodedBuilder.processDocument(XFormURLEncodedBuilder.java:112) at org.apache.synapse.commons.builders.XFormURLEncodedBuilder.processDocument(XFormURLEncodedBuilder.java:36) at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:118) at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107) Any idea what Im doing wrong? This should be straight forward, Thanks -- Regards, Uvindra Mobile: 33962 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Asanka DissanayakeSoftware Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com/* *email: asan...@wso2.com ruch...@wso2.com, blog: cyberwaadiya.blogspot.com http://cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com http://asankastechtalks.wordpress.com mobile: +94 71 8373821* -- Regards, Uvindra Mobile: 33962 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB-XPath] Retrive OM element as parameter in template function always evaluate to String
Hi
please refer the highlighted section
*expression=$func:message1/ser:request/xsd:symbol* it always prints null
because, evaluation at *getEvaluatedParamValue *convert property to *string*
regardless of property element type
if '*$func:message1*' assigned back to another variable with OM type
started to evaluate correctly
proxy xmlns=http://ws.apache.org/ns/synapse;
name=Moo
transports=https,http
statistics=disable
trace=disable
startOnLoad=true
target
inSequence
enrich
source type=body clone=true/
target type=property property=ORGINAL_MSG/
/enrich
property name=api.common.errorEntries
expression=get-property('ORGINAL_MSG')
type=OM/
clone
target
sequence
call-template target=HelloWorld_Logger
with-param name=message value=Bonjour tout le
monde!!/
with-param name=message1
value={$ctx:api.common.errorEntries}/
/call-template
/sequence
/target
/clone
drop/
/inSequence
/target
description/
/proxy
template xmlns=http://ws.apache.org/ns/synapse; name=HelloWorld_Logger
parameter name=message/parameter
parameter name=message1/parameter
sequence
log level=custom
property xmlns:ns2=http://org.apache.synapse/xsd; xmlns:ns=
http://org.apache.synapse/xsd; name=CLONE-IN
expression=$func:message1/property
/log
property xmlns:ns2=http://org.apache.synapse/xsd; xmlns:ns=
http://org.apache.synapse/xsd; name=templateMessage
expression=$func:message1 type=OM/property
*log*
* property xmlns:xsd=http://services.samples/xsd
http://services.samples/xsd xmlns:ns2=http://org.apache.synapse/xsd
http://org.apache.synapse/xsd xmlns:ns=http://org.apache.synapse/xsd
http://org.apache.synapse/xsd xmlns:ser=http://services.samples
http://services.samples name=message##
expression=$func:message1/ser:request/xsd:symbol/property*
* /log*
/sequence
/template
Please refer the configuration
private Object getEvaluatedParamValue(MessageContext synCtx, String
parameter, Value expression) {
if (expression != null) {
if (expression.getExpression() != null) {
if(expression.hasExprTypeKey()){
if(expression.hasPropertyEvaluateExpr()){
//TODO:evalute the string expression get the value
//String evaluatedPath ={//m0:getQuote/m0:request};
return expression.evalutePropertyExpression(synCtx);
}
return expression.getExpression();
} else {
*return expression.evaluateValue(synCtx);*
}
} else if (expression.getKeyValue() != null) {
return expression.evaluateValue(synCtx);
}
}
return null;
}
public String evaluateValue(MessageContext synCtx) {
if (keyValue != null) {
return keyValue;
} else if (expression != null) {
//if dynamic key return evaluated value
* return expression.stringValueOf(synCtx);*
} else {
handleException(Can not evaluate the key: +
key should be static or dynamic key);
return null;
}
}
public jira created
https://wso2.org/jira/browse/ESBJAVA-3517
cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Asanka Abeyweera
___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Priya Kishok Software Engineer WSO2, Inc : http://wso2.com Mob : +94774457404 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in Kafka producer load testing
ulimit ? have you set them in your OS On Sat, Oct 4, 2014 at 8:48 PM, Kathees Rajendram kath...@wso2.com wrote: Hi, I tried to send 5000 messages to Kafka broker using Jmeter ( 10 thread and 500 messages per a thread,one message size is 105 byes). After 2000 messages I am getting the following exception. Exception shows Too many open files error.So I changed to increase no. of open files limit on my machine. http://askubuntu.com/questions/162229/how-do-i-increase-the-open-files-limit-for-a-non-root-user and changed buffer size (socket.request.max.bytes) value in server.properties file but still I am getting same exception. What is the cause for this issue? [2014-10-03 12:31:07,051] ERROR - Utils$ fetching topic metadata for topics [Set(test1)] from broker [ArrayBuffer(id:0,host:localhost,port:9092)] failed kafka.common.KafkaException: fetching topic metadata for topics [Set(test1)] from broker [ArrayBuffer(id:0,host:localhost,port:9092)] failed at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:67) at kafka.producer.BrokerPartitionInfo.updateInfo(BrokerPartitionInfo.scala:82) at kafka.producer.async.DefaultEventHandler$$anonfun$handle$2.apply$mcV$sp(DefaultEventHandler.scala:78) at kafka.utils.Utils$.swallow(Utils.scala:167) at kafka.utils.Logging$class.swallowError(Logging.scala:106) at kafka.utils.Utils$.swallowError(Utils.scala:46) at kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:78) at kafka.producer.Producer.send(Producer.scala:76) at kafka.javaapi.producer.Producer.send(Producer.scala:33) at org.wso2.carbon.connector.KafkaProduce.send(KafkaProduce.java:71) at org.wso2.carbon.connector.KafkaProduce.connect(KafkaProduce.java:28) at org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32) at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78) 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.template.TemplateMediator.mediate(TemplateMediator.java:77) at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129) at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78) 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.processNonEntityEnclosingRESTHandler(ServerWorker.java:344) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:385) 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.net.SocketException: Too many open files at sun.nio.ch.Net.socket0(Native Method) at sun.nio.ch.Net.socket(Net.java:423) at sun.nio.ch.Net.socket(Net.java:416) at sun.nio.ch.SocketChannelImpl.init(SocketChannelImpl.java:104) at sun.nio.ch.SelectorProviderImpl.openSocketChannel(SelectorProviderImpl.java:60) at java.nio.channels.SocketChannel.open(SocketChannel.java:142) at kafka.network.BlockingChannel.connect(BlockingChannel.scala:48) at kafka.producer.SyncProducer.connect(SyncProducer.scala:141) at kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156) at kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68) at kafka.producer.SyncProducer.send(SyncProducer.scala:112) at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53) ... 29 more Thanks, Kathees -- Kathees Software Engineer, email: kath...@wso2.com mobile: +94772596173 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman
Re: [Dev] Question about securing a service in ESB, providing Integrity
Hi Read description of again, what it says signed using symmetric key then encrypt using service public key, so server end only way to verify now decrypt message using service private key, and validate signature with symmetric key. Now validating integrity : symmetric key is shared only between to agreed parties, so they store symmetric keys in their respective key stores, and there is almost no chance that intruder can stand in between and generate new symmetric key because, symmetric key is a agreement between client and service, even if some one generate new symmetric key should inform service beforehand (and normally services wont store symmetric keys randomly unless verified and authenticated). Cheers, Dushan On Wed, Sep 24, 2014 at 1:21 PM, Lahiru Chandima lahi...@wso2.com wrote: Hi All, Following is the diagram given by ESB about how it provides integrity for a service. (Securing a service using basic scenario No. 3) [image: Inline image 1] According to the diagram, client uses a generated symmetric key to sign the message, encrypts the used key using server's public key and sends along with the message. But, I cannot understand how this provides integrity. As I see, someone can intercept the message sent by the client, alter the message, generate a new symmetric key, sign the altered message using this key, encrypt the key using server's public key and send along with the message without a problem. Since the original message is now altered, there's no integrity. Can somebody please explain what I have gotten wrong? Thanks -- Lahiru Chandima *Senior Software Engineer* Mobile : +94 (0) 772 253283 lahi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] Altering SecureServiceClient loaded for axis2.xml adding[text/html] content type
Hi Running ProxyServiceSecurityTestCase, How can I inject customized axis2.xml to SecureServiceClient is this configurable? https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/products/esb/4.8.1/modules/integration/tests-service/src/test/java/org/wso2/carbon/esb/proxyservice/test/secureProxy Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [jira] (ESBJAVA-3215) Sample 256 is not working - Mail Transport
+1, don't think we should fix this lets comment about this and close it down. On Mon, Jul 14, 2014 at 3:25 PM, Miyuru Wanninayaka miy...@wso2.com wrote: Seems someone changed google password which used in mail transport sample. I don't think that there is a permanent solution other than asking users to use their own mail account when trying this sample. -- Forwarded message -- From: Miyuru Daminda (JIRA) j...@wso2.org Date: Mon, Jul 14, 2014 at 2:56 PM Subject: [jira] (ESBJAVA-3215) Sample 256 is not working - Mail Transport To: miy...@wso2.com Miyuru Daminda https://wso2.org/secure/ViewProfile.jspa?name=miyuru%40wso2.com commented on [image: Bug] ESBJAVA-3215 https://wso2.org/browse/ESBJAVA-3215 *Sample 256 is not working - Mail Transport* https://wso2.org/browse/ESBJAVA-3215 Seems credentials in mail transport sample is no longer valid This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Miyuru Wanninayaka Senior Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to change version of Twitter4j at Orbit
There will be multiple connector versions if any API changes happen also we will maintaining API version in use at the connector store as meta info On Tuesday, July 8, 2014, Gayashan Amarasinghe gayas...@wso2.com wrote: Small correction in line. Thanks. On Tue, Jul 8, 2014 at 11:14 PM, Gayashan Amarasinghe gayas...@wso2.com javascript:_e(%7B%7D,'cvml','gayas...@wso2.com'); wrote: Hi KasunG, Assuming that we keep this in the orbit i have a question. Since we are having a version range in the twitter4j dependency here, wouldn't it create an issue with the possible [API] changes of the future versions of the library? And also in terms of our orbit bundle naming convention? dependency groupIdorg.twitter4j/groupId artifactIdtwitter4j-core/artifactId version*[4.0,)*/version /dependency For an example, anyone who builds the orbit [and not download the dependency from the nexus] later may get a new twitter4j dependency and might cause build failures if there are API changes within the dependency? ​​Should be changed to, might cause build failures within ​Twitter-Connector or any other project which depends on twitter4j 4.0.0.wso2v1 bundle, if there are API changes within the dependency.​ Is it possible or am i understanding it wrong here? Thanks. /Gayashan On Tue, Jul 8, 2014 at 5:46 PM, Kasun Gajasinghe kas...@wso2.com javascript:_e(%7B%7D,'cvml','kas...@wso2.com'); wrote: Hi Buddhima, Your parent pom reference needs to be updated. You also need to add distributionManagement configuration. Then, work with Maheshika to get this orbit released. Regards, KasunG On Tue, Jul 8, 2014 at 5:35 PM, Buddhima Wijeweera buddh...@wso2.com javascript:_e(%7B%7D,'cvml','buddh...@wso2.com'); wrote: Hi Sagara, Thank you for the information. I sent a pull request to wso2-orbit with this change. Link: https://github.com/wso2/orbit/pull/5 On Tue, Jul 8, 2014 at 4:37 PM, Sagara Gunathunga sag...@wso2.com javascript:_e(%7B%7D,'cvml','sag...@wso2.com'); wrote: On Tue, Jul 8, 2014 at 4:34 PM, Buddhima Wijeweera buddh...@wso2.com javascript:_e(%7B%7D,'cvml','buddh...@wso2.com'); wrote: Hi, Currently some operations relate to Twitter-Connector are not functioning. Eg: getFriendsIds getFriends getFollowersIds getFollowers To fix that it is essential to change the version of Twitter4J which is currently in use at here: https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/twitter/ I have locally made the change and tested. After the change all those operations are working as expect. I would like to know how can I fix that in the above mentioned location. If the Orbit bundle is released you can't change it, you have to create new version of Orbit bundle. Thanks ! Thank You! -- Buddhima Wijeweera Software Engineer; WSO2 Inc.; http://wso2.com , Email: buddh...@wso2.com javascript:_e(%7B%7D,'cvml','buddh...@wso2.com'); Blog: https://buddhimawijeweera.wordpress.com GitHub Profile: https://github.com/Buddhima ___ Dev mailing list Dev@wso2.org javascript:_e(%7B%7D,'cvml','Dev@wso2.org'); http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Buddhima Wijeweera Software Engineer; WSO2 Inc.; http://wso2.com , Email: buddh...@wso2.com javascript:_e(%7B%7D,'cvml','buddh...@wso2.com'); Blog: https://buddhimawijeweera.wordpress.com GitHub Profile: https://github.com/Buddhima ___ Dev mailing list Dev@wso2.org javascript:_e(%7B%7D,'cvml','Dev@wso2.org'); http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org ___ Dev mailing list Dev@wso2.org javascript:_e(%7B%7D,'cvml','Dev@wso2.org'); http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] https://wso2.org/jira/browse/DOCUMENTATION-280
-Alive [2014-07-09 08:39:04,926] DEBUG - headers http-incoming-5 POST /services/EchoProxy HTTP/1.1 [2014-07-09 08:39:04,926] DEBUG - headers http-incoming-5 Accept-Encoding: gzip,deflate [2014-07-09 08:39:04,926] DEBUG - headers http-incoming-5 Content-Type: application/json [2014-07-09 08:39:04,927] DEBUG - headers http-incoming-5 Content-Length: 1109 [2014-07-09 08:39:04,927] DEBUG - headers http-incoming-5 Host: kit:8243 [2014-07-09 08:39:04,927] DEBUG - headers http-incoming-5 Connection: Keep-Alive [2014-07-09 08:39:04,927] DEBUG - headers http-incoming-5 User-Agent: Apache-HttpClient/4.1.1 (java 1.5) [2014-07-09 08:39:04,927] DEBUG - headers http-incoming-5 Authorization: Basic YWRtaW46YWRtaW4= [2014-07-09 08:39:05,170] INFO - LogMediator To: /services/EchoProxy, MessageID: urn:uuid:7ff37db2-8b0c-45df-ad7a-424c1abfdfb4, Direction: request [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 HTTP/1.1 200 OK [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Authorization: Basic YWRtaW46YWRtaW4= [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Host: kit:8243 [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Accept-Encoding: gzip,deflate [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Content-Type: application/json; charset=UTF-8 [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Date: Wed, 09 Jul 2014 03:09:04 GMT [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Transfer-Encoding: chunked [2014-07-09 08:39:05,175] DEBUG - headers http-incoming-5 Connection: Keep-Alive -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] https://wso2.org/jira/browse/DOCUMENTATION-280
I am waiting for Sandapas explanation..
On Wed, Jul 9, 2014 at 10:26 AM, Rukshani Weerasinha ruksh...@wso2.com
wrote:
Hi,
I tried applying basic authentication (UsernameToken security scenario) in
ESB 4.8.1 as well as ESB 4.6.0. It worked in both versions. So shall we
specify page [1] as the solution for Documentation-280 jira?
[1]
http://docs.wso2.com/display/ESB481/Service-Level+Security+Implementation
Best Regards,
Rukshani.
On Wed, Jul 9, 2014 at 8:43 AM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi
Regarding $subject any reason for workaround ? did we test 4.8.0
onwards, I tried with 4.9.0 pack and seems basic auth working for proxy.
proxy xmlns=http://ws.apache.org/ns/synapse;
name=EchoProxy
transports=https
statistics=disable
trace=disable
startOnLoad=true
target
inSequence
log/
respond/
/inSequence
/target
parameter name=ScenarioIDscenario1/parameter
enableSec/
policy
key=conf:/repository/axis2/service-groups/EchoProxy/services/EchoProxy/policies/UTOverTransport/
description/
/proxy
Failure Invalid UN or PW
===
HTTP/1.1 401 Unauthorized
WWW-Authenticate: BASIC realm=WSO2 Enterprise Service Bus
Content-Type: application/json; charset=UTF-8
Date: Wed, 09 Jul 2014 03:10:00 GMT
Transfer-Encoding: chunked
Connection: Keep-Alive
{Fault:{faultcode:axis2ns2:FailedAuthentication,faultstring:The
security token could not be authenticated or authorized; nested exception
is: \n\tjavax.security.auth.callback.UnsupportedCallbackException: Check
failed : System error,detail:null}}
[2014-07-09 08:36:53,042] DEBUG - headers http-incoming-4 POST
/services/EchoProxy HTTP/1.1
[2014-07-09 08:36:53,042] DEBUG - headers http-incoming-4
Accept-Encoding: gzip,deflate
[2014-07-09 08:36:53,043] DEBUG - headers http-incoming-4
Content-Type: application/json
[2014-07-09 08:36:53,043] DEBUG - headers http-incoming-4
Content-Length: 1109
[2014-07-09 08:36:53,043] DEBUG - headers http-incoming-4 Host:
kit:8243
[2014-07-09 08:36:53,043] DEBUG - headers http-incoming-4 Connection:
Keep-Alive
[2014-07-09 08:36:53,043] DEBUG - headers http-incoming-4 User-Agent:
Apache-HttpClient/4.1.1 (java 1.5)
[2014-07-09 08:36:53,045] DEBUG - headers http-incoming-4 HTTP/1.1 401
Unauthorized
[2014-07-09 08:36:53,046] DEBUG - headers http-incoming-4
WWW-Authenticate: BASIC realm=WSO2 Enterprise Service Bus
[2014-07-09 08:36:53,046] DEBUG - headers http-incoming-4 Date: Wed,
09 Jul 2014 03:06:53 GMT
[2014-07-09 08:36:53,046] DEBUG - headers http-incoming-4
Transfer-Encoding: chunked
[2014-07-09 08:36:53,046] DEBUG - headers http-incoming-4 Connection:
Keep-Alive
[2014-07-09 08:36:53,051] DEBUG - headers http-incoming-4 POST
/services/EchoProxy HTTP/1.1
[2014-07-09 08:36:53,051] DEBUG - headers http-incoming-4
Accept-Encoding: gzip,deflate
[2014-07-09 08:36:53,051] DEBUG - headers http-incoming-4
Content-Type: application/json
[2014-07-09 08:36:53,051] DEBUG - headers http-incoming-4
Content-Length: 1109
[2014-07-09 08:36:53,052] DEBUG - headers http-incoming-4 Host:
kit:8243
[2014-07-09 08:36:53,052] DEBUG - headers http-incoming-4 Connection:
Keep-Alive
[2014-07-09 08:36:53,053] DEBUG - headers http-incoming-4 User-Agent:
Apache-HttpClient/4.1.1 (java 1.5)
[2014-07-09 08:36:53,053] DEBUG - headers http-incoming-4
Authorization: Basic YWRtaW46YWRtaW4x
[2014-07-09 08:36:53,064] ERROR - AxisEngine The security token could not
be authenticated or authorized; nested exception is:
javax.security.auth.callback.UnsupportedCallbackException: Check failed
: System error
org.apache.axis2.AxisFault: The security token could not be authenticated
or authorized; nested exception is:
javax.security.auth.callback.UnsupportedCallbackException: Check failed
: System error
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:344)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:385)
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$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused
Re: [Dev] [ESB] writing test case for ESB sample 650
it should be in axis2.xml !-- Synapse Configuration file location relative to CARBON_HOME -- parameter name=SynapseConfig.ConfigurationFile locked=falserepository/deployment/server/synapse-configs/parameter On Mon, Jul 7, 2014 at 10:10 AM, Krishantha Samaraweera krishan...@wso2.com wrote: I think it doesn't cover the intended sample scenario. The documentation says The SynapseServer class which is responsible for starting the server accepts a file path as an argument from where to load the configuration. But once check the sample and other configurations, no file path was defined with synapse artifacts. @ESB team - Please let us know where to set the file path for synapse configs resides out side ESB distribution ? Thanks, Krishantha. On Mon, Jul 7, 2014 at 9:11 AM, Waruna Perera waru...@wso2.com wrote: Hi, I am trying to write test case for [1] . In this sample you can give a directory path instead of synapse config xml. I got it working by iterating through the config directory and adding proxies, sequences etc... But does it cover the intended sample scenario here? [1] https://docs.wso2.com/display/ESB460/Sample+650%3A+File+Hierarchy-Based+Configuration+Builder -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Fault mediator doesn't display full error details when used with POX format
For soap 1.1 vs soap 1.2 fault there is a clear specification so what ever web service engine whose executing soap 1.2 or soap 1.1 fault know how to deal with when it receives faults according. SOAP 1.1SOAP 1.2 e:Fault e:Fault faultcode e:Code, e:Subcode, e:Value faultstring e:Reason faultactor e:Node, e:Role detail e:Detail SOAP 1.1SOAP 1.2 e:Fault faultcodee:Server.Memory/faultcode faultstringOut of memory/faultstring /e:Fault e:Fault e:Code e:Valuee:Receiver/e:Value e:Subcode e:Valuep:Memory/e:Value /e:Subcode /e:Code e:ReasonOut of memory/e:Reason /e:Fault *Table 2* for *POX* fault no specification so we just wrapping around with Exception tag with relevant fault On Thu, Jul 3, 2014 at 7:45 AM, Ishara Premadasa ish...@wso2.com wrote: Hi all, Any idea on this. Would be great if i can know the reason for the difference here. Thanks! On Wed, Jul 2, 2014 at 3:15 AM, Ishara Premadasa ish...@wso2.com wrote: Hi, I used fault mediator with both soap 1.1 and pox format where the format of the generated fault response appeared to be different. With the pox format some elements of the fault message was missing. For e.g: This is the response getting for Soap 1.1 format soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcode xmlns:soap11Env= http://schemas.xmlsoap.org/soap/envelope/ soap11Env:VersionMismatch/faultcode faultstringVersion Mismatch!!/faultstring detailThere is a version mismatch in the input message/detail /soapenv:Fault /soapenv:Body /soapenv:Envelope This is how it looks like for POX format. soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body ExceptionThere is a version mismatch in the input message/Exception /soapenv:Body /soapenv:Envelope I have two concerns on this. 1. The fault reason, code entries we set in the mediator are ommitted when creating POX fault. 2. For the Pox format it generates an empty Header element but in Soap 1.1 that is missing. When debugging the fault mediator i could see the below reasons for this output. 1. When we create POX fault there is an if-else block where it first checks 'faultDetail' and else if goes to 'faultDetailExpr' etc. Therefore when the fault detail is there, the other values are ommitted for the fault payload. However when we create SOAP fault all the details are taken and set into SOAPFault object as below. setFaultCode(synCtx, factory, fault, soapVersion); setFaultReason(synCtx, factory, fault, soapVersion); setFaultDetail(synCtx, factory, fault); I would like to know whether there is any specific reason for doing that. IMO there is no harm if we provide all data with the POX fault as well rather than skipping them, since the data are already in the message context. 2. In the POX fault we add the fault payload as a child and replace the body. But in SOAP fault the whole envelope is getting replaced with new fault envelope. May be this is why the soapenv:Header/ is missing there ? Thanks! Ishara -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] Entitlement Mediator issue {https://wso2.org/jira/browse/ESBJAVA-3113}
Guys please do let me know timelines when this can be fixed? On Mon, Jun 23, 2014 at 4:26 PM, Dushan Abeyruwan dus...@wso2.com wrote: $subject, this should be own by IS team and please resolve this. Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] BLOCKER https://wso2.org/jira/browse/CARBON-14842
HI We hit with blocker (binding invalid ports when ESB starts windows) ,this should be due to carbon changers. https://wso2.org/jira/browse/CARBON-14842 Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] JSON Path Evaluation prints logs which is really not needed
Hi Ishan,
We need to fix this, don't think this required to be printed.
$.hash. Returning empty result. Error invalid path
[2014-06-27 10:22:39,097] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,097] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.list. Returning empty result. Error invalid path
[2014-06-27 10:22:39,098] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,098] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.revLimit. Returning empty result. Error invalid
path
[2014-06-27 10:22:39,099] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,099] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.includeMediaInfo. Returning empty result. Error
invalid path
[2014-06-27 10:22:39,100] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,100] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.fromCopyRef. Returning empty result. Error
invalid path
[2014-06-27 10:22:39,101] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,101] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.overwrite. Returning empty result. Error
invalid path
[2014-06-27 10:22:39,103] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,102] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.parentRev. Returning empty result. Error
invalid path
[2014-06-27 10:22:39,104] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,104] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.uploadId. Returning empty result. Error invalid
path
[2014-06-27 10:22:39,853] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,853] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.apiUrl. Returning empty result. Error invalid
path
[2014-06-27 10:22:39,853] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39,853] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path $.accessToken. Returning empty result. Error
invalid path
[2014-06-27 10:22:39,854] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2014-06-27 10:22:39
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [DEV] MSMP L1 Issues {ESBJAVA-3034/ESBJAVA-3018}
Hi Shafreen Please do update with necessary detail for the queries raised under following jira - https://wso2.org/jira/browse/ESBJAVA-3034 For this particular issue I did generated pull request but the integration test is full of failures, please do attach correct artifacts. - https://wso2.org/jira/browse/ESBJAVA-3018 Need clear instruction and we need proper pull requests ACK ASAP.. Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] Who owns {https://github.com/wso2-dev/carbon-rules/tree/master/components/rule/org.wso2.carbon.rule.mediation}
Hi Vanji/Nandika, $subject, should mediators pack under https://github.com/dushansachinda/carbon-mediation/tree/master/components/mediators ? Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] Who owns {https://github.com/wso2-dev/carbon-rules/tree/master/components/rule/org.wso2.carbon.rule.mediation}
Have we decided to remove Rule mediator?. why we committed section
file
sourcesrc/main/conf/jndi.properties/source
outputDirectorywso2esb-${pom.version}/repository/conf/outputDirectory
destNamejndi.properties/destName
filteredtrue/filtered
*/file*
*!--file--*
*
!--source../p2-profile/target/wso2carbon-core-${carbon.kernel.version}/repository/conf/rule-engine-config.xml/source--*
*
!--outputDirectorywso2esb-${pom.version}/repository/conf/outputDirectory--*
*!--/file--*
file
source../../LICENSE.txt/source
outputDirectorywso2esb-${pom.version}/outputDirectory
filteredtrue/filtered
fileMode644/fileMode
/file
!--file--
!--source../../README.
On Mon, Jun 23, 2014 at 12:43 PM, Nandika Jayawardana nand...@wso2.com
wrote:
Since other product mediators are also under mediators, let move the rule
mediator also there. If there is a problem, BRS team can look into it.
Regards
Nandika
On Mon, Jun 23, 2014 at 11:49 AM, Dushan Abeyruwan dus...@wso2.com
wrote:
Hi Vanji/Nandika,
$subject, should mediators pack under
https://github.com/dushansachinda/carbon-mediation/tree/master/components/mediators
?
Cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Nandika Jayawardana
Senior Technical Lead
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please do send us the pull request {https://wso2.org/jira/browse/ESBJAVA-3019}
$subject Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] Entitlement Mediator issue {https://wso2.org/jira/browse/ESBJAVA-3113}
$subject, this should be own by IS team and please resolve this. Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [ESB] Can we increase height size of source view
Hi Please create a public jira, we will consider this but IMO this not a showstopper, as most of the time user experience relying on the DevS Cheers, Dushan On Fri, Jun 13, 2014 at 10:39 AM, Seshika Fernando sesh...@wso2.com wrote: Hi, Can we increase the height of the source view to improve user friendliness? Currently only half of the screen is used for source view and user needs to keep scrolling. See attachment. Eventhough the full screen option is available, its still better if we better use the available space to enhance user experience. Seshika ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Connector-Store] ES 1.1.0 M3 when try to add new assert
anoter blocker , https://wso2.org/jira/browse/STORE-438
On Sat, Jun 14, 2014 at 7:11 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi Sameera and ES Team,
Created jira please regard this as high priority blocker,
https://wso2.org/jira/browse/STORE-436
Cheers,
Dushan
On Fri, Jun 13, 2014 at 8:50 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi Dushan,
This error is not due to the configurations in the user-mgt.xml.
The RXT used in the ES has configured to use the username in storage
path.
The special character are not allowed in resource path, so you need to
clear this with ES team.
Thanks.
Ajith.
On Fri, Jun 13, 2014 at 8:26 PM, Dushan Abeyruwan dus...@wso2.com
wrote:
Hi
Have done changes to user-mgt.xml, instead of *uid*, changes to *mail*
address, getting exception how to avoid ?
--
UserStoreManager
class=org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager
Property
name=TenantManagerorg.wso2.carbon.user.core.tenant.CommonHybridLDAPTenantManager/Property
Property name=ReadOnlytrue/Property
Property name=Disabledfalse/Property
Property name=MaxUserNameListLength100/Property
Property name=ConnectionURL/Property
Property name=ConnectionName*uid=connectorstoreuse*
r,/Property
Property name=ConnectionPasswordx/Property
Property name=passwordHashMethodMD5/Property
Property name=UserSearchBaseou=user,/Property
Property
name=UserNameListFilter(objectClass=inetOrgPerson)/Property
Property
name=UserNameSearchFilter(amp;(objectClass=inetOrgPerson)*(mail=?)*
)/Property
Property name=UserNameAttribute*mail*/Property
Property name=ReadGroupstrue/Property
Property name=GroupSearchBasexx/Property
Property
name=GroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=GroupNameSearchFilter(amp;(objectClass=groupOfNames)(cn=?))/Property
Property name=GroupNameAttributecn/Property
Property name=SharedGroupNameAttributecn/Property
Property
name=SharedGroupSearchBaseou=SharedGroups/Property
Property
name=SharedGroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=SharedTenantNameListFilter(objectClass=organizationalUnit)/Property
Property nam
artifact id: 789b9249-1605-4d70-ba6d-cda88dce4bd2. The path
'/_system/governance/esbconnectors/dus...@wso2.com/Test123/1.0.0'
contains one or more illegal characters (~!@#;%^*()+={}|\',)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:216)
at
org.wso2.carbon.governance.api.generic.GenericArtifactManager.addGenericArtifact(GenericArtifactManager.java:170)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 97 more
Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException:
The path '/_system/governance/esbconnectors/
dus...@wso2.com/Test123/1.0.0' contains one or more illegal characters
(~!@#;%^*()+={}|\',)
at
org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:262)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:465)
at
org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:657)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:194)
... 103 more
Cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Connector-Store] ES 1.1.0 M3 when try to add new assert
problem was due to some malformed text data, Sameera knows this well
On Mon, Jun 16, 2014 at 9:24 AM, Ayesha Dissanayaka aye...@wso2.com wrote:
Hi Dushan,
Same blocker mentioned in https://wso2.org/jira/browse/STORE-438 has
occurred to me, when there were mismatches between asset-type.rxt and
relevant asset-type.json. I was able to resolve it by configuring
asset-type.json file.
On Mon, Jun 16, 2014 at 7:44 AM, Dushan Abeyruwan dus...@wso2.com wrote:
anoter blocker , https://wso2.org/jira/browse/STORE-438
On Sat, Jun 14, 2014 at 7:11 PM, Dushan Abeyruwan dus...@wso2.com
wrote:
Hi Sameera and ES Team,
Created jira please regard this as high priority blocker,
https://wso2.org/jira/browse/STORE-436
Cheers,
Dushan
On Fri, Jun 13, 2014 at 8:50 PM, Ajith Vitharana aji...@wso2.com
wrote:
Hi Dushan,
This error is not due to the configurations in the user-mgt.xml.
The RXT used in the ES has configured to use the username in storage
path.
The special character are not allowed in resource path, so you need to
clear this with ES team.
Thanks.
Ajith.
On Fri, Jun 13, 2014 at 8:26 PM, Dushan Abeyruwan dus...@wso2.com
wrote:
Hi
Have done changes to user-mgt.xml, instead of *uid*, changes to
*mail* address, getting exception how to avoid ?
--
UserStoreManager
class=org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager
Property
name=TenantManagerorg.wso2.carbon.user.core.tenant.CommonHybridLDAPTenantManager/Property
Property name=ReadOnlytrue/Property
Property name=Disabledfalse/Property
Property name=MaxUserNameListLength100/Property
Property name=ConnectionURL/Property
Property name=ConnectionName*uid=connectorstoreuse*
r,/Property
Property name=ConnectionPasswordx/Property
Property name=passwordHashMethodMD5/Property
Property name=UserSearchBaseou=user,/Property
Property
name=UserNameListFilter(objectClass=inetOrgPerson)/Property
Property
name=UserNameSearchFilter(amp;(objectClass=inetOrgPerson)
*(mail=?)*)/Property
Property name=UserNameAttribute*mail*/Property
Property name=ReadGroupstrue/Property
Property name=GroupSearchBasexx/Property
Property
name=GroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=GroupNameSearchFilter(amp;(objectClass=groupOfNames)(cn=?))/Property
Property name=GroupNameAttributecn/Property
Property name=SharedGroupNameAttributecn/Property
Property
name=SharedGroupSearchBaseou=SharedGroups/Property
Property
name=SharedGroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=SharedTenantNameListFilter(objectClass=organizationalUnit)/Property
Property nam
artifact id: 789b9249-1605-4d70-ba6d-cda88dce4bd2. The path
'/_system/governance/esbconnectors/dus...@wso2.com/Test123/1.0.0'
contains one or more illegal characters (~!@#;%^*()+={}|\',)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:216)
at
org.wso2.carbon.governance.api.generic.GenericArtifactManager.addGenericArtifact(GenericArtifactManager.java:170)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 97 more
Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException:
The path '/_system/governance/esbconnectors/
dus...@wso2.com/Test123/1.0.0' contains one or more illegal
characters (~!@#;%^*()+={}|\',)
at
org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:262)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:465)
at
org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:657)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:194)
... 103 more
Cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Dushan Abeyruwan | Associate Tech Lead
[Dev] [Connector-Store] ES 1.1.0 M3 when try to add new assert
Hi
Have done changes to user-mgt.xml, instead of *uid*, changes to *mail*
address, getting exception how to avoid ?
--
UserStoreManager
class=org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager
Property
name=TenantManagerorg.wso2.carbon.user.core.tenant.CommonHybridLDAPTenantManager/Property
Property name=ReadOnlytrue/Property
Property name=Disabledfalse/Property
Property name=MaxUserNameListLength100/Property
Property name=ConnectionURL/Property
Property name=ConnectionName*uid=connectorstoreuse*
r,/Property
Property name=ConnectionPasswordx/Property
Property name=passwordHashMethodMD5/Property
Property name=UserSearchBaseou=user,/Property
Property
name=UserNameListFilter(objectClass=inetOrgPerson)/Property
Property
name=UserNameSearchFilter(amp;(objectClass=inetOrgPerson)*(mail=?)*
)/Property
Property name=UserNameAttribute*mail*/Property
Property name=ReadGroupstrue/Property
Property name=GroupSearchBasexx/Property
Property
name=GroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=GroupNameSearchFilter(amp;(objectClass=groupOfNames)(cn=?))/Property
Property name=GroupNameAttributecn/Property
Property name=SharedGroupNameAttributecn/Property
Property
name=SharedGroupSearchBaseou=SharedGroups/Property
Property
name=SharedGroupNameListFilter(objectClass=groupOfNames)/Property
Property
name=SharedTenantNameListFilter(objectClass=organizationalUnit)/Property
Property nam
artifact id: 789b9249-1605-4d70-ba6d-cda88dce4bd2. The path
'/_system/governance/esbconnectors/dus...@wso2.com/Test123/1.0.0' contains
one or more illegal characters (~!@#;%^*()+={}|\',)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:216)
at
org.wso2.carbon.governance.api.generic.GenericArtifactManager.addGenericArtifact(GenericArtifactManager.java:170)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 97 more
Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException: The
path '/_system/governance/esbconnectors/dus...@wso2.com/Test123/1.0.0'
contains one or more illegal characters (~!@#;%^*()+={}|\',)
at org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:262)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:465)
at
org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:657)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:194)
... 103 more
Cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ESB 4.8.1 Integration tests
Can't find 4.8.1 related references hosted in http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/ Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.8.1 Integration tests
PING ! did we or didn't ? or do we need to refer somewhere else? Index of /nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/Name Last ModifiedSizeDescriptionParent Directory http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/ maven-metadata.xml http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/maven-metadata.xml Wed Dec 04 10:17:16 PST 2013406 maven-metadata.xml.md5 http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/maven-metadata.xml.md5 Thu May 15 07:04:40 PDT 201433 maven-metadata.xml.sha1 http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/maven-metadata.xml.sha1 Thu May 15 07:04:40 PDT 201441 4.5.0/ http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/4.5.0/Thu Sep 13 00:09:43 PDT 2012 4.6.0/ http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/4.6.0/Fri Dec 21 09:30:19 PST 2012 4.7.0/ http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/4.7.0/Tue Aug 06 04:18:28 PDT 2013 4.8.0/ http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/4.8.0/Wed Dec 04 10:17:09 PST 2013 On Mon, Jun 9, 2014 at 1:34 PM, Dushan Abeyruwan dus...@wso2.com wrote: Can't find 4.8.1 related references hosted in http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/esb/esb-integration-tests/ Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] JavaScript API for Script mediator
I tried following script language=js ![CDATA[var a=dushanabeyruwan; var b=a.substring(1,6); print(b)]]/script it works [2014-05-31 20:22:35,699] INFO - LogMediator Progress check = Starting *pring##ushan* even you can directly invoke Rihno to see what sort of string funtions available dushan@xx:~/poc/rihno/rhino1_7R4/build/rhino1_7R4$ java -jar js.jar Rhino 1.7 release 4 2014 02 18 js var a=abced js var b=a.substring(1,3) js print(b) bc js On Thu, May 29, 2014 at 3:53 PM, Ramindu Deshapriya rasad...@gmail.com wrote: Hi Ishan, Thanks. Seems most Synapse-based methods are implemented as JavaScript functions. However, when I attempted to use the substring function, it gave the following error: com.sun.phobos.script.util.ExtendedScriptException: org.mozilla.javascript.EcmaError: TypeError: Cannot find function substring. (Unknown Source#25) in Unknown Source at line number 25 Are the basic JavaScript functions not available? Thanks. On Thu, May 29, 2014 at 3:43 PM, Ishan Jayawardena-2 [via WSO2 Oxygen Tank] [hidden email] http://user/SendEmail.jtp?type=nodenode=97416i=0 wrote: You can find it in org.apache.synapse.mediators.bsf.ScriptMessageContext. Thanks, Ishan. On Thu, May 29, 2014 at 3:29 PM, Ramindu Deshapriya [hidden email] http://user/SendEmail.jtp?type=nodenode=97415i=0 wrote: Hi, I am having trouble finding the functions available to the JavaScript API when used within a Script Mediator in the ESB. Could someone please direct me to a list of functions which are available for use within a Script Mediator? Thanks. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-JavaScript-API-for-Script-mediator-tp97411.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=97415i=1 http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ishan Jayawardena Senior Software Engineer Mobile: a href=tel:%2B94%20%2877%29%20408%202330 value=+94774082330 target=_blank+94 (77) 408 2330 ___ Dev mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=97415i=2 http://wso2.org/cgi-bin/mailman/listinfo/dev -- If you reply to this email, your message will be added to the discussion below: http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-JavaScript-API-for-Script-mediator-tp97411p97415.html To start a new topic under WSO2 Development, email [hidden email] http://user/SendEmail.jtp?type=nodenode=97416i=1 To unsubscribe from WSO2 Development, click here. NAML http://wso2-oxygen-tank.10903.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- Au revoir! Ramindu Deshapriya. Member - Sahana Software Foundation http://sahanafoundation.org http://rdeshapriya.com http://www.facebook.com/rdeshapriya http://twitter.com/#%21/rami_desh https://plus.google.com/113801459480978566130 http://www.linkedin.com/profile/view?id=84017607trk=tab_pro http://rdeshapriya.com http://lmakuthan.blogspot.com -- View this message in context: Re: [Dev] [ESB] JavaScript API for Script mediator http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-JavaScript-API-for-Script-mediator-tp97411p97416.html Sent from the WSO2 Development mailing list archive http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Class mediator - task scheduler error
ute(MessageInjector.java:315) at org.apache.synapse.startup.quartz.SimpleQuartzJob.execute(SimpleQuartzJob.java:88) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) Caused by: java.lang.NullPointerException at org.wso2.cloud.monitor.agent.esb.mediators.icinga.IcingaAdapter.mediate(IcingaAdapter.java:89) what this class mediator does ? its obvious theat error thrown from your class mediator, debug it. at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78) ... 11 more [2014-05-30 15:16:12,137] ERROR - ErrorLogger Job (synapse.simple.quartz.TriggerSequence threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: org.apache.synapse.SynapseException: Error occured in the mediation of the class mediator] at org.quartz.core.JobRunShell.run(JobRunShell.java:224) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) Caused by: org.apache.synapse.SynapseException: Error occured in the mediation of the class mediator at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:82) 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.filters.InMediator.mediate(InMediator.java:61) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:228) at org.apache.synapse.startup.tasks.MessageInjector.execute(MessageInjector.java:315) at org.apache.synapse.startup.quartz.SimpleQuartzJob.execute(SimpleQuartzJob.java:88) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) ... 1 more Caused by: java.lang.NullPointerException at org.wso2.cloud.monitor.agent.esb.mediators.icinga.IcingaAdapter.mediate(IcingaAdapter.java:89) at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78) ... 11 more Any help would be much appreciated! Thanks. /Gayashan -- Gayashan Amarasinghe Software Engineer WSO2, Inc. ; http://wso2.com lean. enterprise. middleware Mobile: +94718314517 Blog: gayashan-a.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB Connector Store Icons
HI Chanaka, Can't we have more closer (i.e similar to connector store icons banners), for me devs icons almost in same color. Cheers, Dushan On Tue, May 13, 2014 at 6:06 AM, Chanaka Jayasena chan...@wso2.com wrote: Hi Dushan, upload those images to Drive under Dev Studio Icons. thanks, Chanaka On Mon, May 12, 2014 at 9:51 AM, Chanaka Jayasena chan...@wso2.comwrote: Sure, Dushan. I will provide them by EOD. thanks, Chanaka On Mon, May 12, 2014 at 7:49 AM, Dushan Abeyruwan dus...@wso2.comwrote: Hi Chanaka, Additionally, we need icon for devloper studio as well ref https://github.com/dushansachinda/esb-connectors/tree/master/salesforce/1.0.0/src/main/resources/icon can we get icons as well for all the connectors (other than, salesfoce,googlesh,twitter,twilio,jira) Cheers, Dushan On Thu, May 8, 2014 at 11:23 AM, Chanaka Jayasena chan...@wso2.comwrote: 580 x 300 banner 220 x 200 icon thumb thanks, Chanaka On Thu, May 8, 2014 at 8:49 AM, Malaka Silva mal...@wso2.com wrote: Hi Chanaka, What is the resolution you have used for log and banner. We may need to use the same for other connectors? Best Regards, Malaka On Sun, May 4, 2014 at 11:26 AM, Chanaka Jayasena chan...@wso2.comwrote: Hi Dushan, the Google drive is updated with the latest. thanks, Chanaka On Fri, May 2, 2014 at 5:35 PM, Chanaka Jayasena chan...@wso2.comwrote: Noted. I will update and provide you with the remaining connector icons as well. Thanks, Chanaka On Fri, May 2, 2014 at 1:20 PM, Dushan Abeyruwan dus...@wso2.comwrote: Hi ChanakaJ On Fri, May 2, 2014 at 9:00 AM, Malaka Silva mal...@wso2.comwrote: Hi All, IMO we should not modify the backgroung color and layout outside what vendors(Third parties) are using. Eg: - Salesforce logo is in green color whereas standard is blue. Yes, I feel the same as we should not modify exiting vendors layout colors, overall felt only salesforce has such issue. meantime, can we get the remaining connector images as well [1] shows you the connectors we have at the moment https://github.com/wso2-dev/esb-connectors we should add, facebook,gmail.amazon s3,google drive,suvaymonkey, sugerCRM. Best Regards, Malaka On Fri, May 2, 2014 at 8:08 AM, Chanaka Jayasena chan...@wso2.com wrote: Hi Dushan, [1] contains the images you requested for the Connector Store. Amazon s3 and Survey Monkey icons are missing. I will upload those ones they are done. 1 - https://drive.google.com/a/wso2.com/folderview?id=0B_CCkDYHWyB9VGlJc0MzWnRpYkUusp=sharing#grid thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http
Re: [Dev] WSO2 ESB Connector Store Icons
Hi Chanaka, Additionally, we need icon for devloper studio as well ref https://github.com/dushansachinda/esb-connectors/tree/master/salesforce/1.0.0/src/main/resources/icon can we get icons as well for all the connectors (other than, salesfoce,googlesh,twitter,twilio,jira) Cheers, Dushan On Thu, May 8, 2014 at 11:23 AM, Chanaka Jayasena chan...@wso2.com wrote: 580 x 300 banner 220 x 200 icon thumb thanks, Chanaka On Thu, May 8, 2014 at 8:49 AM, Malaka Silva mal...@wso2.com wrote: Hi Chanaka, What is the resolution you have used for log and banner. We may need to use the same for other connectors? Best Regards, Malaka On Sun, May 4, 2014 at 11:26 AM, Chanaka Jayasena chan...@wso2.comwrote: Hi Dushan, the Google drive is updated with the latest. thanks, Chanaka On Fri, May 2, 2014 at 5:35 PM, Chanaka Jayasena chan...@wso2.comwrote: Noted. I will update and provide you with the remaining connector icons as well. Thanks, Chanaka On Fri, May 2, 2014 at 1:20 PM, Dushan Abeyruwan dus...@wso2.comwrote: Hi ChanakaJ On Fri, May 2, 2014 at 9:00 AM, Malaka Silva mal...@wso2.com wrote: Hi All, IMO we should not modify the backgroung color and layout outside what vendors(Third parties) are using. Eg: - Salesforce logo is in green color whereas standard is blue. Yes, I feel the same as we should not modify exiting vendors layout colors, overall felt only salesforce has such issue. meantime, can we get the remaining connector images as well [1] shows you the connectors we have at the moment https://github.com/wso2-dev/esb-connectors we should add, facebook,gmail.amazon s3,google drive,suvaymonkey, sugerCRM. Best Regards, Malaka On Fri, May 2, 2014 at 8:08 AM, Chanaka Jayasena chan...@wso2.comwrote: Hi Dushan, [1] contains the images you requested for the Connector Store. Amazon s3 and Survey Monkey icons are missing. I will upload those ones they are done. 1 - https://drive.google.com/a/wso2.com/folderview?id=0B_CCkDYHWyB9VGlJc0MzWnRpYkUusp=sharing#grid thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] CAR deployment broken due to following changes
HI KasunG,
Previous workable deployment,
SynapseAppDeployer.java
---
/**
* Finds the correct deployer for the given artifact type
*
* @param axisConfig - AxisConfiguration instance
* @return Deployer instance
*/
private Deployer getDeployer(AxisConfiguration axisConfig, String
directory) {
Deployer deployer = null;
// access the deployment engine through axis config
DeploymentEngine deploymentEngine = (DeploymentEngine)
axisConfig.getConfigurator();
String tenantId = AppDeployerUtils.getTenantIdString(axisConfig);
SynapseEnvironmentService environmentService =
DataHolder.getInstance().
getSynapseEnvironmentService(Integer.parseInt(tenantId));
if (environmentService != null) {
String synapseConfigPath =
ServiceBusUtils.getSynapseConfigAbsPath(
environmentService.getSynapseEnvironment().getServerContextInformation());
String endpointDirPath = synapseConfigPath
+ File.separator + directory;
deployer = deploymentEngine.getDeployer(endpointDirPath,
ServiceBusConstants.ARTIFACT_EXTENSION);
}
return deployer;
}
change You have done.. GIT ref* {79e529f18c4db6b45d7d0c8fd5f2288a70aee680}*
/**
* Finds the correct deployer for the given artifact type
*
* @param axisConfig - AxisConfiguration instance
* @return Deployer instance
*/
private Deployer getDeployer(AxisConfiguration axisConfig, String
directory) {
// access the deployment engine through axis config
DeploymentEngine deploymentEngine = (DeploymentEngine)
axisConfig.getConfigurator();
String endpointDirPath = getArtifactDirPath(axisConfig, directory);
return deploymentEngine.getDeployer(endpointDirPath,
SynapseAppDeployerConstants.ARTIFACT_EXTENSION);
}
questions ?
Any reason why this done ? for the same reason ESB CAP deployment broken ..
cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Bean Mediator Property Serialization
Hi Sohani,
IMO the config language of bean mediator,
bean action=CREATE | REMOVE | SET_PROPERTY | GET_PROPERTY class=string
property=string value=string | {xpath} var=string
/bean
On Fri, May 2, 2014 at 4:54 PM, Sohani Weerasinghe soh...@wso2.com wrote:
Hi All,
In ESB Management Console all possible properties for Bean Mediator are
displayed and also serialized regardless of the Action (i.e Remove, Create,
Set_Property,Get_Property). I think only relevant properties should be
displayed and serialized as listed below.
If the Action is Create - Var and Class
If the Action is Remove - Var
If the Action is Set_Property - Var, Property, Value type and Literal
If the the Action is Get_Property - Var, Property, Target type and Literal.
I agree with these changes so basically hope you try to implement a
validation rules am I ?
anyway Bean Mediator it self can not use independently as it should use
along side with EJB mediator..
WDYT? Please correct if this is wrong
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB Connector Store Icons
Hi ChanakaJ On Fri, May 2, 2014 at 9:00 AM, Malaka Silva mal...@wso2.com wrote: Hi All, IMO we should not modify the backgroung color and layout outside what vendors(Third parties) are using. Eg: - Salesforce logo is in green color whereas standard is blue. Yes, I feel the same as we should not modify exiting vendors layout colors, overall felt only salesforce has such issue. meantime, can we get the remaining connector images as well [1] shows you the connectors we have at the moment https://github.com/wso2-dev/esb-connectors we should add, facebook,gmail.amazon s3,google drive,suvaymonkey, sugerCRM. Best Regards, Malaka On Fri, May 2, 2014 at 8:08 AM, Chanaka Jayasena chan...@wso2.com wrote: Hi Dushan, [1] contains the images you requested for the Connector Store. Amazon s3 and Survey Monkey icons are missing. I will upload those ones they are done. 1 - https://drive.google.com/a/wso2.com/folderview?id=0B_CCkDYHWyB9VGlJc0MzWnRpYkUusp=sharing#grid thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures while running product integration tests on Jenkins due to SecurityConfigException
$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679) 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.NullPointerException at org.wso2.carbon.security.config.SecurityConfigAdmin.init(SecurityConfigAdmin.java:162) ... 49 more -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the git location for mediation security
https://github.com/wso2-dev/carbon-mediation/tree/master/components/mediation-admin/org.wso2.carbon.mediation.security/ On Wed, Apr 30, 2014 at 7:03 PM, Udara Liyanage ud...@wso2.com wrote: Hi, $subject. I looked at [1], but could not find it. [1] https://github.com/wso2/carbon-mediation/tree/master/components -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] The type javax.xml.stream.XMLStreamException cannot be resolved. It is indirectly referenced from required .class files
Hi Kasun,
Thanks, will take update in kernal.
Cheers,
Dushan
On Wed, Apr 30, 2014 at 11:21 AM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Dushan,
This has been fixed in kernel. It seems there are build failure in there
hence the commits are not reflected in nexus yet.
Regards,
KasunG
On Wed, Apr 30, 2014 at 10:47 AM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi
Test wso2esb-4.9.0-SNAPSHOT build 24th April.
$subject can I know why this happens ? it seems only JSPs not able to
pick the depenecies correctly, to test this class loader issue, I just
copied..
same code segment.. to ProxyServiceAdminClient and it works. only issue
here IMO JSP compilation has some issue in resolving dependencies..
et threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [1] in the generated java file:
[/home/dushan/poc/server/5.0.0/wso2esb-4.9.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_1129124789/org/apache/jsp/proxyservices/source_jsp.java]
The type javax.xml.stream.XMLStreamException cannot be resolved. It is
indirectly referenced from required .class files
An error occurred at line: [26] in the generated java file:
[/home/dushan/poc/server/5.0.0/wso2esb-4.9.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_1129124789/org/apache/jsp/proxyservices/source_jsp.java]
The import javax.xml.stream.XMLStreamException cannot be resolved
An error occurred at line: 96 in the jsp file: /proxyservices/source.jsp
XMLStreamException cannot be resolved to a type
93: try {
94: elem= AXIOMUtil.stringToOM(source);
95: XMLPrettyPrinter.prettify(elem,stream);
96: } catch (XMLStreamException e) {
97: e.printStackTrace();
98: } catch (Exception e) {
99: e.printStackTrace();
An error occurred at line: 97 in the jsp file: /proxyservices/source.jsp
e cannot be resolved
94: elem= AXIOMUtil.stringToOM(source);
95: XMLPrettyPrinter.prettify(elem,stream);
96: } catch (XMLStreamException e) {
97: e.printStackTrace();
98: } catch (Exception e) {
99: e.printStackTrace();
100: }
Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:468)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
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.GeneratedMethodAccessor42.invoke(Unknown Source
Re: [Dev] [ESB] Adding attachment to Synapse MessageContext
HI Ramindu, There is a gmail connector which has pretty similar implementation can you follow that.. meantime @adding Sewwandi [1] https://github.com/wso2-dev/esb-connectors/blob/master/gmail/src/main/java/org/wso2/carbon/connector/gmail/GmailUtils.java Cheers, Dushan On Mon, Apr 28, 2014 at 7:33 AM, Malaka Silva mal...@wso2.com wrote: Hi Jeewantha, I guess they are trying this using out-only. It can be simulated using a class mediator. Enabling MTOM will not help in this case? On Fri, Mar 21, 2014 at 11:13 AM, Jeewantha Dharmaparakrama jeewan...@wso2.com wrote: Hi Ramindu, Is SOAP with attachments enabled in the ESB? You might need to enable MTOM [1] [1] https://docs.wso2.org/pages/viewpage.action?pageId=26838822 Jeewantha On Wed, Mar 19, 2014 at 2:10 PM, Ramindu Deshapriya rasad...@gmail.comwrote: Hi Paul, Paul Fremantle-2 wrote How are you serializing the message? I'm not serializing it, as far as I can tell. I'm receiving an input stream for a file from a backend service (Google Contacts API) and attempting to attach it to the Synapse message context by assigning it to a DataHandler. Thanks. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Adding-attachment-to-Synapse-MessageContext-tp93759p93761.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Jeewantha Dharmaparakrama Software Engineer; WSO2, Inc.; http://wso2.com/ Phone : (+94) 774726790 Skype : prasad.jeewantha LinkedIn : http://www.linkedin.com/in/jeewanthad Twitter: https://twitter.com/jeewamp Blog: http://jeewanthad.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESBJAVA-1777 is reproducible in ESB 4.7.0, 4.8.0, and 4.8.1
Hi, Did you try same with SimpleStockQuote BE? Cheers, Dushan On Sat, Mar 29, 2014 at 5:05 AM, Lahiru Sandaruwan lahi...@wso2.com wrote: Sent the proxy config with wrong endpoint, On Fri, Mar 28, 2014 at 10:09 AM, Lahiru Sandaruwan lahi...@wso2.comwrote: Hi, $subject. Here is the proxy i try. Am i doing something wrong? ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapsehttp://www.google.com/url?q=http%3A%2F%2Fws.apache.org%2Fns%2Fsynapsesa=Dsntz=1usg=AFQjCNHXEm-DVy-kXjma9HiDSOzvmv4DoA name=utTockenProxy transports=https statistics=disable trace=disable startOnLoad=true target inSequence log level=full/ send endpoint address uri=https://localhost:8280/services/echo/ /endpoint /send /inSequence /target parameter name=ScenarioIDscenario1/parameter enableSec/ policy key=conf:/repository/axis2/service-groups/utTockenProxy/services/utTockenProxy/policies/UTOverTransport/ description/ /proxy *Error,* [2014-03-28 10:05:23,262] INFO - LogMediator To: /services/normalProxy.normalProxyHttpsSoap12Endpoint, WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:fcc30644-4305-43d8-ae58-cb49694c3873, Direction: request, Envelope: ?xml version=1.0 encoding=utf-8?soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Bodyp:echoInt xmlns:p=http://echo.services.core.carbon.wso2.org;!--0 to 1 occurrence--in23/in/p:echoInt/soapenv:Body/soapenv:Envelope [2014-03-28 10:05:23,322] ERROR - NativeWorkerPool Uncaught exception org.apache.axiom.soap.SOAPProcessingException: SOAP Envelope can not have children other than SOAP Header and Body at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.checkChild(SOAPEnvelopeImpl.java:110) at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.insertBefore(SOAPEnvelopeImpl.java:164) at org.apache.ws.security.util.WSSecurityUtil.prependChildElement(WSSecurityUtil.java:646) at org.apache.ws.security.util.WSSecurityUtil.findWsseSecurityHeaderBlock(WSSecurityUtil.java:722) at org.apache.ws.security.message.WSSecHeader.insertSecurityHeader(WSSecHeader.java:145) at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:406) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61) 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.Axis2Sender.sendBack(Axis2Sender.java:163) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225) 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) Thanks. -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESBJAVA-1777 is reproducible in ESB 4.7.0, 4.8.0, and 4.8.1
Hi Anyways will test this once again.It was fixed and verified in 460 , may be this has been broken again due to some other fixes its a regression issue.. On Sat, Mar 29, 2014 at 7:17 AM, Dushan Abeyruwan dus...@wso2.com wrote: Hi, Did you try same with SimpleStockQuote BE? Cheers, Dushan On Sat, Mar 29, 2014 at 5:05 AM, Lahiru Sandaruwan lahi...@wso2.comwrote: Sent the proxy config with wrong endpoint, On Fri, Mar 28, 2014 at 10:09 AM, Lahiru Sandaruwan lahi...@wso2.comwrote: Hi, $subject. Here is the proxy i try. Am i doing something wrong? ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapsehttp://www.google.com/url?q=http%3A%2F%2Fws.apache.org%2Fns%2Fsynapsesa=Dsntz=1usg=AFQjCNHXEm-DVy-kXjma9HiDSOzvmv4DoA name=utTockenProxy transports=https statistics=disable trace=disable startOnLoad=true target inSequence log level=full/ send endpoint address uri=https://localhost:8280/services/echo/ /endpoint /send /inSequence /target parameter name=ScenarioIDscenario1/parameter enableSec/ policy key=conf:/repository/axis2/service-groups/utTockenProxy/services/utTockenProxy/policies/UTOverTransport/ description/ /proxy *Error,* [2014-03-28 10:05:23,262] INFO - LogMediator To: /services/normalProxy.normalProxyHttpsSoap12Endpoint, WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:fcc30644-4305-43d8-ae58-cb49694c3873, Direction: request, Envelope: ?xml version=1.0 encoding=utf-8?soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Bodyp:echoInt xmlns:p=http://echo.services.core.carbon.wso2.org;!--0 to 1 occurrence--in23/in/p:echoInt/soapenv:Body/soapenv:Envelope [2014-03-28 10:05:23,322] ERROR - NativeWorkerPool Uncaught exception org.apache.axiom.soap.SOAPProcessingException: SOAP Envelope can not have children other than SOAP Header and Body at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.checkChild(SOAPEnvelopeImpl.java:110) at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.insertBefore(SOAPEnvelopeImpl.java:164) at org.apache.ws.security.util.WSSecurityUtil.prependChildElement(WSSecurityUtil.java:646) at org.apache.ws.security.util.WSSecurityUtil.findWsseSecurityHeaderBlock(WSSecurityUtil.java:722) at org.apache.ws.security.message.WSSecHeader.insertSecurityHeader(WSSecHeader.java:145) at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:406) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61) 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.Axis2Sender.sendBack(Axis2Sender.java:163) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:274) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225) 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) Thanks. -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Getting random NullPointerException on Operation Client during Connector Integration Tests
Hi Shall we try with 5s Cheers Dushan On Wed, Mar 12, 2014 at 1:05 PM, Ramindu Deshapriya rasad...@gmail.comwrote: Hi Dushan, Dushan Abeyruwan wrote [2]https://wso2.org/jira/browse/ESBJAVA-2419 Thank you very much for this solution. The fix for this suggests increasing the wait time for transport listener shutdown. What is the default time and what level of increase would you suggest? Thanks. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Getting-random-NullPointerException-on-Operation-Client-during-Connector-Integration-Tests-tp93294p93342.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Getting random NullPointerException on Operation Client during Connector Integration Tests
Hi In ESB you need to pass -Dtransport.listener.shutdown.wait.sec=xx pass by embedding either that to wso2server.sh or ./wso2server.sh -Dtransport.listener.shutdown.wait.sec=xx On Wed, Mar 12, 2014 at 4:47 PM, Ramindu Deshapriya rasad...@gmail.comwrote: Hi Dushan, Dushan Abeyruwan wrote Hi Shall we try with 5s Thanks a lot, test runs are passing with 5s. Is there a way to set this parameter via a configuration in the ESB? Thanks. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Getting-random-NullPointerException-on-Operation-Client-during-Connector-Integration-Tests-tp93294p93356.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Getting random NullPointerException on Operation Client during Connector Integration Tests
Hi Ramidu
Can I know I you terminate your client operations? when searching issue
related to the stack you posted, it seems like the client handler shutdown
immediately but still there are some requests being processing.
based on the searching [1] reported similar issue and to avoid what we have
suggested [2]
[1]https://wso2.org/jira/browse/CARBON-10439
[2]https://wso2.org/jira/browse/ESBJAVA-2419
Cheers,
Dushan
https://wso2.org/jira/browse/CARBON-10439
On Tue, Mar 11, 2014 at 3:15 PM, Ramindu Deshapriya rasad...@gmail.comwrote:
Hi,
I have written 50+ Integration Tests for the Google Drive Cloud Connector
using a ServiceClient to send messages to the ESB. I use the following
method to build the client:
public static OperationClient buildMEPClient(EndpointReference endpoint,
OMElement request) throws AxisFault {
ServiceClient serviceClient = new ServiceClient();
Options serviceOptions = new Options();
serviceOptions.setTo(endpoint);
serviceOptions.setAction(mediate);
serviceClient.setOptions(serviceOptions);
MessageContext messageContext = new MessageContext();
SOAPEnvelope soapEnvelope =
TransportUtils.createSOAPEnvelope(request);
messageContext.setEnvelope(soapEnvelope);
OperationClient mepClient =
serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
mepClient.addMessageContext(messageContext);
return mepClient;
}
after which I call mepClient.execute(true) to receive a response in the
following manner within each test:
mepClient = ConnectorIntegrationUtil.buildMEPClient(new EndpointReference(
getProxyServiceURL(CONNECTOR_NAME + _ + methodName)),
requestEnvelope);
mepClient.execute(true);
MessageContext responseMsgCtx =
mepClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
However, when running this test suite, sometimes I receive random
NullPointerExceptions on different methods. Note that I do not get this
exception on the same test methods, rather I might get it on one or two
random methods during a single test run or I might not get it at all. The
stack trace for a typical occurrence is;
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.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:270)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.connector.integration.test.googledrive.GoogledriveConnectorIntegrationTest.testgetCommentByIDOptionalParams(GoogledriveConnectorIntegrationTest.java:1316)
In these instances, I have noticed that the correct response is returned by
the backend API via monitoring the wire log, however, the test will simply
fail giving the above stack trace.
Is there any way to overcome this issue?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Getting-random-NullPointerException-on-Operation-Client-during-Connector-Integration-Tests-tp93294.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Getting random NullPointerException on Operation Client during Connector Integration Tests
Hi Ramidu,
[found few typo error in previous reply] please do apologize.
Anyway what i need to know,
How you terminate your client operations ?
Anyway, found similar sort of issues reported [1] and possible workaround
in [2]
[1]https://wso2.org/jira/browse/CARBON-10439
[2]https://wso2.org/jira/browse/ESBJAVA-2419
Cheers,
Dushan
On Tue, Mar 11, 2014 at 9:37 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi Ramidu
Can I know I you terminate your client operations? when searching issue
related to the stack you posted, it seems like the client handler shutdown
immediately but still there are some requests being processing.
based on the searching [1] reported similar issue and to avoid what we
have suggested [2]
[1]https://wso2.org/jira/browse/CARBON-10439
[2]https://wso2.org/jira/browse/ESBJAVA-2419
Cheers,
Dushan
https://wso2.org/jira/browse/CARBON-10439
On Tue, Mar 11, 2014 at 3:15 PM, Ramindu Deshapriya rasad...@gmail.comwrote:
Hi,
I have written 50+ Integration Tests for the Google Drive Cloud Connector
using a ServiceClient to send messages to the ESB. I use the following
method to build the client:
public static OperationClient buildMEPClient(EndpointReference endpoint,
OMElement request) throws AxisFault {
ServiceClient serviceClient = new ServiceClient();
Options serviceOptions = new Options();
serviceOptions.setTo(endpoint);
serviceOptions.setAction(mediate);
serviceClient.setOptions(serviceOptions);
MessageContext messageContext = new MessageContext();
SOAPEnvelope soapEnvelope =
TransportUtils.createSOAPEnvelope(request);
messageContext.setEnvelope(soapEnvelope);
OperationClient mepClient =
serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
mepClient.addMessageContext(messageContext);
return mepClient;
}
after which I call mepClient.execute(true) to receive a response in the
following manner within each test:
mepClient = ConnectorIntegrationUtil.buildMEPClient(new EndpointReference(
getProxyServiceURL(CONNECTOR_NAME + _ +
methodName)),
requestEnvelope);
mepClient.execute(true);
MessageContext responseMsgCtx =
mepClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
However, when running this test suite, sometimes I receive random
NullPointerExceptions on different methods. Note that I do not get this
exception on the same test methods, rather I might get it on one or two
random methods during a single test run or I might not get it at all. The
stack trace for a typical occurrence is;
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.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:270)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.connector.integration.test.googledrive.GoogledriveConnectorIntegrationTest.testgetCommentByIDOptionalParams(GoogledriveConnectorIntegrationTest.java:1316)
In these instances, I have noticed that the correct response is returned
by
the backend API via monitoring the wire log, however, the test will simply
fail giving the above stack trace.
Is there any way to overcome this issue?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Getting-random-NullPointerException-on-Operation-Client-during-Connector-Integration-Tests-tp93294.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
[Dev] [dev]Multipart Form Builder/formatter issue
Hi If I submit a form with following, via ESB which is actually building the message context POST http://localhost:8281/services/MultiPartProxyForm HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: multipart/form-data; boundary==_Part_102_1087728996.1394197391830 MIME-Version: 1.0 Authorization: bearer AG5nTAAAyJ7YVsK5uOqUV7dKA7TyRTVXheo%3DH3WEcdgt6MUJ9iTMcHZVjZGKombXB7BBB2AAdgKag0 Transfer-Encoding: chunked Host: localhost:8281 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) --=_Part_102_1087728996.1394197391830 Content-Type: image/jpeg; name=images.jpg Content-Transfer-Encoding: binary Content-Disposition: form-data; name=images.jpg; filename=images.jpg and when build message intermediately via ESB it selects messageBuilder contentType=multipart/form-data class=org.apache.axis2.builder.MultipartFormDataBuilder/ messageFormatter contentType=multipart/form-data class=org.apache.axis2.transport.http.MultipartFormDataFormatter/ above is correct but the out put messages derived is not same as to how it receives and the i problem is BE is not accepting if multipart-form re-generated as given below, this must be a bug in axis2 builder or,provide me a hint on how to overcome this in more generic way.. POST /CKFileUploadApp/UploadServlet HTTP/1.1 Authorization: bearer AG5nTAAAyJ7YVsK5uOqUV7dKA7TyRTVXheo%3DH3WEcdgt6MUJ9iTMcHZVjZGKombXB7BBB2AAdgKag0 MIME-Version: 1.0 Accept-Encoding: gzip,deflate Content-Type: multipart/form-data; charset=UTF-8; boundary=MIMEBoundary_8064db5a95965d4e0caa302d87fbd3713b0e7b93a34ee1a2 Transfer-Encoding: chunked Host: 127.0.0.1:9765 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO 68c --MIMEBoundary_8064db5a95965d4e0caa302d87fbd3713b0e7b93a34ee1a2 Content-Disposition: form-data; name=images.jpg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit /9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAkGBwgHBgkIBwgKCgkLDRYPDQwMDRsUFRAWIB0iIiAdHx8kKDQsJCYxJx8fLT0tMTU3Ojo6Iys/PD9EQzQ5OjcBCgoKDQwOGw8PGjcjICUxNDU3MzQ3NzQ0Nzc4MDc3NzY0NzIvOC83NC03NCwsNzQvNCw3OC8wLiwsODQ0LDQsNP/AABEIACoAKgMBEQACEQEDEQH/xAAbAAACAgMBBgQFAgMHAf/EADMQAAEDAwEHAQQLAQECAwQABRESBhMhMUFRYXEzkaHSFCIjJDJSgYSiwdEW/8QAGgEAAgMBAQQBAgUDBv/EAC0RAAEEAAMECgMBAAEAAgMEERIhBTJRYRMUIiMxUoGRofAVQXHh/9oADAMBAAIRAxEAPwDuNCFV3K9s2+SGHGXnFaAvKNOMHPcjtSNvaENVwbJjql5bDYjgQoR2thg4MWV/D5qXG2ax4+3+rl16PgfvqpFs2ji3GZ9FaZfbc0lQLgTgjPgnvTle5HOcGLrFZZKcArmmkwihC1yFrbYcW03vXEpJSjONR7Z6VBxA0UEkDRJNwuKLg8HpNuKXAnQdMxaCMdCNPTjXnLO0qz34TQ4kaarMksMce0zX+qA47BH4rc4f36/lrkLlH9QrkZYfJ8rKFeIdtkiRGtit7jSPvZVnPTBTTUF+Bju6iwJVo7UUZ7DNf6ugQn1yIrbrjRaWpIKkE50ntnrW80kjErWaSQCVvqVKKEJZ2mtJWFToYBWB9q2nmodx5HxHpWPtTZ/WB0jN4fKRt183bb4pMfdGCcjHPNeZa1ZBKYNkrHv1i4TUYA9ihQ5efWvUbNpdE3pHjU/C06VbDvHjX9J4SABhPKtZaS9oQly63CQ7IkRozwaLIwUjGSSkEZPQcenGnoIW5Q94xxWdZsPDixhwwUCyJjxpX0mdLlGVpwS5qKB6HiPjV7AkeMrWjDl4qtZ0TTme45ufgtci2WZy6plJnMiMTqUxnhq8ePFY34jvuly+nNSY6xkz5hhw5ov6ra4oyIM2S3LCMJUxnSccgeIHuIrcqsmHZc0FvNUtSQntNcQ7l9wWGz20U1E2PDmq3yXjoBx9ZJx36j1410uUo2sMjNMFSndkLxG/XFPIORmsdbCpbzs9GuTokBS2JIGN60cEjse9MwW5IRlGo4FKz045jmOh4hUzmzt7aJ3NwadHTeN4PvpwXoTvM9ikjs+Ybr/cLUbHf1DClMfos/5Vuu1/KfvqqdQs+YffRY/8pdHvbSm0DrpSSan8kwbrFI2ZId56urJsvGtrgeUpTr351/1SNi5JPodBwT1elFAcRqeKYOVKptFCEUIRQhFCEUIRQhf/2Q== --MIMEBoundary_8064db5a95965d4e0caa302d87fbd3713b0e7b93a34ee1a2-- 0 Cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Script mediator vs Filter mediator
Hi Can I know your use case ? why you need script mediator ? why you rationalize the difference between filter and script ? In general ScriptMediator uses 3rd party libs and Filter mediator is in build with synapse so ideally Filter should be perform well, since script mediator injecting 3rd party script engines i.e java script or groovy engines and in the context of performance aspect, it depend what you will try to do with that. Cheers, Dushan On Thu, Feb 20, 2014 at 9:02 PM, Krishantha Dinesh kr...@krishantha.comwrote: Hi, I have short question. is there any significant performance hit between script mediator and filter mediator? what is recommended to use? ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Encode Url in ESB
Hi OK,then how about falling back to your original fix (which uses) script mediator, encode http://www.linkedin.com/pub/X-/87/998/935 to http%3A%2F%2Fwww.linkedin.com http://2fwww.linkedin.com/% 2Fpub%2FX-%2F87%2F998%2F935. basically replace : and / then use setup mediator then use header mediator header name=To expression=add encoded rul/, and send request via Default endpoints to send message. Cheers, Dushan On Mon, Feb 17, 2014 at 11:03 AM, Jay janaka.n.ranathu...@gmail.com wrote: Hi Dushan, LinkedIn API required URL encoded value, such as; http://www.linkedin.com/pub/X-/87/998/935 should to be encoded in to http%3A%2F%2Fwww.linkedin.com%2Fpub%2FX-%2F87%2F998%2F935. But if we use fn:base64Encode(), value is encoded in to aHR0cDovL3d3dy5saW5rZWRpbi5jb20vcHViL3dzbzJjb25uZWN0b3ItYW JkZXJhLzg3Lzk5OC85MzU%3D. this value is not accept by LinkedIn api. Thanks, -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Encode-Url-in-ESB-tp92179p92255.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] REST API - query.param or uri.var ? where to use?
Hi Susinda,
GET http://192.168.2.1:8280/test?type=crust
in short term property name=type expression=$url:type/ should work
On Fri, Feb 14, 2014 at 8:49 PM, Amila Maha Arachchi ami...@wso2.comwrote:
According to your first mail, you have used query.param.val, but it
should be query.param.Symbol. That might be the place where you went
wrong.
On Fri, Feb 14, 2014 at 8:12 PM, Susinda Perera susi...@wso2.com wrote:
Yes it worked, thanks, Dnt know where i have gone wrong.
On Fri, Feb 14, 2014 at 8:00 PM, Kasun Indrasiri ka...@wso2.com wrote:
The following works fine. Please check again.
GET http://192.168.2.1:8280/test?type=crust
api xmlns=http://ws.apache.org/ns/synapse; name=Test
context=/test
resource methods=GET
inSequence
property name=FOO expression=$ctx:query.param.type
type=STRING/property
log level=custom
property name=FOO
expression=get-property('FOO')/property
/log
/inSequence
/resource
/api
On Fri, Feb 14, 2014 at 6:46 PM, Susinda Perera susi...@wso2.comwrote:
I tried to access query parameters using property mediators in
both query.param and uri.var ways, but only uri.var gives me an output.
What i thought was syntax like
resource uri-template=/view/{symbol} methods=GET use uri.var
and syntax like
resource uri-template=/view?Symbol={symbol} methods=GET uses
query.param but i was not able to use query.param in second syntax
Neither
property name=Val expression=$ctx:query.param.val/property nor
property name=Val expression=get-property('query.param.val')/
property
syntax gave me an output. Where i might have gone wrong or is this a
bug?
--
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
--
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Encode Url in ESB
Hi
Can you try following then use call mediator as above, no need to use
javascript for encoding purpose.
property name=apiUrl expression=fn:base64Encode($func:publicUrl) /
property name=uri.var.publicUrl expression=$ctx:apiUrl: /
On Thu, Feb 13, 2014 at 6:34 PM, Jay janaka.n.ranathu...@gmail.com wrote:
Hi,
I need to pass an Url encoded value
(Ex:http://www.linkedin.com/pub/-/87/998/935) to an endpoint as a
part of the Url.
I am using following synapse template;
template name=getProfile xmlns=http://ws.apache.org/ns/synapse;
property name=uri.var.accessToken
expression=$func:accessToken
/
property name=uri.var.apiUrl expression=$func:apiUrl /
parameter name=publicUrl description=public url of the
requested
profile /
sequence
property name=uri.var.publicUrl
expression=$func:publicUrl /
call
endpoint
http method=get
uri-template={uri.var.apiUrl}/v1/people/url={uri.var.publicUrl}?oauth2_access_token={uri.var.accessToken}amp;format=json
/
/endpoint
/call
/sequence
/template
encoded url should be assigned to uri.var.publicUrl.
My problem is after encoding Url using script mediator, in call mediator
Url
is encoding again.
Following is my script mediator;
This is the result after calling script mediator:
http%3a%2f%2fwww.linkedin.com%2fpub%2f-%2f87%2f998%2f935
When calling End point % characters in above url is encode again and
result is
http%253a%252f%252fwww.linkedin.com
%252fpub%252f-%252f87%252f998%252f935%253
Is there any way to prevent encode url in end point? Or any way to encode
url in call mediator itself?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Encode-Url-in-ESB-tp92179.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception handling on REST call
Hi,
No its wrong, we shouldn't response with 200 OK for exceptions. IMO ideal
way as I think, to do this by keep the catalog of connector specific error
code and embedded in the error message and explain those _ _connector
specific error _ _ catalog in documentation more specifically, and
returning a generic error with status code to client.
for error catalogs you could refer [1][2]
[1]http://www.twilio.com/docs/errors/reference
[2]
http://www.stormpath.com/blog/spring-mvc-rest-exception-handling-best-practices-part-1
e.g
{
status: 404,
* code: 40483,*
message: Oops! It looks like that file does not exist.,
developerMessage: File resource for path /uploads/foobar.txt
does not exist. Please wait 10 minutes until the upload batch
completes before checking again.,
moreInfo: http://www.mycompany.com/errors/40483;
}
On Tue, Feb 11, 2014 at 9:51 AM, Krishantha Dinesh kr...@krishantha.comwrote:
Hi Dushan/Dev
I tried ur solution and its work. but i have other question. when it catch
FAULT (500 error) on return message of client http code is 200 OK
for example let say endpoint is fail the it catch that fault. but in
client point of view http respond code of his response is 200
other than 500 client getting correct http response code. the problem may
be this is originate by ESB it self than come as response to ESB. btw is
there any solution for this.
On Sat, Feb 8, 2014 at 7:30 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi Kirshantha,
Handling fault has two flavors,
- Handle internal fault such as service EP not available and all the
issues related .
- Handle Service faults.
Ideally when BE is SOAP and if it returns SOAP fault in order to handle
such queries we normally append FORCE_ERROR_ON_SOAP_FAULT property, this
works only of BE return Service faults and when such happen if we need to
divert such responses to the faultSequence that we have defined.
On the other hand if that is RESTful BE, we do not have a inbuilt
function to determine whether its a fault at transport level, so the
workaround that we normally do is to use the Filter base on the HTTP_SC.
If you look at [1] status codes represents 100 series and 200- series
regards as non faulty responses, and other than that we can determine them
as faults or defect, to overcome such station when deal with RESTful
services personally I am using filters i.e
OutSequence ..etc , below logic just evaluates the response and if that
not falls between 200 series normally you can add your customize faulty
response logic ..
filter source=$axis2:HTTP_SC regex=^[^2][0-9][0-9]
then
log level=custom
- can include payload
- can setup HTTP_SC to axis2 context
- can use respond mediator to reply client with error.
..
..
/then
/filter
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
On Fri, Feb 7, 2014 at 7:54 PM, Krishantha Dinesh
kr...@krishantha.comwrote:
I have used following code to handle error on soap call
proxy
==
faultSequence
makefault version=soap11
code xmlns:tns=http://www.w3.org/2003/05/soap-envelope
value=get-property('FAULT_CODE') /
reason expression=get-property('ERROR_CODE') /
detail expression=get-property('ERROR_MESSAGE') /
/makefault
send /
/faultSequence
Output
==
soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
soapenv:Fault
faultcode xmlns:tns=http://www.w3.org/2003/05/soap-envelope
123456/faultcode
faultstringabc/faultstring
detailxyz/detail
/soapenv:Fault
/soapenv:Body
/soapenv:Envelope
I need to know what is the best approach to handle exception on REST
calls.
i tried to apply same way just for try but it only give ERROR_MESSAGE
not another...
my expectation is to deliver all exception to client (caller). eg:
transport error due to unavailable endpoint.. etc
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception handling on REST call
Hi
You can setup HTTP_SC in axis2 context set 400 (which represents bad
Request)
On Tue, Feb 11, 2014 at 10:42 AM, Krishantha Dinesh kr...@krishantha.comwrote:
Hi Dushan,
Thanks for prompt reply.
I do agree with you. my concern is http response got which client get on
transport headers.
pls refer below
This is what client get as exception
Response xmlns=http://cd-rhettige/services/paypal_lookupSale;
error_code101503/error_code
error_messageError connecting to the back end/error_message
/Response
this is the raw content. pls pay your attention for http status code
HTTP/1.1 200 OK
Authorization: Bearer OQaph7mMZJbvNDJ-8u9ICVm4Q4kkJmNj.w5dQJZ5u8E
Host: cd-rhettige:8280
Accept-Encoding: gzip,deflate
Content-Type: application/json
Date: Tue, 11 Feb 2014 05:06:58 GMT
Server: WSO2-PassThrough-HTTP
Transfer-Encoding: chunked
Connection: Keep-Alive
{ error_code:101503,
error_message:Error connecting to the back end
}
On Tue, Feb 11, 2014 at 10:04 AM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi,
No its wrong, we shouldn't response with 200 OK for exceptions. IMO
ideal way as I think, to do this by keep the catalog of connector specific
error code and embedded in the error message and explain those _ _connector
specific error _ _ catalog in documentation more specifically, and
returning a generic error with status code to client.
for error catalogs you could refer [1][2]
[1]http://www.twilio.com/docs/errors/reference
[2]
http://www.stormpath.com/blog/spring-mvc-rest-exception-handling-best-practices-part-1
e.g
{
status: 404,
* code: 40483,*
message: Oops! It looks like that file does not exist.,
developerMessage: File resource for path /uploads/foobar.txt does not
exist. Please wait 10 minutes until the upload batch completes before
checking again.,
moreInfo: http://www.mycompany.com/errors/40483;
}
On Tue, Feb 11, 2014 at 9:51 AM, Krishantha Dinesh
kr...@krishantha.comwrote:
Hi Dushan/Dev
I tried ur solution and its work. but i have other question. when it
catch FAULT (500 error) on return message of client http code is 200 OK
for example let say endpoint is fail the it catch that fault. but in
client point of view http respond code of his response is 200
other than 500 client getting correct http response code. the problem
may be this is originate by ESB it self than come as response to ESB. btw
is there any solution for this.
On Sat, Feb 8, 2014 at 7:30 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi Kirshantha,
Handling fault has two flavors,
- Handle internal fault such as service EP not available and all
the issues related .
- Handle Service faults.
Ideally when BE is SOAP and if it returns SOAP fault in order to
handle such queries we normally append FORCE_ERROR_ON_SOAP_FAULT property,
this works only of BE return Service faults and when such happen if we need
to divert such responses to the faultSequence that we have defined.
On the other hand if that is RESTful BE, we do not have a inbuilt
function to determine whether its a fault at transport level, so the
workaround that we normally do is to use the Filter base on the HTTP_SC.
If you look at [1] status codes represents 100 series and 200- series
regards as non faulty responses, and other than that we can determine them
as faults or defect, to overcome such station when deal with RESTful
services personally I am using filters i.e
OutSequence ..etc , below logic just evaluates the response and if that
not falls between 200 series normally you can add your customize faulty
response logic ..
filter source=$axis2:HTTP_SC regex=^[^2][0-9][0-9]
then
log level=custom
- can include payload
- can setup HTTP_SC to axis2 context
- can use respond mediator to reply client with error.
..
..
/then
/filter
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
On Fri, Feb 7, 2014 at 7:54 PM, Krishantha Dinesh kr...@krishantha.com
wrote:
I have used following code to handle error on soap call
proxy
==
faultSequence
makefault version=soap11
code xmlns:tns=
http://www.w3.org/2003/05/soap-envelope;
value=get-property('FAULT_CODE') /
reason expression=get-property('ERROR_CODE') /
detail expression=get-property('ERROR_MESSAGE') /
/makefault
send /
/faultSequence
Output
==
soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
soapenv:Fault
faultcode xmlns:tns=http://www.w3.org/2003/05/soap-envelope
123456/faultcode
faultstringabc/faultstring
detailxyz/detail
Re: [Dev] Exception handling on REST call
Hi Kirshantha,
Handling fault has two flavors,
- Handle internal fault such as service EP not available and all the
issues related .
- Handle Service faults.
Ideally when BE is SOAP and if it returns SOAP fault in order to handle
such queries we normally append FORCE_ERROR_ON_SOAP_FAULT property, this
works only of BE return Service faults and when such happen if we need to
divert such responses to the faultSequence that we have defined.
On the other hand if that is RESTful BE, we do not have a inbuilt
function to determine whether its a fault at transport level, so the
workaround that we normally do is to use the Filter base on the HTTP_SC.
If you look at [1] status codes represents 100 series and 200- series
regards as non faulty responses, and other than that we can determine them
as faults or defect, to overcome such station when deal with RESTful
services personally I am using filters i.e
OutSequence ..etc , below logic just evaluates the response and if that not
falls between 200 series normally you can add your customize faulty
response logic ..
filter source=$axis2:HTTP_SC regex=^[^2][0-9][0-9]
then
log level=custom
- can include payload
- can setup HTTP_SC to axis2 context
- can use respond mediator to reply client with error.
..
..
/then
/filter
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
On Fri, Feb 7, 2014 at 7:54 PM, Krishantha Dinesh kr...@krishantha.comwrote:
I have used following code to handle error on soap call
proxy
==
faultSequence
makefault version=soap11
code xmlns:tns=http://www.w3.org/2003/05/soap-envelope;
value=get-property('FAULT_CODE') /
reason expression=get-property('ERROR_CODE') /
detail expression=get-property('ERROR_MESSAGE') /
/makefault
send /
/faultSequence
Output
==
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
soapenv:Body
soapenv:Fault
faultcode xmlns:tns=http://www.w3.org/2003/05/soap-envelope
123456/faultcode
faultstringabc/faultstring
detailxyz/detail
/soapenv:Fault
/soapenv:Body
/soapenv:Envelope
I need to know what is the best approach to handle exception on REST calls.
i tried to apply same way just for try but it only give ERROR_MESSAGE not
another...
my expectation is to deliver all exception to client (caller). eg:
transport error due to unavailable endpoint.. etc
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB]LDAP Connector for WSO2 ESB : Asking for feedbacks
Hi Dimuthu,
- Code require proper exception handling and of cause some cleanup (i.e
for for users, we should compile proper error message use AbstractMediator
handleException)
- Use Logs not sysouts(see synapse inbuilt mediators)
- Integration tests ?
- Only CURD operations ?
- Documentation refer
http://docs.wso2.org/display/ESB480/ESB+Connectorsfor templates
protected static DirContext getContext(String providerUrl,String
securityPrincipal,String credentials) {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
com.sun.jndi.ldap.LdapCtxFactory);
*env.put(Context.PROVIDER_URL,
providerUrl);//ldap://192.168.1.164:389/ http://192.168.1.164:389/
env.put(Context.SECURITY_PRINCIPAL,securityPrincipal);//
cn=admin,dc=wso2,dc=com
env.put(Context.SECURITY_CREDENTIALS, credentials);//comadmin*
DirContext ctx = null;
try {
ctx = new InitialDirContext(env);
} catch (NamingException e) {
log.error(Error connecting to LDAP server, e);
e.printStackTrace();
}
return ctx;
}
- see highlighted section I don't think this will work in Multi-threaded
environment, because connectors are subjected open for multiple LDAP
connections (may be in single proxy you can define multiple LDAPs to
connect then using Environment variables as seen above ?)
Cheers
Dushan
On Fri, Feb 7, 2014 at 7:26 AM, Samisa Abeysinghe sam...@wso2.com wrote:
ESB team, can we please have a look into this?
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Developer Evangelism
WSO2 Inc.
http://wso2.com
On Fri, Jan 31, 2014 at 9:34 AM, Dimuthu Upeksha dimut...@wso2.comwrote:
Hi all,
We are working on our intern project Infra portal. We needed to do some
LDAP operations in our project. To make the integration easy we implemented
a LDAP connector [1] for WSO2 ESB 4.8.0. We hope this will be useful to
other groups which are working on LDAP authentication stuff. So we decided
to share this with everyone. Detailed descriptions of currently available
operations are mentioned in this[2] blog. We hope that this should be
improved further because this includes only basic LDAP operations.
It will be a great help for us I you can give us some feedbacks about
improvements we can do in this connector.
[1] https://svn.wso2.com/wso2/interns/2013/dimuthuu/ldap_connector/
[2]
http://dimuthuupeksha.blogspot.com/2014/01/ldap-connector-for-wso2-esb.html
Thanks
Dimuthu
--
Dimuthu Upeksha
Engineering Intern
WSO2 inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pass JSON array through SOAP Request
Hi
On Fri, Jan 31, 2014 at 6:04 PM, Rasika Hettige rasi...@gmail.com wrote:
Hi,
In AmazonS3 REST API, PUT Bucket policy method expects a dynamic JSON
array to create bucket policies.
Is it a best practice to send dynamic JSON array through SOAP request as
below?
Please note that the policies change from each other and does not have a
fix
nature.
Please guide us, if the following way is not a good practice.
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
xmlns:urn=wso2.connector.amazons3.createbucketpolicy
soapenv:Header/
soapenv:Body
urn:accessKeyIdAKIAIGURZM7GJ7TRO6KQ/urn:accessKeyId
urn:secretAccessKeyasAX8CJoDKzeOd0Ve5dMCFk4STUFDRHkGX6m0CcY/urn:secretAccessKey
urn:methodTypePUT/urn:methodType
urn:contentTypeapplication/json/urn:contentType
urn:bucketNameimagesBucket5/urn:bucketName
urn:xAmzDatetrue/urn:xAmzDate
urn:bucketUrlhttp://s3.amazonaws.com/imagesBucket5/urn:bucketUrl
urn:uriRemainder/?policy/urn:uriRemainder
urn:bucketPolicy{
Version:2012-10-17,
Statement:[
{
Sid:Policy1,
Effect:Allow,
Principal: {
AWS: *},
Action:[s3:GetObject],
Resource:arn:aws:s3:::imagesBucket5/*,
Condition:{
StringLike:{
aws:Referer:[
http://www.example.com/*;,
http://example.com/*;
]
}
}
}
]
}/urn:bucketPolicy
/soapenv:Body
/soapenv:Envelope
No this is absolutely wrong, you can not send something like this its not
compliance to the RESTful protocol, I am not quite sure what you trying to
achieve by embedding JSON content inside SOAP ..if that's a RESTful API you
should absolutely need to have a clear idea on how RESTful API can be
called please refer
please do study [1]
[1] http://docs.wso2.org/display/ESB480/JSON+Support
and as Imesh mention you shoul call
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTpolicy.htmlwithout
messing any SOAP with RESTful invocations.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Pass-JSON-array-through-SOAP-Request-tp91556.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Parsing JSON as XML and handling exceptions
Hi
On Fri, Jan 31, 2014 at 7:56 PM, Rasika Hettige rasi...@gmail.com wrote:
Hi,
Please find the below queries which are currently en-counted.
1. Java Connector - parsing JSON as XML
We found the following method in the Twitter connector to parse JSON as
XML:
private static OMElement parseJsonToXml(String sb) throws JSONException,
XMLStreamException,
IOException {
OMElement elm = JsonBuilder.toXml(new
ByteArrayInputStream(sb.getBytes()), false);
return elm;
}
The JsonBuilder.toXml method seems to be deprecated. Is there an
alternative
for this?
We did major refactoring to JSON by moving from Jettison to Staxon,
please refer org.apache.synapse.commons.json.JsonUtil under synapse commons.
2. To handle exceptions thrown within a Class mediator, we are using the
following method as specified in Google Spreadsheets and Twitter ESB
connectors:
public static void storeErrorResponseStatus(MessageContext ctxt, Exception
e) {
ctxt.setProperty(SynapseConstants.ERROR_EXCEPTION, e);
ctxt.setProperty(SynapseConstants.ERROR_MESSAGE, e.getMessage());
}
Is this type of error handling sufficient? Or do we need to have a fault
sequence within each synapse template?
throwing exception there is nothing to re-invent, look at simple inbuilt
mediators, such as Iterator, Payload etc.. see how exceptions are handled..
catch (AxisFault af) {
handleException(Error creating an iterated copy of the
message, af, synCtx);
}
/**
* Perform an error log message to all logs @ ERROR. Writes to the
general log, the service log
* and the trace log (of trace is on) and throws a SynapseException
* @param msg the log message
* @param e an Exception encountered
* @param msgContext the message context
*/
protected void handleException(String msg, Exception e, MessageContext
msgContext) {
log.error(msg, e);
if (msgContext.getServiceLog() != null) {
msgContext.getServiceLog().error(msg, e);
}
if (shouldTrace(msgContext.getTracingState())) {
trace.error(msg, e);
}
throw new SynapseException(msg, e);
}
Thanks Regards
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Parsing-JSON-as-XML-and-handling-exceptions-tp91557.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] SVN based dep synch not working as expected {ESBJAVA-2658}
Hi $subject, any reason why this happens? KasunG and I did test the behavior yesterday and somehow recent artifacts not checkout properly, currently subversion 1.7 installed in my workstation and SVN dep sych only supports subversion 6 and we are assuming svnClient lib to behave without issues but seems it does not, anyway now we are hit with blocker in W/M setup, where if you play around with QoS scenarios whole system getting crash so we need a solution for this faster. Meantime I got to know we are now recommending GIT base DepSynch and if so were we can find proper documentation I can't find anything [1] [1]http://docs.wso2.org/display/Carbon403/WSO2+Carbon+Documentation FYI Evanthika and QA do you guys testing the Alpaha release with Git base depsych or SVN base deyp sych ? Cheers Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SVN based dep synch not working as expected {ESBJAVA-2658}
But it does not have Git based Deployment Synchronizer. On Tue, Jan 28, 2014 at 10:22 AM, Jackie Wheeler jac...@wso2.com wrote: That link is to documentation for Carbon 4.0.3. The latest info on Deployment Synchronizer is in the Clustering Guide: http://docs.wso2.org/display/CLUSTER420/Introduction+to+Deployment+Synchronizer On Mon, Jan 27, 2014 at 8:47 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi $subject, any reason why this happens? KasunG and I did test the behavior yesterday and somehow recent artifacts not checkout properly, currently subversion 1.7 installed in my workstation and SVN dep sych only supports subversion 6 and we are assuming svnClient lib to behave without issues but seems it does not, anyway now we are hit with blocker in W/M setup, where if you play around with QoS scenarios whole system getting crash so we need a solution for this faster. Meantime I got to know we are now recommending GIT base DepSynch and if so were we can find proper documentation I can't find anything [1] [1]http://docs.wso2.org/display/Carbon403/WSO2+Carbon+Documentation FYI Evanthika and QA do you guys testing the Alpaha release with Git base depsych or SVN base deyp sych ? Cheers Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Twitter Connector SSL handshaking fails
%2F%2Fapi.twitter.com%2Foauth2%2Ftokensa=Dsntz=1usg=AFQjCNE4_apO1KFJZjWn-dwt_6XfwAOR-Q Thanks, -- *Gayan Kaushalya Yalpathwala* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 8682704 http://asia14.wso2con.com/ http://asia14.wso2con.com/ -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [DEV] https://wso2.org/jira/browse/ESBJAVA-2849
Hi Dev
AFAIU we should destroy current context before setup new Tenant domain, but
in TenantAxisUtils, seems like we are not cleaning up current context which
leads to throw exception as shown in below [2] shall we do the changes as
required WDYT?
private static ConfigurationContext
createTenantConfigurationContext(ConfigurationContext mainConfigCtx,
String tenantDomain) throws Exception {
synchronized (tenantDomain.intern()) { // lock based on tenant
domain
MapString, ConfigurationContext tenantConfigContexts =
getTenantConfigurationContexts(mainConfigCtx);
ConfigurationContext tenantConfigCtx =
tenantConfigContexts.get(tenantDomain);
if (tenantConfigCtx != null) {
return tenantConfigCtx;
}
long tenantLoadingStartTime = System.currentTimeMillis();
int tenantId = getTenantId(tenantDomain);
if (tenantId == MultitenantConstants.SUPER_TENANT_ID ||
tenantId == MultitenantConstants.INVALID_TENANT_ID) {
throw new Exception(Tenant + tenantDomain + does not
exist);
}
* PrivilegedCarbonContext.destroyCurrentContext(); need to be
here..*
PrivilegedCarbonContext carbonContext =
PrivilegedCarbonContext.getThreadLocalCarbonContext();
carbonContext.setTenantId(tenantId);
[2]
TID: [0] [ESB] [2014-01-21 12:06:54,005] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
{org.wso2.carbon.context.internal.CarbonContextDataHolder} - Trying to set
the domain from 3 to 6
{org.wso2.carbon.context.internal.CarbonContextDataHolder}
java.lang.IllegalStateException: Trying to set the domain from 3 to 6
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
at
org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
at
org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
at
org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] https://wso2.org/jira/browse/ESBJAVA-2849
Hi Azeez,
On Thu, Jan 23, 2014 at 11:55 PM, Afkham Azeez az...@wso2.com wrote:
No! TenantAxisUtils is a util. You can't destroy the context there. You
have no idea at what point that code will be called. The context cleanup,
if necessary should have been performed by some upstream code.
got it, then required clean up will be doing at
PassThroughNHttpGetProcessor
On Thu, Jan 23, 2014 at 10:15 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi Dev
AFAIU we should destroy current context before setup new Tenant domain,
but in TenantAxisUtils, seems like we are not cleaning up current context
which
leads to throw exception as shown in below [2] shall we do the changes as
required WDYT?
private static ConfigurationContext
createTenantConfigurationContext(ConfigurationContext mainConfigCtx,
String tenantDomain) throws
Exception {
synchronized (tenantDomain.intern()) { // lock based on tenant
domain
MapString, ConfigurationContext tenantConfigContexts =
getTenantConfigurationContexts(mainConfigCtx);
ConfigurationContext tenantConfigCtx =
tenantConfigContexts.get(tenantDomain);
if (tenantConfigCtx != null) {
return tenantConfigCtx;
}
long tenantLoadingStartTime = System.currentTimeMillis();
int tenantId = getTenantId(tenantDomain);
if (tenantId == MultitenantConstants.SUPER_TENANT_ID ||
tenantId == MultitenantConstants.INVALID_TENANT_ID) {
throw new Exception(Tenant + tenantDomain + does not
exist);
}
* PrivilegedCarbonContext.destroyCurrentContext(); need to be
here..*
PrivilegedCarbonContext carbonContext =
PrivilegedCarbonContext.getThreadLocalCarbonContext();
carbonContext.setTenantId(tenantId);
[2]
TID: [0] [ESB] [2014-01-21 12:06:54,005] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest}
TID: [0] [ESB] [2014-01-21 12:07:11,420] ERROR
{org.wso2.carbon.context.internal.CarbonContextDataHolder} - Trying to set
the domain from 3 to 6
{org.wso2.carbon.context.internal.CarbonContextDataHolder}
java.lang.IllegalStateException: Trying to set the domain from 3 to 6
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
at
org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
at
org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:284)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:104)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getAxisService(TenantAxisUtils.java:195)
at
org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor.process(PassThroughNHttpGetProcessor.java:300)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:155)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 %2B94%2077%203320919 blog: *
*http://blog.afkham.org* http://blog.afkham.org
*twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
http://lk.linkedin.com/in/afkhamazeez*
*Lean . Enterprise . Middleware*
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] https://wso2.org/jira/browse/ESBJAVA-2899 Reprodcuiable due to recent XCML changers in IS
Hi IS Team,
ESB 4.8.1 M1 pack built today with IS 4.6.0 (released)
This is reproducible, seems like now response wrap
with urn:oasis:names:tc:xacml:3.0:core:schema:wd-17 and no longer
if(decisionString != null){
OMElement decisionElement =
AXIOMUtil.stringToOM(decisionString);
* simpleDecision = decisionElement.getFirstChildWithName(new
QName(Result)).getFirstChildWithName(new QName(Decision)).getText();*
obligations = decisionElement.getFirstChildWithName(new
QName(Obligations));
advice = decisionElement.getFirstChildWithName(new
QName(AdviceExpressions));
if(log.isDebugEnabled()){
log.debug(Entitlement Decision is : +
simpleDecision);
}
it suppose to be
*decisionElement.getFirstChildWithName(new
QName(urn:oasis:names:tc:xacml:3.0:core:schema:wd-17,Result)) or may be
we might have to test both..*
So, IS team please review this and do any necessary changers to
Entitlement Mediator, this a BLOCKER and required your attention.
New Response Type..
Response
xmlns=urn:oasis:names:tc:xacml:3.0:core:schema:wd-17ResultDecisionNotApplicable/DecisionStatusStatusCode
Value=urn:oasis:names:tc:xacml:1.0:status:ok/StatusCode/Status/Result/Response
Cheers,
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Invoke Proxy Services RESTfully via MultiTenant broken [https://wso2.org/jira/browse/ESBJAVA-2906]
Hi Manoj, Modified patched attached https://wso2.org/jira/secure/attachment/30083/FixRESTfulInvokeMultitenant.txt Cheers Dushan On Tue, Jan 21, 2014 at 12:10 PM, Manoj Kumara ma...@wso2.com wrote: Hi Dushan, Provided patch is not complete according to [1], Please update the patch. You may need to update update README.txt file and bin.xml file as well. [1] http://docs.wso2.org/display/Carbon420/Creating+a+Carbon+Kernel+Patch Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 On Tue, Jan 21, 2014 at 11:57 AM, Dushan Abeyruwan dus...@wso2.comwrote: Hi Manoj, $subject, the patch is attached in [1] please do apply this ASAP to carbon core MultitenantMessageReceiver [1] https://wso2.org/jira/browse/ESBJAVA-2906 cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Invoke Proxy Services RESTfully via MultiTenant broken [https://wso2.org/jira/browse/ESBJAVA-2906]
Hi Manoj, $subject, the patch is attached in [1] please do apply this ASAP to carbon core MultitenantMessageReceiver [1] https://wso2.org/jira/browse/ESBJAVA-2906 cheers, Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Adding new Assert throws following exception [ES 1.0.0]
$subject,
[2014-01-17 18:43:24,669] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2014-01-17 18:43:24,669+0530]
[2014-01-17 18:43:24,823] INFO {JAGGERY.controllers.acs:jag} - Emitting
event : login
[2014-01-17 18:44:33,480] ERROR {JAGGERY.assets.default.asset:jag} -
org.mozilla.javascript.EcmaError: TypeError: Cannot call method execute
of null (/publisher/modules/ext/core/extension.management.js#93)
at
org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3687)
at
org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3665)
at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3693)
at org.mozilla.javascript.ScriptRuntime.typeError2(ScriptRuntime.java:3712)
at
org.mozilla.javascript.ScriptRuntime.undefCallError(ScriptRuntime.java:3731)
at
org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThisHelper(ScriptRuntime.java:2258)
at
org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2251)
at
org.jaggeryjs.rhino.publisher.modules.ext.core.c3._c_anonymous_7(/publisher/modules/ext/core/extension.management.js:93)
at
org.jaggeryjs.rhino.publisher.modules.ext.core.c3.call(/publisher/modules/ext/core/extension.management.js)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.assets.default.c1._c_anonymous_8(/publisher/assets/default/asset.jag:187)
at
org.jaggeryjs.rhino.publisher.assets.default.c1.call(/publisher/assets/default/asset.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c4._c_anonymous_12(/publisher/modules/router-g.js:183)
at
org.jaggeryjs.rhino.publisher.modules.c4.call(/publisher/modules/router-g.js)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.assets.default.c1._c_anonymous_1(/publisher/assets/default/asset.jag:345)
at
org.jaggeryjs.rhino.publisher.assets.default.c1.call(/publisher/assets/default/asset.jag)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c6._c_anonymous_17(/publisher/modules/publisher.js:436)
at
org.jaggeryjs.rhino.publisher.modules.c6.call(/publisher/modules/publisher.js)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at
org.mozilla.javascript.gen._store__server_js_11._c_anonymous_17([store]/server.js:271)
at org.mozilla.javascript.gen._store__server_js_11.call([store]/server.js)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c6._c_anonymous_16(/publisher/modules/publisher.js:431)
at
org.jaggeryjs.rhino.publisher.modules.c6.call(/publisher/modules/publisher.js)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.assets.default.c1._c_script_0(/publisher/assets/default/asset.jag:15)
at
org.jaggeryjs.rhino.publisher.assets.default.c1.call(/publisher/assets/default/asset.jag)
at
org.jaggeryjs.rhino.publisher.assets.default.c1.exec(/publisher/assets/default/asset.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:570)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.executeScript(WebAppManager.java:271)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.include(WebAppManager.java:125)
at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.publisher.controllers.c5._c_anonymous_1(/publisher/controllers/asset_router.jag:81)
at
org.jaggeryjs.rhino.publisher.controllers.c5.call(/publisher/controllers/asset_router.jag)
at org.mozilla.jav
Cheers.
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP Serlvet Transport and HTTP Request Object
Hi
On Thu, Dec 26, 2013 at 4:20 PM, Aliosha aliosh...@gmail.com wrote:
hi, i need to access the HttpServletRequest as i need to process a rest
http call structured like the following:
http://localhost:port/myService/[param1,param2,...,paramN]/myIpAddress
Do you have idea how much parameters embedded as given above, if that
static,you can define a RESful API [1] and you can define your url-template
as uri-template=/myService/{parameter1,parameter2,paramter3}/myIpAddress*
Then you should be able to access those variables in via mediation
flow as ,
get-property('uri.var.parameter1')
get-property('uri.var.parameter2')
But if you don't have any well defined parameter set, above logic will not
work
refer [2]
[1]http://docs.wso2.org/display/ESB480/Getting+Started+with+REST+APIs
[2]http://docs.wso2.org/display/ESB480/Configuring+Specific+Use+Cases
i want to avoid in my mediator to process the string
param1,param2,...,paramN]/myIpAddress to obtain my parameters. I prefer
to invoke a POST request passing them inside Http payload parameters in the
way i can get them by:
httpRequest.getParameter(param1)
I tried to change the transport receiver inside the axis2.xml using the
org.wso2.carbon.core.transports.http.HttpTransportListener
( I suppose it s not an implementation of the http based on the synapse
http NIO core... so the performance will get lower. isn't? )
in this way i can get the HttpServletRequest object. But i realized that
this object has Parameters not null only if i append them in the url like a
query string ( i.e. ?param1=param1param2=param2) even if i m sending a
post request. I m using for testing the chrom advanced Rest client and
mozilla poster.
Am i doing anything wrong?
regards
Il 26/dic/2013 08:50 Dushan Abeyruwan dus...@wso2.com ha scritto:
Hi
On Tue, Dec 24, 2013 at 2:57 AM, Aliosha aliosh...@gmail.com wrote:
i have developed a custom mediator and i want to try to publish it as a
REST service con my WSO2 ESB 4.7.0.
Once i created the REST API, the ESB publishes it on the 8280 port.
On the client side, the POST REST call needs to specify some http
parameters that i need to recover later in the mediator by this code:
You should refer http://docs.wso2.org/display/ESB480/HTTP+Endpoint where
you can easily generate request, no need of having custom mediators
org.apache.axis2.context.MessageContext axis2MsgContext;
axis2MsgContext = ((Axis2MessageContext)
synapseMsgContext).getAxis2MessageContext();
HttpServletRequest obj =
(HttpServletRequest)axis2MsgContext.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST);
if (obj != null) {
System.out.println(Method :+ obj.getMethod());
System.out.println(Content-type : +obj.getContentType());
System.out.println(Content-length :+obj.getContentLength());
System.out.println(Remote
addtress+obj.getSession().getLastAccessedTime());
}
The object i get is always null.
That's probably because on 8280 ESB uses the NHttp transport.
In what way can i solve this problem?
Have i to activate the HTTP Servlet Transport? How can i do this?
Can I know why you need to use HTTP Servlet for RESTful application
communication ? Do you have any specific requirement to use it? Why default
transport shipped with ESB (PTT) not works for you?
What's the difference between HTTP and NHTTP? Does the ESB performance
get lower?
Obviously, NHTTP far more efficient than Servelet Transport,because
NHTTP is non blocking invocation and it uses NIO for communication.. by
default we recommend to use NHTTP because its faster and has high
performance numbers..
Thanks a lot.
Best Regards.
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] JSON string in request being reformatted by ESB
HI
Enable wire logs and post the logs
On Thu, Dec 26, 2013 at 4:32 PM, indika prasad indika@gmail.com wrote:
Reposting:
Hi Dushan,
Thanks for your response.
However, we're seeing the correct output with the proxy you provided, but
the request times out with our synapse template + proxy combo.
Contents of the template:
template xmlns=http://ws.apache.org/ns/synapse; name=sendActivity
sequence
header name=x-li-format scope=transport value=json/header
payloadFactory media-type=json
format {contentType:linkedin-html,body:hello Test}
/format
/payloadFactory
property name=messageType value=application/json
scope=axis2/property
property name=FORCE_HTTP_1.0 value=true scope=axis2/property
call
endpoint
http method=post
uri-template=http://localhost:8281/;/http
/endpoint
/call
/sequence
/template
Proxy:
?xml version=1.0 encoding=UTF-8?
proxy xmlns=http://ws.apache.org/ns/synapse;
name=sendActivity
transports=https,http
statistics=disable
trace=disable
startOnLoad=true
target
inSequence
call-template target=sendActivity
/call-template
respond/
/inSequence
outSequence
send/
/outSequence
/target
description/
/proxy
The JSON message sent out to TCP Mon is correct now. Copy pasting the TCP
mon request headers and body to SoapUI and running as a REST project
returns
the correct 201 status from the LinkedIn API, so we know this configuration
is sending out the correct message. When redirecting the synapse template
to
LinkedIn by setting the correct URL in it, the request times out. Could
this
be because LinkedIn is returning an HTTP 201 status?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/JSON-string-in-request-being-reformatted-by-ESB-tp90183p90195.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] JSON string in request being reformatted by ESB
Hi Indika,
Did a small test with simple JSON payload this what I have observed [2],
anyway please send us your configuration, and also please see any error in
console,if so please do post them,meantime to very just create simple proxy
and try to submit the given request and see whether its getting dispatch
successfully to BE..
proxy name=FooProxy
transports=https http
startOnLoad=true
trace=disable
description/
target
inSequence
payloadFactory media-type=json
format{
contentType:linkedin-html,
body:update body
}/format
args/
/payloadFactory
property name=messageType value=application/json
scope=axis2/
send
endpoint
address uri=http://localhost:8281/services/jsonService;
format=rest/
/endpoint
/send
/inSequence
/target
/proxy
TCP mon..
l2]
Accept-Encoding: gzip,deflate
Content-Type: application/json
SOAPAction:
Transfer-Encoding: chunked
Host: 127.0.0.1:8281
Connection: Keep-Alive
User-Agent: Synapse-PT-HttpComponents-NIO
47
{
contentType:linkedin-html,
body:update body
}
0
On Wed, Dec 25, 2013 at 8:29 PM, indika prasad indika@gmail.com wrote:
Hi Kasun,
Actually it gives the same JSON output when uri.var is removed. Ignore the
last post.
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/JSON-string-in-request-being-reformatted-by-ESB-tp90183p90191.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP Serlvet Transport and HTTP Request Object
Hi
On Tue, Dec 24, 2013 at 2:57 AM, Aliosha aliosh...@gmail.com wrote:
i have developed a custom mediator and i want to try to publish it as a
REST service con my WSO2 ESB 4.7.0.
Once i created the REST API, the ESB publishes it on the 8280 port.
On the client side, the POST REST call needs to specify some http
parameters that i need to recover later in the mediator by this code:
You should refer http://docs.wso2.org/display/ESB480/HTTP+Endpoint where
you can easily generate request, no need of having custom mediators
org.apache.axis2.context.MessageContext axis2MsgContext;
axis2MsgContext = ((Axis2MessageContext)
synapseMsgContext).getAxis2MessageContext();
HttpServletRequest obj =
(HttpServletRequest)axis2MsgContext.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST);
if (obj != null) {
System.out.println(Method :+ obj.getMethod());
System.out.println(Content-type : +obj.getContentType());
System.out.println(Content-length :+obj.getContentLength());
System.out.println(Remote
addtress+obj.getSession().getLastAccessedTime());
}
The object i get is always null.
That's probably because on 8280 ESB uses the NHttp transport.
In what way can i solve this problem?
Have i to activate the HTTP Servlet Transport? How can i do this?
Can I know why you need to use HTTP Servlet for RESTful application
communication ? Do you have any specific requirement to use it? Why default
transport shipped with ESB (PTT) not works for you?
What's the difference between HTTP and NHTTP? Does the ESB performance get
lower?
Obviously, NHTTP far more efficient than Servelet Transport,because
NHTTP is non blocking invocation and it uses NIO for communication.. by
default we recommend to use NHTTP because its faster and has high
performance numbers..
Thanks a lot.
Best Regards.
--
Dushan Abeyruwan | Associate Tech Lead
Integration Technologies Team
PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:http://dushansview.blogspot.com/
Mobile:(0094)713942042
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] Servicemeta file not deleting properly {https://wso2.org/jira/browse/ESBJAVA-2616}
Hi All,
It seems like service metatafile not deleted properly when deleting proxy
as in AbstractFilePersistenceManager. it looks *detach* nodes *instead of
deleting* is this a correct behavior..
public boolean delete(String resourceId, String xpathStr) {
ResourceFileData fileData = resourceMap.get(resourceId);
try {
if (fileData != null fileData.isTransactionStarted()) {
OMElement sgElement = fileData.getOMElement();
AXIOMXPath xpathExpr = new AXIOMXPath(xpathStr);
OMElement el = (OMElement)
xpathExpr.selectSingleNode(sgElement);
if (el == null) {
return false;
}
if (el.getParent() == null) { //this is the root element
fileData.setOMElement(null);
} *else {*
*el.detach();*
*}*
setMetaFileModification(resourceId);
return true;
} else {
log.error(The Element specified by path not found or a
transaction isn't started yet. +
xpathStr);
return false;
}
} catch (JaxenException e) {
log.error(Error parsing xpath string + resourceId +
xpathStr, e);
return false;
}
}
Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] Servicemeta file not deleting properly {https://wso2.org/jira/browse/ESBJAVA-2616}
commitTransaction has some relation with the above method, which means
el.detach means not setting to fileData.setOMElement(null); thus skipping
the deletion operation
public synchronized void commitTransaction(String resourceId) throws
PersistenceException {
if (fileData != null * fileData.getOMElement() == null) {* //the
resource has been deleted
String childFilePath =
getFilePathFromResourceId(resourceId);
f = new File(metafilesDir, childFilePath);
if (f.exists()) {
* FileUtils.forceDelete(f);*
}
if(log.isDebugEnabled()){
log.debug(Successfully deleted persisted resource
contents + resourceId + + f.getName());
}
resourceMap.remove(resourceId);
return;
} else if (fileData != null) {
f = fileData.getFile();
} else {
resourceMap.remove(resourceId);
throw new PersistenceException(persistence data not
found);
}
On Wed, Nov 13, 2013 at 5:19 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi All,
It seems like service metatafile not deleted properly when deleting proxy
as in AbstractFilePersistenceManager. it looks *detach* nodes *instead of
deleting* is this a correct behavior..
public boolean delete(String resourceId, String xpathStr) {
ResourceFileData fileData = resourceMap.get(resourceId);
try {
if (fileData != null fileData.isTransactionStarted()) {
OMElement sgElement = fileData.getOMElement();
AXIOMXPath xpathExpr = new AXIOMXPath(xpathStr);
OMElement el = (OMElement)
xpathExpr.selectSingleNode(sgElement);
if (el == null) {
return false;
}
if (el.getParent() == null) { //this is the root element
fileData.setOMElement(null);
} *else {*
*el.detach();*
*}*
setMetaFileModification(resourceId);
return true;
} else {
log.error(The Element specified by path not found or a
transaction isn't started yet. +
xpathStr);
return false;
}
} catch (JaxenException e) {
log.error(Error parsing xpath string + resourceId +
xpathStr, e);
return false;
}
}
Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ http://wso2.com/*
*Mobile:(+94)714408632 %28%2B94%29714408632*
--
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ http://wso2.com/*
*Mobile:(+94)714408632 %28%2B94%29714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !
Hi It seems like connectors are not updated correctly with the Alpha pack shared, anyway for QA process for 4.8.0 Alpha please do download the latest connectors from [1] [1]https://svn.wso2.org/repos/wso2/people/shafreen/connectors/ On Wed, Nov 13, 2013 at 8:16 PM, Shafreen Anfar shafr...@wso2.com wrote: Hi, ESB version 4.8.0 Alpha is available at, https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip Connectors can be found in $ESB_HOME/repository/connectors -- Regards, *Shafreen* Software Engineer WSO2 Inc Mobile : 077-556-395-1 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout
$subject,when ELB 2.1.0 with W/M when particular EP goes suspend or timeout, LB keep tying the same message forever.. This required immediate attention FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha pack. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout
This should be something ELB team need to attend and fix am I? On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka miy...@wso2.com wrote: I think what happens is leaf endpoints never get suspended and failover retry set to true. So request keeps retrying with next active endpoint forever. On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan dus...@wso2.com wrote: $subject,when ELB 2.1.0 with W/M when particular EP goes suspend or timeout, LB keep tying the same message forever.. This required immediate attention FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha pack. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
$subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout
https://wso2.org/jira/browse/LB-126 On Thu, Nov 14, 2013 at 9:40 AM, Miyuru Wanninayaka miy...@wso2.com wrote: We can't fix it now as ELB is already released. Any fix has to go to next ELB release. Pls report a L1 against it. On Thu, Nov 14, 2013 at 9:35 AM, Dushan Abeyruwan dus...@wso2.com wrote: This should be something ELB team need to attend and fix am I? On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka miy...@wso2.comwrote: I think what happens is leaf endpoints never get suspended and failover retry set to true. So request keeps retrying with next active endpoint forever. On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan dus...@wso2.comwrote: $subject,when ELB 2.1.0 with W/M when particular EP goes suspend or timeout, LB keep tying the same message forever.. This required immediate attention FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha pack. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
This required immediate attention..https://wso2.org/jira/browse/LB-127 On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.com wrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
Once more shutting down ELB cause following NEP ctive:true [2013-11-14 09:49:37,179] ERROR - NativeWorkerPool Uncaught exception java.lang.NullPointerException at org.apache.synapse.endpoints.DynamicLoadbalanceEndpoint.getEndpoint(DynamicLoadbalanceEndpoint.java:435) at org.apache.synapse.endpoints.DynamicLoadbalanceEndpoint.sendToApplicationMember(DynamicLoadbalanceEndpoint.java:304) at org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint.access$400(TenantAwareLoadBalanceEndpoint.java:46) at org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint$TenantDynamicLoadBalanceFaultHandlerImpl.onFault(TenantAwareLoadBalanceEndpoint.java:518) at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54) at org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:622) at org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:471) at org.apache.synapse.endpoints.AddressEndpoint.onFault(AddressEndpoint.java:43) at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:249) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:167) at org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:134) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [2013-11-14 09:49:37,352] INFO - CarbonServerManager Shutdown complete [2013-11-14 09:49:37,352] INFO - CarbonServerManager Halting JVM On Thu, Nov 14, 2013 at 9:48 AM, Dushan Abeyruwan dus...@wso2.com wrote: This required immediate attention..https://wso2.org/jira/browse/LB-127 On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.com wrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi ami...@wso2.comwrote: You need to have at least one WK member in a given time when you are dealing with hazelcast. If ELB is the only WK member in your setup, when you restart the ELB, others will never join the ELB until they are restarted. Is this kind of a norm .. a hard fasten rule we have seutp with the newst WK implementation. ? Wonder I should agree on this or not..assume there is a pool which as larger number of wrks..and Do i need to restart them all? Is that what you trying to emphasis.. l.e assume my prod set has only 1 ELB and 30 works.. :)... so I need to start all 30 if ELB goes down ...woops.. :( To get this working, ELB also should have a WK member (can be the ESB mgt node) and workers should have both ELB and MGT node as WK members. AFAIK QA team is aware of this. If you want, talk to IsuruW. On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.com wrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
On Thu, Nov 14, 2013 at 9:55 AM, Dushan Abeyruwan dus...@wso2.com wrote: On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi ami...@wso2.comwrote: You need to have at least one WK member in a given time when you are dealing with hazelcast. If ELB is the only WK member in your setup, when you restart the ELB, others will never join the ELB until they are restarted. To get this working, ELB also should have a WK member (can be the ESB mgt node) and workers should have both ELB and MGT node as WK members. AFAIK QA team is aware of this. If you want, talk to IsuruW. Do we have any document reference ? FYI Jackie On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.comwrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
