We Keep Coding

The Tomcat installation directory is not valid. It is missing expected file or folder tcruntime-ctl.sh

Even after searching too much i couldn't find any suitable answer for my problem.
I am using Spring Tool Suite and trying to create a new server but getting error as The specified server is not valid. The .tc-runtime-instance file is missing.
So, I tried updating pivotal using Windows> Preferences and tried editing pivotal with new release but got the error as attached:
I tried changing tomcat version from 9 to 7 too but still no success. Please help.

It looks like you are trying to use the server adapter for the "Pivotal tc Server" to configure your server in the IDE. This server adapter is for the Pivotal tc Server only and doesn't work with a plain Tomcat installation on your disc. For that, you should select the "Apache Tomcat" server adapter when creating a server instance in your IDE.

how to install jautodoc in eclipse mars version

Hi i am trying to install jautodoc in my mars version but i got following error please help me
HTTP Server 'Service Unavailable': http://jautodoc.sourceforge.net/update/content.xml
HttpComponents connection error response code 503.

In your eclipse you can get it from help -->Eclipse MarketPlace --> search for jAutodoc this is one way.. If it is not supporting in your eclipse
2nd way is copy from your old eclipse pluggins
go to your eclipse pluggins location ........
C:\Program Files\eclipse\plugins and copy the net.sf.jautodoc.velocity_1.12 jar
net.sf.jautodoc_1.12.jar (if u have in your previous eclipse)

HTTP Error 503 - Service unavailable
The Web server (running the Web site) is currently unable to handle
the HTTP request due to a temporary overloading or maintenance of the
server
Please check attached screen shot SourceForge is under maintenance mode

500 server error with servlet after deploy it on app engine

please take a look to my problem below i deployed my website (java) on my app engine account the url it work to show html and jsp pages but the servlet pages it make error rather than show it correctly this is what appear:
Error: Server Error The server encountered an error and could
not complete your request. If the problem persists, please report your
problem and mention this error message and the query that caused it.
notice :: that all work on localhost server but on app engine !! what can i
do to avoid this problem !!!!

web/ASS2webServlet : Unsupported major.minor version 51.0, java.lang.UnsupportedClassVersionError
Indicates that you are using a higher version of Java than GAE supports. Quoting from documentation of GAE:
"App Engine runs Java applications using the Java 6 virtual machine (JVM). The App Engine SDK supports Java 5 and later, and the Java 6 JVM can use classes compiled with any version of the Java compiler up to Java 6"
So can you check what version are you using on local Eclipse to compile your classes?

Java EE "JDI Event Dispatch" error

When I try to debug any project in Java EE INDIGO (64 bit) in win 7 and place a breakpoint somewhere the program acts as expected but when I hit f6 or f5 to go further eclipse throws an error which reads (I have Spring installed):
An internal error occurred during: "JDI Event Dispatch".
com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
(No typo, "Z" does appear)
Now I can't debug any program because it always gives this error. Can anyone help?
From the eclipse error log:
!MESSAGE com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
!STACK 0
java.lang.AbstractMethodError: com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
at org.eclipse.contribution.jdt.debug.DebugHooksAspect.isInterestingLaunch(DebugHooksAspect.aj:253)
at org.eclipse.contribution.jdt.debug.DebugHooksAspect.ajc$inlineAccessMethod$org_eclipse_contribution_jdt_debug_DebugHooksAspect$org_eclipse_contribution_jdt_debug_DebugHooksAspect$isInterestingLaunch(DebugHooksAspect.aj:1)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.getStepFilters_aroundBody1$advice(JDIDebugTarget.java:195)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.getStepFilters(JDIDebugTarget.java:1)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.attachFiltersToStepRequest(JDIThread.java:2154)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.createStepRequest(JDIThread.java:2065)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.createStepRequest(JDIThread.java:2040)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.step(JDIThread.java:1989)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.stepOver(JDIThread.java:1412)
at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.stepOver(JDIStackFrame.java:418)
at org.eclipse.debug.internal.core.commands.StepOverCommand.step(StepOverCommand.java:27)
at org.eclipse.debug.internal.core.commands.StepCommand.doExecute(StepCommand.java:34)
at org.eclipse.debug.core.commands.AbstractDebugCommand$1.run(AbstractDebugCommand.java:213)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

This seems to be a similar bug to this bug in codehaus jira (see comments section). I was able to switch back to an older eclipse installation (from two weeks ago) to get rid of the current problem and will upgrade to Eclipse 3.7 as soon as time permits.

As crazy as this sounds, I too was getting this error when debugging an Android App and trying to step into a specific method, and resolved it by renaming the method I was trying to step into.
I had tried:
completely reinstalling the app
cleaning in Eclipse
reboot of device (phone), OS, and restart of Eclipse
increasing debug timeouts in Preferences | Java | Debug
My method was called "getMessageInfoFromDb"... and was in a class that didn't extend anything, but implemented Serializable ;-)

Try disabling simple step filtering, especially filtering of simple getters.

delete the Temp folder from yourlocalpath\domainfolder\server\AdminServer
domains\base_domain\servers\AdminServer

Have you done any DB import twice or more time on the same DB that you use for the application in which you are running in debug mode. Because I am also getting similar error with the caption JDI while starting Application Server with deployed .ear in Eclipse based IDE as a popup.
When db is imported twice user created tables gets imported if it's been tried in the same kind of databases. But Oracle App & System Specific tables throws error in process of importing. And some crash in that....
I hope this is what scenario yours as well....
In my scenario I had imported Oracle db from UNIX environment to Oracle XE in Windows environment.

ICEFaces 1.7.2 and Websphere Application Server 7

We recently migrated from WAS6 to WAS7. One of our application, which was working perfectly fine in WAS6 is not working in WAS7 with following error.
java.lang.NoSuchMethodError: com/sun/faces/util/Util.verifyFactoriesAndInitDefaultRenderKit(Ljavax/servlet/ServletContext;)V
at com.ibm.faces.context.MultipartFacesContextFactoryImpl.getFacesContext(MultipartFacesContextFactoryImpl.java:73)
The piece of code, which is giving that error is
FacesContextFactory contextFactory = (FacesContextFactory)
FactoryFinder.getFactory(FactoryFinder.FACES_CONTEXT_FACTORY);
facesContext = contextFactory.getFacesContext(
request.getSession().getServletContext(), request, response, lifecycle);
Found these info while debugging the app in WAS6 vs WAS7
contextfactory: com.ibm.faces.context.MultipartFacesContextFactoryImpl - JSF-IBM.jar - WAS7
contextfactory: com.icesoft.faces.context.FacesContextFactoryImpl - icefaces.jar - WAS6
I tried some suggestions like creating a Shared Lib and associating that to the EAR and changing the class loader schemes from "Parent Last" to "Parent First".
But no matter what I do, In WAS7 I am getting MultipartFacesContextFactoryImpl as the value of contextFactory.
I tried to replace 1.7.2 with 1.8 version of icefaces.jar and icefaces-comps.jar. But still the same result.
Please help. Please let me know if you need more details.

It could be that WAS6 used Java 5 as native and WAS7 uses Java 6. Try recompiling your classes with Java 6.