|
I found the thread on the JTOpen forums that led to the technique we are using to create a second connection. Apparently, we are using the "copy constructor" of the AS400 class. http://www-912.ibm.com/j_dir/JTOpen.nsf/8178b1c14b1e9b6b8525624f0062fe9f/45CB6BBC5EF457F486256DBF004E9193?OpenDocument I do not think that RSE should know about this connection object we create, nor even obtain a reference to it, so I do not see how it could hand it out. For example, when you do a disconnect in RSE it does not disconnect this connection, we had to add code to listen for the RSE disconnect and do it ourselves. If RSE has a reference to the connection it is likely that it could have disconnected it. All of that being said, at least anecdotally the problems described do sound like you are getting the same connection that we created. This would explain the "timeout" message since we have the connection perpetually in-use if something else tried to use it, it would eventually have to timeout. Perhaps the problem is somewhere deep in the bowels of the AS400 class from JT400? If you want to email me a code snippet of what you do to obtain the connection from RSE and then a sample of what you do, such as run some command, I can see if we can recreate and perhaps resolve the problem. I guess a first step would also be to see if turning off the option to monitor your interactive queue for messages stops the problem from occurring. If it doesn't then the problem must be something else. Mark To wdsci-l@xxxxxxxxxxxx cc bcc Subject [WDSCI-L] Re: RSE Connections Continue To Get Lost or Confused? David Gibbs <dgibbs@xxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 01/15/2004 11:53 AM CST <HR><font size=-1>Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx></font><HR> <font size=-1></font> Mark Phippard wrote: > The QZRCSRVS jobs are the program call/command jobs and is where the bulk > of the work is done (although the spooled file plugin does not use these). > I would guess that the Implementer plugin is running commands and programs, > so it is likely using these jobs. Actually, I worked with Duie on this issue :) Here's what I observed ... for some reason there were TWO (maybe more, I don't completely remember) QZRCSRVS jobs active for his session ... one with the 'iSeries Commands' subsystem library list defined, and the other without. Our plugin simply asks RSE for the AS400 object in order to do issue commands and perform PCML program calls. We assume that the library list defined on the "iSeries Commands" subsystem will be in place. Our requests, however, were being executed on the second QZRCSRVS job ... which didn't have the library list set. > Finally, I believe that our messages plugin will use its own server > QZRCSRVS server job if you use the option to monitor your interactive > message queue. Any chance that this is causing RSE to hand out a new AS400 object (that doesn't have the library list set) when the Implementer plugin asks for it? Of course, if a plug-in asks for an AS400 object, and a RSE decides that a new connection is required, I would expect it to setup the connection properly. david -- David Gibbs Sr. Software Engineer / R&D / MKS Inc., www.mks.com Lombard, IL, USA; tel: 630-495-2108; fax: 630-495-3591 Build Better Software _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.