date:20100702

Re: using Servlet Filter to rewrite domain of JSESSIONID cookie?

2010-07-02 Thread André Warnier

Christopher Schultz wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nikita,

On 7/1/2010 6:37 PM, Nikita Tovstoles wrote:

I borrowed sub-domain from Google Analytics terminology. I have one
server, running one tomcat instance with one virtual host. That host is
running one app - a JS/html widget that is embedded on multiple sites.

We need to track usage per-deployment (per site embedding the wiget). For
(google) analytics purposes, the easiest way to do so is to have a different
(sub)domain per deployment. So the same tomcat instance is responding to
requests for site1.widget.com, site2.widget.com, etc.

a user may interact with 2 widget deployed on 2 different sites (and thus
served from different (sub)domains) within 30 minutes. It is for this case
that we want user to share the same HttpSession:

- go to some site A where our widget is deployed at site1.widget.com
- go to some other site B where our widget is deployed at site2.widget.com
- reuse the same JSESSIONID because its' domain is set to .widget.com

This sounds like a job for a non-JSESSIONID cookie that is created from
your own code.

But I am still lost as to what you are calling sites and subdomains and deployed at
site1.widget.com.

If I follow the explanation above, you have something like this :
Host name=localhost appBase=webapps
Aliassite1.widget.com/Alias
Aliassite2.widget.com/Alias
Aliassite3.widget.com/Alias
Aliassite4.widget.com/Alias
...
/Host

Is that it ?
And if so, where is the widget-webapp deployed (on disk), and how many times
really ?

I am not trying to be a pedant, just to make sure I understand the layout, so that we
might maybe come up with a suggestion to solve your problem (even if it is not by changing
the JSESSIONID cookie domain)

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: SSL and non SSL configuration on tomcat 6.0.26, confused

2010-07-02 Thread Pid

On 01/07/2010 20:11, John-Paul Ranaudo wrote:
 I wish I could provide more information. At least I have narrowed down
 the problem. I am having a meeting with the architects of both
 frameworks today so perhaps I'll get some details.

Given some examples of URLs that fail, and bits of code/HTML/JSP that
are relevant would be a start.


p

 Thanks.
 
 On Thu, Jul 1, 2010 at 2:54 PM, Pid p...@pidster.com
 mailto:p...@pidster.com wrote:
 
 On 01/07/2010 19:38, John-Paul Ranaudo wrote:
  I did more tracing and remote debugging and I was mistaken (too many
  late nights). Each framework is sending us the request via port
 80. The
  problem comes from the fact the one of the frameworks uses HTTPS
 before
  the load balancers so when we send back a redirect it is using the
 wrong
  scheme. HTTP instead of HTTPS. I need a way of knowing which framework
  made the request so I can alter the scheme on redirect for just
 the one
  framework.
 
  btw, the frameworks are proprietary and much like existing portal
  frameworks.
 
  So I am wondering if I can do this with virtual hosts or somehow
 detect
  the incoming URL to tell which domain its coming from and handle
  appropriately.
 
 I wondering too, but mostly because you're not really giving us any real
 information about what's happening.
 
 The word 'framework' might mean something specific to you, but it
 doesn't help me understand what's happening on your server(s).
 
 We can't help you without accurate and detailed information.
 
 
 I /guess/ that virtual hosts won't help you.
 
 I /guess/ that the domain it's coming from won't matter so much as the
 domain requested.
 
 
 p
 
 
 
  On Thu, Jul 1, 2010 at 11:31 AM, Pid p...@pidster.com
 mailto:p...@pidster.com
  mailto:p...@pidster.com mailto:p...@pidster.com wrote:
 
  On 01/07/2010 16:01, John-Paul Ranaudo wrote:
   I am confused no doubt. What you say here is correct:
  
   /In your description of the issue so far, you've said that the
   application *is* using SSL.  The load-balancers might be
  terminating it
forwarding unencrypted connections/
   /
   /
   /I think I understand what you mean by redirecting. Our current
   configuration. Framework A does not use SSL thus uses connector
  port 80.
   Framework B, the problem, uses SSL/port 443. /
 
  It might help illuminate matters if you explain exactly what
 Frameworks
  A  B actually are.  Are they separate web applications?  How
 do they
  relate to each other, are they on separate URLs?
 
   Connector port=80 protocol=HTTP/1.1
 connectionTimeout=2 /
   (Used by framework A)
   Connector port=443 protocol=HTTP/1.1
 connectionTimeout=2
   scheme=https secure=true / (Used by framework B)
  
   Now I could change the port 80 connector to have a redirectPort
   attribute like so:
  
   /
   Connector port=80 protocol=HTTP/1.1
 connectionTimeout=2
   redirectPort=443/
  
   The problem with this approach is that framework A which
 does not use
   SSL now will use it via he redirect port. We'll then get the
 same
  mixed
   content warnings in the browser.
 
  It won't use it unless it's told to.  So what's telling it to?
 
  As far as I can see, there's nothing stopping the whole site
 running
  under 443, which would prevent you seeing mixed content errors.
 
  Have you identified exactly which resources are being served
 via HTTP
  within an HTTPS page?  What are they?
 
 
  p
 
   I hope this explains the problem more clearly.
   /
   /
  
  
   Redirecting as I explained below just means that you can
  upgrade to
   HTTPS for specific paths.  The load-balancer still
 handles it.
  
  
If we use anything that forces SSL it will fail for
 the other
   framework which does
not use SSL.
  
   Why?
  
   How are you switching back to HTTP for 'the other
 framework',
  once the
   user has been on a page served under HTTPS?
  
  
   p
  
  
On Thu, Jul 1, 2010 at 3:59 AM, Pid p...@pidster.com
 mailto:p...@pidster.com
  mailto:p...@pidster.com mailto:p...@pidster.com
   mailto:p...@pidster.com mailto:p...@pidster.com
 mailto:p...@pidster.com mailto:p...@pidster.com
mailto:p...@pidster.com mailto:p...@pidster.com
 mailto:p...@pidster.com

Re: Tomcat 6.0.26 with Java 6 update 20 on Sun Solaris 5.8 Sparc - Web application unable to execute properly

2010-07-02 Thread Mikolaj Rydzewski


On 07/02/2010 01:23 AM, rahul wrote:
1. I tried building the war in Windows and worked fine. I transferred 
the war to UNIX, it mis-behaves as described earlier.

2. I tried building the war in UNIX, it mis-behaves as described earlier. I 
transferred the war to Windows and it worked fine.
   


I guess there are jsp:include page / and %@ include file % 
directives in you webapp. Check them for case sensitivity.



--

Mikolaj Rydzewskim...@ceti.pl


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

JNI error under tomcat: java.lang.UnsatisfiedLinkError

2010-07-02 Thread dennis ch

Hi,

I have a java class (eval.java) that invokes a native method in an so file
(libmodel.so, using SWIG 1.3.29 to generate JNI code/wrapper and compiled
the library). I can use System.loadLibrary() to load the libmodel.so without
any error (-Djava.library.path=/usr/lib), and the native method initModel()
works fine as a standalone application.

However, when I deploy it as a web service (tomcat 6.0.26 + axis2 1.5.1 +
eclipse jee helios) to call the native method, I got the following error
(the first line means the .so was successfully loaded):

Load library successfully

[ERROR] com.model.modelJNI.initModel()V
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)
at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.UnsatisfiedLinkError: com.model.modelJNI.initModel()V
at com.model.modelJNI.initModel(Native Method)
at com.model.model.initModel(model.java:13)
at com.webservice.run(EvalVita.java:763)
... 25 more


Below is the body of Eval.java:

import com.model.*;

public class Eval {

  static void loadModel() {

try {
System.loadLibrary(model);

System.out.println(Load library successfully);

} catch (UnsatisfiedLinkError e) {

System.err.println(Native code library failed to load. + e);

}
  }
  public void run() {

loadModel();
model.initModel();
  }
}


Do I miss anything here?  Any input is appreciated!

Dennis

Re: [OT] Using httpd's mod_rewrite with mod_jk

2010-07-02 Thread André Warnier

Christopher Schultz wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rainer,

On 7/1/2010 4:54 AM, Rainer Jung wrote:

Usually mod_rewrite is perfectly compatible with mod_jk. I must confess,
that I'm not 100% sure about the case, where you try to rewrite a
request that originally would have been handled by mod_jk to something
that should not be handled by it.

It appears that my setup (rewriting a request that normally would go to
jk to one that shouldn't go to jk) still ends up being handled by jk.

Christopher,

I personally find it hard to visualise when exactly in the Apache request handling cycle
the JkMount directive intervenes. Like, /before RewriteRule/ or /after RewriteRule/.
I am sure that it is at a very specific place in the cycle and with a very specific
precedence, but neither the Apache httpd nor the mod_jk documentation explicitly indicate
this (*). (Unlike, for example, in this page, where the precedence is clear :
http://httpd.apache.org/docs/2.2/sections.html#mergin)

And if even Rainer isn't sure..

That is why, with Apache/mod_jk, I tend to prefer working with the alternative to JkMount
explained here (at the very end of the page) :
http://tomcat.apache.org/connectors-doc/reference/apache.html

(section: Using SetHandler and Environment Variables)

To me, this makes it clearer, because the proxying to Tomcat is now embedded in a
Location section, which has a clear precedence in the Apache configuration logic.

Using that syntax, the directives

JkMount /context/some-specific-path/foo workerX
JkMount /context/some-other-path/bar workerX
JkMount /context/*.do workerX
JkMount /context/*.jsp workerX

would be expressed as

Location /context/some-specific-path
# covers the 1st one above
setHandler jakarta-servlet
SetEnv JK_WORKER_NAME workerX
# but, as an example, exclude some URLs from the proxying
SetEnvIf REQUEST_URI \.(css|gif|jpe?g|js)$ no-jk
...
/Location
...
LocationMatch /context/.*\.(do|jsp)$
# covers #3 and #4 above
setHandler jakarta-servlet
SetEnv JK_WORKER_NAME workerX
...
/Location

Now, the problem becomes : are these Location and LocationMatch sections evaluated before,
or after the Rewrite rules ?

But for that, the Apache documentation is explicit.
Rewrite happens *before* the URL is compared to the Location* sections.

(*) probably, because it is difficult to explain precisely in less than 2 pages of html
full of Apache internals which most users would not understand anyway, so Rainer is
discouraged from even attempting to... ;-)

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: SSL Not working on tomcat 5.5.29

2010-07-02 Thread Pid

On 02/07/2010 06:30, kareem_s_m wrote:
 
 Hi All,
 
 I am working on upgrading tomcat from 5.5.28 to 5.5.29 for one of the
 applications. I see that the website renders and works fine in 5.5.29 on
 port 8080 (non SSL) but with  SSL (port 8443) the website doesnot run at
 all. When I try to see what's going on in Fiddle, I see 502 error. Also
 nothing is written to the log flies. It is as if tomcat is not even running
 in port 8443.
 
 Under tomcat 5.5.28, the site renders fine with SSL and non SSL.
 
 Is there something I could be missing?

Are the Connector definitions in server.xml files identical?

You can post it inline here, if you remove the comments and any passwords.


p



signature.asc
Description: OpenPGP digital signature

Re: using Servlet Filter to rewrite domain of JSESSIONID cookie?

2010-07-02 Thread Pid

On 02/07/2010 08:31, André Warnier wrote:
 Christopher Schultz wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Nikita,

 On 7/1/2010 6:37 PM, Nikita Tovstoles wrote:
 I borrowed sub-domain from Google Analytics terminology. I have one
 server, running one tomcat instance with one virtual host. That host is
 running one app - a JS/html widget that is embedded on multiple sites.

 We need to track usage per-deployment (per site embedding the wiget).
 For
 (google) analytics purposes, the easiest way to do so is to have a
 different
 (sub)domain per deployment. So the same tomcat instance is responding to
 requests for site1.widget.com, site2.widget.com, etc.

 a user may interact with 2 widget deployed on 2 different sites (and
 thus
 served from different (sub)domains) within 30 minutes. It is for this
 case
 that we want user to share the same HttpSession:

 - go to some site A where our widget is deployed at site1.widget.com
 - go to some other site B where our widget is deployed at
 site2.widget.com
 - reuse the same JSESSIONID because its' domain is set to .widget.com

 This sounds like a job for a non-JSESSIONID cookie that is created from
 your own code.

 +1
 
 But I am still lost as to what you are calling sites and subdomains
 and deployed at site1.widget.com.
 If I follow the explanation above, you have something like this :
 Host name=localhost appBase=webapps
  Aliassite1.widget.com/Alias
  Aliassite2.widget.com/Alias
  Aliassite3.widget.com/Alias
  Aliassite4.widget.com/Alias
 ...
 /Host

You can omit the aliases and just rely on the defaultHost setting in
Engine to route all requests to a specific Host.


p

 Is that it ?
 And if so, where is the widget-webapp deployed (on disk), and how many
 times really ?
 
 I am not trying to be a pedant, just to make sure I understand the
 layout, so that we might maybe come up with a suggestion to solve your
 problem (even if it is not by changing the JSESSIONID cookie domain)
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 




signature.asc
Description: OpenPGP digital signature

Re: Application vars -

2010-07-02 Thread André Warnier

Eric P wrote:

So it makes sense to go into what disruption means. I'm not 100% sure
about the following, it would be good if a tomcat heavyweight would
confirm/refute what I say.

When you initiate a webapp reload, Tomcat waits for requests that have
already started processing to terminate. This ensures that people who
accessed your app just before the webapp get a complete response. Once
that's done, the application is reloaded and your servlets' init
methods are
called if necessary. During this time, incoming requests aren't
denied, they

are just paused until the reload is complete.

So the only disruption people see is your application freezing up for the
time it takes to reload (which is going to depend on what you your
initialization consists of). No ugly server unavailable errors or
anything

of the sort.

If you don't like the idea of your app freezing, think about this.
Rereading

environment params without reloading has its own risks, namely potential
race conditions. Imagine you have 5 parameters, and requests are
coming in
as you are reading these in and initializing your webapp. A request
might be
handled while 2 params have been read, but 3 still contain the old
values.

If you start to think about locking/synchronization to solve this you're
definitely better off just using Tomcat's reload mechanism.

So my answer would be, trust Tomcat's reloading process unless you
absolutely want to avoid your webapp freezing for the time it will
take for

it to init (this depends on the webapp). If you want to do your own
reloading, think long and hard about potential race conditions
(which will

occur in all except the simplest cases).

Again, all this should probably be verified, you can set up very
simple test

cases with a JSP that sleeps, etc.

Shay,
I think you made a good case for keeping app vars in web.xml (i.e.,
seems pretty apparent now that's where they belong).

Thanks for taking the time to respond. I sincerely appreciate it!
Eric P.

+1
Very neat explanation.

While not being a great specialist, I would just like to expone what may be an
alternative, if one really wants to diminish the (apparent) time it takes for a new
version of a webapp to become available. Since I am no great specialist, I will just
outline the idea without Java/servlet specifics.

(Maybe also I am barging through an open door, and there already exists a standard
mechanism for doing this, but oh well..)

Imagine that you have 2 identical versions of the same intrinsic webapp
deployed, like

catalina_base/webapps/webappA
catalina_base/webapps/webappB

You create a 3rd webapp webappX, which is the one the users see, and which is just a
dispatcher to either one of the two webapps webappA and webappB.

So you now have :

catalina_base/webapps/webappX
catalina_base/webapps/webappA
catalina_base/webapps/webappB

The users always use the URL /webappX.
When a call is made to webappX, /it/ decides, in function of some external parameter Y,
whether to dispatch the call to either webappA or webappB.

Say that initially the external parameter Y (which could be a system-wide property) is set
so that all calls to /webappX are currently dispatched to /webappA.

Now you want to update webappA.
You change the parameter Y so that calls are now dispatched to (identical)
/webappB.
Then you update (redeploy) webappA. Users see no delay, because they get
directed to webappB.
When webappA is deployed and started (which you could check by calling it
directly),
you can reset the parameter Y to its former value, and users will again be dispatched to
webappA. Now you can redeploy webappB, to keep it in sync.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: SSL Not working on tomcat 5.5.29

2010-07-02 Thread André Warnier


kareem_s_m wrote:

Hi All,

I am working on upgrading tomcat from 5.5.28 to 5.5.29 for one of the
applications. I see that the website renders and works fine in 5.5.29 on
port 8080 (non SSL) but with  SSL (port 8443) the website doesnot run at
all. When I try to see what's going on in Fiddle, I see 502 error. Also
nothing is written to the log flies. It is as if tomcat is not even running
in port 8443.

Under tomcat 5.5.28, the site renders fine with SSL and non SSL.

Is there something I could be missing?

On the face of it, I would estimate the probability of that at so close to 1 as cannot be 
distinguished from it.
But if you want someone here to help, you will have to provide some more details, such as 
for example a copy-and-paste of your Connector tags, and maybe tell us which platform 
this is, and where these Tomcat's are coming from.
Useful : go to the Tomcat bin subdirectory with a console window, run version.sh or 
version.bat, and paste the result in your next message.





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 5.5 creates 0 byte files

2010-07-02 Thread Murat Birben

Hi all,

I have a very simple file upload mechanism in java. I just take the file and
save it on the server. I'm testing this simple code with selenium and *when
a timeout occurs in the selenium test *tomcat creates 0 byte files under
tomcat_home/work/Catalina/localhost/uploadServlet/ directory as MultiPart*
files. It creates thousands of files, until there is no disk space left on
device. What may cause this problem? How can I solve this? Is there anyone
has an idea about this?

My environment is: Ubuntu - 8.04 server, apache tomcat - 5.5.29, sun java
1.6

Thanks,

Here is the code snippet that i use

File fFile = null;
FileOutputStream fileOutputStream = null;
FileInputStream fileInputStream = null;
try {

String strFileName = request.getParameter(FileName);
String strPath = request.getParameter(Path);
//String strMediaType = request.getParameter(MediaType);

//String strDescription = request.getParameter(Description);
fFile = (File) request.getAttribute(Content);

int index = strPath.length() - 1; //If the user forgets to
put the last / for the path... We put it for him/her

if (strPath.charAt(index) != '/') {
strPath += /;
}
if (!new File(strPath).exists()) {
new File(strPath).mkdirs();
}

File file = new File(strPath + strFileName);
fileOutputStream = new FileOutputStream(file);
fileInputStream = new FileInputStream(fFile);

byte[] bBuf = new byte[1024];

int iBufLen = 0;
int iReadLen = 1024;
int iTotelLen = 0;
/*read 1024 bytes at a time*/
while ((iBufLen = fileInputStream.read(bBuf)) != -1) {

fileOutputStream.write(bBuf);
fileOutputStream.flush();
iTotelLen += iBufLen;
if (fileInputStream.available()  iReadLen) {
iReadLen = fileInputStream.available();

break;
}
}

byte[] tempbBuf = new byte[iReadLen];
fileInputStream.read(tempbBuf, 0, iReadLen);

fileOutputStream.write(tempbBuf);


} catch (IOException ex) {
ex.printStackTrace();
} finally {
fileOutputStream.close();
fileInputStream.close();

if (fFile.exists()) {

fFile.delete();
}
}



-- 
Murat BIRBEN

Re: using Servlet Filter to rewrite domain of JSESSIONID cookie?

2010-07-02 Thread André Warnier


Pid wrote:

On 02/07/2010 08:31, André Warnier wrote:

Christopher Schultz wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nikita,

On 7/1/2010 6:37 PM, Nikita Tovstoles wrote:

I borrowed sub-domain from Google Analytics terminology. I have one
server, running one tomcat instance with one virtual host. That host is
running one app - a JS/html widget that is embedded on multiple sites.

We need to track usage per-deployment (per site embedding the wiget).
For
(google) analytics purposes, the easiest way to do so is to have a
different
(sub)domain per deployment. So the same tomcat instance is responding to
requests for site1.widget.com, site2.widget.com, etc.

a user may interact with 2 widget deployed on 2 different sites (and
thus
served from different (sub)domains) within 30 minutes. It is for this
case
that we want user to share the same HttpSession:

- go to some site A where our widget is deployed at site1.widget.com
- go to some other site B where our widget is deployed at
site2.widget.com
- reuse the same JSESSIONID because its' domain is set to .widget.com

This sounds like a job for a non-JSESSIONID cookie that is created from
your own code.


+1

But I am still lost as to what you are calling sites and subdomains
and deployed at site1.widget.com.
If I follow the explanation above, you have something like this :
Host name=localhost appBase=webapps
 Aliassite1.widget.com/Alias
 Aliassite2.widget.com/Alias
 Aliassite3.widget.com/Alias
 Aliassite4.widget.com/Alias
...
/Host


You can omit the aliases and just rely on the defaultHost setting in
Engine to route all requests to a specific Host.


I know, but I am trying to get a grip of what the OP means by sites etc..
This is to try to figure out if, apart from modifying the domain of the JSESSIONID cookie 
(which seems difficult), there is a better solution to the OP's underlying issue (Google 
Analytics).
Maybe this thing can be solved by a simple servlet filter, or UrlRewriteFilter, or some 
dispatching servlet, or having the application do a getHostName() or ..


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

52 matches

Mail list logo