kumar_t's Posts

Remote plugin sample Websocket not working

by Enthusiast in vSphere Client SDK Discussions
‎11-09-2023 12:59 AM
‎11-09-2023 12:59 AM
Hi, We are trying to implement websockets in our plugin UI and it is giving 502 error. To confirm on the support, we had taken 8.0U1 SDK sample and deployed it on Client 8.0U1 and found that same e... See more...
Hi, We are trying to implement websockets in our plugin UI and it is giving 502 error. To confirm on the support, we had taken 8.0U1 SDK sample and deployed it on Client 8.0U1 and found that same error is coming for sample plugin as well. Could you please confirm/help on fixing the sample? we were able to establish the socket connection directly without going through the plugin reverse proxied manifest/backend server(htmlClientSdk.app.getPluginBackendInfo) address. I remember the recommendation is to tunnel all interaction through proxied backend server URL . Does establishing socket connection directly to  plugin backend is acceptable or not? Any implication on plugin certification? Error: vSphere Client version 8.0.0.10000 Sample jar Server log: 2023-11-09 02:21:38.135 ERROR 7164 --- [io-8443-exec-17] c.v.s.r.w.WebSocketMessageHandler : Transport error java.io.IOException: Unable to unwrap data, invalid status [CLOSED] at org.apache.tomcat.util.net.SecureNioChannel.read(SecureNioChannel.java:632) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1257) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1230) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1200) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:72) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1468) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_392-392] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_392-392] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.lang.Thread.run(Thread.java:750) [na:1.8.0_392-392] 2023-11-09 02:21:38.135 ERROR 7164 --- [io-8443-exec-17] c.v.s.r.w.WebSocketMessageHandler : Transport error java.io.IOException: java.io.IOException: Unable to wrap data, invalid status [CLOSED] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:592) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:480) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.close(WsSession.java:445) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:236) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:136) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at com.vmware.sample.remote.websocket.WebSocketMessageHandler.handleTransportError(WebSocketMessageHandler.java:66) [classes!/:na] at org.springframework.web.socket.handler.WebSocketHandlerDecorator.handleTransportError(WebSocketHandlerDecorator.java:80) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.handleTransportError(LoggingWebSocketHandlerDecorator.java:64) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.handleTransportError(ExceptionWebSocketHandlerDecorator.java:68) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onError(StandardWebSocketHandlerAdapter.java:156) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.onError(WsHttpUpgradeHandler.java:216) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1468) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_392-392] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_392-392] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.lang.Thread.run(Thread.java:750) [na:1.8.0_392-392] Caused by: java.io.IOException: Unable to wrap data, invalid status [CLOSED] at org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:675) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:101) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:157) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint.java:1276) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBase.java:670) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.flushBlocking(SocketWrapperBase.java:607) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.flush(SocketWrapperBase.java:597) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:96) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:494) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] ... 22 common frames omitted
Labels

Re: How to hide the actions instead of disable using Dynamic Extensions in vSphere Client

by Enthusiast in vSphere Client SDK Discussions
‎10-04-2023 05:33 AM
‎10-04-2023 05:33 AM
Please update the sdk documentation. https://developer.vmware.com/docs/19273/GUID-14852F91-1D99-4D2E-AC54-DF27872D98DE.html

How to hide the actions instead of disable using Dynamic Extensions in vSphere Client

by Enthusiast in vSphere Client SDK Discussions
‎09-28-2023 03:43 AM
‎09-28-2023 03:43 AM
Hi, Our plugin is build on SDK 7.0U3 and is the minimum supported vSphere client version as well.  We have some actions on vsphere entity(say datastore entity), we would like to show/Hide actions d... See more...
Hi, Our plugin is build on SDK 7.0U3 and is the minimum supported vSphere client version as well.  We have some actions on vsphere entity(say datastore entity), we would like to show/Hide actions depending on the various factors. As per the vSphere Client SDK guide, we were able to enable/disable the actions. But we want to hide the actions instead of Disable like the local plugin SDK does. Is there a way to achieve it? Thanks, Kumar  

Re: What's new in vSphere Client SDK 8.0

by Enthusiast in vSphere Client SDK Discussions
‎01-12-2023 02:48 AM
‎01-12-2023 02:48 AM
Navigating Actions Defined in the Remote plug-in Manifest File - developers are now able to define navigating actions along with the modal menu actions in the plug-in manifest file. This will enable... See more...
Navigating Actions Defined in the Remote plug-in Manifest File - developers are now able to define navigating actions along with the modal menu actions in the plug-in manifest file. This will enable users to use the action to navigate to a view defined by the plug-in Can you please elaborate this feature with an example/use case? Please point me to the code snippet in sample if it is part of sdk sample.  

vSphere Remote Plugin SDK: Dynamic extensions for Summary cards

by Enthusiast in vSphere Client SDK Discussions
‎01-12-2023 02:43 AM
‎01-12-2023 02:43 AM
As per vSphere 8.0 SDK release notes, the Dynamic extension support on Summary cards got added. Our interpretation is this Dynamic extension support for Summary cards will not work in any vSphere 7.... See more...
As per vSphere 8.0 SDK release notes, the Dynamic extension support on Summary cards got added. Our interpretation is this Dynamic extension support for Summary cards will not work in any vSphere 7.x version and the minimum required version is vSphere 8.0 Please confirm.     Thanks, Kumar
Labels

Regarding API info in vSphere 8.0 client SDK

by Enthusiast in vSphere Client SDK Discussions
‎11-04-2022 06:35 PM
‎11-04-2022 06:35 PM
Hi, I'm going through the vSphere client 8.0 release notes and it is mentioned that a new javascript API(refreshPluginItemsState) was introduced. However, I could not find it in the SDK documentatio... See more...
Hi, I'm going through the vSphere client 8.0 release notes and it is mentioned that a new javascript API(refreshPluginItemsState) was introduced. However, I could not find it in the SDK documentation  Could please provide some info on the usage and when to use? Thanks, Kumar

Remote plugin sdk sample Task names are not rendering

by Enthusiast in vSphere Client SDK Discussions
‎06-22-2022 12:01 PM
‎06-22-2022 12:01 PM
Hi, I'm trying out the client SDK(7.0U3) sample deployed on vSphere Client version 7.0.3.00500 and observing that none of the task names were rendering I had registered the plugin using  ./ext... See more...
Hi, I'm trying out the client SDK(7.0U3) sample deployed on vSphere Client version 7.0.3.00500 and observing that none of the task names were rendering I had registered the plugin using  ./extension-registration.bat -action registerPlugin -remote -url https://myvcenter/sdk -username administrator@vsphere.local -password mysecret -key com.vmware.sample.remote -version 1.0.0 -pluginUrl https://mydevbox:8443/sample-ui/plugin.json -serverThumbprint 19:FD:2B:0E:62:5E:0E:10:FF:24:34:7A:81:F1:D5:33:19:A7:22:A0:DA:33:27:07:90:0F:8E:8D:72:F1:BD:F1 -c 'Example, Inc.' -n 'Remote Plug-in' -s 'This is a sample plug-in' --taskList remote-plugin-path\registration\resources\taskList.json --faultList remote-plugin-path\registration\resources\faultList.json --privilegeList remote-plugin-path\registration\resources\privilegeList.json --resourceList remote-plugin-path\registration\resources\resourceList.json However, I see that resourceList was not set.  How can we make it work?

Global Refresh event callback leak with Remote Plugin SDK sample code

by Enthusiast in vSphere Client SDK Discussions
‎01-19-2021 10:26 AM
‎01-19-2021 10:26 AM
Hi, I had deployed the sample remote plugin of vSphere client 7.0 SDK and found while testing that the callback of globalRefresh event which was registered for chassis is being carried to other view... See more...
Hi, I had deployed the sample remote plugin of vSphere client 7.0 SDK and found while testing that the callback of globalRefresh event which was registered for chassis is being carried to other views as well. Attaching the exact steps to reproduce.  
Labels

How to retrieve list of vCenters with FQDN and GUID in a Enhanced linked mode using web services sdk

by Enthusiast in vSphere SDK for Java Discussions
‎01-07-2021 10:47 AM
‎01-07-2021 10:47 AM
How to retrieve list of vCenters with FQDN and GUID in a Enhanced linked mode using web services sdk?

Remote Plugin: How to get vCenters list with FQDN in Remote Plugin UI?

by Enthusiast in vSphere Client SDK Discussions
‎01-07-2021 08:58 AM
‎01-07-2021 08:58 AM
We are following singleton plugin topology for our plugin. But need to have a custom vCenter selector dropdown as our views are specific to a vCenter as below:   Basically i'm looking to get th... See more...
We are following singleton plugin topology for our plugin. But need to have a custom vCenter selector dropdown as our views are specific to a vCenter as below:   Basically i'm looking to get the info Linkedmode vCenters which has my plugin registered. Expected data as below [{ "vCenterFQDN": "10.60.6.64", "vCenterGuid": "44594890-e3db-43c6-befa-e236ba3114d9" }, { "vCenterFQDN": "10.60.6.74", "vCenterGuid": "64594890-e3ba-43c6-bcfa-e236ba3114d9" }]    The current JS API getPluginBackendInfo() will not give vCenterFQDN. It just gives VC UUID's as below: {   allPluginBackendServers: [    {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.150-8443", type: "AUX_SERVER_1"},    {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.149-5432", type: "COMMON_SERVER"},    {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.151-8443", type: "AUX_SERVER_2"}   ],   backendServersPerVc: {    vc-guid-1: [     {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.150-8443", type: "AUX_SERVER_1"},     {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.149-5432", type: "COMMON_SERVER"}    ],    vc-guid-2: [     {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.151-8443", type: "AUX_SERVER_2"},     {proxiedBaseUrl: "/plugins/remote~1.0~8/10.30.198.149-5432", type: "COMMON_SERVER"}    ]   }  }   How do I get vCenter FQDN with UUID? Is there a API available?
Labels

vSphere 7.0U1 Remote SDK- Specifying an Auxiliary server as Dynamic views endpoint URL(proxy base)

by Enthusiast in vSphere Client SDK Discussions
‎11-17-2020 09:53 PM
‎11-17-2020 09:53 PM
Hi, As per the sample the dynamicUri endpoint is always uses manifest server(first index of servers info array) as proxy base. How do I intercept this call or make it use of an auxiliary server ins... See more...
Hi, As per the sample the dynamicUri endpoint is always uses manifest server(first index of servers info array) as proxy base. How do I intercept this call or make it use of an auxiliary server instead of manifest server? In our architecture, we had decoupled UI service and plugin backend service as different services. I mean the manifest server just serves static UI related resources like .js,.html,.json running on a spring boot based tomcat and no rest implementation. Actual backend REST API server will be registered as an Auxiliary Server and all HTTP/REST calls will be pointing to it. In this scenario, the dynamicUri endpoints also needed to be calling auxiliary server instead of manifest server. How could we do this?   Thanks, Kumar   
Labels

Re: vSphere Client SDK 7.0 Update 1 is GA!

by Enthusiast in vSphere Client SDK Discussions
‎11-10-2020 06:03 AM
‎11-10-2020 06:03 AM
Im trying to use SHA 256 of vCenter 7.0U1 for vCenter registration and manifest server run java -jar target\remote-plugin-sample-7.0.1.00000-SNAPSHOT.jar --vcenter.guid=a7020581-6ae0-4973-a1a8-72956... See more...
Im trying to use SHA 256 of vCenter 7.0U1 for vCenter registration and manifest server run java -jar target\remote-plugin-sample-7.0.1.00000-SNAPSHOT.jar --vcenter.guid=a7020581-6ae0-4973-a1a8-72956b7e69f5 --vcenter.thumbprint=3e5e1dba4cd04f550f9f6311ff0a5a45ae58a4ca0f7b0bf1727c967c26ada6a5 --vcenter.fqdn=VC_FQDN --vcenter.port=443 .\extension-registration.bat -action registerPlugin -remote -url https://VC_FQDN/sdk -username administrator@vsphere.local -password password1! -key com.vmware.sample.remote -version 1.0.0 -pluginUrl https://<MANIFEST_SERVER>:8443/sample-ui/plugin.json -serverThumbprint 59:93:D9:CF:54:CB:32:60:93:58:CE:45:AD:4D:D7:1F:1C:08:1D:0D:B6:A5:3D:F5:3E:D7:A9:CA:E2:32:DE:41 -c 'Example, Inc.' -n 'RemoteU1 Plug-in' -s 'This is a sample plug-in' --taskList C:\Users\Administrator\Desktop\registration\resources\taskList.json --faultList C:\Users\Administrator\Desktop\registration\resources\faultList.json --privilegeList C:\Users\Administrator\Desktop\registration\resources\privilegeList.json --resourceList C:\Users\Administrator\Desktop\registration\resources\resourceList.json -vct 3e5e1dba4cd04f550f9f6311ff0a5a45ae58a4ca0f7b0bf1727c967c26ada6a5 <-- VC's SHA 256 fingerprint    we are seeing the attached deployment error. But if we use SHA1 fingerprint it is getting deployed. Is this expected behavior?

Re: vSphere Client SDK 7.0 Update 1 is GA!

by Enthusiast in vSphere Client SDK Discussions
‎11-02-2020 04:13 AM
‎11-02-2020 04:13 AM
Hi vladi, I'm trying to register and run the remote plugin sample in vCenter Client 7.0(vSphere Client version 7.0.0.10100). Plugin is not deployed and giving  the below error: Plugin json... See more...
Hi vladi, I'm trying to register and run the remote plugin sample in vCenter Client 7.0(vSphere Client version 7.0.0.10100). Plugin is not deployed and giving  the below error: Plugin json manifest validation failed. Check the detailed information of the relevant vCenter Server task in the Task Console. com.vmware.vise.extensionfw.impl.plugin.util.PluginManifestValidationException: Plugin manifest failed schema validation: file:/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.vmware.sample.remote-1.0.0.0/plugin.json Errors: $.requirements.plugin.api.version: does not have a value in the enumeration [1.0.0, 1.0.1, 1.1.0] $.requirements.plugin.dynamic.extensions: is not defined in the schema and the schema does not allow additional properties $.manifestVersion: does not have a value in the enumeration [1.0.0, 1.0.1, 1.1.0] $.objects.VirtualMachine.configure.views[0].dynamic: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.configure.dynamicUri: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.dynamicUri: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.actions[0].id: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.actions[0].dynamic: is not defined in the schema and the schema does not allow additional properties com.vmware.vise.extensionfw.impl.plugin.JsonPluginManifestParserImpl.parse(JsonPluginManifestParserImpl.java:59) Can't we run vSphere 7.0U1 sample in vSphere 7.0 GA client? Thanks, Kumar

Re:Plugin(local & remote HTML plugin) rendering issues with vCenter 7.0 and chrome v70

by Enthusiast in vSphere Client SDK Discussions
‎09-23-2020 06:22 AM
‎09-23-2020 06:22 AM
Thanks for the response. But VMware vCenter client requirements documentation is mentioned as supported. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-EC8083... See more...
Thanks for the response. But VMware vCenter client requirements documentation is mentioned as supported. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-EC80836B-BE02-4CB2-9F40-15928AFB6E20.html Is this documentation needs updation/correction?

Plugin(local & remote HTML plugin) rendering issues with vCenter 7.0 and chrome v70

by Enthusiast in vSphere Client SDK Discussions
‎09-13-2020 03:01 AM
‎09-13-2020 03:01 AM
Hi Team, We are observing rending issues for our local plugin with vCenter client 7.0.0.10100 and Google chrome v70.0.3538.77. In order to reproduced i had used vCenter client SDK 7.0 remote p... See more...
Hi Team, We are observing rending issues for our local plugin with vCenter client 7.0.0.10100 and Google chrome v70.0.3538.77. In order to reproduced i had used vCenter client SDK 7.0 remote plugin  sample as shown in the attached gif. But plugins(local/remote) rendering works fine in later chrome versions say v80, v85 etc and on Mozilla firefox. As per VMWare official documentation it supposed to work from chrome v50 and above. Please clarify whether it is bug or any change in recommended minimum chrome browser. Thanks, Kumar

Re:vCenter Client plugin is not appearing in 6.7U1 version getting bundle conflict

by Enthusiast in vSphere Client SDK Discussions
‎06-23-2020 01:31 AM
‎06-23-2020 01:31 AM
I found the issue in the build script which is having source/target jar compatibility as 1.8 which supposed to be ""1.7" as per sdk samples.

vCenter Client plugin is not appearing in 6.7U1 version getting bundle conflict

by Enthusiast in vSphere Client SDK Discussions
‎06-15-2020 01:40 AM
‎06-15-2020 01:40 AM
Hi, We had upgraded our plugin service layer spring version as per the upgrade guide(attached) from VMware to support with 6.5U2 and above. Our plugin is not coming up on vCenter 6.7U1 but it... See more...
Hi, We had upgraded our plugin service layer spring version as per the upgrade guide(attached) from VMware to support with 6.5U2 and above. Our plugin is not coming up on vCenter 6.7U1 but it is working fine in 6.5U2, 6.5U2, 6.7U2, 6.7U3 and 7.0GA as well. Below is the conflict snippet from virgo server log: [2020-06-12T14:11:46.557Z] [INFO ] fs-watcher                    o.e.virgo.kernel.userregion.internal.quasi.DependencyCalculator   Calculating missing dependencies of bundle(s) 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0' [2020-06-12T14:11:46.649Z] [INFO ] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         ME0003I Dump '/usr/lib/vmware-vsphere-ui/server/serviceability/dump/2020-06-12-14-11-646' generated [2020-06-12T14:11:46.665Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0002E Installation of par 'com.acme.prodh5' version '9.7.0.23531' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' at version '9.7.0': Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))"> 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.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225) at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79) at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380) at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289) at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49) at java.lang.Thread.run(Thread.java:748) [2020-06-12T14:11:46.666Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0' [2020-06-12T14:11:46.666Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0'. [2020-06-12T14:11:46.667Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.vmware.wsvim25' version '6.7.0' [2020-06-12T14:11:46.667Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.vmware.wsvim25' version '6.7.0'. [2020-06-12T14:11:46.668Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.google.gson' version '2.3.1' [2020-06-12T14:11:46.668Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.google.gson' version '2.3.1'. [2020-06-12T14:11:46.668Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service' version '9.7.0' [2020-06-12T14:11:46.669Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service' version '9.7.0'. [2020-06-12T14:11:46.669Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for par 'com.acme.prodh5' version '9.7.0.23531' [2020-06-12T14:11:46.670Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for par 'com.acme.prodh5' version '9.7.0.23531'. [2020-06-12T14:11:46.672Z] [ERROR] plugin-deploy11               com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.acme.prodh5-9.7.0.23531 java.lang.Exception: Bundle: <com.acme.prodh5,9.7.0.23531> failure: Install Failed at com.vmware.vise.extensionfw.impl.BundleLifeCycleListenerImpl.collectDeployFailure(BundleLifeCycleListenerImpl.java:156) at com.vmware.vise.extensionfw.impl.BundleLifeCycleListenerImpl.onInstallFailed(BundleLifeCycleListenerImpl.java:76) at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactStateMonitor.onInstallFailed(StandardArtifactStateMonitor.java:132) at org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact.failInstall(AbstractInstallArtifact.java:120) at org.eclipse.virgo.kernel.deployer.core.internal.Plumber$3.operate(Plumber.java:116) at org.eclipse.virgo.kernel.install.pipeline.stage.visit.internal.VisitationStage.doProcessNode(VisitationStage.java:51) at org.eclipse.virgo.kernel.install.pipeline.stage.visit.internal.VisitationStage.doProcessGraph(VisitationStage.java:65) at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41) at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.compensate(CompensatingPipeline.java:93) at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:78) 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.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225) at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79) at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380) at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289) at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49) at java.lang.Thread.run(Thread.java:748) [2020-06-12T14:11:46.672Z] [INFO ] plugin-deploy11               com.vmware.vise.extensionfw.impl.HotDeployBundleDeployer          Deleting bundle file: /usr/lib/vmware-vsphere-ui/server/pickup/com.acme.prodh5-9.7.0.23531.par [2020-06-12T14:11:46.675Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0500E Unable to install application from URI 'file:/usr/lib/vmware-vsphere-ui/server/pickup/com.acme.prodh5-9.7.0.23531.par'. Cannot satisfy constraints for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0'. Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' at version '9.7.0': Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}         A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))"> 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.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225) at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79) at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380) at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289) at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49) at java.lang.Thread.run(Thread.java:748) Service layer manifest file: Manifest-Version: 1.0 Bundle-Vendor: acme Bundle-Version: 9.7.0 Tool: Bundlor 1.1.0.RELEASE Bundle-Name: myhtmlplugin-service Bundle-ManifestVersion: 2 Bundle-SymbolicName: com.acme.myhtmlplugin.myhtmlplugin-service Export-Package: com.acme.myhtmlplugin.mvc;version="1.0.0", com.acme.myhtmlplugin.util;version="1.0.0", com.acme.myhtmlplugin.dashboard.service;version="1.0.0", com.acme.myhtmlplugin.storagesystem.service;version="1.0.0", com.acme.myhtmlplugin.datastore.service;version="1.0.0", com.acme.myhtmlplugin.storage.service;version="1.0.0", com.acme.myhtmlplugin.privileges.service;version="1.0.0", com.acme.myhtmlplugin.reports.service;version="1.0.0", com.acme.myhtmlplugin.home.service;version="1.0.0", com.acme.myhtmlplugin.appliance.service;version="1.0.0", com.acme.myhtmlplugin.vcenter.service;version="1.0.0", com.acme.myhtmlplugin.vvolreports.service;version="1.0.0", com.acme.myhtmlplugin.datastore.service;version="1.0.0", com.acme.myhtmlplugin.privileges.service;version="1.0.0", com.acme.myhtmlplugin.managecapability.service;version="1.0.0", com.acme.myhtmlplugin.vsphereportlet.service;version="1.0.0", com.acme.myhtmlplugin.thresholds.service;version="1.0.0", com.acme.myhtmlplugin.nfsvaai.service;version="1.0.0", com.acme.myhtmlplugin.inventory.service;version="1.0.0", com.acme.myhtmlplugin.vsphereentity.service;version="1.0.0", com.acme.myhtmlplugin.hosts.service;version="1.0.0", com.acme.myhtmlplugin.storagemapping.service;version="1.0.0", com.acme.myhtmlplugin.esxihost.service;version="1.0.0", com.acme.myhtmlplugin.credentials.service;version="1.0.0", com.acme.myhtmlplugin.storagecapabilityprofile.service;version="1.0.0", com.acme.myhtmlplugin.vvoldashboard.service;version="1.0.0" Import-Package: org.apache.commons.logging;version="1.1.1", com.vmware.vise.data;version="0", com.vmware.vise.data.query;version="0", com.vmware.vise.data.uri;version="0", com.vmware.vise.usersession;version="0", com.vmware.vise.security;version="0", com.vmware.vise.vim.data;version="0", com.vmware.vim25;version="6.5.0", com.google.gson;version="2.3.1", javax.servlet.http;version="3.0", javax.net.ssl;version="0", org.springframework.beans.factory.annotation;version="0", org.springframework.http;version="0", org.springframework.stereotype;version="0", org.springframework.web.bind.annotation;version="0", org.springframework.web.client;version="0", org.springframework.util;version="0", org.springframework.web.util;version="0" UI layer Manifest file: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: myhtmlplugin-ui Bundle-SymbolicName: com.acme.myhtmlplugin.myhtmlplugin-ui Bundle-Version: 9.7.0 Bundle-Vendor: acme Web-ContextPath: vsphere-client/myhtmlplugin Import-Package: com.acme.myhtmlplugin.mvc;version="1.0.0", com.acme.myhtmlplugin.storage.service;version="1.0.0", com.acme.myhtmlplugin.storagesystem.service;version="1.0.0", com.acme.myhtmlplugin.util;version="1.0.0", com.acme.myhtmlplugin.dashboard.service;version="1.0.0", com.acme.myhtmlplugin.reports.service;version="1.0.0", com.acme.myhtmlplugin.storagecapabilityprofile.service;version="1.0.0", com.acme.myhtmlplugin.home.service;version="1.0.0", com.acme.myhtmlplugin.appliance.service;version="1.0.0", com.acme.myhtmlplugin.vcenter.service;version="1.0.0", com.acme.myhtmlplugin.datastore.service;version="1.0.0", com.acme.myhtmlplugin.vvolreports.service;version="1.0.0", com.acme.myhtmlplugin.privileges.service;version="1.0.0", com.acme.myhtmlplugin.vsphereportlet.service;version="1.0.0", com.acme.myhtmlplugin.managecapability.service;version="1.0.0", com.acme.myhtmlplugin.nfsvaai.service;version="1.0.0", com.acme.myhtmlplugin.inventory.service;version="1.0.0", com.acme.myhtmlplugin.vsphereentity.service;version="1.0.0", com.acme.myhtmlplugin.esxihost.service;version="1.0.0", com.acme.myhtmlplugin.thresholds.service;version="1.0.0", com.acme.myhtmlplugin.hosts.service;version="1.0.0", com.acme.myhtmlplugin.storagemapping.service;version="1.0.0", com.acme.myhtmlplugin.credentials.service;version="1.0.0", com.acme.myhtmlplugin.vvoldashboard.service;version="1.0.0", com.vmware.vise.data.query;version="0", com.vmware.vise.security;version="0", org.eclipse.virgo.web.dm;version="3.6.0", org.springframework.web.servlet;version="3.1.4", org.springframework.web.servlet.view;version="3.1.4", org.springframework.web.servlet.view.json;version="3.1.4", org.springframework.web.servlet.config;version="3.1.4" Please suggest what is wrong? Is there a know issue with in VC 6.7U1? Thanks, Kumar