Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 908758

Summary: It is impossible to create new JMS Connection factory
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jakub Cechacek <jcechace>
Component: Web ConsoleAssignee: Heiko Braun <hbraun>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: brian.stansberry, hbraun, jkudrnac, rsvoboda, smcgowan
Target Milestone: ER4   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 920491    
Bug Blocks:    

Description Jakub Cechacek 2013-02-07 12:52:31 UTC
The following error response is a result of creating new Connection factory. The problems seems to be in value of "connector" attribute {"netty" => UNDEFINED} -- UNDEFINED should be written in lower case -- the correct value is  {"netty" => undefined}


Unexpected HTTP response: 500

Request
{
    "failover-on-server-shutdown" => false,
    "compress-large-messages" => false,
    "failover-on-initial-connection" => false,
    "use-global-pools" => true,
    "address" => [
        ("profile" => "full"),
        ("subsystem" => "messaging"),
        ("hornetq-server" => "default"),
        ("connection-factory" => "test")
    ],
    "operation" => "add",
    "entries" => ["java:/test"],
    "connector" => {"netty" => UNDEFINED}
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "JBAS014688: Wrong type for connector. Expected [STRING] but was TYPE"},
    "rolled-back" => true
}

Comment 1 Heiko Braun 2013-02-12 15:12:27 UTC
Related to https://issues.jboss.org/browse/AS7-4377

Comment 2 Shelly McGowan 2013-03-20 19:48:14 UTC
The referenced issue is marked RESOLVED but this EAP 6.1 issue is linked as related.  Why is the issue in MODIFIED state?  Is that correct?

Comment 3 Jakub Cechacek 2013-04-16 08:33:48 UTC
Verified  6.1.0.ER4