6 Replies Latest reply on Feb 2, 2006 12:14 PM by adrian.brock

    JMS Message Size Max Limit

    johnmeah

      Hi all,
      We are using the JMS Provider within JBoss and have messages that can range in size from 1kb - 2MB. Is there a way to configure the size limit in JBossMQ to allow for large message sizes? We've found errors publishing messages > 1MB in size.

      Thanks,
      John Meah

        • 1. Re: JMS Message Size Max Limit
          johnmeah

          All,
          I spent the better part of the last couple of days researching this on and off with little support offered by the forums. The resolution for this is to create a BLOB column with the appropriate message size you expect. By default I believe it is 1MB. The table of interest is JMS_MESSAGES. The column of intereste is MESSAGEBLOB. This column should be set to the max message size you expect. In our case we decided to create the column with a 4MB size.

          If this data were in the jBoss Application Server Guide I would have saved an awful lot of time.

          P.S. I'm not sure why these forums are treated like newsgroups. This is a major marketing tool for jBoss so great support here would further the product.

          Thanks,
          John Meah

          • 2. Re: JMS Message Size Max Limit
            genman


            What database are you using? JBoss version? How do you set what you want set?

            Ironically, if users like yourself treated this like a for-pay service, then perhaps they would be more articulate and specific. This is probably the main reason this forum sucks--people ask stupid questions and are rude and then expect their problems to be solved.

            If you can formulate exactly what you mean, they will add it to the documentation. Or, it may only take you 10 minutes to add a page on the Wiki.

            • 3. Re: JMS Message Size Max Limit

               

              "johnmeah" wrote:

              P.S. I'm not sure why these forums are treated like newsgroups. This is a major marketing tool for jBoss so great support here would further the product.


              Read this:
              http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp

              I wouldn't describe a dumping ground for problems that are usually nothing to
              do with JBoss - like this question about your (unknown) database's blob support
              a "marketing tool" :-)

              It is mostly a waste of our time. I think I've seen 6 real JBoss problems
              (i.e. not FAQs, didn't read the docs, etc.) reported here in the last year.

              • 4. Re: JMS Message Size Max Limit
                johnmeah

                Here are the details.

                Problem: Cannot pass JMS message > 1MB. Client publisher returns error.

                System Details:
                jBoss: 4.01 SP1
                Database: IBM DB2 8.02
                OS: Linux

                Fix: Set the MESSAGEBLOB column in the JMS_MESSAGES table to the appropriate size during create (i.e. 4MB). This will resolve the message size issue.

                Open Issue of mine: Cannot find documentation regarding known message size limits (e.g. Will passing through 500 MB message cause errors?). Is this all driven by this column size in the database?

                Read all of jBoss App Server Guide, FAQs, and searched site before posting.

                • 5. Re: JMS Message Size Max Limit
                  schrouf

                  There is no hard message size limit. JBossMQ is primarily limited by size of available JVM memory (or underlying database limitations, as you already know). Anyway the idea of passing 500MB messages does not sound very attractive. Maybe you should rethink your general design...

                  Regards
                  Ulf

                  • 6. Re: JMS Message Size Max Limit

                     

                    "johnmeah" wrote:

                    Read all of jBoss App Server Guide, FAQs, and searched site before posting.


                    You should have tried the IBM DB2 site. This is not the DB2 support forum.

                    If you'd actually posted the errors instead of saying "it does not work"
                    it would be obvious to any causual browser that it was a database/jdbc problem.