I am doing upgrade from AEM 6.1 author with mongodb to AEM 6.3 author.
1. Pre upgrade task is done
2. Replaced AEM 6.1 jar with AEM 6.3 jar alone parallel AEM 6.1 crx instance
3. Unpacked AEM 6.3 jar with runmode mongo and it shows
Build number changed, running in upgrade mode
UpgradeUtil.handleInstallAndUpgrade has mode UPGRADE
Started the AEM 6.3 jar
Instance started with upgrade mode. Finally, its got started but not able to login. The below error is throwing.
11.11.2017 18:25:23.190 ERROR [0:0:0:0:0:0:0:1 [1510404923182] GET /libs/granite/core/content/login.html HTTP/1.1] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.
11.11.2017 18:25:23.190 ERROR [0:0:0:0:0:0:0:1 [1510404923182] GET /libs/granite/core/content/login.html HTTP/1.1]
com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible
reasons: login page not existing or not accessible
11.11.2017 18:25:23.592 ERROR [qtp316797819-2676] com.day.crx.delite.impl.servlets.InitServlet Error while retrieving
infos java.lang.NullPointerException: null at
com.day.crx.delite.impl.servlets.InitServlet.getFormattedName(InitServlet.java:126)
at
com.day.crx.delite.impl.servlets.InitServlet.doService(InitServlet.java:84)
at com.day.crx.delite.impl.AbstractServlet.service(AbstractServlet.java:52)
at com.day.crx.delite.impl.MainServlet.doService(MainServlet.java:129)
at com.day.crx.delite.impl.MainServlet.service(MainServlet.java:107)
at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:85)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.jav
a:79)
at com.adobe.granite.license.impl.LicenseCheckFilter.doFilter(LicenseCheckFilter.java:308)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.jav
a:74)
at org.apache.felix.http.sslfilter.internal.SslFilter.doFilter(SslFilter.java:96)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.jav
a:74)
at org.apache.sling.security.impl.ReferrerFilter.doFilter(ReferrerFilter.java:295)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at
org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.jav
a:74)
at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:138)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.jav
a:74)
Related
'main' o.s.web.context.ContextLoader : Context initialization failed
java.lang.ClassNotFoundException: org.w3c.dom.DOMError cannot be found by msg-searching-portlet_1.0
could anyone suggest how to handle this error.
Thanks in Advance
while running liferay 7.1 tomcat server and after hot deploy of portlets , i am getting the error.
any way to resolve this error.
We are using WSO2 identity server for user authentication in our product suite. Recently we have upgraded its version from 5.0.0 to 5.1.0.
After upgrading to WSO2 identity server 5.1.0 version we are getting following exception when we enable IWA (Integrated Windows Authentication)
TID: [-1234] [] [2016-07-21 18:46:52,606] DEBUG {waffle.servlet.spi.NegotiateSecurityFilterProvider} - security package: Negotiate, connection id: fe80:0:0:0:f1da:6adb:d83e:18d6%6:64966
TID: [-1234] [] [2016-07-21 18:46:52,622] DEBUG {waffle.servlet.spi.NegotiateSecurityFilterProvider} - token buffer: 1629 byte(s)
TID: [-1234] [] [2016-07-21 18:46:52,675] ERROR {org.apache.catalina.core.StandardWrapperValve} - Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception
com.sun.jna.platform.win32.Win32Exception: The token supplied to the function is invalid
at waffle.windows.auth.impl.WindowsAuthProviderImpl.acceptSecurityToken(WindowsAuthProviderImpl.java:137)
at waffle.servlet.spi.NegotiateSecurityFilterProvider.doFilter(NegotiateSecurityFilterProvider.java:102)
at waffle.servlet.spi.SecurityFilterProviderCollection.doFilter(SecurityFilterProviderCollection.java:116)
at org.wso2.carbon.identity.application.authenticator.iwa.servlet.IWAServelet.doPost(IWAServelet.java:89)
at org.wso2.carbon.identity.application.authenticator.iwa.servlet.IWAServelet.doGet(IWAServelet.java:64)
After searching for the problem on Google we came across following post.
https://github.com/dblock/waffle/issues/107
It looks like there was some issue in the earlier version of Waffle library which is resolved in 1.7.4 version.
WSO2 Identity server 5.1.0 comes with Waffle library version 1.6.0 (waffle-jna_1.6.0.wso2v4.jar).
Now my question is do we have any WSO2 Identity server patch available which includes the latest Waffle library (version 1.7.4 or above)?
Can we simply download the latest version of Waffle and put into “wso2is-5.1.0\repository\components\plugins” folder? Will it work?
We need to see if it resolves the above stated problem. We are unable to find any other solution to this issue.
Putting the new version in the plugins folder won't work. You'll need to follow these steps,
Get the waffle 1.7.4 wrapped as an OSGi bundle. You can refer this pom file which does the same for 1.6 version. Make sure the versions are properly updated in the new pom file.
Build from the pom file you created above to get the OSGi bundle
Put it into repository\components\dropins\ folder and restart the IS
[Validation Step][Optional] Start IS in OSGI console with wso2server.bat -DosgiConsole. Once the server is up run ss in the osgi console and locate the bundle id for org.wso2.carbon.identity.application.authenticator.iwa (This will be an integer below ~500). And then b <bundle_id> and make sure it binds the 1.7 versions of waffle packages.
I am developing simple VSphere Web Client plugin in Eclipse Juno with Vijava 5.5 and Vsphere sdk 5.5.. My project was working fine till yesterday. Today I tried to change the sdk to Vsphere sdk 6.0. From that onwards I am getting Following Error while deploying my UI project in Virgo Server.
Later, I again reverted to my Vsphere sdk 5.5 itself. But still i am getting this error. I don't know what I missed. Why it showing in my UI project? Is there anything i can change my dependencies there?
Error is,
2015-06-11 19:27:26.160] [INFO ] TCP Connection(11)-127.0.0.1 <DE0004I> Starting bundle 'test-provider' version '0.0.0'.
[2015-06-11 19:27:26.160] [INFO ] start-signalling-1 <DE0005I> Started bundle 'test-provider' version '0.0.0'.
[2015-06-11 19:27:26.957] [INFO ] TCP Connection(11)-127.0.0.1 <DE0000I> Installing bundle 'com.mycompany.testui.testui' version '1.0.0'.
[2015-06-11 19:27:27.051] [INFO ] TCP Connection(11)-127.0.0.1 <ME0003I> Dump 'C:\ProgramData\vmware\vSphere Web Client\serviceability\dump\2015-06-11-19-27-051' generated
[2015-06-11 19:27:27.066] [ERROR] TCP Connection(11)-127.0.0.1 <DE0002E> Installation of bundle 'com.mycompany.testui.testui' version '1.0.0' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.mycompany.testui.testui' at version '1.0.0': Cannot resolve: com.mycompany.testui.testui
Resolver report:
An Import-Package could not be resolved. Resolver error data <Import-Package: com.mycompany.testprovider; version="0.0.0">. Caused by missing constraint in bundle <com.mycompany.testui.testui_1.0.0>
constraint: <Import-Package: com.mycompany.testprovider; version="0.0.0">
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)
at org.eclipse.virgo.kernel.deployer.management.StandardDeployer.deploy(StandardDeployer.java:52)
at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75)
at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279)
When you deploy your UI, you must deploy your service com.mycompany.testprovide previously
Service provider is not linked with Plugin UI project. In order to do that,
need to do the following..
Right-click on the Plugin UI project and select vSphere SDK Tools > Package vSphere Client plugin.
In that, select your service provider project. That's it.
To make sure the service bundle is deployed before the ui bundle use the <bundlesOrder> tag in the plugin-package.xml.
vSphere Client (HTML) versions 6.5U1 and above improve on this by introducing a dedicated scope for each plugin (OSGi sandboxing feature).
I was using primefaces 3.5 in my project and now have updated to 4.0 but its failing to deploy on Glassfish after upgrading and resulting in the following error:
Severe: Critical error during deployment:
com.sun.faces.config.ConfigurationException: java.lang.Exception:
No Function Found on type: org.primefaces.util.ComponentUtils with
signature: java.lang.String resolveWidgetVar(java.lang.String)
I have removed the 3.5 version JAR and placed the new one in the project library, but still failing to deploy with the mentioned error given.
I'm using:
Glassfish: 4.1,
Netbeans 8.0.1
You should clear glassfish cache because old primefaces library which referred in the class path of your app server.
Stop the glassfish server.
Delete the content of the osgi-cache, by removing the felix directory in your domain. This is usually found in glassfish4/glassfish/domains/domain1/osgi-cache
I'm trying to move an application from JBoss 4.2.2 AS to 6.x AS. Right now I'm trying to get jbpm 3.x running on the AS I have this problem when trying to upload a .par file to the server:
13:41:51,713 ERROR [org.jbpm.db.GraphSession] (http-127.0.0.1-8888-1) java.lang.ClassCastException: org.jbpm.graph.def.Node_$$_javassist_92 cannot be cast to javassist.util.proxy.ProxyObject
Which then results in:
13:41:51,740 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/app].[ProcessUploadServlet]] (http-127.0.0.1-8888-1) Servlet.service() for servlet ProcessUploadServlet threw exception: org.jbpm.JbpmException: couldn't find process definition 'ProcessName'.
I've tried using both old and new versions of javassist which has no positive effect. Any ideas?
It seems you are using eclipse plugins and you have class loader problem between 2 plugins, make sure that you have only one class loader to load ProxyObject (Javassist)