[
https://issues.jboss.org/browse/JBDS-2957?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2957:
-------------------------------------------
Okey - so here is my theory:
The proxy is blocking non-browser access and since eclipse does not look like a browser
but is trying to access stuff over http/https it is being rejected.
That rejection contains a response (my guess is some "You shall not pass"-html
response) as opposed to an actual proper response (i.e. http 400 error code or something
similar) which p2 is thus trying to parse than thus you get
"NoSuchElementException".
If we actually was denied access or without a proxy I would expect it to show something
like "Connection time out" or some other more concrete error.
This would explain why you can access data via IE but not from a tool like eclipse - since
eclipse does not identify itself as an browser (neither should it)
JBDS can't access update site via proxy
---------------------------------------
Key: JBDS-2957
URL:
https://issues.jboss.org/browse/JBDS-2957
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.1.0.GA
Environment: JBDS 7.1.0 / trying to get FSW tooling
Reporter: Rick Wagner
Attachments: jbds.docx
The user says:
version: Version: 7.1.0.GA
I am trying to see if i can install switchyard plugin thru software updates. i have proxy
setting as "native" - it shows the right proxy ip and port. i have an eclipse
juno with same proxy setting working without problem. but his is what i got with jbds when
checking for updates:
Some sites could not be found. See the error log for more detail.
Unable to read repository at
https://devstudio.jboss.com/updates/7.0/compositeContent.xml.
java.util.NoSuchElementException
Unable to read repository at
https://devstudio.jboss.com/updates/7.0/central/integration-stack/composi....
java.util.NoSuchElementException
i dont have problem accessing the url thru ie.
--
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