[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15830:
-------------------------------------
Affects Version/s: 4.1.1.Beta1
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15831) Server side errors while creating most of the scalable app. on Openshift Enterprise
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15831:
------------------------------------------
we decided to implement a client-lib specific default timeout that a user may override via system properties: JBIDE-15880
> Server side errors while creating most of the scalable app. on Openshift Enterprise
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15831
> URL: https://issues.jboss.org/browse/JBIDE-15831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.x
>
> Attachments: gateway-timeout.png
>
>
> Most of the application while creating process of application show dialog with server error 504 (Gateway timeout), or server error 503 (service unavailable).
> !gateway-timeout.png!
> Altough, application in cloud is created, can be correctly showed in browser, in JBDS / JBT (tested in both) shows dialog with given error
> "Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout" or "Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com"
> This happens only with Openshift Enterprise. Openshift Online works fine.
> Eclipse log for HTTP error 504
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:176)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:83)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
> Eclipse log for HTTP error 503
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:155)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:79)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":null,"field":null,"severity":"error","text":"error adding app record test-test.itos.redhat.com"}],"status":"service_unavailable","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.2"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15835) Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15835?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15835:
------------------------------------------
we decided to implement a client-lib specific default timeout that a user may override via system properties: JBIDE-15880
> Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15835
> URL: https://issues.jboss.org/browse/JBIDE-15835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.CR1
>
>
> Attempt to add to existing (or can be added when creating new) application PostgreSQL database cartridge cause connection time out. Dialog with text
> {code}Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out {code} is shown.
> Finally, cartridge seems to be added correctly (seems to be embedded well, environment variables are correctly set up for the given cartridge etc.)
> This happens only on Openshift Enterprise (Openshift Online works fine)
> Eclipse log:
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209
> !MESSAGE Could not embed cartridges for application dasda
> !STACK 0
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
> at sun.security.ssl.InputRecord.read(InputRecord.java:480)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 10 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-1591) JBDS Installer as a Native Mac OS X Application
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-1591?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-1591:
-------------------------------------
OK, but we can't have both universal installer (this feature request dates before we had that) and native mac installer, so that's the main reason why this will probably never happen even if izpack supports it.
> JBDS Installer as a Native Mac OS X Application
> -----------------------------------------------
>
> Key: JBDS-1591
> URL: https://issues.jboss.org/browse/JBDS-1591
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.0.0.GA
> Environment: Mac OS X
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.0.x
>
>
> This is an enhancement for your consideration. Feel free to reject it.
> Currently, all the installers of JBDS for Mac OS X and other platforms are just plain jar files which you launch either with "java -jar" or by double clicking if the OS supports this.
> When you launch the jar, the icon that appears in the Dock is just a default app icon. It would be possible to bundle the installer on the Mac so that it would be a native Mac OS X app called e.g. "JBDS 4 Installer.app".
> The instructions on how to achieve this are described here:
> http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
> I just tried it and it's easy.
> I think it would be easy to implement this in the building process. The benefit would be an installer with our custom icon in the Dock and also on the installer itself - i.e. in Finder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15880) openshift-java-client: provide its own lib specific timeout that may be set via system properties
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15880:
----------------------------------------
Summary: openshift-java-client: provide its own lib specific timeout that may be set via system properties
Key: JBIDE-15880
URL: https://issues.jboss.org/browse/JBIDE-15880
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.1.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.1.CR1
client timeouts when talking to OpenShift are unfortunaltey still a topic and cause errors (JBIDE-15835, JBIDE-15831) when OpenShift is installed on systems with poor performance. We should thus provide a client-lib specific default timeout that a user may override by setting it in the system properties.
The timeout-setting order would thus then be:
1) specific operation timeout (ex. JBT is currently using a specific creation timeout)
2) client-lib default timeout (which may be set by a system property)
3) HttpUrlConnection default timeout (jdk timeout: -Dsun.net.client.defaultConnectTimeout=600000)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2690) Internal problem when spring project from jboss central is used
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ]
Jiri Peterka reassigned JBDS-2690:
----------------------------------
Assignee: Nick Boldt (was: Jiri Peterka)
Nick, assigning back to you, if you still miss info here just let me know. Error has slightly changed but it similar
{code}
java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2482)
at java.lang.Class.getDeclaredMethods(Class.java:1838)
at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:130)
at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:109)
at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:259)
at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:86)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:749)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:742)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:626)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:585)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:451)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 23 more
{code}
> Internal problem when spring project from jboss central is used
> ---------------------------------------------------------------
>
> Key: JBDS-2690
> URL: https://issues.jboss.org/browse/JBDS-2690
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-dependencies, upstream
> Affects Versions: 7.0.0.CR1
> Environment: JBDS 7.0.0.CR1a, L64
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.x, 8.0.x
>
>
> I have this error when Spring 3.2 or Spring 3.3 is installed:
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2690) Internal problem when spring project from jboss central is used
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-2690:
------------------------------------
Issue is still here. Although project already has Spring nature set by default, when removed and re-added, issue is here. Tested with JBDS 7.1.0.Beta1b, L64
> Internal problem when spring project from jboss central is used
> ---------------------------------------------------------------
>
> Key: JBDS-2690
> URL: https://issues.jboss.org/browse/JBDS-2690
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-dependencies
> Affects Versions: 7.0.0.CR1
> Environment: JBDS 7.0.0.CR1a, L64
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Fix For: 7.1.x, 8.0.x
>
>
> I have this error when Spring 3.2 or Spring 3.3 is installed:
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2690) Internal problem when spring project from jboss central is used
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ]
Jiri Peterka updated JBDS-2690:
-------------------------------
Component/s: upstream
> Internal problem when spring project from jboss central is used
> ---------------------------------------------------------------
>
> Key: JBDS-2690
> URL: https://issues.jboss.org/browse/JBDS-2690
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-dependencies, upstream
> Affects Versions: 7.0.0.CR1
> Environment: JBDS 7.0.0.CR1a, L64
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Fix For: 7.1.x, 8.0.x
>
>
> I have this error when Spring 3.2 or Spring 3.3 is installed:
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months