4 Replies Latest reply on Mar 4, 2013 1:13 PM by muthukumaran_m

connection-pool dynamic-load-provider on Jboss 7.1.2.Final

muthukumaran_m Mar 4, 2013 10:54 AM

Hello,

I configured connection-pool dynamic-load-provider on Jboss 7.1.2.Final as specified in the below link.

https://docs.jboss.org/author/display/AS7/High+Availability+Guide

But I get the following error while starting the server, if I comment out "connection-pool" server startsup fine.

---------------------------------------------------------------

15:50:06,055 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceExceptio

n: JBAS014676: Failed to parse configuration

at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-redh

at-1.jar:7.1.2.Final-redhat-1]

at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]

at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.

1.2.Final-redhat-1]

at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[292,21]

Message: "JBAS014839: Invalid value connection-pool for type; legal values are [heap, requests, sessions, busyness, send-traffic, mem, cpu, receive-tra

ffic]"

at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:154) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.

1.2.Final-redhat-1]

at org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:207) [jboss-as-controller-7.1.2.Final-

redhat-1.jar:7.1.2.Final-redhat-1]

at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.parseLoadMetric(ModClusterSubsystemXMLReader_1_0.java:232)

at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.parseDynamicLoadProvider(ModClusterSubsystemXMLReader_1_0.java:211)

at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.parseModClusterConfig(ModClusterSubsystemXMLReader_1_0.java:90)

at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.readElement(ModClusterSubsystemXMLReader_1_0.java:66)

at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.readElement(ModClusterSubsystemXMLReader_1_0.java:45)

at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]

at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.F

inal-redhat-1]

at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:905) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-r

edhat-1]

at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:331) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Fina

l-redhat-1]

at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1

]

at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:99) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]

at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]

at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]

at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-redh

at-1.jar:7.1.2.Final-redhat-1]

... 3 more

15:50:06,070 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

15:50:06,078 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) stopped in 5ms

---------------------------------------------------------------

Thanks,

Muthu

1. Re: connection-pool dynamic-load-provider on Jboss 7.1.2.Final

rhusar Mar 4, 2013 11:07 AM (in response to muthukumaran_m)

connection-pool is not supported as stated in the docs.

BTW you can look into docs/schemas/ for list of supported metrics:

<xs:simpleType name="loadMetricEnum">
    <xs:restriction base="xs:token">
      <xs:enumeration value="cpu"/>
      <xs:enumeration value="mem"/>
      <xs:enumeration value="heap"/>
      <xs:enumeration value="sessions"/>
      <xs:enumeration value="requests"/>
      <xs:enumeration value="send-traffic"/>
      <xs:enumeration value="receive-traffic"/>
      <xs:enumeration value="busyness"/>
    </xs:restriction>
</xs:simpleType>
Actions
2. Re: connection-pool dynamic-load-provider on Jboss 7.1.2.Final

muthukumaran_m Mar 4, 2013 11:39 AM (in response to rhusar)

oh man.. I missed this "(NOT SUPPORTED)" in the doc....

Thanks Husar.
Actions
3. Re: connection-pool dynamic-load-provider on Jboss 7.1.2.Final

rhusar Mar 4, 2013 12:33 PM (in response to muthukumaran_m)

No worries. Can you at least desribe your use case here? The exhaustion of the connection pool does not directly represent the cost/load unlike e.g. CPU usage does. Maybe you mainly want to prevent a complete pool exhaustion?

I created a Jira here https://issues.jboss.org/browse/AS7-6669 that you might want to follow.
Actions
4. Re: connection-pool dynamic-load-provider on Jboss 7.1.2.Final

muthukumaran_m Mar 4, 2013 1:13 PM (in response to rhusar)

Yes, you are correct. Thanks for creating the JIRA for me.

We are currently on Jboss 5.1 and we use the connection pool metrics to make sure that we dont exahust all the connection.

Thanks,
Muthu
Actions

Go to original post