Re: Websphere JMS problem when doing a GET with a large message
I'm not sure that I ever saw any kind of answer on thisI thought that I read somewhere something about a problem related to messages that were greater than 32K. I know that your message was around 8K. However, I'd make sure that you have the latest CSD applied and see if that solves the problem. Ron __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
Grrr...bloody Microsoft Windows calculator... Ok, so it was my goof but I figure if anything Microsoft was in the mix I have plausible deniability! -- T.Rob -Original Message- From: Jim Ford [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 5:07 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message Actually, 104,857,600 is exactly 100 mb (100*1024*1024). "Wyatt, T. Rob" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] MERICA.COM> cc: Sent by: MQSeries Subject: Re: Websphere JMS problem when doing a GET with a large List message <[EMAIL PROTECTED] C.AT> 09/19/2003 03:53 PM Please respond to MQSeries List It's exactly 300K larger than 100MB. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 3:40 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message I'm still thinking you should trust the RC=2030 as exactly that. Are you certain that you are supplying a correct message length to JMS? For grins, maybe try setting maxmsgl smaller. Not sure where 104... comes from, it seems larger than 100MB. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 4:58 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > Dennis, > > Thanks for the suggestion, however the MAXMSGL on the qmgr is set to 104,857,600. This is much larger than any message we are creating. > > Allen. > > -Original Message- > From: Miller, Dennis [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 3:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > > What about MAXMSGL at the qmgr level. Could be large enough to accomodate your message, but too small for your message + the jms envelope. > > > -Original Message- > > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2003 2:11 PM > > To: [EMAIL PROTECTED] > > Subject: Websphere JMS problem when doing a GET with a large message > > > > Hope you guys can help... > > > > Running MQ 5.3 CSD03 > > > > We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. > > Normally works ok. > > > > The problem is when trying to read a large message > 8mb. > > We get the error > > > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > > > We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. > > (This is also alluded to in the corrective action of the 2030 error) > > > > Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. > > > > My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. > > > > Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) > > > > PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. > > > > Thanks in advance for your assistance. > > > > Allen > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.
Re: Websphere JMS problem when doing a GET with a large message
Actually, 104,857,600 is exactly 100 mb (100*1024*1024). "Wyatt, T. Rob" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] MERICA.COM> cc: Sent by: MQSeries Subject: Re: Websphere JMS problem when doing a GET with a large List message <[EMAIL PROTECTED] C.AT> 09/19/2003 03:53 PM Please respond to MQSeries List It's exactly 300K larger than 100MB. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 3:40 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message I'm still thinking you should trust the RC=2030 as exactly that. Are you certain that you are supplying a correct message length to JMS? For grins, maybe try setting maxmsgl smaller. Not sure where 104... comes from, it seems larger than 100MB. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 4:58 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > Dennis, > > Thanks for the suggestion, however the MAXMSGL on the qmgr is set to 104,857,600. This is much larger than any message we are creating. > > Allen. > > -Original Message- > From: Miller, Dennis [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 3:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > > What about MAXMSGL at the qmgr level. Could be large enough to accomodate your message, but too small for your message + the jms envelope. > > > -Original Message- > > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2003 2:11 PM > > To: [EMAIL PROTECTED] > > Subject: Websphere JMS problem when doing a GET with a large message > > > > Hope you guys can help... > > > > Running MQ 5.3 CSD03 > > > > We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. > > Normally works ok. > > > > The problem is when trying to read a large message > 8mb. > > We get the error > > > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > > > We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. > > (This is also alluded to in the corrective action of the 2030 error) > > > > Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. > > > > My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. > > > > Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) > > > > PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. > > > > Thanks in advance for your assistance. > > > > Allen > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
It's exactly 300K larger than 100MB. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 3:40 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message I'm still thinking you should trust the RC=2030 as exactly that. Are you certain that you are supplying a correct message length to JMS? For grins, maybe try setting maxmsgl smaller. Not sure where 104... comes from, it seems larger than 100MB. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 4:58 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > Dennis, > > Thanks for the suggestion, however the MAXMSGL on the qmgr is set to 104,857,600. This is much larger than any message we are creating. > > Allen. > > -Original Message- > From: Miller, Dennis [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 3:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > > What about MAXMSGL at the qmgr level. Could be large enough to accomodate your message, but too small for your message + the jms envelope. > > > -Original Message- > > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2003 2:11 PM > > To: [EMAIL PROTECTED] > > Subject: Websphere JMS problem when doing a GET with a large message > > > > Hope you guys can help... > > > > Running MQ 5.3 CSD03 > > > > We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. > > Normally works ok. > > > > The problem is when trying to read a large message > 8mb. > > We get the error > > > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > > > We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. > > (This is also alluded to in the corrective action of the 2030 error) > > > > Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. > > > > My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. > > > > Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) > > > > PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. > > > > Thanks in advance for your assistance. > > > > Allen > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
I'm still thinking you should trust the RC=2030 as exactly that. Are you certain that you are supplying a correct message length to JMS? For grins, maybe try setting maxmsgl smaller. Not sure where 104... comes from, it seems larger than 100MB. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 4:58 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > Dennis, > > Thanks for the suggestion, however the MAXMSGL on the qmgr is set to 104,857,600. > This is much larger than any message we are creating. > > Allen. > > -Original Message- > From: Miller, Dennis [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 3:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Websphere JMS problem when doing a GET with a large message > > > What about MAXMSGL at the qmgr level. Could be large enough to accomodate your > message, but too small for your message + the jms envelope. > > > -Original Message- > > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2003 2:11 PM > > To: [EMAIL PROTECTED] > > Subject: Websphere JMS problem when doing a GET with a large message > > > > Hope you guys can help... > > > > Running MQ 5.3 CSD03 > > > > We have an application that uses Websphere JMS to get messages from one Q and > > place them on another Q. > > Normally works ok. > > > > The problem is when trying to read a large message > 8mb. > > We get the error > > > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > > > We know this is not the real error as the Q is plenty large enough. The real > > error is that the buffer size on the GET is not large enough to retrieve the > > message. > > (This is also alluded to in the corrective action of the 2030 error) > > > > Normally we would correct this by getting the DataLength from the failed GET and > > re issuing a GET with this length in the BufferSize. > > > > My dilemma is that the developer working on this informs me that within JMS you > > can not specify the BufferSize as it is dynamically calculated by the JMS API. > > > > Has anyone encountered this before and if so how did you resolve it? ( excluding > > MQMF_SEGMENTATION_ALLOWED in the MQMD) > > > > PS. I realize/realise that the application could be redesigned to use smaller > > messages however that is a different bridge to cross. > > > > Thanks in advance for your assistance. > > > > Allen > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
Dennis, Thanks for the suggestion, however the MAXMSGL on the qmgr is set to 104857600. This is much larger than any message we are creating. Allen. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 3:45 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message What about MAXMSGL at the qmgr level. Could be large enough to accomodate your message, but too small for your message + the jms envelope. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 2:11 PM > To: [EMAIL PROTECTED] > Subject: Websphere JMS problem when doing a GET with a large message > > Hope you guys can help... > > Running MQ 5.3 CSD03 > > We have an application that uses Websphere JMS to get messages from one Q and place > them on another Q. > Normally works ok. > > The problem is when trying to read a large message > 8mb. > We get the error > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > We know this is not the real error as the Q is plenty large enough. The real error > is that the buffer size on the GET is not large enough to retrieve the message. > (This is also alluded to in the corrective action of the 2030 error) > > Normally we would correct this by getting the DataLength from the failed GET and re > issuing a GET with this length in the BufferSize. > > My dilemma is that the developer working on this informs me that within JMS you can > not specify the BufferSize as it is dynamically calculated by the JMS API. > > Has anyone encountered this before and if so how did you resolve it? ( excluding > MQMF_SEGMENTATION_ALLOWED in the MQMD) > > PS. I realize/realise that the application could be redesigned to use smaller > messages however that is a different bridge to cross. > > Thanks in advance for your assistance. > > Allen > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
What about MAXMSGL at the qmgr level. Could be large enough to accomodate your message, but too small for your message + the jms envelope. > -Original Message- > From: Hughes, Allen [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 2:11 PM > To: [EMAIL PROTECTED] > Subject: Websphere JMS problem when doing a GET with a large message > > Hope you guys can help... > > Running MQ 5.3 CSD03 > > We have an application that uses Websphere JMS to get messages from one Q and place > them on another Q. > Normally works ok. > > The problem is when trying to read a large message > 8mb. > We get the error > > Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q > > We know this is not the real error as the Q is plenty large enough. The real error > is that the buffer size on the GET is not large enough to retrieve the message. > (This is also alluded to in the corrective action of the 2030 error) > > Normally we would correct this by getting the DataLength from the failed GET and re > issuing a GET with this length in the BufferSize. > > My dilemma is that the developer working on this informs me that within JMS you can > not specify the BufferSize as it is dynamically calculated by the JMS API. > > Has anyone encountered this before and if so how did you resolve it? ( excluding > MQMF_SEGMENTATION_ALLOWED in the MQMD) > > PS. I realize/realise that the application could be redesigned to use smaller > messages however that is a different bridge to cross. > > Thanks in advance for your assistance. > > Allen > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
Jim, Thanks for pointing out the msg is related to the PUT side of the program. The TO & FROM Q'S are identical size. Max Msg Length = 104857600. We are able to put msgs on the Q if we do not use JMS. Cheers, Allen. -Original Message- From: Jim Ford [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 2:42 PM To: [EMAIL PROTECTED] Subject: Re: Websphere JMS problem when doing a GET with a large message Are you sure that you're getting the 2030 on the get? The reason I'm asking is that 2030 is a reason code associated with puts, not gets. While your queue may be "big enough," I would verify that the MAXMSGL parameter for the output queue is also big enough. Generally, this parameter defaults to 4 meg, and if you exceed MAXMSGL your put will get a 2030 reason code. "Hughes, Allen" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] ERBROS.COM> cc: Sent by: MQSeries Subject: Websphere JMS problem when doing a GET with a large message List <[EMAIL PROTECTED] .AC.AT> 09/18/2003 04:11 PM Please respond to MQSeries List Hope you guys can help... Running MQ 5.3 CSD03 We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. Normally works ok. The problem is when trying to read a large message > 8mb. We get the error Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. (This is also alluded to in the corrective action of the 2030 error) Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. Thanks in advance for your assistance. Allen Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Websphere JMS problem when doing a GET with a large message
Are you sure that you're getting the 2030 on the get? The reason I'm asking is that 2030 is a reason code associated with puts, not gets. While your queue may be "big enough," I would verify that the MAXMSGL parameter for the output queue is also big enough. Generally, this parameter defaults to 4 meg, and if you exceed MAXMSGL your put will get a 2030 reason code. "Hughes, Allen" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] ERBROS.COM> cc: Sent by: MQSeries Subject: Websphere JMS problem when doing a GET with a large message List <[EMAIL PROTECTED] .AC.AT> 09/18/2003 04:11 PM Please respond to MQSeries List Hope you guys can help... Running MQ 5.3 CSD03 We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. Normally works ok. The problem is when trying to read a large message > 8mb. We get the error Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. (This is also alluded to in the corrective action of the 2030 error) Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. Thanks in advance for your assistance. Allen Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Websphere JMS problem when doing a GET with a large message
Hope you guys can help... Running MQ 5.3 CSD03 We have an application that uses Websphere JMS to get messages from one Q and place them on another Q. Normally works ok. The problem is when trying to read a large message > 8mb. We get the error Reason Code 2030x'7EE'MQRC_MSG_TOO_BIG_FOR_Q We know this is not the real error as the Q is plenty large enough. The real error is that the buffer size on the GET is not large enough to retrieve the message. (This is also alluded to in the corrective action of the 2030 error) Normally we would correct this by getting the DataLength from the failed GET and re issuing a GET with this length in the BufferSize. My dilemma is that the developer working on this informs me that within JMS you can not specify the BufferSize as it is dynamically calculated by the JMS API. Has anyone encountered this before and if so how did you resolve it? ( excluding MQMF_SEGMENTATION_ALLOWED in the MQMD) PS. I realize/realise that the application could be redesigned to use smaller messages however that is a different bridge to cross. Thanks in advance for your assistance. Allen Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem
take a look at the JNDI configuration.look under "TRANSPORT" property ...u need to make some setting here. -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 10:04 PM To: [EMAIL PROTECTED] Subject: JMS Problem Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive - The information in this Internet email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Internet email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Internet email are subject to the terms and conditions expressed in any applicable governing ING's terms of business or client engagement letter. Visit us at www.ing.com - Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem
When you are running outside of AS, I'm guessing you're not using JMS, i.e. you're using the MQSeries utilities. Therefore since that works, and the JNDI calls are working fine, it seems to be something with the mapping of your JMS queue and connection factory to the MQSeries definitions - this is definitely a little tricky - the web interface isn't the most intuitive. Other things to review are: what JRE are you using? What is the classpath? (Since you mention it works outside of AS, are you developing in WSAD, but will be running as a standalone app, or on the web server?) -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 12:47 PM To: [EMAIL PROTECTED] Subject: Re: JMS Problem I know this is an important question, just forgot to include. We are using V5 of WebSphere. Jeff = Jeff, What version of WebSphere Application Server are you using? Regards, Guy Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem
You may need the MQSeries client to get to the remote MQSeries QM. >>> [EMAIL PROTECTED] 06/25/03 11:08 AM >>> Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem
I know this is an important question, just forgot to include. We are using V5 of WebSphere. Jeff = Jeff, What version of WebSphere Application Server are you using? Regards, Guy Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem
Jeff, What version of WebSphere Application Server are you using? Regards, Guy |-+> | | Jeff A Tressler | | | <[EMAIL PROTECTED]| | | >| | | Sent by: MQSeries| | | List | | | <[EMAIL PROTECTED]| | | N.AC.AT> | | || | || | | 06/25/03 10:04 AM| | | Please respond to| | | MQSeries List| | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: JMS Problem | | | >--| Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
JMS Problem
Hi We have ran into a few problems. We think it is just some small configuration we missed. We are new to the whole JMS / Application Server world. Using the embedded AS in WebSphere Studio, we configured a connection factory and a queue. The queue definition points to a queue manager running on a remote machine. The remote machine has the queue manager running and a queue defined. The queue manager and queue match the configuration in the JMS configuration. The queue manager is running, we have the correct ip address and port number. When we run code outside the AS, the code connects to the queue manager and accesses the queue. When we run the code as part of the AS we get MQJMS 2005 which maps to MQ2059 queue manager does not exist. We have tried setting the properties directly and using the JNDI and we get the same error in all cases. I know this is not much, but if you have any ideas, we would appreciate it. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem(Urgent)
Could you please give some more input how to implement this. Vivek Vhatkar <[EMAIL PROTECTED]> wrote: Use connectionconsumers!! -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 20, 2002 7:32 PMTo: [EMAIL PROTECTED]Subject: JMS Problem(Urgent) HI, I am using a startup servlet in my application for registering listener to a queue. So when a message comes to queue it is picked up by listener and process it. My concern is if there are multiple mesaage appears in queue , the listener process it one by one as queuesession is single threded. So how can i design it so that it will process the message parallaly. NB. I can not use MDB as i am using websphere 3.5.5 Any suggestion is welcome. Thanks, Subhendu Do You Yahoo!?Sign-up for Video Highlights of 2002 FIFA World CupDo You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup
Re: JMS Problem(Urgent)
Use connectionconsumers!! -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 20, 2002 7:32 PMTo: [EMAIL PROTECTED]Subject: JMS Problem(Urgent) HI, I am using a startup servlet in my application for registering listener to a queue. So when a message comes to queue it is picked up by listener and process it. My concern is if there are multiple mesaage appears in queue , the listener process it one by one as queuesession is single threded. So how can i design it so that it will process the message parallaly. NB. I can not use MDB as i am using websphere 3.5.5 Any suggestion is welcome. Thanks, Subhendu Do You Yahoo!?Sign-up for Video Highlights of 2002 FIFA World Cup
Re: JMS Problem(Urgent)
How about this :
Use a single session to get the data out from the message, then spawn a
thread to handle processing of the data. The thread is not aware of any
queues, it only needs to worry about the data parsed out of the message.
My 2 cents.
Vijay
-Original Message-
From: Denilson Nastacio
To: [EMAIL PROTECTED]
Sent: 6/20/02 11:17 AM
Subject: Re: JMS Problem(Urgent)
I don't know if it solves, but you could try and use multiple
javax.jms.QueueConnection objects. I would hope each
one to have its separate sets of resources.
Regards,
Denilson
==
Notes: Denilson Nastacio/Raleigh/IBM@IBMUS
Internet: [EMAIL PROTECTED]
Phone: +1 (919) 224-1743Fax: 919-224-2580
RTP 510/4F47
subhendu mohanty <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/20/2002 10:01 AM
Please respond to MQSeries List
To:[EMAIL PROTECTED]
cc:
Subject: JMS Problem(Urgent)
HI,
I am using a startup servlet in my application for registering listener
to a queue. So when a message comes to queue it is picked up by listener
and process it. My concern is if there are multiple mesaage appears in
queue , the listener process it one by one as queuesession is single
threded. So how can i design it so that it will process the message
parallaly.
NB. I can not use MDB as i am using websphere 3.5.5
Any suggestion is welcome.
Thanks,
Subhendu
_
Do You Yahoo!?
<http://rd.yahoo.com/welcome/*http://fifaworldcup.yahoo.com/fc/en/spl>
Sign-up for Video Highlights of 2002 FIFA World Cup
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: JMS Problem(Urgent)
Hi Gopi, Thanks for reply. But can you give some more information how to implement it. Thanks, Subhendu Gopi Krishna <[EMAIL PROTECTED]> wrote: Hi, Use ConnectionConsumer interface provided with JMS -Original Message-From: subhendu mohanty [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 20, 2002 7:32 PMTo: [EMAIL PROTECTED]Subject: JMS Problem(Urgent) HI, I am using a startup servlet in my application for registering listener to a queue. So when a message comes to queue it is picked up by listener and process it. My concern is if there are multiple mesaage appears in queue , the listener process it one by one as queuesession is single threded. So how can i design it so that it will process the message parallaly. NB. I can not use MDB as i am using websphere 3.5.5 Any suggestion is welcome. Thanks, Subhendu Do You Yahoo!?Sign-up for Video Highlights of 2002 FIFA World CupDo You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup
