[JBoss Messaging] - Re: Messaging blocked by long time-out again
by lanceliao1
We are using Jboss4.2.4 with JBM 1.4.2.GA-SP1 and jboss-remoting-2.2.2.SP11.jar.
| <invoker transport="bisocket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4557</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
|
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
| <attribute name="numberOfRetries" isParam="true">10</attribute>
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
| <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
| <attribute name="callbackTimeout">10000</attribute>
| </invoker>
|
The remoting guys resolve the problem by setting TCP TTL.This is a ugly way.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223154#4223154
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223154
17 years
[Microcontainer] - More trouble in the bean-deployer schema
by david.lloyd＠jboss.com
The following construct doesn't validate, even though it's allowed by the bean deployer (which fortunately doesn't validate, but that's another thread):
| ...
| <parameter class="...">
| <bean name="..." class="...">
| ...
| </bean>
| </parameter>
| ...
|
The error is something like this (formatted for readability):
| Error:Error:line (15)cvc-complex-type.2.4.a: Invalid content was found starting with element 'bean'.
| One of
| '{"urn:jboss:bean-deployer:2.0":value,
| "urn:jboss:bean-deployer:2.0":inject,
| "urn:jboss:bean-deployer:2.0":value-factory,
| "urn:jboss:bean-deployer:2.0":collection,
| "urn:jboss:bean-deployer:2.0":list,
| "urn:jboss:bean-deployer:2.0":set,
| "urn:jboss:bean-deployer:2.0":array,
| "urn:jboss:bean-deployer:2.0":map,
| "urn:jboss:bean-deployer:2.0":null,
| "urn:jboss:bean-deployer:2.0":this,
| WC[##other:"urn:jboss:bean-deployer:2.0"],
| "urn:jboss:bean-deployer:2.0":annotation}'
| is expected.
|
The xsd for bean-deployer is a bit too crazy for me to parse mentally, so I don't know what the problem is.
Also, the following validation errors have been popping up lately:
| /home/david/src/java/microcontainer/trunk/kernel/src/main/resources/schema/bean-deployer_2_0.xsd
| Error:Error:line (139)rcase-RecurseLax.2: There is not a complete functional mapping between the particles.
| Error:Error:line (139)src-redefine.6.2.2: Group 'valueGroup' does not properly restrict the group it redefines; constraint violated: 'rcase-RecurseLax.2'.
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223150#4223150
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223150
17 years