I am trying to learn how to use Chainsaw. I have a text log4j file in SystemOut.log with rolling files. I set the file URL in a file pattern receiver to file:///C:/AppDev/prodlogs/SystemOut.log which is where I copied production logs to. The pattern is [TIMESTAMP] THREAD * LEVEL [*] (FILE:LINE) - MESSAGE. Timestamp format is MM/dd/yyyy HH:mm:ss:SSS EDT.
Yet, when I set all of this. Nothing happens. No tabs pop up, even if I restart the receiver or try to manually use the File->Load Log4j File menu. No errors pop up or anything. Just...nothing.
What am I doing wrong?
I don't really know why it doesn't work, yet it's been a while now that Chainsaw didn't receive any update: the last version v1.99.99 was built in 2006.
I would recommend using something like LogMX (or some of its clones) instead. You simply have to put your Log4j pattern (or any other pattern) in its configuration (i.e. new "Parser") to be able to parse, view, filter, search, monitor in real-time, ... (don't need to purchase a license, the free version already does more than Chainsaw in my opinion).
Try the latest developer snapshot of Chainsaw, available at http://people.apache.org/~sdeboy
There are a lot of new features in the developer snapshot.
Are you using a pattern layout? I assume so. Chainsaw has built-in support for log4j's pattern layout.
Select 'process a log file' from the 'Load Chainsaw configuration' menu item.
specify the log file URL
change the 'log file format type' to PatternLayout
specify the pattern layout
specify the timestamp format
Choose the 'always start Chainsaw with this configuration' or just save the configuration off as an xml file so you can use it later from this same dialog (just select the 'Use a chainsaw config file' option if you reload this config.
If you still have problems, feel free to include a few lines of your log file.
Related
I need to add version info and retrieve it from the CHM file to make it possible to make an alert message to a user about a new CHM-file version available and downloaded.
It means, that I should compare versions of CHM on different machines (Server and clients).
The other way is date and time checking, but I should remember about time zones, so this is complicated, because also one should remember about different file systems, according to Windows SDK help about SetFileTime function and FILETIME structure.
If someone knows the trick - please share.
.chm files don't have version information. You will need to find some alternative way to mark the file version.
One way that occurs to me is to include a topic in the help file that contains the version. I imagine that this topic would be hidden, that is not linked by any other topic, not in the table of contents, etc.
All that remains is for your application to be able to read that topic from the help file. I'm sure that can be done with a .chm file parser, if you can obtain one. Perhaps more easily you can get the platform browser to read the topic for you. You can use IHTMLDocument2 to read a URI like this:
mk:#MSITStore:C:\somedir\somefile.chm::/html/SomeTopic.html
As far as I understand, APEX 5.1 does not support Excel files to be loaded into tables.
I found this package that seems to make it possible to SELECT from Excel files, but it does not show how to use it with, for example, files loaded via the "File Browse" Item.
Now, I am very new to this environment, so please explain it from the beginning.
What I did is I upload the package script to the SQL workshop and executed it, without errors. But now?
APEX 5.1 doesn't support it out of the box, but you can use the EXCEL2COLLECTION plugin (available here).
It is very straightforward, just create a file browse page item with an upload button which calls an onsubmit process (e.g. CreateCollection) of type Excel2Collection[Plug In] - specify the file browse item, a collection name and the CSV separator, then you can do as you please with the data (e.g. you may want to run some validations on the data then insert it into a table where you can access it as normal).
As per the documentation, DailyRollingFileAppender will do the file rolling at midnight of each day. But, if we close the appender and open the new appender for same log file, then it roll over the existing file and creates the new one. My requirement is, to reuse of the existing log file instead of rolling the log file. Please someone help me to achieve this.
Thank you for your advanced help
This is basically a historical behaviour. Recently a contributor has added a RollOnClose property the appender on 1.2.x branch that allows you to turn this behaviour off.
I ran into my first Core Data versioning problem - learn something every day!
Following instructions found here, I made a new version of the model, added the code for lightweight migration, and then went to set the active version…
Uhhh, where do you do that? The docs don't actually say, and other threads here talk about "click on the main file". WHAT "main file"?
The original xcdatamodel has no version number in it. Is that a problem? Is the Migration Manager still going to be able to figure this out?
All I did was add a field, this seems like a lot of work…
Core Data model files don't use version numbers. The files might include a number in their name, but that's for people to see, Core Data doesn't care about it. It uses entity hashes to compare models.
The "main file" is the .xcdatamodeld that contains all the versions (which have names ending in .xcdatamodel).
Select that then look in the file inspector pane on the right. It has a pop-up menu that you use to select the current version.
I am developing an add-on installer using Installshield 2011 and project type is Basic MSI. I got a requirement where i need to update app.config file; the mentioned app.config is not part of current installer; app.config will be available by installing the base product. And on top of this my add-on installer will update the app.config file.
I am using XML File Changes feature provided by Installshield, i have configured it in the following steps:
Import the updated app.config file under XML File changes view.
Create a new element and assign key and value to it.
Repeated 1 and 2 and added 7 to 8 new entries as per the requirement
During testing i am seeing that the app.config file has been updated but entries are in single line instead of one below the other. I cannot enable "Format XML after changes" because one of the service which is referenced to app.config is not working and when i revoke the option services runs perfectly.
Is there any workaround/option to tell/ask installshield insert xml tag one below the other not in sinlge line using XML File Changes?
Thanks,
Chetan
If XML Changes isn't formatting the document in a way that's acceptable, you could consider using the Text File Changes which is just a simpler search and replace without understanding the schema of XML. Otherwise options are to check out Windows Installer XML ( you can use the XmlConfig elements found in the Util extension in a merge module and then use that merge module in InstallShield ) or to just write your own custom actions.