Bug 908758 - It is impossible to create new JMS Connection factory
Summary: It is impossible to create new JMS Connection factory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: EAP 6.1.0
Assignee: Heiko Braun
QA Contact:
URL:
Whiteboard:
Depends On: 920491
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-07 12:52 UTC by Jakub Cechacek
Modified: 2015-02-01 22:59 UTC (History)
5 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-4377 0 Major Resolved Failed to create messaging connection factory 2016-03-01 06:28:59 UTC

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


Note You need to log in before you can comment on or make changes to this bug.