I am trying to to debug why I get the error
System.IndexOutOfRangeException: Index was outside the bounds of the array Exception with TestPlansAndSuitesMigrationContext
I have downloaded the latest version of the code and the tool is also up to date. I have made sure the config files have an updated 'Version' hardcoded to and that the debugger points to them.
However, during debug, I get the below suggesting that the version I am running is 0.0
[11:36:41 INF] Running with args: execute
[11:36:41 INF] OSVersion: Microsoft Windows NT 6.2.9200.0
[11:36:41 INF] Version: 0.0.0.1
[11:36:41 INF] Latest version detected as 11.9.33.0
[11:36:41 WRN] You are currently running version 0.0.0.1 and a newer version (11.9.33.0) is available. You should upgrade now using Chocolatey command 'choco upgrade vsts-sync-migrator' from the command line.
[11:36:41 DBG] Hosting starting
[11:36:42 INF] Application started. Press Ctrl+C to shut down.
[11:36:42 INF] Hosting environment: Production
[11:36:42 INF] Content root path: C:\Users\davidkin\source\repos\azure-devops-migration-tools-master\src\MigrationTools.ConsoleFull\bin\Debug\net472
[11:36:42 INF] Press Ctrl+C to shut down.
[11:36:42 DBG] Hosting started
[11:36:42 INF] Config Found, creating engine host
[11:36:42 ERR] The config version 11.9 does not match the current app version 0.0. There may be compatibility issues and we recommend that you generate a new default config and then transfer the settings across.
Can anyone suggest how to fix please?
This is the version set within Visual Studio. If you were to download the packaged tool, it would match version 11.9.
Update your version within your configuration.json to 0.0:
"Version": "0.0",
Related
This has been happening ever since I have updated Intellij (IDEA CE 2020.3) to a newer version (today). I am getting this exception from the plugin when running the Develop on Kubernetes Run Configuration that I usually use with my local Minikube instance to get all of the services in the cluster up and running, and able to Debug in debug mode.
My local Minikube instance is fine shown by the following:
(Dev) $ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
I've tried checking for updates, restarting Intellij, and I am still getting the same thing. It must be something in relation to my Intellij Update but we'll have to see...
The full stack trace is:
java.util.ServiceConfigurationError: io.grpc.ManagedChannelProvider: io.grpc.netty.shaded.io.grpc.netty.NettyChannelProvider not a subtype
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1236)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1264)
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1299)
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1384)
at io.grpc.ServiceProviders.loadAll(ServiceProviders.java:67)
at io.grpc.ServiceProviders.load(ServiceProviders.java:42)
at io.grpc.ManagedChannelProvider.<clinit>(ManagedChannelProvider.java:37)
at io.grpc.ManagedChannelBuilder.forAddress(ManagedChannelBuilder.java:37)
at com.google.cloud.tools.intellij.kubernetes.skaffold.events.SkaffoldEventHandler.newManagedChannel(SkaffoldEventHandler.kt:319)
at com.google.cloud.tools.intellij.kubernetes.skaffold.events.SkaffoldEventHandler.listenEvents(SkaffoldEventHandler.kt:75)
at com.google.cloud.tools.intellij.kubernetes.skaffold.run.SkaffoldCommandLineState$startProcess$1.invokeSuspend(SkaffoldCommandLineState.kt:189)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:740)
I am getting the same behaviour in both DEBUG mode and RUN mode.
Environment Info
IDE type: IntelliJ
IDE version: Community Edition 2020.3
Cloud Code version: 20.10.1-202
Skaffold version: v1.14.0
Operating System: Windows 10 Pro 64-bit
Any help, suggestions or resolutions would be really appreciated so thank you in advance! Thanks
This issue was fixed with patch release 20.12.1 that was put out shortly after the EAP release. Please try it out and if you run into any other issues feel free to post on our GitHub. – eshaul
I am new to use Mulesoft and thus I have started learning it by following the steps in "https://docs.mulesoft.com/mule-user-guide/v/3.7/build-a-hello-world-application".
However, when I try to run the project by selecting "Run As > Mule Application", It gives me this error messages:
Launching a JVM...
JVM exited while loading the application.
Automatic JVM Restarts disabled. Shutting down.
backend pipe closed.
backend pipe closed.
<-- Wrapper Stopped
Note that: I am using Windows 7 (64 bit), Mulesoft 7.1 (64 bit), jdk1.8.0_171 (64 bit) and I have added java home into system variable as instructed in this post "https://forums.mulesoft.com/questions/90429/unable-to-install-mule-4-anypoint-studio-71.html"
Any suggestion, please !!!
See image and check your Run configuration I have post image under bellow url...
I have created a Windows Server 2016 VM, build 15063.2.
I installed Docker EE according to these instructions.
I can pull images and list them. But I cannot run them.
I tried running microsoft/windowsservercore using this command.
docker run -it microsoft/windowsservercore cmd
It fails saying the version of the OS doesn't match. Full error output is below.
docker: Error response from daemon: container
266a8f9f77f7ee57efb41ecd74001721b57fbbf1fc85150fd5156627782b6f61
encountered an error during CreateContainer: failure in a Windows
system call: The operating system of the container does not match the
operating system of the host. (0xc0370101) extra info:
{"SystemType":"Container","Name":"266a8f9f77f7ee57efb41ecd74001721b57fbbf1fc85150fd5156627782b6f61","Owner":"docker","IsDummy":false,"VolumePath":"\\?\Volume{8adf7e25-dc21-4bb9-8aaf-80408b5d5085}","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\ProgramData\docker\windowsfilter\266a8f9f77f7ee57efb41ecd74001721b57fbbf1fc85150fd5156627782b6f61","Layers":[{"ID":"9ca74b81-1d43-5ae3-b82e-4c584e5ebba7","Path":"C:\ProgramData\docker\windowsfilter\1e0c3f8d0cd7905b72efc4b4114c33b4585623e82a3d661636c68a5637a213d2"},{"ID":"86613523-d1d5-5b5b-8889-fc0c33a7d7ab","Path":"C:\ProgramData\docker\windowsfilter\31578f2c995a3891bb3af19de88efff45dbec9f9bdc6067c133abcf05a451171"}],"HostName":"266a8f9f77f7","MappedDirectories":[],"HvPartition":false,"EndpointList":["43f9f400-ce4f-48e9-89a1-b3b804285e61"],"Servicing":false,"AllowUnqualifiedDNSQuery":true}.
How do I figure the correct version of the host OS to use?
I have installed the Weblogic 12c (12.1.3) on my Windows 7 machine. After creating the Admin server and logging in, I am trying to create a new Managed Server. But when I press the create button, it takes a lot of time showing the loading symbol and finally gives the error Timed out waiting for completion: Activate State: STATE_DISTRIBUTED Target Servers States: AdminServer STATE_DISTRIBUTED.
Earlier I was working on weblogic 10.3.2 and it was working fine, but after this installation it gives me the error and I am unable to create a new Managed Server.
My JAVA_HOME is pointing to JDK 1.8 currently. Also there is this entry in the PATH variable which is something like 'C:\ProgramData\Oracle\java\javapath' which has 3 SYMLINKS to java.exe, javaw.exe and javaws.exe to my JRE 1.8 instead of the JDK 1.8. I uninstalled the JRE and just kept the JDK for the time being but still did not work.
Please advice.
Was able to find the solution for it. Pointed my JAVA_HOME back to JDK 1.7 and at the same time changed the port of NodeManager from the default 5556 to 5557 and was able to successfully create and link the Machine and the Managed Server.
I am getting following error when I try to start the server in Eclipse
Launching WorkLight_new (WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639) on Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_05-b13 (en_US)
[AUDIT ] CWWKE0001I: The server WorkLight_new has been launched.
[AUDIT ] CWWKE0055I: Server shutdown requested on Monday, September 29, 2014 at 5:49 PM. The server WorkLight_new is shutting down.
[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.
[AUDIT ] CWWKF0011I: The server WorkLight_new is ready to run a smarter planet.
[AUDIT ] CWWKE0036I: The server WorkLight_new stopped after 1 minutes, 0.818 seconds.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Dev environment:-
Windows 7 Pro x64
Eclipse J2ee Juno SR2 x64
JDK 1.8.0_05 x64
Worklight Server 6.2(online install)
Any help will be greatly appreciated.
----Update----
I have uploaded the server startup logs in 2 parts on pastebin. Below are the URLs
Part 1 - http://pastebin.com/601dDV0b
Part 2 - http://pastebin.com/aY5t398D
I Hope this helps
Why does it say "WorkLight_new"? This name suggests to me that you have created a 'new' server to work with instead of the default-provided Worklight Development Server, but you do not provide any details on what you've done while creating it.
My suggestion to you is to first test with the default configuration. Easiest is to simply start Eclipse with a new workspace and start the default server instead. Otherwise, you need to provide something more substantial than what you provided in the question.
Additionally,
This may also happen due to using Java 1.8 (see IBM Worklight 6.1 - Error TRAS0033E).
Downgrade to either 1.6 or 1.7 and make sure to setup Eclipse to use the JRE of 1.6 or 1.7.
On command prompt check java -version. Ensure that is 1.6 or 1.7
Open Eclipse > Window > Preferences > Java > Installed JREs. Ensure that is JDK 1.6 or 1.7