I don't find any code path that would cause that to happen, so I'll need a test case that recreates the problem.
Rick On Wed, Jun 3, 2009 at 6:28 AM, Rony G. Flatscher <rony.flatsc...@wu-wien.ac.at> wrote: > Rick McGuire wrote: >> Are you loading this by registering the instance in memory, or by >> explicitly requesting a library to be loaded? > The library gets loaded via Java once. > > Then, whenever a Rexx instance is created in native code via JNI, the > optionName "REGISTER_LIBRARY" is used to register the functions in the > in memory library. > > In the reported case five different threads will go through this path as > one Rexx interpreter instance will be created for each thread. > >> And if you'd like a fix, the appropriate means for requesting that is to >> open a bug report. >> > Well, I have not been sure whether this is a bug or intentional. > > Before going the long haul in creating and setting up a showcase, > splitting the archive and uploading the chunks, just to learn later, > that it was not a bug in the first place, I prefer to just simply ask > here before doing that. > > Also, sometimes it may be already sufficient to describe what happens, > saving the need to create a showcase (which in these cases take quite > some time to create). > > Finally, I am not sure whether it would be preferable to have functions > registered at a per Rexx instance level, rather than process global. > > However, if it is a bug according to the design specs, I would file a > bug report, trying first to describe the code-path, hoping that this is > sufficient already (to safe the time to create an own showcase, if > possible). > > ---rony > > >> On Wed, Jun 3, 2009 at 2:45 AM, Rony G. Flatscher >> <rony.flatsc...@wu-wien.ac.at> wrote: >> >>> Just for the record: currently, rev. 4751, debug version, when creating >>> Rexx interpreter instances on different (Java) threads on Windows, the >>> loader function of BSF4Rexx gets loaded for each thread. This behaviour >>> may be fine (actually I would prefer it), however, I think that in the >>> past a DLL was supposed to only be loaded once in a process, hence >>> reporting it. >>> > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
