Hi Tharindu, I think we need to upgrade the Kernel to get the fix to APIM 2.2.0. We encounter the same issue in APIM 2.1.0 fresh pack and WUM updated one fixed it.
Thanks, Harsha On Wed, Nov 29, 2017 at 2:23 PM, Tharindu Edirisinghe <tharin...@wso2.com> wrote: > Hi Devs, > > I'm trying to build the APIM 2.2.0 (to be released) pack. For that, I > built the carbon-apimgt [1] and then the product-apim [2]. Build was > successful and I got the *wso2am-2.2.0-SNAPSHOT* pack. > > Then, I need to test secure vault and for that I ran *./ciphertool.sh > -Dconfigure* from bin directory without changing anything. Then I started > the pack and it prints the following error and the pack doesn't startup. > > [2017-11-29 14:16:20,748] INFO - TemplateDeployerServiceTrackerDS > Successfully deployed the execution manager tracker service > > *[2017-11-29 14:16:21,528] FATAL - TomcatBundleActivator Error while > starting server NOT_FOUND_ERR: An attempt is made to reference a node in a > context where it does not exist.org.w3c.dom.DOMException: NOT_FOUND_ERR: An > attempt is made to reference a node in a context where it does not exist.* > at org.apache.xerces.dom.AttributeMap.internalRemoveNamedItem(Unknown > Source) > at org.apache.xerces.dom.AttributeMap.removeNamedItem(Unknown Source) > at org.wso2.carbon.tomcat.internal.ServerManager.init( > ServerManager.java:107) > at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.start( > TomcatBundleActivator.java:45) > at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run( > BundleContextImpl.java:711) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.framework.internal.core.BundleContextImpl. > startActivator(BundleContextImpl.java:702) > at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start( > BundleContextImpl.java:683) > at org.eclipse.osgi.framework.internal.core.BundleHost. > startWorker(BundleHost.java:381) > at org.eclipse.osgi.framework.internal.core.AbstractBundle. > resume(AbstractBundle.java:390) > at org.eclipse.osgi.framework.internal.core.Framework. > resumeBundle(Framework.java:1176) > at org.eclipse.osgi.framework.internal.core.StartLevelManager. > resumeBundles(StartLevelManager.java:559) > at org.eclipse.osgi.framework.internal.core.StartLevelManager. > resumeBundles(StartLevelManager.java:544) > at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL( > StartLevelManager.java:457) > at org.eclipse.osgi.framework.internal.core.StartLevelManager. > doSetStartLevel(StartLevelManager.java:243) > at org.eclipse.osgi.framework.internal.core.StartLevelManager. > dispatchEvent(StartLevelManager.java:438) > at org.eclipse.osgi.framework.internal.core.StartLevelManager. > dispatchEvent(StartLevelManager.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager. > dispatchEvent(EventManager.java:230) > > It seems this is the same issue reported in [3] (according to JIRA, it's > already fixed). I tested above scenario with APIM 2.1.0 (both vanilla and > WUM packs) and there was no error. > > So, I guess this should have been introduced in the 2.2.0 pack. > > Please check. > > [1] https://github.com/wso2/carbon-apimgt/tree/6.x > [2] https://github.com/wso2/product-apim/tree/2.x > [3] https://wso2.org/jira/browse/CARBON-16104 > > Thanks, > TharinduE > -- > > Tharindu Edirisinghe > Senior Software Engineer | WSO2 Inc > Platform Security Team > Blog : http://tharindue.blogspot.com > mobile : +94 775181586 <+94%2077%20518%201586> > -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
