[Dev] PKIX exception when accessing a https url from the BE
Hi,
One of the services in BAM, uploads a file from a given url. The following
exception is seen if the URL is https. Even if I explicitly intialize the
trust store this exception comes.
It seems the trust store has an issue? Was there any change done recently?
[2013-01-30 16:09:14,179] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
org.wso2.carbon.bam.toolbox.deployer.exception.BAMToolboxDeploymentException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at
org.wso2.carbon.bam.toolbox.deployer.service.BAMToolBoxUploaderService.deployToolBoxFromURL(BAMToolBoxUploaderService.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.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.bam.toolbox.deployer.stub.BAMToolboxDepolyerServiceStub.deployToolBoxFromURL(BAMToolboxDepolyerServiceStub.java:1474)
at
org.wso2.carbon.bam.toolbox.deployer.ui.client.BAMToolBoxDeployerClient.installToolBoxFromURL(BAMToolBoxDeployerClient.java:150)
at
org.wso2.carbon.bam.toolbox.deployer.ui.upload.ToolBoxUploader.execute(ToolBoxUploader.java:93)
at
org.wso2.carbon.ui.transports.fileupload.AbstractFileUploadExecutor.executeGeneric(AbstractFileUploadExecutor.java:104)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$CarbonXmlFileUploadExecHandler.execute(FileUploadExecutorManager.java:392)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$FileUploadExecutionHandlerManager.startExec(FileUploadExecutorManager.java:276)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager.execute(FileUploadExecutorManager.java:125)
at
org.wso2.carbon.ui.transports.FileUploadServlet.doPost(FileUploadServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
Re: [Dev] PKIX exception when accessing a https url from the BE
Also, this was working fine before...
On Wed, Jan 30, 2013 at 4:13 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi,
One of the services in BAM, uploads a file from a given url. The following
exception is seen if the URL is https. Even if I explicitly intialize the
trust store this exception comes.
It seems the trust store has an issue? Was there any change done recently?
[2013-01-30 16:09:14,179] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
org.wso2.carbon.bam.toolbox.deployer.exception.BAMToolboxDeploymentException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at
org.wso2.carbon.bam.toolbox.deployer.service.BAMToolBoxUploaderService.deployToolBoxFromURL(BAMToolBoxUploaderService.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.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.bam.toolbox.deployer.stub.BAMToolboxDepolyerServiceStub.deployToolBoxFromURL(BAMToolboxDepolyerServiceStub.java:1474)
at
org.wso2.carbon.bam.toolbox.deployer.ui.client.BAMToolBoxDeployerClient.installToolBoxFromURL(BAMToolBoxDeployerClient.java:150)
at
org.wso2.carbon.bam.toolbox.deployer.ui.upload.ToolBoxUploader.execute(ToolBoxUploader.java:93)
at
org.wso2.carbon.ui.transports.fileupload.AbstractFileUploadExecutor.executeGeneric(AbstractFileUploadExecutor.java:104)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$CarbonXmlFileUploadExecHandler.execute(FileUploadExecutorManager.java:392)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$FileUploadExecutionHandlerManager.startExec(FileUploadExecutorManager.java:276)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager.execute(FileUploadExecutorManager.java:125)
at
org.wso2.carbon.ui.transports.FileUploadServlet.doPost(FileUploadServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
Re: [Dev] PKIX exception when accessing a https url from the BE
On Wed, Jan 30, 2013 at 4:15 PM, Tharindu Mathew thari...@wso2.com wrote:
Also, this was working fine before...
AFAIK, we have not done any changes to trust store. But external party
may have changed the CA or trust store has an expired one? Could you try to
import the CA certificate of url in to trust store and try it.
Thanks,
Asela.
On Wed, Jan 30, 2013 at 4:13 PM, Tharindu Mathew thari...@wso2.comwrote:
Hi,
One of the services in BAM, uploads a file from a given url. The
following exception is seen if the URL is https. Even if I explicitly
intialize the trust store this exception comes.
It seems the trust store has an issue? Was there any change done recently?
[2013-01-30 16:09:14,179] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
org.wso2.carbon.bam.toolbox.deployer.exception.BAMToolboxDeploymentException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at
org.wso2.carbon.bam.toolbox.deployer.service.BAMToolBoxUploaderService.deployToolBoxFromURL(BAMToolBoxUploaderService.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.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.bam.toolbox.deployer.stub.BAMToolboxDepolyerServiceStub.deployToolBoxFromURL(BAMToolboxDepolyerServiceStub.java:1474)
at
org.wso2.carbon.bam.toolbox.deployer.ui.client.BAMToolBoxDeployerClient.installToolBoxFromURL(BAMToolBoxDeployerClient.java:150)
at
org.wso2.carbon.bam.toolbox.deployer.ui.upload.ToolBoxUploader.execute(ToolBoxUploader.java:93)
at
org.wso2.carbon.ui.transports.fileupload.AbstractFileUploadExecutor.executeGeneric(AbstractFileUploadExecutor.java:104)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$CarbonXmlFileUploadExecHandler.execute(FileUploadExecutorManager.java:392)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$FileUploadExecutionHandlerManager.startExec(FileUploadExecutorManager.java:276)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager.execute(FileUploadExecutorManager.java:125)
at
org.wso2.carbon.ui.transports.FileUploadServlet.doPost(FileUploadServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
[Dev] Developer Studio 3.0.0 Alpha 2 Released !
Hi All, We have WSO2 Developer Studio 3.0.0 Alpha 2 ready to be downloaded at [1]. This release includes following improvements and bug fixes. Bug Fixes - [TOOLS-148 https://wso2.org/jira/browse/TOOLS-148] - Endpoint name that is given by default should change for each artifact created - [TOOLS-1154 https://wso2.org/jira/browse/TOOLS-1154] - Invalid error message pop up when adding a new registry connection - [TOOLS-1390 https://wso2.org/jira/browse/TOOLS-1390] - unusual date (2010/06/25) is shown in registry resource projects - [TOOLS-1416 https://wso2.org/jira/browse/TOOLS-1416] - While implementing service chaining, inside sequences editor we cannot send a massage to an endpoint from inside sequence of complex mediators. - [TOOLS-1429 https://wso2.org/jira/browse/TOOLS-1429] - Receiving sequences cannot be reuse. - [TOOLS-1430 https://wso2.org/jira/browse/TOOLS-1430] - Wrong graphical interpretation of configurations in graphical editor. - [TOOLS-1438 https://wso2.org/jira/browse/TOOLS-1438] - Wrong serialization with filter Mediator in main sequence (Sample 50). - [TOOLS-1441 https://wso2.org/jira/browse/TOOLS-1441] - Error while deserialization load balance endpoint. - [TOOLS-1442 https://wso2.org/jira/browse/TOOLS-1442] - Error while deserialization fail over endpoint. - [TOOLS-1444 https://wso2.org/jira/browse/TOOLS-1444] - NPE while deserialization WSDL endpoint. - [TOOLS-1457 https://wso2.org/jira/browse/TOOLS-1457] - Failover and Loadbalance endpoints doesn't get serialized in sequence editor. - [TOOLS-1459 https://wso2.org/jira/browse/TOOLS-1459] - If diagram contains multiple failover-endpoints or load-balance endpoints ,Serializers will generate an invalid configuration in source view. - [TOOLS-1460 https://wso2.org/jira/browse/TOOLS-1460] - Incorrect default values in Smooks mediator - [TOOLS-1461 https://wso2.org/jira/browse/TOOLS-1461] - Empty tool tip pops up on every mouse over the graphical editor - [TOOLS-1462 https://wso2.org/jira/browse/TOOLS-1462] - Null value pops up when trying delete the Note attachment form a node using Delete shortcut key - [TOOLS-1463 https://wso2.org/jira/browse/TOOLS-1463] - Error while trying to save a proxy created using graphical editor - [TOOLS-1464 https://wso2.org/jira/browse/TOOLS-1464] - Error when trying open a saved ESB project - [TOOLS-1465 https://wso2.org/jira/browse/TOOLS-1465] - Throttle mediator's onAccept, onReject branches do not deserialize - [TOOLS-1466 https://wso2.org/jira/browse/TOOLS-1466] - NPE when trying to add a sequence to the proxy via graphical editor - [TOOLS-1467 https://wso2.org/jira/browse/TOOLS-1467] - Out Sequence does not deserialize correctly if send mediator contains inside a complex mediator (e.g. aggregate, etc ) - [TOOLS-1468 https://wso2.org/jira/browse/TOOLS-1468] - Cannot add cache mediator or clone mediator to out sequence as a first node, it will automatically remove by the editor - [TOOLS-1469 https://wso2.org/jira/browse/TOOLS-1469] - Cannot serialized/deserialized main sequence without in and out configurations - [TOOLS-1470 https://wso2.org/jira/browse/TOOLS-1470] - URL Rewrite mediator does not serialized/deserialized correctly - [TOOLS-1475 https://wso2.org/jira/browse/TOOLS-1475] - If once deserializer fail to create the diagram that an exception will raised for all other new diagrams - [TOOLS-1476 https://wso2.org/jira/browse/TOOLS-1476] - WSDL from source URL entry does not correctly deserialize in proxy services - [TOOLS-1478 https://wso2.org/jira/browse/TOOLS-1478] - when proxy contain inline endpoint, In sequence may hasn't a send mediator, but serializer change the configuration by adding a send mediator - [TOOLS-1480 https://wso2.org/jira/browse/TOOLS-1480] - ESB sample 350 does not deserialize comes null pointer exception (script mediator) - [TOOLS-1481 https://wso2.org/jira/browse/TOOLS-1481] - Script mediator does not have a proper editor to write inline scripts - [TOOLS-1482 https://wso2.org/jira/browse/TOOLS-1482] - Main Sequence Editor has Proxy Service and API Resource in the Tool box - [TOOLS-1484 https://wso2.org/jira/browse/TOOLS-1484] - StackOverflow Exception thrown when testing ESB Sample 7 - [TOOLS-1487 https://wso2.org/jira/browse/TOOLS-1487] - After creating a new sequence, it doesn't get added to tool palettes of opened editors right after creating the sequence. - [TOOLS-1488 https://wso2.org/jira/browse/TOOLS-1488] - Main Sequence Editor shows the wrong name in the Editor's Title Bar - [TOOLS-1490 https://wso2.org/jira/browse/TOOLS-1490] - Addressing endpoint does not get added to main sequence - [TOOLS-1491 https://wso2.org/jira/browse/TOOLS-1491] - Missing In and Out sequences in the Main sequence throws a NPE upon saving - [TOOLS-1492
[Dev] Ehcache warning at Startup
Getting following during BAM 2.1.1 startup. Any idea how to resolve this?
WARN {net.sf.ehcache.config.ConfigurationFactory} - No configuration found.
Configuring ehcache from ehcache-failsafe.xml found in the classpath:
bundleresource://44.fwk426901684/ehcache-failsafe.xml
Buddhika
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please share the decision made on Access token generation
Hai All, please share the decisions made on the chat with prabath regarding the Access token generation. How to proceed from the current point. Thanks! Ragu ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] PKIX exception when accessing a https url from the BE
Same issue observed when ESB and GReg servers import resources from WSO2
svn repository via https. WSO2 svn CA has been updated since it was
expired. Refer JIRA from[1]
Thanks,
Nuwanw
[1]. https://wso2.org/jira/browse/CARBON-14041
On Wed, Jan 30, 2013 at 4:31 PM, Asela Pathberiya as...@wso2.com wrote:
On Wed, Jan 30, 2013 at 4:15 PM, Tharindu Mathew thari...@wso2.comwrote:
Also, this was working fine before...
AFAIK, we have not done any changes to trust store. But external party
may have changed the CA or trust store has an expired one? Could you try to
import the CA certificate of url in to trust store and try it.
Thanks,
Asela.
On Wed, Jan 30, 2013 at 4:13 PM, Tharindu Mathew thari...@wso2.comwrote:
Hi,
One of the services in BAM, uploads a file from a given url. The
following exception is seen if the URL is https. Even if I explicitly
intialize the trust store this exception comes.
It seems the trust store has an issue? Was there any change done
recently?
[2013-01-30 16:09:14,179] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
org.wso2.carbon.bam.toolbox.deployer.exception.BAMToolboxDeploymentException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at
org.wso2.carbon.bam.toolbox.deployer.service.BAMToolBoxUploaderService.deployToolBoxFromURL(BAMToolBoxUploaderService.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.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.bam.toolbox.deployer.stub.BAMToolboxDepolyerServiceStub.deployToolBoxFromURL(BAMToolboxDepolyerServiceStub.java:1474)
at
org.wso2.carbon.bam.toolbox.deployer.ui.client.BAMToolBoxDeployerClient.installToolBoxFromURL(BAMToolBoxDeployerClient.java:150)
at
org.wso2.carbon.bam.toolbox.deployer.ui.upload.ToolBoxUploader.execute(ToolBoxUploader.java:93)
at
org.wso2.carbon.ui.transports.fileupload.AbstractFileUploadExecutor.executeGeneric(AbstractFileUploadExecutor.java:104)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$CarbonXmlFileUploadExecHandler.execute(FileUploadExecutorManager.java:392)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager$FileUploadExecutionHandlerManager.startExec(FileUploadExecutorManager.java:276)
at
org.wso2.carbon.ui.transports.fileupload.FileUploadExecutorManager.execute(FileUploadExecutorManager.java:125)
at
org.wso2.carbon.ui.transports.FileUploadServlet.doPost(FileUploadServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
[Dev] Multiple profile support in Carbon
Hi, Dileepa working on the $subject. @Dileepa : can you please provide a brief update :) thanks, --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Getting the permitted operations related to a particular stage in App Factory
Hi, According to the current permission scheme , is it possible to do the $subject. After looking in to the current scheme , the permission is decided in the perspective of the user. E.g: the user has permission for a particular stage the user has permission to a particular operation. (demote, promote) Is there a way to check the necessary operations for a particular stage. E.g:: Retire option is available for the Production stage, (and the other operations are not allowed ). Another option is to use a semantic value in the configuration file. (appfactory.xml) . A semantic value can be used , in a scenario where the Production stage is given another name. Thanks, -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting the permitted operations related to a particular stage in App Factory
As per the offline discussion with Manjula, the permission is decided in the perspective of the user and the current scheme does not allow to get the permitted operations for a particular stage. So, how about the option related to the semantic value in the configuration file. How should I proceed ... What will be the best approach for this. Thanks, On Thu, Jan 31, 2013 at 9:05 AM, Achala Aponso ach...@wso2.com wrote: Hi, According to the current permission scheme , is it possible to do the $subject. After looking in to the current scheme , the permission is decided in the perspective of the user. E.g: the user has permission for a particular stage the user has permission to a particular operation. (demote, promote) Is there a way to check the necessary operations for a particular stage. E.g:: Retire option is available for the Production stage, (and the other operations are not allowed ). Another option is to use a semantic value in the configuration file. (appfactory.xml) . A semantic value can be used , in a scenario where the Production stage is given another name. Thanks, -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting the permitted operations related to a particular stage in App Factory
Hi Achala, How about getting the transition events from the lifecycle config? I think that's the best possible way to do this. for eg: lifecycle config may have following transition events for Development stage. state id=Development transition event=Promote target=ReadyForQA/ transition event=On Hold target=OnHold/ /state Please check whether any operation in CustomLifecyclesChecklistAdminService provides this info/or other way we can get this events. Thanks Thilini On Thu, Jan 31, 2013 at 9:54 AM, Achala Aponso ach...@wso2.com wrote: As per the offline discussion with Manjula, the permission is decided in the perspective of the user and the current scheme does not allow to get the permitted operations for a particular stage. So, how about the option related to the semantic value in the configuration file. How should I proceed ... What will be the best approach for this. Thanks, On Thu, Jan 31, 2013 at 9:05 AM, Achala Aponso ach...@wso2.com wrote: Hi, According to the current permission scheme , is it possible to do the $subject. After looking in to the current scheme , the permission is decided in the perspective of the user. E.g: the user has permission for a particular stage the user has permission to a particular operation. (demote, promote) Is there a way to check the necessary operations for a particular stage. E.g:: Retire option is available for the Production stage, (and the other operations are not allowed ). Another option is to use a semantic value in the configuration file. (appfactory.xml) . A semantic value can be used , in a scenario where the Production stage is given another name. Thanks, -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thilini Ishaka WSO2 Inc. http://wso2.com* *bolg: thiliniishaka.blogspot.com* *linkedin: http://lk.linkedin.com/in/thiliniishaka* *twitter: https://twitter.com/#!/ThiliniIsh* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.6 #151 has FAILED. Change made by suho and suresh.
--- WSO2 Carbon 4.0.x Platform 4.0.6 #151 failed. --- Code has been updated by suho, suresh. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA006-151/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 844 tests passed. -- Code Changes -- suho (156171): updating cep core version suho (156172): upgrading cep server feature to 4.0.7 suresh (156170): adding the phone number credential type and external credential type -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Multiple profile support in Carbon
Hi Pradeep and All,
To give a brief introduction on this; the purpose of this implementation is
to be able to pre-provision several products in to one distribution and
select the product to load at startup.
Each product can be considered a separate Product profile and at startup by
passing an argument like -Dprofile={Product.Profile} we should be able to
load the required product.
After doing some background research on Equinox configurations I did a POC
by manually constructing the product distribution structure to support this
(as shown below), and point the equinox.configuration directory to relevant
{Profile}configuration directory at startup. This will load the set of
bundles relevant to the given Product.Profile.
*Things to do;*
Need to look at on how to support feature installations separately to the
loaded Profile. Currently after loading a particular profile and installing
features the newly added bundle entries are not persisted.
I'm currently working on changing the carbon-p2-plugin goals to construct
the modified product distribution structure.
Will update the thread on the progress.
*
Modified Product structure to support multiple-profiles*
*repository/components/configuration *{equinox configuration directory}
|
|--WSO2CarbonProfile
||--config.ini
||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set to
load Carbon product}
|--WSO2ASProfile
||--config.ini
||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set to
load AS product}
*repository/components/p2 *{p2 data directory}
|--org.eclipse.equinox.p2.engine
| |--profileRegistry
||---WSO2CarbonProfile.profile {p2 state of Carbon}
||---WSO2ASProfile.profile {p2 state of AS}
Thanks,
Dileepa
On Thu, Jan 31, 2013 at 8:38 AM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
Dileepa working on the $subject.
@Dileepa : can you please provide a brief update :)
thanks,
--Pradeep
--
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware
Mobile : +94777-857616
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x Platform 4.0.6 #152 has FAILED. Change made by 6 authors.
--- WSO2 Carbon 4.0.x Platform 4.0.6 #152 failed. --- Code has been updated by hasini, suho, johann, ajanthan, suresh, dimuthul. No failed tests found, a possible compilation error. http://wso2.org/bamboo/browse/WCB001-PLA006-152/ - Currently Responsible - No one is responsible for fixing this build. -- Failing Jobs -- - Default Job (Default Stage): 844 tests passed. -- Code Changes -- suho (156185): fixing https://wso2.org/jira/browse/CEP-147 patch by Mohan ajanthan (156184): reverting the mount point config suho (156189): Adding sample of CEP that supports to REST API patch by Mohan -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
