[JCA/JBoss] - #Connections vs Datasources vs. #Jboss Nodes
by Konso
Hi,
we have a problem concering the number of connections during the startup of 4 Jboss Nodes (2 on one phy. machine; no clustering, just farmin with a use of one shared deploy dir using a common binding file).
The instances are bound to virtual eth Interfaces and using the same ports. Just one Info behind the scene. Before this setup we use two apaches mit mod_jk properly configured.
This is our db configuration (DB2),e.g.
<datasources>
|
| <xa-datasource>
| <jndi-name>WLDS</jndi-name>
| <xa-datasource-class>com.ibm.db2.jcc.DB2XADataSource</xa-datasource-class>
| <xa-datasource-property name="DriverType">4</xa-datasource-property>
| <xa-datasource-property name="DatabaseName">GAME</xa-datasource-property>
| <xa-datasource-property name="User">xxx</xa-datasource-property>
| <xa-datasource-property name="Password">xxx</xa-datasource-property>
| <xa-datasource-property name="PortNumber">xxx</xa-datasource-property>
| <xa-datasource-property name="ServerName">xxx</xa-datasource-property>
| <xa-datasource-property name="CurrentSchema">xxx</xa-datasource-property>
| <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>
| <min-pool-size>40</min-pool-size>
| <max-pool-size>40</max-pool-size>
| <track-statements>true</track-statements>
| <track-connection-by-tx>true</track-connection-by-tx>
| <no-tx-separate-pools/>
| <prepared-statement-cache-size>10</prepared-statement-cache-size>
| <set-tx-query-timeout/>
| </xa-datasource>
|
| <no-tx-datasource>
| <jndi-name>QUARTZDS</jndi-name>
| <connection-url>jdbc:db2:xxx:currentSchema=xxxx;</connection-url>
| <driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
| <user-name>xxx</user-name>
| <password>xx</password>
| <min-pool-size>40</min-pool-size>
| <max-pool-size>40</max-pool-size>
| <metadata>
| <type-mapping>DB2</type-mapping>
| </metadata>
| <set-tx-query-timeout/>
| <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>
| <track-statements>true</track-statements>
| <track-connection-by-tx>true</track-connection-by-tx>
| <no-tx-separate-pools/>
| <prepared-statement-cache-size>0</prepared-statement-cache-size>
| <set-tx-query-timeout/>
| </no-tx-datasource>
|
|
| <local-tx-datasource>
| <jndi-name>JMSDS</jndi-name>
| <connection-url>jdbc:db2:JBOSS:currentSchema=JBOSS;</connection-url>
| <driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
| <user-name>xx</user-name>
| <password>xxx</password>
| <min-pool-size>40</min-pool-size>
| <max-pool-size>40</max-pool-size>
| <metadata>
| <type-mapping>DB2</type-mapping>
| </metadata>
| <set-tx-query-timeout/>
| <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>
| </local-tx-datasource>
|
| </datasources>
During the startup of ONE instance i recognize ca. 160 DB connections using "db2 list applications".
Why? Ok, tx-separate-pool is NOT working, so 40+40 for WLDS, 40 JMSDS and 40 for QUARTZ DS? Each further instance produce 120 Connections, so with 4 instances up i have 160+120+120+120. (=too much)
What is the best practice to have 160 Connections at all about all 4 nodes?
Ok, reduce it to 10, but the one machine has only 10 Connections avail and not 40 i would like to have.
(160 is the maximum limit configured concerning the database.)
Any ideas?
Best regards,
Marc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059101#4059101
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059101
17Â years, 8Â months
[JBossWS] - problem with web method returning list
by patel_123
hi
I am exposing ejb components as webservice.Initially i exposed one method as web method,that returns String.This works fine.Next i tried another method which returns array of objects.This leads to following error....
Caused by: javax.xml.rpc.JAXRPCException: org.jboss.xb.binding.JBossXBValueFormatException: Java value for XSD boolean type expected to be an instance of java.lang.Boolean or java.lang.Number. But the value is of type java.util.ArrayList
at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:986)
at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:171)
at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
at org.jboss.ws.soap.SAAJElementWriter.printInternal(SAAJElementWriter.java:163)
at org.jboss.ws.soap.SAAJElementWriter.print(SAAJElementWriter.java:142)
at org.jboss.ws.soap.SAAJElementWriter.printSOAPElement(SAAJElementWriter.java:91)
at org.jboss.ws.server.ServiceEndpoint.postProcessResponse(ServiceEndpoint.java:280)
... 25 more
Caused by: org.jboss.xb.binding.JBossXBValueFormatException: Java value for XSD boolean type expected to be an instance of java.lang.Boolean or java.lang.Number. But the value is of type java.util.ArrayList
at org.jboss.xb.binding.SimpleTypeBindings.marshal(SimpleTypeBindings.java:1120)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalCharacters(MarshallerImpl.java:995)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalSimpleType(MarshallerImpl.java:471)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementType(MarshallerImpl.java:415)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(MarshallerImpl.java:331)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOccurence(MarshallerImpl.java:311)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(MarshallerImpl.java:730)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroupSequence(MarshallerImpl.java:920)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroup(MarshallerImpl.java:860)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(MarshallerImpl.java:641)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalComplexType(MarshallerImpl.java:608)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementType(MarshallerImpl.java:419)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(MarshallerImpl.java:331)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOccurence(MarshallerImpl.java:311)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshallInternal(MarshallerImpl.java:210)
at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshal(MarshallerImpl.java:168)
at org.jboss.ws.jaxb.JBossXBMarshallerImpl.marshal(JBossXBMarshallerImpl.java:146)
at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer.java:107)
at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElement.java:157)
at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:817)
at org.jboss.ws.soap.SOAPContentElement.handleMTOMTransitions(SOAPContentElement.java:1015)
at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:968)
... 33 more
could any body tell me what went wrong?
in the wsdl doc,
-
its taking type as boolean but actaully it should be of type list....
i dont know where i went wrong....please anybody help me
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059090#4059090
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059090
17Â years, 8Â months