Is this a Caché Online Backup? If so, and if the system is active while the backup runs, multiple passes have to be done in order to capture a single-point-in-time record of the database. This means that some of the blocks of the database appear multiple times in the backup file.
Looking at the logfile produced by the backup should give you more information.
Using the extra info from Dinesh, here's what I did to investigate. Admittedly I was on a 2015.1.0 Ensemble on Windows, but the classes are unlikely to have many differences between this and his 2015.1.2 on Solaris.
First I cleared the read-only flag on the CACHELIB database that stores %Net.HttpRequest:
Then I loaded the class into Studio (for safety I set the read-only checkbox during opening), compiled it, used the View\View Other Code option (Ctrl+Shift+V) and jumped to the line of the error Dinesh reported.
I reset the "Always Mount Read-Only" checkbox on CACHELIB, to prevent accidental changes.
In the code several things caught my eye:
Maybe disable the GZIP feature on your SOAP adapters and see if the problem persists. Searching the InterSystems doc for the term GZIPOUTPUT may give you clues (I'm no expert in this area).
I also recommend you ask InterSystems Support (WRC) for help on this, particularly as you're running on a less common platform (Solaris).
What Ensemble version(s)? And what NLS Locales? On more recent Ensembles you can get both these pieces of information via the About link at the top left of Portal:
Thanks Dave. For the benefit of DC readers, here's what the "big red warning" looks like:
Thanks Mark. I'm going to accept Dave's answer, but I appreciate your prompt response too.
You might have been able to monitor progress by running the JOBEXAM utility from another session connected to the %SYS namespace.
That's interesting Jeff. I wonder if you were on the "Developer Community FAQ" page of DC when you clicked the "Create New Post" button? If so, it looks like that'd pre-populate the tag field in the way you reported. @Evgeny Shvarov, maybe this case could be treated as an special case by the DC software, stopping it from proposing the "Developer Community FAQ" tag.
That screenshot doesn't seem to have been taken when the system had run out of licenses. Are you able to get the info when that has happened? And the other license usage pages may be useful as well.
Ultimately though, you may need help from InterSystems support (aka WRC).
Have you set a Source Control Class for the namespace that your Studio is connecting to whenever you start it? If so, perhaps a method in that source control class is spawning a lot of processes.
What Cache version are you running?
Can you use Portal's License Usage pages (under System Operation) to discover more about what's using all your licenses?
I'd be interested to hear why you want to know this.
Jeff, using moderator superpowers I have removed the tag "Developer Community FAQ" from your posting. That tag is intended only for frequently asked questions about this DC platform itself. Please don't tag other posts with it.
Thanks Mike. Knowing your version lets us confirm that the Export method has the capabilities Pete described. Here's a version-specific link.
Joe, using my DC Moderator superpowers I have removed the "Developer Community FAQ" tag from your post. That tag is intended for FAQs about how to use the DC platform.
What Caché version are you working with?
Good work! I like the changes.
@Thembelani Mlalazi - when mentioning a DC member in a post it looks like you're copying and pasting the member name in a way that carries over a hyperlink. That hyperlink markup seems to prevent the DC software from recognizing the user. I recommend using the Preview button as a way of checking that the "mention" syntax is correct.
In any case it may be overkill to mention someone who has already contributed to the thread, since they typically get notified of updates unless they have deliberately unsubscribed.
Have you read the documentation at http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY… ?
If so, please be more specific about what you're trying to do and where you're getting stuck when following the documentation.
With %Library.Integer you can set MINVAL and MAXVAL parameters on your property:
From http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…
To ensure Caché the needed access to all instance database, journal and log files that are outside the Caché installation tree, grant the Cache_Instance_instancename group full access to these files and the directories containing them.
(my highlighting)
Also, remember that in DC you can comment on an answer (like I am doing here) rather than posting your response as though it's another answer.
Looks like the method first appeared in 2014.1.
I'm not aware of the same facility being available earlier than that version, either in a utility routine or as a class method.
If you have access to a 2014.1 or later you could try back-porting the code.
Joyce, I noticed that the HTML of the page you pointed us to has the following minor bug:
<title>Atelier 1.0 Beta Update</title>
What is the $ZV string of the "older version" where you're trying to get this information?
Mike, if you're able to post any more details of your approach it might be useful.
Thanks for your reply Mark. Presumably you want to keep ^oddCOM small because it gets referenced at runtime, and smaller means faster.
How about giving us a compile-time choice about this, akin to the "k" option to keep INT source?
Or adding a property to %Dictionary.CompiledMethod called, say, ActualImplementation, whose stream you'd initialize in a property-get method? Perhaps you'd load the stream my running the relevant generator code, like Paul Waterman suggests in his comment on this post.
That's an interesting suggestion Paul. I might try it out.
Anyone else know if the method generation code always goes into the .G1 routine? Or does it overflow into a .G2 at a certain size?
Dominic, I guess you meant to point us the %GO and %GI utilities, but omitted the % character.
To prevent the "internal" Apache instance from starting up when Caché starts, go to System Administration, Cponfiguration, Additional Settings, Startup and change the WebServer setting to false.
I'm not aware of any built-in ability for a Caché startup to start a different Apache instance.