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
Related
the version of JDeveloper I am using is 12.2.1.4.0 and the JDK version I am using for the application is Java 1.8.0.202.
The issue I am currently having is whenever I am trying to run an application within JDeveloper I am getting this error code:
*** Using HTTP port 7101 ***
*** Using SSL port 7102 ***
C:\Users\Nathan\AppData\Roaming\JDeveloper\system12.2.1.4.42.190911.2248\DefaultDomain\bin\startWebLogic.cmd
[Starting IntegratedWebLogicServer.]
[waiting for the server to complete its initialization...]
Files was unexpected at this time.
Process exited.
[IntegratedWebLogicServer terminated.]
Could someone please explain how I may resolve this?
Thank you.
One thing to try is to use JDK 1.8.0_101 as this older version is proven to work with JDev 12.2.1.4.
If you have access to support you should download the latest bundle patch for 12.2.1.4 and then use the current JDK 1.8.0_2xx.
Facing Some issues while installing tasktop pro in my eclipse, giving the following error:
HTTP Server Unknown HTTP Response Code
(301):http://tasktop.com/downloads/discovery/update/content.xml
General connection error with response code=301
Can Someone help me with issue ?
thanks,
AJ
Error Screenshot
It looks like you had some connection issues with the update site. Or your Eclipse version can't handle a HTTP 301. Did you tried it again?
Otherwise try to install it via "Install New Software"
I tried to install it myself, it works without any problems. I created an Eclipse Profile for you. If you install it, it contains the Tasktop Dev Pro Plugin.
i am getting Could not publish to the server.
java.lang.NullPointerException when i try to run my Jboss7.1 server on my machine.
any idea about that??
in server properties i just clicked on Switch Location and now its running fine .
#Piyush Mittal - I installed another Eclipse (newer edition) with new server and pointed it to use the old workspace. When one of projects is open - it causes the same problem with new server in new location. It seems that the issue must have something to do with workspace/project settings. I got rid of the project and problem.
I have Eclipse Kepler running on my computer. After I installed IBM Websphere 8.5 plug-in from the marketplace and restarted my Kepler, I'm not able to re-open the marketplace.
A progress bar is being displayed that says "Retrieving data from http://marketplace.eclipse.org" for 30 minutes plus.
When I uninstall the plug-in, the marketplace works fine.
Why is this happening? Can anyone help me out in figuring?
Appreciate your help.
PS : there is no issue while accessing the link from a browser.
Thanks,
Madhu.
UPDATE
The below error is logged when clicking on "Install new software"
exception
!STACK 1
org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.eclipse.org/webtools/repository/kepler/compositeContent.xml.
at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:192)
at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.getLocalFile(CompositeMetadataRepositoryFactory.java:73)
at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:98)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.IllegalStateException: Failure initializing default SSL context
at org.apache.http.conn.ssl.SSLSocketFactory.createDefaultSSLContext(SSLSocketFactory.java:211)
at org.apache.http.conn.ssl.SSLSocketFactory.<init>(SSLSocketFactory.java:333)
at org.apache.http.conn.ssl.SSLSocketFactory.getSocketFactory(SSLSocketFactory.java:165)
at org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:45)
at org.apache.http.impl.client.AbstractHttpClient.createClientConnectionManager(AbstractHttpClient.java:294)
at org.apache.http.impl.client.AbstractHttpClient.getConnectionManager(AbstractHttpClient.java:445)
at org.apache.http.impl.client.AbstractHttpClient.createHttpContext(AbstractHttpClient.java:274)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:797)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
... 1 more
Caused by: java.security.KeyStoreException: problem accessing trust storejava.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.ssl.TrustManagerFactoryImpl.engineInit(Unknown Source)
at javax.net.ssl.TrustManagerFactory.init(Unknown Source)
at org.apache.http.conn.ssl.SSLSocketFactory.createSSLContext(SSLSocketFactory.java:190)
at org.apache.http.conn.ssl.SSLSocketFactory.createDefaultSSLContext(SSLSocketFactory.java:209)
... 11 more
UPDATE
I just found out the reason. While creating a WAS 8.5 server in eclipse, there is an option called "security is enabled on this server" which we usually check for a secure mode. This hampers with eclipse's marketplace connection settings and thus preventing it from functioning. The only thing I don't understand is how both of these are related and how to overcome the problem.
Hope someone out there can explain :)
I ran into this too. I was trying to install the WAS v8.5 development tools in a workspace that already has WAS 7.0 server setup. The same error was observed in the log. Trying to uncheck the "security is enabled on this server" option did not work for me. (Eclipse Marketplace would be stuck on lunch.)
So I created a new workspace and Eclipse Marketplace can be launched again. If I then set up a WAS 7.0 Server in this workspace, the same issue occurs. Removed WAS 7.0 server definition, restarted Eclipse and Eclipse Marketplace launches successfully again.
So the workaround is just to create a new workspace and use Eclipse Marketplace and also to perform your updates + installs for Eclipse. Just don't add any WAS server to that new workspace. In fact, just use that new workspace just to launch Marketplace and do install/update. Simple as that.
I am attempting to create/deploy an application onto the Redhat OpenShift Express platform, and am attempting to do this via eclipse using the JBoss OpenShift plugins.
I am following the instructions here: https://www.redhat.com/openshift/community/blogs/getting-started-with-the-openshift-eclipse-plug-in-for-java-applications-on-the-cloud
But when entering my user credentials I get an error preventing me getting any further:
Could not check user credentials: Could not unmarshall response "
{"data":
{"user_info":
{"env_vars":null,
"max_gears":5,
"system_ssh_keys":null,
"uuid":"5a81de3405fe4ac6b5718dbb8540736f",
"rhc_domain":"rhcloud.com",
"rhlogin":"robert.hinds#accenture.com",
"ssh_keys":
{"laptop":{"type":"ssh-rsa","key":"AAAAB3NzaC1yc2EAAAABIwAAAQEAw5GIjtI+B42SBv2kmV32OHI5tCBO7JWmlhF7w9dNy2Tp7MNtK8nE7nLUKYyXSZRzK0i4azPuMDDmmJ4jFpcyAwRdzBM43xZLo/6MlMFneT3t66ukNMNOgYptiRH7Zy8Tmjquwu2dXpui77tRQaEpq4Ms/JxHvanD+YMDNTXlrv8gIDwOjhtetuyeKbf/sr+UK1Bit8eDTgai01UmjXm+u/0Hi1tD6oG/GwNviQKb/2gmrmEs0uPhcJ9Olzrn67Gyu7c2PFOjTEvOXMQHjSUrVp905t8SzffiJ7uWzVnvufrweC5gXlR/v1tp3FrFgRcZVmZX6QlhyOiy5Tr1cLD8pw=="}},
"consumed_gears":0,
"vip":false,
"namespace":"star",
"ssh_key":null,
"ssh_type":null
},
"app_info":{}
},
"api_c":["placeholder"],
"messages":"",
"broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],
"exit_code":0,
"debug":"",
"api":"1.1.3",
"result":""
}
has anyone come across this previously? I am on Win7 Eclipse Indigo on JDK7
Update:
I get this problem using the following versions/steps
Using Eclipse: Eclipse Java EE IDE for Web Developers. Version: Indigo Service Release 2 Build id: 20120216-1857
Installed the OpenShift express tools from the JBoss software update site here: http://download.jboss.org/jbosstools/updates/development/indigo/ today (the current version that is downloaded today!)
Then simply file > new > openshift aplication, then enter my username and password (created today with OpenShift Express) and I get the error.
hope thats helpful - will wait for the update to the software.
this is a "known" issue in the sense that you're not the first that reported this:
https://issues.jboss.org/browse/JBIDE-11431
The "interesting" part is that unmarshalling the response fails because of the following 2 properties with null values:
"ssh_key":null,
"ssh_type":null
This error occurrs since OpenShift added support for several keys. We fixed the unmarhslling issue but still dont know how to reproduce it. If you can we'd be very happy to get your instructions.
The fixed version of our client plugin will make it to our nightly update site in a few days. Stay tuned!