After upgrading Intershop project from version 7.10.29.2 to 7.10.38.9-LTS (using Responsive Starter Store 32.2.3) application server can't be started from Intershop Studio any more.
I noticed that the server launch configuration classpath for tools.jar points to the wrong place (${IS_HOME}/engine/jdk/lib/tools.jar instead %JAVA_HOME%/lib/tools.jar) but I was unable to change the classpath permanently - all changes in classpath configuration are ignored without any warning or error after applying them.
Jun 13, 2022 10:16:21 AM org.apache.tomcat.util.scan.StandardJarScanner processURLs
WARNING: Failed to scan [file:/C:/DEV/intershop-ci/sources/projects/webshop/build/server/local/engine/jdk/lib/tools.jar] from classloader hierarchy
java.io.FileNotFoundException: C:\DEV\intershop-ci\sources\projects\webshop\build\server\local\engine\jdk\lib\tools.jar (The system cannot find the path specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:228)
at java.util.zip.ZipFile.(ZipFile.java:157)
It could be related to the selected Version field in the "Server and Developer Home" configuration. You can find that preference dialog in Window->Preferences->Intershop Studio
Related
I am using latest IntelliJ IDEA (2016.1.1) - but I have seen this behaviour in previous versions too - developing in Scala with latest Scala plugin (3.0.3).
When I try to Run/Debug a test or code, IDEA will start Making the project, but will then stay there several seconds while the "Make" progress bar doesn't progress at all.
After 20-30 seconds of this, the following message appear in the Messages tab:
Warning:scala: Cannot connect to compile server at
localhost/127.0.0.1:59656 Trying to compile without it
The port shown there, 59656, is a port I hard-coded myself in %USER_PROFILE%\.IntelliJIdea2016.1\config\options\scala.xml, after I noticed this problem the first time on the default port, so changing the port did not help...
At this point, the bar will read "Reading compilation settings..." for several more tens of seconds before the code actually runs. It is terribly bothering and I can't seem to be able to fix it definitively. This can easily take up to 3 minutes to run a single test. Very disrupting. I noticed this problem happening intermittently on my work machine (Win7).
Anyone has any idea how to debug/fix this issue?
Thanks
I had the same issue.
I'm using IntelliJ 2017.3. Play framework 2.6. Stb 0.13.15.
Solved with adding -server -Xss1m in the scala compile server JVM parameters:
I had the same problem, and it was caused by conflicting settings files between the settings repository and the local preferences. Your compile server settings are store in a file called scala.xml in your IDEA preferences dir.
If you use "settings sync", i.e. an online repository to sync your IDEA settings, make sure that you have only one scala.xml config file. Go to your Library/Preferences/<IDEA-Dir>/ and remove that file from the options and settingsRepository dirs. This resets to "factory settings".
Restart IntelliJ, setup the compile server again. It should now only write one file, to the settingsRepository dir, with a new ID and port allocation for the compile server.
This fixed it for me.
I don't fully understand this yet, however under Preferences, Languages & Frameworks > Scalac Server there are some settings that might help:
Shutdown server if it is idle for <number> minutes.
Use project home as compiler server working directory (Compile server will be restarted on each compilation of a new project)
JVM SDK is used to instantiate compile server ... (when JVM SDK and module SDK match).
There is a small icon in the bottom right of the IntelliJ window that indicates whether the compile server is running and can be used to stop and start it.
The server will shutdown if it is idle. It should normally start up when needed but this might not happen if the JVM SDK does not match the module SDK. Increasing the idle timeout should help to reduce the frequency of the problem. Matching the JVM SDK to the Module SDK ought to fix the problem, but might not be possible if you have multiple projects using different SDKs.
Using the project home as the compiler server working directory might help if you frequently switch between projects.
Edit
I have this problem again with IntelliJ IDEA Ultimate 2016.3.2 but the usual method of a clean shutdown and reboot hasn't worked. I've pieced together some information on how the compile server works and it seems to me that IntelliJ is looking on the wrong port for the compile server. If I manually force a make then I can see a compile server running, but it isn't the one that IntelliJ is looking for. I still don't have a solution, but this information might get us closer to one.
Finding Files
The first step is working out where IntelliJ stores its configuration and log files. This information is currently published here: IntelliJ Directories
On my Mac this means:
configuration files: ~/Library/Preferences/IntelliJIdea2016.3/options
log files: ~/Library/Logs/IntelliJIdea2016.3
The Compile Server
The compile server is a Java process with a very long command line that ends like this:
org.jetbrains.jps.cmdline.BuildMain <host> <port> <compile-server-id> <compile-server-cache-directory>
The configuration options are stored in ~/Library/Preferences/IntelliJIdea2016.3/options/scala.xml
Some of these are configured in the Preferences -> Languages & Frameworks -> Scala Compiler Server dialog, but other settings can be added by editing the file. Mine currently looks like this:
<application>
<component name="ScalaSettings">
<option name="COMPILE_SERVER_PORT" value="59184" />
<option name="COMPILE_SERVER_ID" value="93f4589e-4707-4e20-a05a-01869045e067" />
<option name="COMPILE_SERVER_SDK" value="1.8" />
<option name="COMPILE_SERVER_MAXIMUM_HEAP_SIZE" value="2048" />
</component>
</application>
I added the COMPILER_SERVER_PORT option by hand, but with this version of IntelliJ the compile server that it uses for single compilations has a different port and id. Unfortunately this process uses a different port if I change COMPILER_SERVER_PORT and restart IntelliJ so I think these are two separate instances.
I used this command to find the compile server process, after manually starting a compile:
ps -ef | grep nailgun
This command finds the ports used by IntelliJ:
lsof -i | grep idea
There is also a log file here:
~/Library/Logs/IntelliJIdea2016.3/idea.log
that indicates that something is not quite right:
2016-12-28 10:19:46,745 [ 50710] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: Build process started. Classpath: /Users/richard/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/163.10154.41/IntelliJ IDEA.app/Contents/lib/jps-launcher.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/lib/tools.jar:/Users/richard/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/163.10154.41/IntelliJ IDEA.app/Contents/lib/optimizedFileManager.jar
2016-12-28 10:59:43,958 [2447923] INFO - ij.compiler.impl.CompileDriver - COMPILATION STARTED (BUILD PROCESS)
2016-12-28 10:59:43,960 [2447925] INFO - j.compiler.server.BuildManager - Using preloaded build process to compile /Users/richard/workspace-scala
2016-12-28 10:59:44,181 [2448146] ERROR - .impl.MessageBusConnectionImpl - java.lang.NullPointerException
java.lang.RuntimeException: java.lang.NullPointerException
at com.intellij.openapi.application.impl.LaterInvocator.invokeAndWait(LaterInvocator.java:189)
at com.intellij.openapi.application.impl.ApplicationImpl.invokeAndWait(ApplicationImpl.java:662)
at com.intellij.openapi.application.impl.ApplicationImpl.invokeAndWait(ApplicationImpl.java:667)
at org.jetbrains.plugins.scala.extensions.package$$anonfun$invokeAndWait$1.apply$mcV$sp(package.scala:567)
at org.jetbrains.plugins.scala.extensions.package$.preservingControlFlow(package.scala:577)
at org.jetbrains.plugins.scala.extensions.package$.invokeAndWait(package.scala:566)
at org.jetbrains.plugins.scala.compiler.ServerMediator$$anon$1.buildStarted(ServerMediator.scala:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.util.messages.impl.MessageBusConnectionImpl.deliverMessage(MessageBusConnectionImpl.java:117)
at com.intellij.util.messages.impl.MessageBusImpl.doPumpMessages(MessageBusImpl.java:381)
at com.intellij.util.messages.impl.MessageBusImpl.pumpMessages(MessageBusImpl.java:368)
at com.intellij.util.messages.impl.MessageBusImpl.sendMessage(MessageBusImpl.java:347)
at com.intellij.util.messages.impl.MessageBusImpl.access$200(MessageBusImpl.java:42)
at com.intellij.util.messages.impl.MessageBusImpl$2.invoke(MessageBusImpl.java:230)
at com.sun.proxy.$Proxy117.buildStarted(Unknown Source)
at com.intellij.compiler.server.BuildManager$NotifyingMessageHandler.buildStarted(BuildManager.java:1435)
at com.intellij.compiler.server.DelegatingMessageHandler.buildStarted(DelegatingMessageHandler.java:18)
at com.intellij.compiler.server.DelegatingMessageHandler.buildStarted(DelegatingMessageHandler.java:18)
at com.intellij.compiler.server.BuildMessageDispatcher.sendBuildParameters(BuildMessageDispatcher.java:115)
at com.intellij.compiler.server.BuildManager.a(BuildManager.java:724)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.intellij.util.concurrency.BoundedTaskExecutor$2.run(BoundedTaskExecutor.java:210)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at org.jetbrains.plugins.scala.compiler.CompileServerLauncher$$anonfun$15.apply(CompileServerLauncher.scala:282)
at org.jetbrains.plugins.scala.compiler.CompileServerLauncher$$anonfun$15.apply(CompileServerLauncher.scala:282)
at scala.collection.TraversableLike$$anonfun$filterImpl$1.apply(TraversableLike.scala:259)
at scala.collection.immutable.Set$Set3.foreach(Set.scala:145)
at scala.collection.TraversableLike$class.filterImpl(TraversableLike.scala:258)
at scala.collection.TraversableLike$class.filter(TraversableLike.scala:270)
at scala.collection.AbstractTraversable.filter(Traversable.scala:104)
at org.jetbrains.plugins.scala.compiler.CompileServerLauncher$.org$jetbrains$plugins$scala$compiler$CompileServerLauncher$$jdkChangeRequired(CompileServerLauncher.scala:282)
at org.jetbrains.plugins.scala.compiler.CompileServerLauncher.start(CompileServerLauncher.scala:56)
at org.jetbrains.plugins.scala.compiler.CompileServerLauncher.tryToStart(CompileServerLauncher.scala:41)
at org.jetbrains.plugins.scala.compiler.ServerMediator$$anon$1$$anonfun$buildStarted$2.apply$mcV$sp(ServerMediator.scala:43)
at org.jetbrains.plugins.scala.extensions.package$$anonfun$invokeAndWait$1$$anon$16.run(package.scala:569)
at com.intellij.openapi.application.TransactionGuardImpl$6.run(TransactionGuardImpl.java:318)
at com.intellij.openapi.application.impl.LaterInvocator$1.run(LaterInvocator.java:166)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.a(LaterInvocator.java:417)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:401)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:843)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:679)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:391)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - IntelliJ IDEA 2016.3.2 Build #IU-163.10154.41
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - JDK: 1.8.0_112-release
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - VM: OpenJDK 64-Bit Server VM
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - Vendor: JetBrains s.r.o
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - OS: Mac OS X
2016-12-28 10:59:44,183 [2448148] ERROR - .impl.MessageBusConnectionImpl - Last Action: CompileDirty
2016-12-28 10:59:48,828 [2452793] INFO - lij.compiler.impl.CompilerUtil - COMPILATION FINISHED (BUILD PROCESS); Errors: 0; warnings: 1 took 4878 ms: 0 min 4sec
CompileServerLauncher.scala indicates that this is something to do with not being able to find a JDK 8 to use, although if it can't find one it looks like it should fail with an error message, not a NullPointerException.
I still got this issue with IntelliJ 2021.2.2 Community Edition and simple restart of IntelliJ IDE resolved it.
I faced the same issue when using IntelliJ 2022.3.1.
I noticed that the compiler server working directory seems to change when switching between projects, so it is good to set the project home as the compiler server's default working directory.
Go to:
File -> Settings -> Build,Execution,Deployment -> Compiler -> ScalaCompiler -> ScalaCompileServer,
then check the box "Start process in project directory"
Also, do ensure that -server -Xss1m is included in the JVM VM options:
I have the following environment:
Windows 7 64-bit OS;
Eclipse Kepler SR2 32-bit + JDK 1.7 32-bit;
MobileFirst Platform Studio 6.3 20150106-1717
When I opened my eclipse I clicked on the green play button to start the development server, I got the following errors; or if I create a simple project and attempt to deploy it on the dev server, same errors come out; or if I delete the server and create a new one and then try to start it; or if I install 64-bit eclipse with 64-bit Java 7:
com.ibm.ws.kernel.boot.LaunchException: Caught unexpected exception java.lang.IllegalArgumentException: URI has an authority component
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.rethrowException(KernelBootstrap.java:418)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:183)
at com.ibm.ws.kernel.boot.Launcher.createPlatform(Launcher.java:131)
at com.ibm.ws.kernel.boot.Launcher.main(Launcher.java:55)
at com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:52)
Caused by: java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.<init>(Unknown Source)
at com.ibm.ws.kernel.boot.cmdline.Utils.getInstallDir(Utils.java:38)
at com.ibm.ws.kernel.productinfo.ProductInfo.getAllProductInfo(ProductInfo.java:53)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.getProductInfoDisplayName(KernelBootstrap.java:395)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:119)
... 3 more
Listening for transport dt_socket at address: 10777
CWWKE0005E: The runtime environment could not be launched.
CWWKE0018E: An exception occurred while launching the runtime environment: java.lang.IllegalArgumentException: URI has an authority component
I tried everything but no luck, so please diagnose this issue, thanks.
This is unrelated to MobileFirst Platform, and may be instead related to the problem described in the following IBM tech note: http://www-01.ibm.com/support/docview.wss?uid=swg21584343
It is unclear from the question and comments if the workspace is in a different network drive than the Eclipse folder. If yes, consider placing both in the the same "physical location".
I did realize my system location was out of sync thus I did open the jvm.options file and copy pasted the below configuration
-Dibm.worklight.admin.db.type=DERBY
-Dfile.encoding=UTF-8
-Duser.language=en
-Duser.country=US
-Djava.awt.headless=true
-Dwas.debug.mode=true
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=10777
-Dcom.ibm.websphere.ras.inject.at.transform=true
-Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=180000
-Dibm.worklight.admin.db.type=DERBY
-Xmx1024m
-Dos.name=Windows
-DwlSyncStart=false
-Dibm.worklight.rhino.debug=transport=socket,address=9000
Which worked in my case , all the best.
i had a problem running Internationalization code (GWT teck. on Eclipse) and had the following console result
Jul 16, 2014 9:45:11 AM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
[WARN] Server class 'org.eclipse.jetty.servlet.listener.ELContextCleaner' could not be found in the web app, but was found on the system classpath
[WARN] Adding classpath entry 'file:/C:/Dev/eclipse-standard-kepler-SR2-win32-x86_64/eclipse/plugins/com.google.gwt.eclipse.sdkbundle_2.6.0/gwt-2.6.0/gwt-dev.jar' to the web app classpath for this session
Searching online found out something about creating new key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Prefs
if So then how to create this KEY??
and what exactly causes this problem??
These are WARN lines, so they shouldn't cause any compilation or runtime problem and your project should eventually compile and run.
It seems some code in your server wants to store something using the java.util.prefs api and it is failing because your preferences repository has some problems (maybe permissions, or it is full, etc) or the class using it is storing something wrong.
The GWT compiler, stores some info in your java preferences as well, but it does it in compile time, so if it failed you should see a different line, see CheckForUpdates class.
Other WARN lines in your logs are normal in dev-mode.
i try to set up super simple exteranl tooling in eclispe , that is javah
what ever i do , that means trying all the links in the web still can set it right .
and when i close the external tool config it gives me error
i tried with and without the -jni still gives me the error:
Exception in thread "main" java.lang.IllegalArgumentException: Not a valid class name: –d
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:177)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:68)
at com.sun.tools.javah.JavahTask.run(JavahTask.java:509)
at com.sun.tools.javah.JavahTask.run(JavahTask.java:335)
at com.sun.tools.javah.Main.main(Main.java:46)
try setting up an ant task - see link
http://ant.apache.org/manual/Tasks/javah.html
I just tried to use Gears in my GWT application and got following error:
Jul 12, 2009 6:26:29 AM com.google.apphosting.utils.jetty.JettyLogger info
INFO: jetty-6.1.x
Jul 12, 2009 6:26:29 AM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed com.google.apphosting.utils.jetty.DevAppEngineWebAppContext#c45809{/,/Users/work/workspace/Athena/war}
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:113)
at org.mortbay.xml.XmlParser.<init>(XmlParser.java:69)
at org.mortbay.jetty.webapp.WebXmlConfiguration.webXmlParser(WebXmlConfiguration.java:83)
at org.mortbay.jetty.webapp.WebXmlConfiguration.<init>(WebXmlConfiguration.java:78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.mortbay.jetty.webapp.WebAppContext.loadConfigurations(WebAppContext.java:838)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:417)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:217)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:147)
at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:116)
at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:211)
at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:86)
at com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:365)
at com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:590)
at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:397)
at com.google.gwt.dev.HostedMode.main(HostedMode.java:232)
I know this error is because I'm using (1) OS X, (2) Eclipse with Google Plugin, (3) JRE 1.5. But I have no choice because Hosted Mode plugin requires JRE 1.5 and when I switch to JRE 1.6 Hosted mode complains. I also tried to set JRE 1.6 just to the project, still Plugin does not like it.
This problem occurs only when I'm including
<inherits name='com.google.gwt.gears.Gears'/>
into my gwt.xml file.
There is one guy who has same problem, he solved it by just switching JRE's but I'm using Mac and I assume there is different story with Mac. Is there any solutions to this problem in my case?
Which version of gwt-gears.jar are you using? Make sure you are
running the latest gwt-gears release (1.2.1) and try
gwt-gears-noredist.jar if you are using the Google Plugin.