Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 591399 Details for
Bug 831513
Impossible to create JMS destination with default settings
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Proposed patch
BZ_831513_Fill_some_defaults,_as_otherwise_destination_creation_fails.patch (text/plain), 8.06 KB, created by
Heiko W. Rupp
on 2012-06-13 08:11:33 UTC
(
hide
)
Description:
Proposed patch
Filename:
MIME Type:
Creator:
Heiko W. Rupp
Created:
2012-06-13 08:11:33 UTC
Size:
8.06 KB
patch
obsolete
>Index: modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml >IDEA additional info: >Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP ><+>UTF-8 >=================================================================== >--- modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml (revision f6ac42c51930aecc42cf6eb006e9abbc8d09584d) >+++ modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml (revision ) >@@ -223,7 +223,7 @@ > <c:map-property name="metadata" required="false" description="Metadata properties."> > <c:simple-property required="false" name="typeMapping"> > <c:description> >- The name of the corresponding type-mapping in conf/standardjbosscmp-jdbc.xml. The type mappings provided by default: DB2, InformixDB, MaxDB, mySQL, Oracle9i, PointBase, InterBase, Mimer SQL, McKoi, SapDB, DB2/400, SOLID, Hypersonic SQL, FirstSQL/J, MS SQLSERVER2000, MS SQLSERVER, Cloudscape, Derby, Firebird, PostgreSQL 8.0, PostgreSQL, Sybase, Ingres. >+ The name of the corresponding type-mapping in conf/standardjbosscmp-jdbc.xml. The type mappings provided by default: DB2, InformixDB, MaxDB, mySQL, Oracle9i, PointBase, InterBase, Mimer SQL, McKoi, SapDB, DB2/400, SOLID, Hypersonic SQL, FirstSQL/J, MS SQLSERVER2000, MS SQLSERVER, Cloudscape, Derby, Firebird, PostgreSQL 8.0, PostgreSQL, Sybase, Ingres. > Note, there may be custom type mappings defined in addition to these predefined mappings. > </c:description> > </c:simple-property> >@@ -286,7 +286,7 @@ > > <c:simple-property name="type-mapping" displayName="Type Mapping" required="false"> > <c:description> >- The name of the corresponding type-mapping in conf/standardjbosscmp-jdbc.xml. The type mappings provided by default: DB2, InformixDB, MaxDB, mySQL, Oracle9i, PointBase, InterBase, Mimer SQL, McKoi, SapDB, DB2/400, SOLID, Hypersonic SQL, FirstSQL/J, MS SQLSERVER2000, MS SQLSERVER, Cloudscape, Derby, Firebird, PostgreSQL 8.0, PostgreSQL, Sybase, Ingres. >+ The name of the corresponding type-mapping in conf/standardjbosscmp-jdbc.xml. The type mappings provided by default: DB2, InformixDB, MaxDB, mySQL, Oracle9i, PointBase, InterBase, Mimer SQL, McKoi, SapDB, DB2/400, SOLID, Hypersonic SQL, FirstSQL/J, MS SQLSERVER2000, MS SQLSERVER, Cloudscape, Derby, Firebird, PostgreSQL 8.0, PostgreSQL, Sybase, Ingres. > Note, there may be custom type mappings defined in addition to these predefined mappings. > </c:description> > </c:simple-property> >@@ -561,11 +561,11 @@ > category="performance"/> > > <metric property="connectionCreatedCount" measurementType="dynamic" displayType="detail" >- displayName="Connection Created Count" >+ displayName="Connection Created Count" > dataType="measurement" category="performance"/> > > <metric property="connectionDestroyedCount" measurementType="dynamic" displayType="detail" >- displayName="Connection Destroyed Count" >+ displayName="Connection Destroyed Count" > dataType="measurement" category="performance"/> > > <metric property="inUseConnectionCount" measurementType="dynamic" displayType="detail" >@@ -1470,7 +1470,7 @@ > <c:simple-property name="isSameRM-override-value" default="false" /> > <c:simple-property name="xa-datasource-class" default="oracle.jdbc.xa.client.OracleXADataSource" /> > <c:simple-property name="exception-sorter-class-name" default="org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter" /> >- <!-- Oracle's XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction >+ <!-- Oracle's XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction > and vice-versa. --> > <c:simple-property name="no-tx-separate-pools" default="true" /> > <c:simple-property name="use-try-lock" default="60000" /> >@@ -1852,7 +1852,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="DLQ"> >+ <c:simple-property required="false" name="DLQ" default="jboss.messaging.destination:service=Queue,name=DLQ"> > <c:description> > The JMX ObjectName of the dead letter queue (DLQ) for this queue (e.g. > "jboss.messaging.destination:service=Queue,name=PrivateDLQ") - overrides the default DLQ on the >@@ -1863,7 +1863,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="expiryQueue"> >+ <c:simple-property required="false" name="expiryQueue" default="jboss.messaging.destination:service=Queue,name=ExpiryQueue"> > <c:description> > The JMX ObjectName of the expiry queue for this queue (e.g. > "jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue") - overrides the default >@@ -1874,7 +1874,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="serverPeer"> >+ <c:simple-property required="false" name="serverPeer" default="jboss.messaging:service=ServerPeer" > > <c:description> > The JMX ObjectName of the server peer this queue was deployed on (e.g. > "jboss.messaging:service=ServerPeer"). Updates to this property will not go into effect until >@@ -2169,7 +2169,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="DLQ"> >+ <c:simple-property required="false" name="DLQ" default="jboss.messaging.destination:service=Queue,name=DLQ"> > <c:description> > The JMX ObjectName of the dead letter queue (DLQ) for this topic (e.g. > "jboss.messaging.destination:service=Queue,name=PrivateDLQ") - overrides the default DLQ on the >@@ -2180,7 +2180,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="expiryQueue"> >+ <c:simple-property required="false" name="expiryQueue" default="jboss.messaging.destination:service=Queue,name=ExpiryQueue"> > <c:description> > The JMX ObjectName of the expiry queue for this topic (e.g. > "jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue") - overrides the default >@@ -2191,7 +2191,7 @@ > </c:constraint> > </c:simple-property> > >- <c:simple-property required="false" name="serverPeer"> >+ <c:simple-property required="false" name="serverPeer" default="jboss.messaging:service=ServerPeer"> > <c:description> > The JMX ObjectName of the server peer this topic was deployed on (e.g. > "jboss.messaging:service=ServerPeer"). Updates to this property will not go into effect until >@@ -2808,13 +2808,13 @@ > The name of the binding set the Service Binding Manager should use when resolving bindings. > Note to JBoss ON or Jopr users (does not apply to JBoss AS admin console): > CHANGING THIS PROPERTY IS POTENTIALLY DANGEROUS because if there are any port conflicts >-on the machine the Application Server is running on, the server will not start up again and >+on the machine the Application Server is running on, the server will not start up again and > it will not be possible to monitor it. > To be able to monitor the server again after the restart you have to update the "Naming Provider Url" > in the "Connection" subtab in the "Inventory" of the Application Server to the value > of "jboss:service=Naming:Port" binding of the active binding set. > I.e. if the "jboss:service=Naming:Port" binding of the active binding set has the port set to 4099 and hostname to 127.0.0.1, >-you have to set the "Naming Provider Url" to jnp://127.0.0.1:4099. >+you have to set the "Naming Provider Url" to jnp://127.0.0.1:4099. > ]]></c:description> > </c:simple-property> > <c:list-property name="standardBindings" description="The standard port bindings inherited by the binding sets.">
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Flags:
hrupp
: review? (
ian.springer
)
Actions:
View
|
Diff
Attachments on
bug 831513
: 591399