2 Replies Latest reply on Oct 14, 2005 4:56 AM by lxfsuccess

    Message Size?

    lxfsuccess

      Is there a maximum message size that the JbossMQ provider can handle? It works fine with 2.6M message sizes(https,database persistence), but if I send anything larger it rejects the message.There is not any exception,but
      I can't find the message in database.
      I guess there's a way to adjust this limit, but I cannot find it.
      Who can help me?Thanks in advance.

        • 1. Re: Message Size?
          starksm64

          There is no limit. Details of server version and jms configuration are needed.

          • 2. Re: Message Size?
            lxfsuccess

            Thank you very much,Scott.
            server version : jboss-4.0.2
            database: postgreSQL 7.4.6
            In my application,I didn't use MDB,just created a jar package as a JMS server which defined a sender interface , a receiver interface and a start() method.
            Configuration details:
            (1)Expose the Naming service interface via HTTPS in the file \deploy\http-invoker.sar\META-INF\jboss-server.xml

            <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
             name="jboss:service=invoker,type=https,target=Naming">
             <!-- The Naming service we are proxying -->
             <attribute name="InvokerName">jboss:service=Naming</attribute>
             <!-- Compose the invoker URL from the cluster node address -->
             <attribute name="InvokerURLPrefix">https://</attribute>
             <attribute name="InvokerURLSuffix">:443/invoker/JMXInvokerServlet</attribute>
             <attribute name="UseHostName">false</attribute>
             <attribute name="ExportedInterface">org.jnp.interfaces.Naming</attribute>
             <attribute name="JndiName"></attribute>
             <attribute name="ClientInterceptors">
             <interceptors>
             <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
             <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
             <interceptor>org.jboss.naming.interceptors.ExceptionInterceptor</interceptor>
             <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
             </interceptors>
             </attribute>
             </mbean>

            (2)Define servlet 'JNDIFactorySSL' in the file \deploy\http-invoker.sar\invoker.war\WEB-INF\web.xml
            (3)Define SSL/TLS Connector in the file \deploy\jbossweb-tomcat55.sar\server.xml
            <Connector port="443" address="${jboss.bind.address}"
             maxThreads="100" strategy="ms" maxHttpHeaderSize="8192"
             emptySessionPath="true"
             scheme="https" secure="true" clientAuth="false"
             keystoreFile="${jboss.server.home.dir}/conf/server.keystore"
             keystorePass="123456" sslProtocol = "TLS" />

            (4)Add two attributes in the file \deploy\jms\jbossmq-httpil.sar\META-INF\jboss-service.xml
            <attribute name="URLPrefix">https://</attribute>
             <attribute name="URLPort">443</attribute>

            (5)database configuration in the file \deploy\postgres-ds.xml:
            <?xml version="1.0" encoding="UTF-8"?>
            <datasources>
             <local-tx-datasource>
             <jndi-name>PostgresDS</jndi-name>
             <connection-url>jdbc:postgresql://hostname:port/db-name</connection-url>
             <driver-class>org.postgresql.Driver</driver-class>
             <user-name>username</user-name>
             <password>password</password>
             <metadata>
             <type-mapping>PostgreSQL 7.4.6</type-mapping>
             </metadata>
             </local-tx-datasource>
            </datasources>