-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 4/17/15 5:04 PM, Robert Anderson wrote:
Issue fixed:
https://github.com/psi-probe/psi-probe/commit/9f233d0f0ccb02062f2b0947
10897b2a551d0ca5
Thanks
for following-up with this one.
- -chris
-BEGIN PGP SIGNATURE-
Version:
Issue fixed:
https://github.com/psi-probe/psi-probe/commit/9f233d0f0ccb02062f2b094710897b2a551d0ca5
2014-09-04 11:07 GMT-03:00 Robert Anderson ranom...@gmail.com:
2014-09-04 10:57 GMT-03:00 Christopher Schultz
ch...@christopherschultz.net:
I don't know. You could inspect a Subversion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 9/3/14 7:47 PM, Robert Anderson wrote:
Does anybody here use psi-probe for monitoring the Tomcat?
Possibly, but your subject doesn't say anything about psi-probe, so
perhaps it's being ignored by those folks. I think it's more likely
2014-09-04 10:57 GMT-03:00 Christopher Schultz ch...@christopherschultz.net
:
I don't know. You could inspect a Subversion log between the two. It's
no fun, but it will show you what actually changed instead of what was
documented to have been changed.
It's exactly what I'm doing at this
Hi,
In a privileged context, a have the following jsp to test a global jndi
resource:
%@ page session=false import=java.util.*,java.sql.*,javax.naming.*,
javax.sql.*,org.apache.commons.dbcp.* contentType=text/html %
%!
protected void doLookup(JspWriter out) throws ServletException, IOException
can you post your configuration file. that will be the only way we can help
you fix it, as I doubt tomcat will go back to pre 6.0.41 days :)
Filip
On Wed, Sep 3, 2014 at 9:36 AM, Robert Anderson ranom...@gmail.com wrote:
Hi,
In a privileged context, a have the following jsp to test a
On Wed, Sep 3, 2014 at 11:36 AM, Robert Anderson ranom...@gmail.com wrote:
Hi,
In a privileged context, a have the following jsp to test a global jndi
resource:
%@ page session=false import=java.util.*,java.sql.*,javax.naming.*,
javax.sql.*,org.apache.commons.dbcp.* contentType=text/html
Ok! :)
Steps to reproduce:
1)Download and unpack 6.0.39
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.39/bin/apache-tomcat-6.0.39.tar.gz
2) Create a global jndi resouce in server.xml
GlobalNamingResources
Resource name=jdbc/cacheapp auth=Container
type=javax.sql.DataSource
On Wed, Sep 3, 2014 at 11:51 AM, Robert Anderson ranom...@gmail.com wrote:
Ok! :)
Steps to reproduce:
1)Download and unpack 6.0.39
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.39/bin/apache-tomcat-6.0.39.tar.gz
2) Create a global jndi resouce in server.xml
Thanks, Daniel. But my question the question is why that was working in
6.0.39 and the firsts releases of 7.0.x?
Tomcat is not bind in java:global name anymore. Was it a feature request
or is it a bug?
Em 03/09/2014 13:48, Daniel Mikusa dmik...@pivotal.io escreveu:
On Wed, Sep 3, 2014 at 11:51
On Wed, Sep 3, 2014 at 1:09 PM, Robert Anderson ranom...@gmail.com wrote:
Thanks, Daniel. But my question the question is why that was working in
6.0.39 and the firsts releases of 7.0.x?
Hard to say because I don't know the application's code, so I'm not sure
what it is doing. It's a pretty
On Wed, Sep 3, 2014 at 11:09 AM, Robert Anderson ranom...@gmail.com wrote:
Thanks, Daniel. But my question the question is why that was working in
6.0.39 and the firsts releases of 7.0.x?
Tomcat is not bind in java:global name anymore. Was it a feature request
or is it a bug?
Not sure, the
This is the complete code that was working:
https://code.google.com/p/psi-probe/source/browse/trunk/core/src/main/java/com/googlecode/psiprobe/beans/ResourceResolverBean.java
public List getApplicationResources() throws NamingException {
logger.info(Reading GLOBAL resources);
This behavior began in versions 6.0.41 and 7.0.54. Before that, everything
worked as expected.
2014-09-03 15:33 GMT-03:00 Robert Anderson ranom...@gmail.com:
This is the complete code that was working:
Am 03.09.2014 um 20:33 schrieb Robert Anderson:
This is the complete code that was working:
https://code.google.com/p/psi-probe/source/browse/trunk/core/src/main/java/com/googlecode/psiprobe/beans/ResourceResolverBean.java
public List getApplicationResources() throws NamingException {
On Wed, Sep 3, 2014 at 2:33 PM, Robert Anderson ranom...@gmail.com wrote:
This is the complete code that was working:
https://code.google.com/p/psi-probe/source/browse/trunk/core/src/main/java/com/googlecode/psiprobe/beans/ResourceResolverBean.java
public List getApplicationResources()
2014-09-03 16:13 GMT-03:00 Daniel Mikusa dmik...@pivotal.io:
Do you see this being logged?
Yes.
Thanks, Felix. We'll analyze this solution.
On Wed, Sep 3, 2014 at 11:51 AM, Robert Anderson ranom...@gmail.com wrote:
Ok! :)
Steps to reproduce:
1)Download and unpack 6.0.39
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.39/bin/apache-tomcat-6.0.39.tar.gz
2) Create a global jndi resouce in server.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 9/3/14 11:36 AM, Robert Anderson wrote:
In a privileged context, a have the following jsp to test a global
jndi resource:
%@ page session=false
import=java.util.*,java.sql.*,javax.naming.*,
javax.sql.*,org.apache.commons.dbcp.*
Does anybody here use psi-probe for monitoring the Tomcat?
I just wanna know what changed in JNDI implemention of Tomcat. Where is the
request in the bugzilla?
Chris, global datasources (java:/name) and application datasources
(java:/comp/env/name) are differents in probe.
Application
20 matches
Mail list logo
