Bug 809721 - [eap6] deployment cannot be created when server is listening on IPv6
Summary: [eap6] deployment cannot be created when server is listening on IPv6
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 919199 as7-plugin
TreeView+ depends on / blocked
 
Reported: 2012-04-04 07:45 UTC by Libor Zoubek
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
deployment creation failure (14.40 KB, application/octet-stream)
2012-04-04 07:45 UTC, Libor Zoubek 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 822218 0 high NEW Investigate dropping -Djava.net.preferIPv4Stack=true from agent options 2022-03-31 04:28:33 UTC

Internal Links: 822218

Description Libor Zoubek 2012-04-04 07:45:59 UTC 
Created attachment 575055 [details]
deployment creation failure

Description of problem:


Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: 8af11c9
EAP6 ER4.1

How reproducible:always


Steps to Reproduce:
1. start EAP standalone by ./standalone.sh -b :: -b management :: -Djava.net.PreferIPv4Stack=false
2. inventory it
3. create a deployment, upload some WAR file
  
Actual results: Creating Deployment child fails with error: 

Failed to open output stream to URL [http://:::9990/management/add-content]: java.net.MalformedURLException: For input string: "::9990"


Expected results: Child resource is successfully created


Additional info: for IPv6 plugin should use http://[::]:9990
Comment 1 Charles Crouch 2012-04-13 00:23:39 UTC 
Lowering priority, this is not a blocker for rhq4.4
Comment 2 Heiko W. Rupp 2012-05-15 10:13:19 UTC 
Even if the above error were fixed, we would very probably run into 
https://bugzilla.redhat.com/show_bug.cgi?id=809125#c3
Note You need to log in before you can comment on or make changes to this bug.