Some Subversion clients (TortoiseSVN, Subclipse) can present some nice
options for integrating with issue trackers.

# bugtraq:append = false
# bugtraq:label = Issue ID:
# bugtraq:message = Issue ID:
# bugtraq:number = true
# bugtraq:url = http://code.google.com/p/psi-probe/issues/detail?id=%BUGID%
# bugtraq:warnifnoissue = false

See http://tortoisesvn.net/issuetracker_integration for more information.

AccessorFactory throws an exception if using probe with JRE 1.6 (Apple) on
OSX 10.5.7.

What steps will reproduce the problem?
1. Use OSX 10.5.7
2. Use Apple JRE 1.6.0_07-b06-153 (delivered with system)
3. Access the "Threads" page

What is the expected output? What do you see instead?
java.lang.RuntimeException: Could not determine JVM version.
    at
org.jstripe.tomcat.probe.tools.AccessorFactory.getInstance(AccessorFactory.java:
32)

What version of the product are you using? On what operating system and
browser?
2.0.0-SNAPSHOT, SVN 39

Please provide any additional information below.
The way the jvm provider is determined is error prone.
E.g. in this case, it checks for "Apple Computer", but the vendor in Apples
1.6 JRE is "Apple Inc.".

What is the vmVendor check good for? Isn't it enough to just check the version?

Probe now supports viewing 'all servlets' or 'all servlet mappings'. This
is done by removing the 'webapp' parameter from the URL when viewing
servlets or servlet mappings.
I think it would be wise to place a link to the pages that show all
servlets and mappings of all applications.

Purpose of code changes on this branch:
r24: "a jsp that displays cumulative average response time of all applications"

When reviewing my code changes, please focus on:
The commit message says that this feature is "an initial draft version."

What steps will reproduce the problem?
1. Go to the Log tab and open any log file.

What is the expected output? What do you see instead?
Line position is always 1 even after scrolling to the last and turning 'pause 
tailing' option off. 

What version of the product are you using? On what operating system?

Windows XP, Google Chrome 2.0.177.1

We should provide instructions on the wiki for how to set up the project in
Eclipse.

What steps will reproduce the problem?
1. Enable auto-deploy.
2. Upload a .war file for deployment.
3. Get lucky.  (It only happens if the auto-deploy triggers during the copy
operation which moves the .war file from the upload location to the
deployment location.)

Proposed solution:
Move the file instead of copying it and then deleting it.

Original report: http://www.lambdaprobe.org/forum2/thread.jspa?threadID=462

Purpose of code changes on this branch:
r9: "added an initial version of application stats charts and stats collector"

When reviewing my code changes, please focus on:
The commit message says that this feature "needs to be worked on."

The graphics and the color themes need to be updated to reflect the
project's new name.

Request for enhancement:

Add the ability to monitor HeapSize, PermGen Space etc. and inform by email
if limits are exceeded

Purpose of code changes on this branch:
r27: No log message.

When reviewing my code changes, please focus on:
The commit message doesn't say what changed.  Find out what changes were made.

What steps will reproduce the problem?
1. put commons-logging-xxx.jar to classpath (\lib\) 
2.
3.

What is the expected output?

see log4j log content at psi/logs/index.htm

What do you see instead?

exception in probe.log:
Could not interrogate context logger for /appname. Enable debug logging to 
see the trace stack

What version of the product are you using? On what operating system and
browser?


Please provide any additional information below.

We should provide instructions on the wiki for how to set up the project in
NetBeans.

Purpose of code changes on this branch:
r17: "modified session list screen to display sessions of all web
applications if a webapp parameter is not specified"

When reviewing my code changes, please focus on:
The commit message says that this feature is "not final."

1. Open up probe
2. View an application. The two charts should be visible on this page.
3. Stop the application using the stop button.

The 'runtime information' table is now disabled, and this message is shown:
"This application is not running, runtime information is unavailable"

However, both statistics charts are still visible. This should not be
possible because the application is turned off.

Which feature would you like to see enhanced?
Deployment through .war file upload.

Please describe the enhancement in detail.
Add a checkbox that will "close this window after successful deployment." 
If checked and the deployment succeeds, the window (tab) will be closed via
Javascript.  If checked and the deployment fails, the window will stay open
and display the error as normal.

How will this enhancement make Probe better?
It will allow someone to focus their attention elsewhere (e.g. to other
browser tabs) while the deployment occurs and not have to come back and
clean up when it finally finishes unless there is a problem.  You see this
option a lot in desktop software which performs lengthy operations. 
Usually, it will "close this program" or "shutdown the computer" when the
operation is done.  This is the equivalent for a web application.

On OSX 10.5, there is no jdk 1.4 available.
Therefore, you can't compile the project on this platform.

The question is:

Is anyone using JDK 1.4 still? No one uses it, shouldn't this module be
dropped?

Another approach could be to:
- deliver the precompiled jdk14-<version>.jar with the project in the
web/src/main/resources dir. 
- With this, you can still work on jdk14 by directly executing
jdk1.4/pom.xml (mvn -f jdk1.4/pom.xml), but we leave it out of the module
definition in the main pom and remove the dependency in web/pom.xml.

The Application Information page displays the session timeout as defined in
web.xml.  The value is displayed with seconds as the unit, but it should be
minutes.

From the Lambda Probe forums:
http://www.lambdaprobe.org/forum2/thread.jspa?threadID=492

web/src/main/webapp/CHANGES.txt doesn't hold the actual progress

It would be helpful to have a manual purge or reset of all connector stats 
on the fly. Maybe a button on the stats page or something.  It would be 
nice to do this without having to re-deploy the webapp. 

This would help me take some accurate performance snapshots during certain 
time periods.  For example I'd like to get some specific metrics for the 
11am - noon hour since it is our busiest time of the day.  The longer 
probe runs the less accurate I find the numbers to be.
Thanks,

Revisions r5 through r30 need to be reviewed and tested.  Pay particular
attention to revisions which no comment or have phrases like "not final,"
"draft," "to be improved," "in progress," or "incomplete" in the comment:

r14, r17, r24, r26, r27

Use the code review feature in the Source tab to vote and comment on these
revisions.  For testing, update to that specific revision, build, and test.
 Bear in mind that some features are updated in cumulative revisions.

[deleted issue]

It would be great to have jconsole like functions within psiprobe.
Mostly you do not get the ports open on production machines for JMX,
therefore it would fit perfectly to this app.

BTW: Great idea to fork the dead lambdaprobe and continue to work on it!

Several property names have changed, and some new properties have been
added.  The translations may need to be updated, but we need to know what
we're missing first.

Brazilian Portuguese has already been evaluated (issue 44).  Remaining
languages are German, French, Japanese, and Russian.

What steps will reproduce the problem?
1. Open the Log tab and view any log file.

What is the expected output? What do you see instead?
the XMLHttpRequest to logs/ff_info.ajax returns the last modified date of 
the log file. Ever the last modified date is the same as previous, the next 
request XMLHttpRequest (logs/follow.ajax) returns the same part of the log 
file again and again (every 3 sec?). It's better to check if last modified 
date was changed and only after that send the logs/follow.ajax request. 

What version of the product are you using? On what operating system?
psi-probe version 1.7b, Apache Tomcat/6.0.14 on Linux, 

Uploading and deploying a .war can sometimes take a while.  The upload
should be AJAX-ified, display a progress bar, and display an activity
indicator to show the stage of deployment (undeploying, discarding work,
deploying, compiling JSPs, etc.)

It's too small. Is it possble to set it to 12x by default as 

main.css

#file_content {
    width: 100%;
    overflow: auto;
    font-size: 12px;
    white-space: nowrap;
}

May be write changed font size to cookies like the language?

@VERSION@ in probe.jsp should be replaced with current version number,
previously defined in build.properties (deleted), now defined in pom.xml. 
There may be a Maven task which can do this.

The server's uptime is already displayed, but not the uptime of each
context or when the context was last deployed.

The "last deployed" timestamp could be determined by the creation time of
the context's path on disk.  The uptime would be either (1) the difference
between the current time and the deployment time or (2) the server's
uptime, whichever is smaller.

Purpose of code changes on this branch:
r14: "modified application summary to refresh runtime info periodically"

When reviewing my code changes, please focus on:
The commit message says that this feature is "not final."

The entire project needs to be re-structured so it's IDE-agnostic.  The
interdependencies will still need to be expressed, perhaps through Maven.

I would like the ability to have a configurable parameter to set all probe 
traffic to "ignore".  This setting would keep all Memory, Thread, Request 
and error data related to probe from being presented in the numbers.

This would help tremendously when trying to establish benchmarks and 
performance metrics for a specific webapp.  For example if I need to study 
webapp1 when I launch probe all the numbers spike due to the heavy amount 
of requests that probe has to make.  Eliminating this traffic would give 
me a more accurate measure of the webapp being studied.
Thank you,

Purpose of code changes on this branch:
r26: "consolidate multiple web applications stats in a single chart"

When reviewing my code changes, please focus on:
The commit message says that this feature is "to be improved."

psi-probe should be able to display and edit global as well as
application-local datasources for Tomcat.

1. Display global and application-local resources on the same page.
2. Allow defining / redefining / undefining global datasources and JNDI
bindings.
3. Allow defining / redefining / undefining resource links and
application-local datasources for applications that are not defined in
server.xml.
4. Provide for creating application-local datasources and resource links
for an application at deploy-time; the need for this step can be detected
by looking for the resource-ref elements in web.xml.

Initial discussion:
http://groups.google.com/group/psi-probe-discuss/browse_thread/thread/44e819315c
9d8580

What steps will reproduce the problem?
1. Log into probe, go to the LOG tab and click any log file.

What is the expected output?
I expect to see the actual log output.

What do you see instead?
The last line is always duplicated after every refresh. This might lead to
confusion. I thought my logs where duplicated, but it's a glich in the Ajax
or something, because the physical files are correct.

What version of the product are you using? On what operating system and
browser?
PSI-Probe 1.7b

The context name should be determined by using the first defined value
encountered from among these sources:

1. The value defined in the "context name" field of the deployment form.
2. The path attribute of the context element in META-INF/context.xml.
3. The name of the .war file.

If a value is supplied for the context name that does not match the path
attribute in context.xml, a warning/error should be displayed.

Some UI elements, such as labeled checkboxes or radio buttons, may be
introduced to help make the options more obvious...

Context name:
o Determined from .war file name
o Determined from META-INF/context.xml
o User-defined: [_________] (ex. /dummy)

From Robert Oschwald:

To use the buildnumber-maven-plugin, you must fix your urls. They are
currently wrong. You must change to:

<scm>
  <connection>scm:svn:https://psi-probe.googlecode.com/svn/</connection>

<developerConnection>scm:svn:https://psi-probe.googlecode.com/svn/trunk/</develo
perConnection>
  <url>scm:svn:https://psi-probe.googlecode.com/svn/</url>
</scm>

Please describe the feature you would like to see added.
The ability to store settings locally, perhaps to a user's home directory.

How will this feature make Probe better?
If configurable settings are not persistent, they would have to be
re-entered after Probe or Tomcat is restarted.  This feature would allow
user settings to persist through a Probe or Tomcat restart.  At least one
proposed feature would be nearly unusable without this (see issue 14), and
it opens up the possibility for additional features which require some
level of configuration.

Hi,

I've sent to Vlad Ilyushchenko a Brazilian Portuguese translation of Lambda
Probe back in 2007, it seems it did not make into a newer version of Lambda
because there were no newer version of Lambda after I sent the patch :(

I've come across this project after MuleSoft announced GA of their Tcat
Server on TheServerSide
(http://www.theserverside.com/news/thread.tss?m=c.reply&thread_id=58164).
Their server is based on Lambda and made me remember it after a long time...

I'm attaching the translation in this issue.

Thank you for keeping the project alive :)

readme.txt should state:

- Environment needed to compile the project
- Environment variables needed
- Runtime env needed

Currently, on an IBM JDK, you have to open a port and turn jmx console 
authentication off to run psiprobe. This is absolutely unacceptable in a 
production environment for security reasons.

Example:
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=11111
-Dcom.sun.management.jmxremote.authenticate=false

The workaround is to firewall the port... assuming all the badguys are 
outside your network (not true).

Using IBM JDK6_64 on AIX

a nice fix would be to put username/password in a properties file somewhere 
or as system properties passed to the vm

History graphs like in Memory utilization has only 2 hours history time
frame. It would be nice to have larger history, for example 2 days. 

It could be simply parametrized by define on tomcat command line (for
example -Dhistory.timeframe=t) or better/later in probe web UI.

In general, Java code other than the JRE should not depend on sun.*
packages, as they are subject to change.  These dependencies ought to be
removed.

These references only exist in the jdk1.4 and jdk1.5 sub-projects.  Project
restructuring is addressed by issue 2.

Issue 3 took care of associating revisions with issues.  Now we need a
post-commit hook that ties issues back to revisions.

Which feature would you like to see enhanced?
Deployment through .war file upload.

Please describe the enhancement in detail.
On the deployment page, an option should exist to perform a distributed
deployment.  Probe could also display warnings based on the user's
selection and whether the .war file is <distributable />.  It will likely
use JMX.

How will this enhancement make Probe better?
Tomcat's FarmWarDeployer doesn't work and there are currently no plans to
fix it.  If you want to deploy to a Tomcat cluster, you must deploy to each
container individually.  Implementing this enhancement would make that
process much faster and more convenient.

The Oracle JDBC driver, ojdbc14.jar, is bound by Oracle's distribution license:
http://www.oracle.com/technology/software/popup-license/distribution-license.htm
l

We need to answer these questions:
- How exactly does this license affect our work?
- Will Probe still work if we remove the .jar from the packaged .war?
- Should we remove the .jar from the repository, too?
  - If we need to remove it, we'll have to reset the repository and
re-import it without that .jar file to remove it from the history.
  - If we leave it, will the Oracle license have to apply to our source?

jdk, log4j, and commons logging all have a mechanism for controlling the
logging level.

jdk: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, OFF
log4j: ALL, FATAL, ERROR, WARNING, INFO, DEBUG, TRACE, OFF
commons: fatal, error, warn, info, debug, trace

It would be very convenient to have a feature where the logging level is
editable via the web UI.  Any changes would persist until the corresponding
logger is destroyed, presumably when the context is reset or redeployed.

This feature could also include a mechanism to "restore defaults," which
would reset all logging levels to their original settings, as defined by
each application.

Notes:
It appears the "org.apache.catalina.logger" package was removed in Tomcat 5.

References:
http://java.sun.com/javase/6/docs/api/java/util/logging/Level.html
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html
http://commons.apache.org/logging/commons-logging-1.1.1/apidocs/org/apache/commo
ns/logging/Log.html
http://tomcat.apache.org/tomcat-4.1-doc/catalina/docs/api/org/apache/catalina/lo
gger/package-summary.html

The error page should include links to
- discussion group: http://groups.google.com/group/psi-probe-discuss
- issue entry page: http://code.google.com/p/psi-probe/issues/entry

[deleted issue]

The class org.jstripe.tomcat.probe.controllers.deploy.UploadWarController
contains a reference to the property "probe.src.deploy.war.notinstalled"
which does not exist.