date:20110701

Dear all,

I use org.apache.catalina.startup.Tomcat to do unit test,  but the instance
of which cannot be started or stopped correctly.

I start and stop embedding tomcat for each test case, but first test can be
passed, the second one will be failed by 503 Service,  unavailable, the
tomcat.start() method has been invoked, but the tomcat return 503 error.

My code for tomcat start  stop:

public static Tomcat startServer() throws LifecycleException {
Tomcat tomcat = new Tomcat();
tomcat.setPort(8088);
 Context context = tomcat.addContext(,
System.getProperty(java.io.tmpdir));
 Wrapper servlet = Tomcat.addServlet(
context,
MyServlet.class.getSimpleName(),
MyServlet.class.getName());
 context.addServletMapping(/*, servlet.getName());
tomcat.start();
return tomcat;
}

public static void stop(Tomcat tomcat) {
if (tomcat == null || tomcat.getServer() == null) {
return;
}
if (tomcat.getServer().getState() != LifecycleState.DESTROYED) {
if (tomcat.getServer().getState() != LifecycleState.STOPPED) {
try {
tomcat.stop();
} catch (LifecycleException e) {
LOGGER.error(Stop tomcat error., e);
}
}
try {
tomcat.destroy();
} catch (LifecycleException e) {
LOGGER.error(Destroy tomcat error., e);
}
}
}
}

Thanks.

Zijian

Re: How to start stop embedding Tomcat correctly?

On 01/07/2011 10:07, Rehtron wrote:
 Dear all,
 
 I use org.apache.catalina.startup.Tomcat to do unit test,  but the instance
 of which cannot be started or stopped correctly.
 
 I start and stop embedding tomcat for each test case, but first test can be
 passed, the second one will be failed by 503 Service,  unavailable, the
 tomcat.start() method has been invoked, but the tomcat return 503 error.

Take a look at how Tomcat does this in it's own unit tests. Tomcat uses
a new port for each test to prevent this sort of problem.

Mark



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

RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Hi All,

Is some more information required for this?

Thanks.

-Original Message-
From: Rohan Kadam 
Sent: Thursday, June 30, 2011 7:26 PM
To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Hi,

I am using JAVA 1.6 update 23 version.

Thanks,
Rohan Kadam.

-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, June 30, 2011 7:22 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 30/06/2011 13:01, Rohan Kadam wrote:
 Hi All,

 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were earlier 
 facing problem that tomcat was not able to connect using Static IP 
 address. The fix that we found was adding address = 0.0.0.0 in the 
 Connector tag of server.xml in the conf directory.

 After upgrading tomcat to  7.0.14, we have done the same process, but 
 we are not able to connect.

Have you also upgraded Java?  What version (exactly) of Java are you using?

p

Legal Disclaimer: This electronic message and all contents contain information 
from Cybage Software Private Limited which may be privileged, confidential, or 
otherwise protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is strictly prohibited. If 
you have received this electronic message in error please notify the sender by 
reply e-mail to and destroy the original message and all copies. Cybage has 
taken every reasonable precaution to minimize the risk of malicious content in 
the mail, but is not liable for any damage you may sustain as a result of any 
malicious content in this e-mail. You should carry out your own malicious 
content checks before opening the e-mail or attachment. 
www.cybage.com

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

Re: How to start stop embedding Tomcat correctly?

Yes, I use same port for all test, but I think the port should be release
after tomcat stopped.

thanks.

2011/7/1 Mark Thomas ma...@apache.org

 On 01/07/2011 10:07, Rehtron wrote:
  Dear all,
 
  I use org.apache.catalina.startup.Tomcat to do unit test,  but the
 instance
  of which cannot be started or stopped correctly.
 
  I start and stop embedding tomcat for each test case, but first test can
 be
  passed, the second one will be failed by 503 Service,  unavailable, the
  tomcat.start() method has been invoked, but the tomcat return 503 error.

 Take a look at how Tomcat does this in it's own unit tests. Tomcat uses
 a new port for each test to prevent this sort of problem.

 Mark



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

Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

2011-07-01 Thread André Warnier


Well, answering Christopher's questions would be a good start.

Then also maybe paste the content of your Connector tag in your next message.


Rohan Kadam wrote:

Hi All,

Is some more information required for this?

Thanks.

-Original Message-
From: Rohan Kadam 
Sent: Thursday, June 30, 2011 7:26 PM

To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Hi,

I am using JAVA 1.6 update 23 version.

Thanks,
Rohan Kadam.

-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, June 30, 2011 7:22 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 30/06/2011 13:01, Rohan Kadam wrote:

Hi All,

We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were earlier 
facing problem that tomcat was not able to connect using Static IP 
address. The fix that we found was adding address = 0.0.0.0 in the 
Connector tag of server.xml in the conf directory.



After upgrading tomcat to  7.0.14, we have done the same process, but 
we are not able to connect.


Have you also upgraded Java?  What version (exactly) of Java are you using?


p


Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment. 
www.cybage.com




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





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

Re: How to start stop embedding Tomcat correctly?

On 01/07/2011 10:29, Rehtron wrote:
 Yes, I use same port for all test, but I think the port should be release
 after tomcat stopped.

What OS are you using?

Mark

 
 thanks.
 
 2011/7/1 Mark Thomas ma...@apache.org
 
 On 01/07/2011 10:07, Rehtron wrote:
 Dear all,

 I use org.apache.catalina.startup.Tomcat to do unit test,  but the
 instance
 of which cannot be started or stopped correctly.

 I start and stop embedding tomcat for each test case, but first test can
 be
 passed, the second one will be failed by 503 Service,  unavailable, the
 tomcat.start() method has been invoked, but the tomcat return 503 error.

 Take a look at how Tomcat does this in it's own unit tests. Tomcat uses
 a new port for each test to prevent this sort of problem.

 Mark



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


 




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

RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Please find my connector tag below, I have modified it to listen 7070  -

Connector port=7070 maxHttpHeaderSize=8192
   maxThreads=150 minSpareThreads=25 maxSpareThreads=75
   enableLookups=false redirectPort=8443 acceptCount=100
   connectionTimeout=2 disableUploadTimeout=true 
address=0.0.0.0 /


-Original Message-
From: André Warnier [mailto:a...@ice-sa.com] 
Sent: Friday, July 01, 2011 3:00 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Well, answering Christopher's questions would be a good start.

Then also maybe paste the content of your Connector tag in your next message.


Rohan Kadam wrote:
 Hi All,
 
 Is some more information required for this?
 
 Thanks.
 
 -Original Message-
 From: Rohan Kadam
 Sent: Thursday, June 30, 2011 7:26 PM
 To: Tomcat Users List
 Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 
 7.0.14)
 
 Hi,
 
 I am using JAVA 1.6 update 23 version.
 
 Thanks,
 Rohan Kadam.
 
 -Original Message-
 From: Pid [mailto:p...@pidster.com]
 Sent: Thursday, June 30, 2011 7:22 PM
 To: Tomcat Users List
 Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 
 7.0.14)
 
 On 30/06/2011 13:01, Rohan Kadam wrote:
 Hi All,

 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were 
 earlier facing problem that tomcat was not able to connect using 
 Static IP address. The fix that we found was adding address = 
 0.0.0.0 in the Connector tag of server.xml in the conf directory.


 After upgrading tomcat to  7.0.14, we have done the same process, but 
 we are not able to connect.
 
 Have you also upgraded Java?  What version (exactly) of Java are you using?
 
 
 p
 
 
 Legal Disclaimer: This electronic message and all contents contain 
 information from Cybage Software Private Limited which may be privileged, 
 confidential, or otherwise protected from disclosure. The information is 
 intended to be for the addressee(s) only. If you are not an addressee, any 
 disclosure, copy, distribution, or use of the contents of this message is 
 strictly prohibited. If you have received this electronic message in error 
 please notify the sender by reply e-mail to and destroy the original message 
 and all copies. Cybage has taken every reasonable precaution to minimize the 
 risk of malicious content in the mail, but is not liable for any damage you 
 may sustain as a result of any malicious content in this e-mail. You should 
 carry out your own malicious content checks before opening the e-mail or 
 attachment. 
 www.cybage.com
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 


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



Legal Disclaimer: This electronic message and all contents contain information 
from Cybage Software Private Limited which may be privileged, confidential, or 
otherwise protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is strictly prohibited. If 
you have received this electronic message in error please notify the sender by 
reply e-mail to and destroy the original message and all copies. Cybage has 
taken every reasonable precaution to minimize the risk of malicious content in 
the mail, but is not liable for any damage you may sustain as a result of any 
malicious content in this e-mail. You should carry out your own malicious 
content checks before opening the e-mail or attachment. 
www.cybage.com



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

Re: Tomcat 7 Embedded: Manager

2011-07-01 Thread Dark Before Dawn


Hi again,
this is realy driving me nuts for weeks :)

I am developing a Java SE application using *Tomcat* 7 in embedded mode. 
 I am attempting to use the *tomcat* manager application 
(ManagerServlet) and Ant tasks to perform operations on the running 
*tomcat* instance.  Tasks such as list, start, stop work fine, however 
the deploy and undeploy tasks *fail* with the following *exception* (see 
below).  I actually get the same *exception* when trying to use the 
manager web interface (HTMLManagerServlet) which leads me to believe 
that this is a general configuration issue somewhere or misunderstanding 
in my code.


I guess there is still something wrong with my mappings as Chuck noticed.

/manager/html
/manager/jmxproxy
/manager/status
/manager/text

I realy read the API Documentation and UnitTest examples and haven't got 
any further :(


Code:
http://www.pastie.org/private/rehlryloo0zyl9korkupq

Errors via ANT and Web:

FAIL - Encountered exception javax.management.InstanceNotFoundException: 
Tomcat:type=Deployer,host=localhost

Trace:
01.07.2011 11:28:57 org.apache.catalina.core.ApplicationContext log
manager-servlet: managerServlet.check[/sample]
javax.management.InstanceNotFoundException: Tomcat:type=Deployer,host=localhost
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at 
org.apache.catalina.manager.ManagerServlet.isServiced(ManagerServlet.java:1433)
at 
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:721)
at 
org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:399)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:317)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:204)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:311)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

Cheers Darky

Am 28.06.2011 03:42, schrieb Caldarale, Charles R:

From: Dark Before Dawn [mailto:dark.before.d...@gmail.com]
Subject: Re: Tomcat 7 Embedded: Manager
When using HTMLManagerServlet and navigating to http://localhost/manager
the Manager's HTML Interface will appear.

It shouldn't, unless you've been playing with the mappings in WEB-INF/web.xml.  
The valid URL paths are:

/manager/html
/manager/jmxproxy
/manager/status
/manager/text

There is no /manager mapping, nor is there supposed to be one.  Note that each 
mapping has its own security constraint.

  - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


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

Re: How to start stop embedding Tomcat correctly?

Windows XP, did you mean I should use different port for every test?

Thanks.

2011/7/1 Mark Thomas ma...@apache.org

 On 01/07/2011 10:29, Rehtron wrote:
  Yes, I use same port for all test, but I think the port should be release
  after tomcat stopped.

 What OS are you using?

 Mark

 
  thanks.
 
  2011/7/1 Mark Thomas ma...@apache.org
 
  On 01/07/2011 10:07, Rehtron wrote:
  Dear all,
 
  I use org.apache.catalina.startup.Tomcat to do unit test,  but the
  instance
  of which cannot be started or stopped correctly.
 
  I start and stop embedding tomcat for each test case, but first test
 can
  be
  passed, the second one will be failed by 503 Service,  unavailable, the
  tomcat.start() method has been invoked, but the tomcat return 503
 error.
 
  Take a look at how Tomcat does this in it's own unit tests. Tomcat uses
  a new port for each test to prevent this sort of problem.
 
  Mark
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 




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

Re: How to start stop embedding Tomcat correctly?

On 01/07/2011 10:56, Rehtron wrote:
 Windows XP, did you mean I should use different port for every test?

I have seen all OSes hold on to ports after Tomcat has shutdown. Windows
isn't as bad as Linux but it does happen sometimes.

Yes, you need to use a new port for each test. Again, take a look at
Tomcat's own unit tests.

Mark

 
 Thanks.
 
 2011/7/1 Mark Thomas ma...@apache.org
 
 On 01/07/2011 10:29, Rehtron wrote:
 Yes, I use same port for all test, but I think the port should be release
 after tomcat stopped.

 What OS are you using?

 Mark


 thanks.

 2011/7/1 Mark Thomas ma...@apache.org

 On 01/07/2011 10:07, Rehtron wrote:
 Dear all,

 I use org.apache.catalina.startup.Tomcat to do unit test,  but the
 instance
 of which cannot be started or stopped correctly.

 I start and stop embedding tomcat for each test case, but first test
 can
 be
 passed, the second one will be failed by 503 Service,  unavailable, the
 tomcat.start() method has been invoked, but the tomcat return 503
 error.

 Take a look at how Tomcat does this in it's own unit tests. Tomcat uses
 a new port for each test to prevent this sort of problem.

 Mark



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







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


 




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

Re: How to start stop embedding Tomcat correctly?

OK,  thank you very much for your help!


2011/7/1 Mark Thomas ma...@apache.org

 On 01/07/2011 10:56, Rehtron wrote:
  Windows XP, did you mean I should use different port for every test?

 I have seen all OSes hold on to ports after Tomcat has shutdown. Windows
 isn't as bad as Linux but it does happen sometimes.

 Yes, you need to use a new port for each test. Again, take a look at
 Tomcat's own unit tests.

 Mark

 
  Thanks.
 
  2011/7/1 Mark Thomas ma...@apache.org
 
  On 01/07/2011 10:29, Rehtron wrote:
  Yes, I use same port for all test, but I think the port should be
 release
  after tomcat stopped.
 
  What OS are you using?
 
  Mark
 
 
  thanks.
 
  2011/7/1 Mark Thomas ma...@apache.org
 
  On 01/07/2011 10:07, Rehtron wrote:
  Dear all,
 
  I use org.apache.catalina.startup.Tomcat to do unit test,  but the
  instance
  of which cannot be started or stopped correctly.
 
  I start and stop embedding tomcat for each test case, but first test
  can
  be
  passed, the second one will be failed by 503 Service,  unavailable,
 the
  tomcat.start() method has been invoked, but the tomcat return 503
  error.
 
  Take a look at how Tomcat does this in it's own unit tests. Tomcat
 uses
  a new port for each test to prevent this sort of problem.
 
  Mark
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 




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

Re: webapps and TCP/UDP listening sockets

On 01/07/2011 04:45, Tim Judd wrote:
 Hi Christopher, all
 
 'machine' was meant to indicate one of two choices, the computer that is 
 running 
 the tomcat server, or the computer who is the client in a client-server 
 relationship.  

So you meant the client or the server.

 I don't know the intricities of webapps yet in how they run.  

Probably a good idea to read up on that if you're going to build one.

 This thread was just trying to understand if I'm barking up the wrong tree.
 
 Your second paragraph is better phrased.  which computer/'machine' is doing 
 the 
 binding?  

Whichever one the code for creating a socket is running on.  When you
create a client socket it still uses a port local to the JVM you're
running the code in.


 Writing a standalone Java desktop app is most definately going to bind 
 to it's own machine.  I don't need to delegate anything to Tomcat itself, I 
 need 
 to know if I run a webapp and it binds and listens to a socket, which machine 
 does it bind on?

Some confusion here still, it's nothing to do with a webapp and entirely
to do with the location of the code.


 Lastly, your statement about making it a webapp if http is not involved is 
 because to centrally deploy an application is often served off http; I wanted 
 to 
 get into Java/webapps so I elected this route.

You want to get into webapps, so you're build an app which has nothing
to do with webapps?


 If they are standalone protocols 
 (and they will be) to communicate between many clients to one (or a farm) of 
 servers, why can't I launch it from http?

Why would you?  What does the servlet container offer that running the
code independantly doesn't?

You're not describing an application which uses the http connectors
provided by Tomcat to operate, you're just using Tomcat as a launch
wrapper for your app.


p



  If opportunity doesn't knock, build a door.
 I can is a way of life.
 More and Bigger is not always Better.
 The road to success is always uphill.
 
 
 
 
 
 From: Christopher Schultz ch...@christopherschultz.net
 To: Tomcat Users List users@tomcat.apache.org
 Sent: Thu, June 30, 2011 8:07:55 PM
 Subject: Re: webapps and TCP/UDP listening sockets
 
 Tim,
 
 On 6/30/2011 7:14 PM, Tim Judd wrote:
 If I develop a webapp that listens for TCP/UDP sockets, which machine is 
 actually listening?
 
 When you say machine... you mean ... what, exactly?
 
 If you develop a webapp that listens for TCP/UDP sockets, where is the
 socket bind occurring? If it's your webapp, then it really has nothing
 to do with Tomcat at all: it's just like writing a non-webapp program
 that binds to a socket and listens.
 
 If you want to delegate incoming requests to threads from Tomcat's
 request processor pool, that might be a bit tricky. Is that what you'd
 like to do?
 
 Do you really need Tomcat in this situation?
 
 Is the tomcat server listening (because the webapp is 
 running on that tomcat) or is the client listening (because he is running 
 the 
 webapp on the tomcat server)!
 
 Probably both, but it depends on your answer to the above questions.
 
 My goal is to have:
   single UDP listening at tomcat server for packets, and
   multicast UDP listening at the clients that is getting resended off the 
 single 
 
 above UDP port from the webapp tomcat server
 
 Why do you want to build this as a web-based application if HTTP isn't
 really involved?
 
 -chris

-
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: Tomcat 7 Embedded: Manager

On 01/07/2011 10:40, Dark Before Dawn wrote:
 this is realy driving me nuts for weeks

so *does* the arbit*rary* use of *bold* for me.


p



signature.asc
Description: OpenPGP digital signature

Re: Tomcat 7 Embedded: Manager

On 01/07/2011 10:40, Dark Before Dawn wrote:
 Hi again,
 this is realy driving me nuts for weeks :)


 FAIL - Encountered exception javax.management.InstanceNotFoundException:
 Tomcat:type=Deployer,host=localhost

1. Connect to your running instance with JConsole*.
2. Examine the MBeans published by the instance.
3. Confirm that you are connecting to the correct MBean.


I wouldn't expect:

 Tomcat:type=Deployer,host=localhost

to work.


p


* or VisualVM with the JConsole plugin enabled.



signature.asc
Description: OpenPGP digital signature

Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 30/06/2011 21:57, Christopher Schultz wrote:
 Rohan,
 
 On 6/30/2011 8:01 AM, Rohan Kadam wrote:
 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were earlier facing
 problem that tomcat was not able to connect using Static IP address. The fix
 that we found was adding
 address = 0.0.0.0 in the Connector tag of server.xml in the conf 
 directory.
 
 This was likely because your JVM prefers an IPv6 stack, while using an
 IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address.
 
 When you say not able to connect, do you mean that the client couldn't
 reach Tomcat, or that Tomcat couldn't connect to some other server?
 
 After upgrading tomcat to 7.0.14, we have done the same process, but we are
 not able to connect.

Hint:  JAVA_OPTS=-Djava.net.preferIPv4Stack=true  can be set in
setenv.sh|bat


p



signature.asc
Description: OpenPGP digital signature

Re: Tomcat 7 Embedded: Manager

2011-07-01 Thread Dark Before Dawn


sorry for that :) diddn't want to annoy
Cheers
Darky


Am 01.07.2011 12:41, schrieb Pid:

On 01/07/2011 10:40, Dark Before Dawn wrote:

this is realy driving me nuts for weeks

so *does* the arbit*rary* use of *bold* for me.


p




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

RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

I have tries to set this java option in catalane .bat, but no success

-Djava.net.preferIPv4Stack=true

I am using tomcat as a service, so configures the same in Java properties as 
well. But it is not working.

Please suggest.

-Original Message-
From: Pid [mailto:p...@pidster.com] 
Sent: Friday, July 01, 2011 4:18 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 30/06/2011 21:57, Christopher Schultz wrote:
 Rohan,
 
 On 6/30/2011 8:01 AM, Rohan Kadam wrote:
 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were 
 earlier facing problem that tomcat was not able to connect using 
 Static IP address. The fix that we found was adding address = 
 0.0.0.0 in the Connector tag of server.xml in the conf directory.
 
 This was likely because your JVM prefers an IPv6 stack, while using an
 IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address.
 
 When you say not able to connect, do you mean that the client 
 couldn't reach Tomcat, or that Tomcat couldn't connect to some other server?
 
 After upgrading tomcat to 7.0.14, we have done the same process, but 
 we are not able to connect.

Hint:  JAVA_OPTS=-Djava.net.preferIPv4Stack=true  can be set in setenv.sh|bat


p


Legal Disclaimer: This electronic message and all contents contain information 
from Cybage Software Private Limited which may be privileged, confidential, or 
otherwise protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is strictly prohibited. If 
you have received this electronic message in error please notify the sender by 
reply e-mail to and destroy the original message and all copies. Cybage has 
taken every reasonable precaution to minimize the risk of malicious content in 
the mail, but is not liable for any damage you may sustain as a result of any 
malicious content in this e-mail. You should carry out your own malicious 
content checks before opening the e-mail or attachment. 
www.cybage.com

Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 01/07/2011 12:07, Rohan Kadam wrote:
 I have tries to set this java option in catalane .bat, but no success
 
 -Djava.net.preferIPv4Stack=true
 
 I am using tomcat as a service, so configures the same in Java properties as 
 well. But it is not working.

How are you setting it, exactly?


p


 -Original Message-
 From: Pid [mailto:p...@pidster.com] 
 Sent: Friday, July 01, 2011 4:18 PM
 To: Tomcat Users List
 Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
 
 On 30/06/2011 21:57, Christopher Schultz wrote:
 Rohan,

 On 6/30/2011 8:01 AM, Rohan Kadam wrote:
 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were 
 earlier facing problem that tomcat was not able to connect using 
 Static IP address. The fix that we found was adding address = 
 0.0.0.0 in the Connector tag of server.xml in the conf directory.

 This was likely because your JVM prefers an IPv6 stack, while using an
 IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address.

 When you say not able to connect, do you mean that the client 
 couldn't reach Tomcat, or that Tomcat couldn't connect to some other server?

 After upgrading tomcat to 7.0.14, we have done the same process, but 
 we are not able to connect.
 
 Hint:  JAVA_OPTS=-Djava.net.preferIPv4Stack=true  can be set in 
 setenv.sh|bat
 
 
 p
 
 
 Legal Disclaimer: This electronic message and all contents contain 
 information from Cybage Software Private Limited which may be privileged, 
 confidential, or otherwise protected from disclosure. The information is 
 intended to be for the addressee(s) only. If you are not an addressee, any 
 disclosure, copy, distribution, or use of the contents of this message is 
 strictly prohibited. If you have received this electronic message in error 
 please notify the sender by reply e-mail to and destroy the original message 
 and all copies. Cybage has taken every reasonable precaution to minimize the 
 risk of malicious content in the mail, but is not liable for any damage you 
 may sustain as a result of any malicious content in this e-mail. You should 
 carry out your own malicious content checks before opening the e-mail or 
 attachment. 
 www.cybage.com




signature.asc
Description: OpenPGP digital signature

RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

Sorry Folks...I forgot to mention, I have also restarted the service after the 
changes were done.

-Original Message-
From: Rohan Kadam 
Sent: Friday, July 01, 2011 5:26 PM
To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

We have created a service named say ABCTomcat

Then we navigated to bin directory of tomcat, typed the following command -

tomcat7w.exe //ES//ABCTomcat

After that Iwent to Java Tab, and added the below line in Java Option Section.

Please let me know if I am missing something.

-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Friday, July 01, 2011 5:07 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 01/07/2011 12:07, Rohan Kadam wrote:
 I have tries to set this java option in catalane .bat, but no success

 -Djava.net.preferIPv4Stack=true

 I am using tomcat as a service, so configures the same in Java properties as 
 well. But it is not working.

How are you setting it, exactly?

p

 -Original Message-
 From: Pid [mailto:p...@pidster.com]
 Sent: Friday, July 01, 2011 4:18 PM
 To: Tomcat Users List
 Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 
 7.0.14)

 On 30/06/2011 21:57, Christopher Schultz wrote:
 Rohan,

 On 6/30/2011 8:01 AM, Rohan Kadam wrote:
 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were 
 earlier facing problem that tomcat was not able to connect using 
 Static IP address. The fix that we found was adding address = 
 0.0.0.0 in the Connector tag of server.xml in the conf directory.

 This was likely because your JVM prefers an IPv6 stack, while using 
 an
 IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address.

 When you say not able to connect, do you mean that the client 
 couldn't reach Tomcat, or that Tomcat couldn't connect to some other server?

 After upgrading tomcat to 7.0.14, we have done the same process, but 
 we are not able to connect.

 Hint:  JAVA_OPTS=-Djava.net.preferIPv4Stack=true  can be set in 
 setenv.sh|bat

 p

 Legal Disclaimer: This electronic message and all contents contain 
 information from Cybage Software Private Limited which may be privileged, 
 confidential, or otherwise protected from disclosure. The information is 
 intended to be for the addressee(s) only. If you are not an addressee, any 
 disclosure, copy, distribution, or use of the contents of this message is 
 strictly prohibited. If you have received this electronic message in error 
 please notify the sender by reply e-mail to and destroy the original message 
 and all copies. Cybage has taken every reasonable precaution to minimize the 
 risk of malicious content in the mail, but is not liable for any damage you 
 may sustain as a result of any malicious content in this e-mail. You should 
 carry out your own malicious content checks before opening the e-mail or 
 attachment. 
 www.cybage.com

Legal Disclaimer: This electronic message and all contents contain information 
from Cybage Software Private Limited which may be privileged, confidential, or 
otherwise protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is strictly prohibited. If 
you have received this electronic message in error please notify the sender by 
reply e-mail to and destroy the original message and all copies. Cybage has 
taken every reasonable precaution to minimize the risk of malicious content in 
the mail, but is not liable for any damage you may sustain as a result of any 
malicious content in this e-mail. You should carry out your own malicious 
content checks before opening the e-mail or attachment. 
www.cybage.com

RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

We have created a service named say ABCTomcat

Then we navigated to bin directory of tomcat, typed the following command -

tomcat7w.exe //ES//ABCTomcat

After that Iwent to Java Tab, and added the below line in Java Option Section.

Please let me know if I am missing something.

-Original Message-
From: Pid [mailto:p...@pidster.com] 
Sent: Friday, July 01, 2011 5:07 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

On 01/07/2011 12:07, Rohan Kadam wrote:
 I have tries to set this java option in catalane .bat, but no success
 
 -Djava.net.preferIPv4Stack=true
 
 I am using tomcat as a service, so configures the same in Java properties as 
 well. But it is not working.

How are you setting it, exactly?


p


 -Original Message-
 From: Pid [mailto:p...@pidster.com]
 Sent: Friday, July 01, 2011 4:18 PM
 To: Tomcat Users List
 Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 
 7.0.14)
 
 On 30/06/2011 21:57, Christopher Schultz wrote:
 Rohan,

 On 6/30/2011 8:01 AM, Rohan Kadam wrote:
 We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were 
 earlier facing problem that tomcat was not able to connect using 
 Static IP address. The fix that we found was adding address = 
 0.0.0.0 in the Connector tag of server.xml in the conf directory.

 This was likely because your JVM prefers an IPv6 stack, while using 
 an
 IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address.

 When you say not able to connect, do you mean that the client 
 couldn't reach Tomcat, or that Tomcat couldn't connect to some other server?

 After upgrading tomcat to 7.0.14, we have done the same process, but 
 we are not able to connect.
 
 Hint:  JAVA_OPTS=-Djava.net.preferIPv4Stack=true  can be set in 
 setenv.sh|bat
 
 
 p
 
 
 Legal Disclaimer: This electronic message and all contents contain 
 information from Cybage Software Private Limited which may be privileged, 
 confidential, or otherwise protected from disclosure. The information is 
 intended to be for the addressee(s) only. If you are not an addressee, any 
 disclosure, copy, distribution, or use of the contents of this message is 
 strictly prohibited. If you have received this electronic message in error 
 please notify the sender by reply e-mail to and destroy the original message 
 and all copies. Cybage has taken every reasonable precaution to minimize the 
 risk of malicious content in the mail, but is not liable for any damage you 
 may sustain as a result of any malicious content in this e-mail. You should 
 carry out your own malicious content checks before opening the e-mail or 
 attachment. 
 www.cybage.com



Legal Disclaimer: This electronic message and all contents contain information 
from Cybage Software Private Limited which may be privileged, confidential, or 
otherwise protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is strictly prohibited. If 
you have received this electronic message in error please notify the sender by 
reply e-mail to and destroy the original message and all copies. Cybage has 
taken every reasonable precaution to minimize the risk of malicious content in 
the mail, but is not liable for any damage you may sustain as a result of any 
malicious content in this e-mail. You should carry out your own malicious 
content checks before opening the e-mail or attachment. 
www.cybage.com

Access to manager webapp (JAAS exception)

2011-07-01 Thread Chema

Hi:

I've just installed ( unzipped ) Tomcat 7.0.14 and I'm trying to
access to manager web application.

So,

http://127.0.0.1:8080/manager/html

and popup a browser logging form.

My conf/tomcat-users.xml is

tomcat-users
 role rolename=manager-gui/
 user username=tomcat password=tomcat roles=manager-gui/
/tomcat-users


But, when I try to log in, an exception occurs:

01-jul-2011 16:10:51 org.apache.catalina.realm.JAASRealm authenticate
java.lang.SecurityException:
at com.sun.security.auth.login.ConfigFile.init(Unknown Source)


Why ? There isnt configured in my server to use JAAS.
Indeed , conf/server.xml has

 GlobalNamingResources
Resource auth=Container
factory=org.apache.catalina.users.MemoryUserDatabaseFactory
name=UserDatabase pathname=conf/tomcat-users.xml
type=org.apache.catalina.UserDatabase/
  /GlobalNamingResources

Any ideas ?

Thanks and regards

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

Re: Access to manager webapp (JAAS exception)

On 01/07/2011 15:22, Chema wrote:
 Hi:
 
 I've just installed ( unzipped ) Tomcat 7.0.14 and I'm trying to
 access to manager web application.

What else did you change?

Mark

 
 So,
 
 http://127.0.0.1:8080/manager/html
 
 and popup a browser logging form.
 
 My conf/tomcat-users.xml is
 
 tomcat-users
  role rolename=manager-gui/
  user username=tomcat password=tomcat roles=manager-gui/
 /tomcat-users
 
 
 But, when I try to log in, an exception occurs:
 
 01-jul-2011 16:10:51 org.apache.catalina.realm.JAASRealm authenticate
 java.lang.SecurityException:
   at com.sun.security.auth.login.ConfigFile.init(Unknown Source)
 
 
 Why ? There isnt configured in my server to use JAAS.
 Indeed , conf/server.xml has
 
  GlobalNamingResources
 Resource auth=Container
 factory=org.apache.catalina.users.MemoryUserDatabaseFactory
 name=UserDatabase pathname=conf/tomcat-users.xml
 type=org.apache.catalina.UserDatabase/
   /GlobalNamingResources
 
 Any ideas ?
 
 Thanks and regards
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 




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

Re: webapps and TCP/UDP listening sockets

2011-07-01 Thread Tim Judd

Hi Pid, all

I'm disappointed the responses I've gotten seemingly to be scolding messages.  
I 
am reading up on documentation, I am reading the APIs, I am reading everything 
I 
can.  Think of Citrix (in Windows environments) - code is executed on the 
server 
and displayed on your desktop; X11 forwarding does the same thing.  I don't 
know 
which machine is executing the code

I understand you guys are trying to help, but I am disappointed all I'm hearing 
is you're doing it wrong basically.  I was hoping a quick answer to know 
which 
machine is executing the code which would be the same side that has it bound.


Does anyone know which machine will bind?




Thanks again!

 If opportunity doesn't knock, build a door.
I can is a way of life.
More and Bigger is not always Better.
The road to success is always uphill.





From: Pid p...@pidster.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Fri, July 1, 2011 4:39:10 AM
Subject: Re: webapps and TCP/UDP listening sockets

On 01/07/2011 04:45, Tim Judd wrote:
 Hi Christopher, all
 
 'machine' was meant to indicate one of two choices, the computer that is 
running 

 the tomcat server, or the computer who is the client in a client-server 
 relationship.  

So you meant the client or the server.

 I don't know the intricities of webapps yet in how they run.  

Probably a good idea to read up on that if you're going to build one.

 This thread was just trying to understand if I'm barking up the wrong tree.
 
 Your second paragraph is better phrased.  which computer/'machine' is doing 
 the 

 binding?  

Whichever one the code for creating a socket is running on.  When you
create a client socket it still uses a port local to the JVM you're
running the code in.


 Writing a standalone Java desktop app is most definately going to bind 
 to it's own machine.  I don't need to delegate anything to Tomcat itself, I 
need 

 to know if I run a webapp and it binds and listens to a socket, which machine 
 does it bind on?

Some confusion here still, it's nothing to do with a webapp and entirely
to do with the location of the code.


 Lastly, your statement about making it a webapp if http is not involved is 
 because to centrally deploy an application is often served off http; I wanted 
to 

 get into Java/webapps so I elected this route.

You want to get into webapps, so you're build an app which has nothing
to do with webapps?


 If they are standalone protocols 
 (and they will be) to communicate between many clients to one (or a farm) of 
 servers, why can't I launch it from http?

Why would you?  What does the servlet container offer that running the
code independantly doesn't?

You're not describing an application which uses the http connectors
provided by Tomcat to operate, you're just using Tomcat as a launch
wrapper for your app.


p



  If opportunity doesn't knock, build a door.
 I can is a way of life.
 More and Bigger is not always Better.
 The road to success is always uphill.
 
 
 
 
 
 From: Christopher Schultz ch...@christopherschultz.net
 To: Tomcat Users List users@tomcat.apache.org
 Sent: Thu, June 30, 2011 8:07:55 PM
 Subject: Re: webapps and TCP/UDP listening sockets
 
 Tim,
 
 On 6/30/2011 7:14 PM, Tim Judd wrote:
 If I develop a webapp that listens for TCP/UDP sockets, which machine is 
 actually listening?
 
 When you say machine... you mean ... what, exactly?
 
 If you develop a webapp that listens for TCP/UDP sockets, where is the
 socket bind occurring? If it's your webapp, then it really has nothing
 to do with Tomcat at all: it's just like writing a non-webapp program
 that binds to a socket and listens.
 
 If you want to delegate incoming requests to threads from Tomcat's
 request processor pool, that might be a bit tricky. Is that what you'd
 like to do?
 
 Do you really need Tomcat in this situation?
 
 Is the tomcat server listening (because the webapp is 
 running on that tomcat) or is the client listening (because he is running 
 the 

 webapp on the tomcat server)!
 
 Probably both, but it depends on your answer to the above questions.
 
 My goal is to have:
   single UDP listening at tomcat server for packets, and
   multicast UDP listening at the clients that is getting resended off the 
 single 
 
 above UDP port from the webapp tomcat server
 
 Why do you want to build this as a web-based application if HTTP isn't
 really involved?
 
 -chris

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

Re: webapps and TCP/UDP listening sockets

2011-07-01 Thread David kerber


On 6/30/2011 11:45 PM, Tim Judd wrote:

Hi Christopher, all

'machine' was meant to indicate one of two choices, the computer that is running
the tomcat server, or the computer who is the client in a client-server
relationship.  I don't know the intricities of webapps yet in how they run.
This thread was just trying to understand if I'm barking up the wrong tree.

Your second paragraph is better phrased.  which computer/'machine' is doing the
binding?  Writing a standalone Java desktop app is most definately going to bind
to it's own machine.  I don't need to delegate anything to Tomcat itself, I need
to know if I run a webapp and it binds and listens to a socket, which machine
does it bind on?


A Webapp by definition runs in tomcat, and will bind on the server.  I 
don't know anything about x11, but if it's similar to Citrix or 
Microsoft RDP, then even a local java app is going to be actually 
running on the server (and therefore binding the sockets there), and 
only sending the console to your client.






Lastly, your statement about making it a webapp if http is not involved is
because to centrally deploy an application is often served off http; I wanted to
get into Java/webapps so I elected this route.  If they are standalone protocols
(and they will be) to communicate between many clients to one (or a farm) of
servers, why can't I launch it from http?


  If opportunity doesn't knock, build a door.
I can is a way of life.
More and Bigger is not always Better.
The road to success is always uphill.





From: Christopher Schultzch...@christopherschultz.net
To: Tomcat Users Listusers@tomcat.apache.org
Sent: Thu, June 30, 2011 8:07:55 PM
Subject: Re: webapps and TCP/UDP listening sockets

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tim,

On 6/30/2011 7:14 PM, Tim Judd wrote:

If I develop a webapp that listens for TCP/UDP sockets, which machine is
actually listening?


When you say machine... you mean ... what, exactly?

If you develop a webapp that listens for TCP/UDP sockets, where is the
socket bind occurring? If it's your webapp, then it really has nothing
to do with Tomcat at all: it's just like writing a non-webapp program
that binds to a socket and listens.

If you want to delegate incoming requests to threads from Tomcat's
request processor pool, that might be a bit tricky. Is that what you'd
like to do?

Do you really need Tomcat in this situation?


Is the tomcat server listening (because the webapp is
running on that tomcat) or is the client listening (because he is running the
webapp on the tomcat server)!


Probably both, but it depends on your answer to the above questions.


My goal is to have:
   single UDP listening at tomcat server for packets, and
   multicast UDP listening at the clients that is getting resended off the
single

above UDP port from the webapp tomcat server


Why do you want to build this as a web-based application if HTTP isn't
really involved?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4NK/sACgkQ9CaO5/Lv0PBlLwCaAqi72qyRX1HCwlrtor+NS62X
YiQAoLuYcbXt4tp9oQ0B+hTCqaocDbkG
=QlO7
-END PGP SIGNATURE-

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




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

Re: Access to manager webapp (JAAS exception)

2011-07-01 Thread Chema

2011/7/1 Mark Thomas ma...@apache.org:
 On 01/07/2011 15:22, Chema wrote:
 Hi:

 I've just installed ( unzipped ) Tomcat 7.0.14 and I'm trying to
 access to manager web application.

 What else did you change?



I think nothing.
There is a log when server starts that I dont understand :

01-jul-2011 17:23:55 org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina

any idea ?

I've downloaded 7.0.16 release and  this log doesnt occur when server starts
I don`t know if I changed something on former installation ( 7.0.14 )  ...


Thanks








 Mark


 So,

 http://127.0.0.1:8080/manager/html

 and popup a browser logging form.

 My conf/tomcat-users.xml is

 tomcat-users
  role rolename=manager-gui/
  user username=tomcat password=tomcat roles=manager-gui/
 /tomcat-users


 But, when I try to log in, an exception occurs:

 01-jul-2011 16:10:51 org.apache.catalina.realm.JAASRealm authenticate
 java.lang.SecurityException:
       at com.sun.security.auth.login.ConfigFile.init(Unknown Source)


 Why ? There isnt configured in my server to use JAAS.
 Indeed , conf/server.xml has

  GlobalNamingResources
     Resource auth=Container
 factory=org.apache.catalina.users.MemoryUserDatabaseFactory
 name=UserDatabase pathname=conf/tomcat-users.xml
 type=org.apache.catalina.UserDatabase/
   /GlobalNamingResources

 Any ideas ?

 Thanks and regards

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





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



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

Re: Access to manager webapp (JAAS exception)

On 01/07/2011 16:26, Chema wrote:
 2011/7/1 Mark Thomas ma...@apache.org:
 On 01/07/2011 15:22, Chema wrote:
 Hi:

 I've just installed ( unzipped ) Tomcat 7.0.14 and I'm trying to
 access to manager web application.

 What else did you change?

 
 
 I think nothing.
 There is a log when server starts that I dont understand :
 
 01-jul-2011 17:23:55 org.apache.catalina.realm.JAASRealm setContainer
 INFO: Set JAAS app name Catalina
 
 any idea ?
 
 I've downloaded 7.0.16 release and  this log doesnt occur when server starts
 I don`t know if I changed something on former installation ( 7.0.14 )  ...

So, you don't know if you changed anything but it doesn't work. Hmm. How
on earth do you expect people on this list to be able to help if you
can't tell them what you have done?

Time to start again with a clean installation and this time keep some notes.

Mark



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

Re: Tomcat 7 Embedded: Manager

On 01/07/2011 12:44, Dark Before Dawn wrote:
 Hi Pid,
 i guess the problem is that the manager-servlet's context is mounted
 at root and the ServletMapping points to /manager.
 
 server.addContext(, baseDirectory);
 ctx.addServletMapping(/manager/*, manager-servlet);
 
 So all relative paths will point to root

That's easy to change, no?

 server.addContext(/manager, baseDirectory);
 ctx.addServletMapping(/text/*, manager-servlet);

Note the additional '*' in the security collection:

 collection.addPattern(/text/*);

(The role usually assigned for the text manager servlet is manager-script)


p


 ie:
 
 localhost/manager/html vs localhost/html
 
 I don't know what I am exactly searching for at jconsole, so here is a 
 overview :)
 Thnx and cheers
 Darky
 
 
 
 
 Am 01.07.2011 12:46, schrieb Pid:
 On 01/07/2011 10:40, Dark Before Dawn wrote:
 Hi again,
 this is realy driving me nuts for weeks :)

 FAIL - Encountered exception javax.management.InstanceNotFoundException:
 Tomcat:type=Deployer,host=localhost
 1. Connect to your running instance with JConsole*.
 2. Examine the MBeans published by the instance.
 3. Confirm that you are connecting to the correct MBean.


 I wouldn't expect:

  Tomcat:type=Deployer,host=localhost

 to work.


 p


 * or VisualVM with the JConsole plugin enabled.

 




signature.asc
Description: OpenPGP digital signature

Re: webapps and TCP/UDP listening sockets

2011-07-01 Thread Tim Judd

David,

Thank you loads.  :)



 If opportunity doesn't knock, build a door.
I can is a way of life.
More and Bigger is not always Better.
The road to success is always uphill.





From: David kerber dcker...@verizon.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Fri, July 1, 2011 9:03:58 AM
Subject: Re: webapps and TCP/UDP listening sockets

On 6/30/2011 11:45 PM, Tim Judd wrote:
 Hi Christopher, all

 'machine' was meant to indicate one of two choices, the computer that is 
running
 the tomcat server, or the computer who is the client in a client-server
 relationship.  I don't know the intricities of webapps yet in how they run.
 This thread was just trying to understand if I'm barking up the wrong tree.

 Your second paragraph is better phrased.  which computer/'machine' is doing 
the
 binding?  Writing a standalone Java desktop app is most definately going to 
bind
 to it's own machine.  I don't need to delegate anything to Tomcat itself, I 
need
 to know if I run a webapp and it binds and listens to a socket, which machine
 does it bind on?

A Webapp by definition runs in tomcat, and will bind on the server.  I 
don't know anything about x11, but if it's similar to Citrix or 
Microsoft RDP, then even a local java app is going to be actually 
running on the server (and therefore binding the sockets there), and 
only sending the console to your client.




 Lastly, your statement about making it a webapp if http is not involved is
 because to centrally deploy an application is often served off http; I wanted 
to
 get into Java/webapps so I elected this route.  If they are standalone 
protocols
 (and they will be) to communicate between many clients to one (or a farm) of
 servers, why can't I launch it from http?


   If opportunity doesn't knock, build a door.
 I can is a way of life.
 More and Bigger is not always Better.
 The road to success is always uphill.




 
 From: Christopher Schultzch...@christopherschultz.net
 To: Tomcat Users Listusers@tomcat.apache.org
 Sent: Thu, June 30, 2011 8:07:55 PM
 Subject: Re: webapps and TCP/UDP listening sockets

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Tim,

 On 6/30/2011 7:14 PM, Tim Judd wrote:
 If I develop a webapp that listens for TCP/UDP sockets, which machine is
 actually listening?

 When you say machine... you mean ... what, exactly?

 If you develop a webapp that listens for TCP/UDP sockets, where is the
 socket bind occurring? If it's your webapp, then it really has nothing
 to do with Tomcat at all: it's just like writing a non-webapp program
 that binds to a socket and listens.

 If you want to delegate incoming requests to threads from Tomcat's
 request processor pool, that might be a bit tricky. Is that what you'd
 like to do?

 Do you really need Tomcat in this situation?

 Is the tomcat server listening (because the webapp is
 running on that tomcat) or is the client listening (because he is running the
 webapp on the tomcat server)!

 Probably both, but it depends on your answer to the above questions.

 My goal is to have:
single UDP listening at tomcat server for packets, and
multicast UDP listening at the clients that is getting resended off the
 single

 above UDP port from the webapp tomcat server

 Why do you want to build this as a web-based application if HTTP isn't
 really involved?

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAk4NK/sACgkQ9CaO5/Lv0PBlLwCaAqi72qyRX1HCwlrtor+NS62X
 YiQAoLuYcbXt4tp9oQ0B+hTCqaocDbkG
 =QlO7
 -END PGP SIGNATURE-

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



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

Re: webapps and TCP/UDP listening sockets

2011-07-01 Thread André Warnier

Tim Judd wrote:

Hi Pid, all

I'm disappointed the responses I've gotten seemingly to be scolding messages. I
am reading up on documentation, I am reading the APIs, I am reading everything I
can. Think of Citrix (in Windows environments) - code is executed on the server
and displayed on your desktop; X11 forwarding does the same thing. I don't know
which machine is executing the code

I understand you guys are trying to help, but I am disappointed all I'm hearing
is you're doing it wrong basically. I was hoping a quick answer to know which
machine is executing the code which would be the same side that has it bound.

Does anyone know which machine will bind?

You are not being scolded, you are being pointed to sources of information about TCP/IP
which may help you phrase your questions in a way that people here may have an easier time
understanding and answering.
Nobody really feels like re-writing what these articles already explain at length, and
which has basically nothing to do with helping people with Tomcat, which is what the
helping souls on this forum are trying to do.

Not because you are - wrongly - complaining, but because it may avoid other people wasting
their time, here is a brief overview :

- a socket is a OS-level structure which represents a network channel between 2
applications (possibly on different computers)

- there are 2 types of sockets :
- a server (or listening) socket
- a client socket
- the terms bind or binding are used only with the server type of socket
- an application can request from the OS to allocate (or open) a socket for it, and when
it does that, it specifies if it wants a server or client socket.
If the requested socket is of the server type, then the action of requesting this socket
may be called binding.
- a server socket is passive : it sits there, waiting for connections to it. When it
receives a connection, it informs the application that is bound to it. This server
application can then read what the other party (a client) sent to this socket, and respond
over the same socket.

- a client socket's purpose is usually to be used to connect to a distant
server socket.
Normally the purpose is to allow the application which owns the client socket, to send
some request or message to the application which is bound to the server socket (which is
at the other end of the link), and to receive a response over that same channel and socket.

- all the above is true for TCP, and a bit less so for UDP.
- and finally, no matter what type of socket we are talking about, when an application
asks the OS to create (open) a socket for it, it is always on the same server where this
application runs. So an application running on server A, can only bind to or open a
socket on server A.

Do you understand now why your questions are a bit confusing ?

Just quoting one of them :
If I develop a webapp that listens for TCP/UDP sockets, which machine is
actually listening?

Hopefully, the above makes clear that an application does not listen for sockets, and
why everyone here is a bit uncertain about what to answer.

And a webapp usually does not open any kind of socket, since it (indirectly) receives
requests and sends responses through Tomcat (which does own sockets for that).
A webapp could open a separate client socket, but it would only do that if it wanted
itself to talk, as a client, to some separate server application somewhere.

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

RE: Tomcat 7 Embedded: Manager

2011-07-01 Thread Caldarale, Charles R

 From: Dark Before Dawn [mailto:dark.before.d...@gmail.com] 
 Subject: Re: Tomcat 7 Embedded: Manager

 i guess the problem is that the manager-servlet's context is 
 mounted at root

I think right there we have a conceptual problem, or at least a terminology 
one.  Webapps aren't mounted in the sense things are in httpd; every webapp 
in a servlet container is independent of the other webapps, and each webapp has 
_one_ unique URI path to select the webapp; normally, the path is also used as 
the deployment location (docBase, in Tomcat terminology).  The exception is the 
default webapp, which must be deployed as ROOT - case sensitive - in Tomcat, 
and has an empty path; it is selected only when no other webapp paths can be 
matched to the request URI.

Servlet mappings exist _within_ a webapp, and do not include the webapp path, 
so that the same webapp can be deployed under different paths as needed without 
changing the deployment descriptor.  Consequently, mappings for servlets within 
the manager webapp are of the form /html/* and /text/* rather than 
/manager/html/* and /manager/text/*.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

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

Re: webapps and TCP/UDP listening sockets

2011-07-01 Thread Mark Eggers

- Original Message -

 From: Tim Judd tjud...@yahoo.com
 To: Tomcat Users List users@tomcat.apache.org
 Cc: 
 Sent: Friday, July 1, 2011 7:52 AM
 Subject: Re: webapps and TCP/UDP listening sockets

 Hi Pid, all

 I'm disappointed the responses I've gotten seemingly to be scolding 
 messages.  I 
 am reading up on documentation, I am reading the APIs, I am reading 
 everything I 

 can.  Think of Citrix (in Windows environments) - code is executed on the 
 server 

 and displayed on your desktop; X11 forwarding does the same thing.  I don't 
 know 
 which machine is executing the code

 I understand you guys are trying to help, but I am disappointed all I'm 
 hearing 
 is you're doing it wrong basically.  I was hoping a quick answer 
 to know which 
 machine is executing the code which would be the same side that has it bound.

 Does anyone know which machine will bind?

I don't think anyone is trying to scold you as such. Some people may be 
wondering why Tomcat is involved with this is all.

That being said, I've written a rather lengthy response to your question. OK, I 
hope it's a proper response.

The first part covers (briefly) running a network server under Tomcat. The 
second part covers an idea (alternative approach) that would actually leverage 
Tomcat's capabilities. I hope this is useful.

Hopefully this is not off the mark.

Here's my understanding of the problem and your solution.

1. Deploy a client-server CRM software package
2. CRM has both point to point and broadcast requirements
3. Centrally deployed server
4. Potentially load-balanced farm of servers

You have tentatively decided on approaching requirement 2 with a
custom UDP and multicast protocol.

You are asking if you can leverage Tomcat (or maybe another servlet
container) to help with communications, deployment, and resiliency of
your solution.

The short answer is probably not, not without a lot of work.

I think the best that you're going to achieve with Tomcat is something
like what Derby does with its derby.war implementation.

Apache Derby comes with a war file that allows you to run a networked
derby database from within Tomcat. This war file provides a command /
control / monitoring interface for the Derby database. This interface
is accessible through Tomcat.

However, Tomcat does not provide the network connection for the actual
database and its clients. This is provided by the network Derby
server, which listens on TCP port 1527 (by default).

The database communication is under complete control of the Derby
network server, and does not use Tomcat resources.

You can accomplish this for your system. You should look at the source
code for the derby.war file to see how the command / control /
monitoring interface is built.

However, I don't think this is all that you want to accomplish.

Now we get to the architecture of your system. If you wish to leverage
Tomcat's resources, then there are several ways of going about
it. Talking off the top of my head, here are some ideas.

1. Use Tomcat 7.0.x

This will allow you to use asynchronous servlets. Coupled with AJAX,
you can then broadcast messages to all waiting clients. With Tomcat
6.0.x, there was a container-specific way of accomplishing this (with
Comet).

2. Use AJAX or AJAX / JSON for normal data communications

This is independent of what server you use (could be Tomcat, Apache
HTTPD, IIS, etc.) or language (Java, Perl, PHP, C#, etc.). This will
make your application more lively. There are security considerations
when doing this, so please research carefully.

3. Desktop application

There's no reason why a platform communicating via HTTP has to be a
web browser. You could write a client in JavaFX (for example) to
interact with the server portion of your application.

In order to go this route (Tomcat, HTTP, asynchronous servlets, AJAX,
JSON), you will have to do some research.

Before diving into the servlet 3.0 specifications and asynchronous
servlets, I recommend getting your feet wet with some basic
concepts. A good book for doing that is:

Head First Servlets and JSP

There's also an AJAX book in the same vein.

Head Rush Ajax

Neither of these books serve as complete references, but they do
introduce you to the concepts necessary for building what I think
you're trying to accomplish.

Once you've wrapped your head around the concepts in these books, then
you would benefit from reading the servlet specification (sounds like
3.0 will fit your requirements as I understand them).

You'll probably want to have your application interact with a
database as well. In that case, Hibernate may be a good fit. There are
several books on that, as well as a Tomcat Wiki article on how to get
Hibernate to work with Tomcat's database pooling mechanism.

Hopefully, this has been useful. I apologize if I'm completely off
base here.

. . . . just my two cents.

/mde/

-
To unsubscribe, e-mail:

Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rohan,

On 7/1/2011 7:56 AM, Rohan Kadam wrote:
 We have created a service named say ABCTomcat
 
 Then we navigated to bin directory of tomcat, typed the following command -
 
 tomcat7w.exe //ES//ABCTomcat
 
 After that Iwent to Java Tab, and added the below line in Java Option Section.
 
 Please let me know if I am missing something.

The line.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4OED4ACgkQ9CaO5/Lv0PBFygCglpsASTcalnv9mU6E7+UfjQvO
BggAoJuFtVP1GbebaBvvQRPgF+at3sjI
=/xpV
-END PGP SIGNATURE-

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

Re: webapps and TCP/UDP listening sockets

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tim,

On 7/1/2011 10:52 AM, Tim Judd wrote:
 I understand you guys are trying to help, but I am disappointed all I'm 
 hearing 
 is you're doing it wrong basically.

You're reading it wrong: I was asking what are you doing? not telling
you that you are doing it wrong.

 I was hoping a quick answer to know which 
 machine is executing the code which would be the same side that has it bound.

The machine where you launch the program is the machine that executes
the code. That's pretty universal, you just need to understand the code
you're talking about.

In your Citrix example, you run the Citrix client on (let's say) your
home computer, and that code continues to run there pretty much for all
time (until you terminate the program). If that program runs /another/
program remotely and displays the contents, then the remote program has
always been remote and you are just being allowed to interact with it at
a distance.

 Does anyone know which machine will bind?

If you are running a webapp, the servlet container will always bind on
the server and a traditional webapp never binds to anything at all: the
container (Tomcat in this case) handles everything.

If you write a program to call-up a web server and request information,
your client program will bind to whatever machine it runs on (your home
computer perhaps) and the two programs exchange information over the wire.

You can't run a program on one machine that binds to a port on another
machine, at least without some super-special black magic going on.

If you write a web application that creates it's own sockets (which is
what we're saying doesn't make any sense to do, but it's hard to tell
what on earth you're talking about in the first place), they will bind
on the server, never the client.

Does that clear anything up?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4OEzEACgkQ9CaO5/Lv0PBdRwCglxGxEUtNGQyM4e78TyxB4o+x
JuIAnikPTGtj9VyG6CMpIgliu67+VIvp
=aIQI
-END PGP SIGNATURE-

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

Re: [OT] webapps and TCP/UDP listening sockets

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

On 7/1/2011 11:03 AM, David kerber wrote:
 I don't know anything about x11, but if it's similar to Citrix or 
 Microsoft RDP

No, it's Citrix and RDP that are like X11 :)

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4OFF8ACgkQ9CaO5/Lv0PBPCwCeIHfsuGyFfBDfKkDDqDEXM4vy
im8AoJVw1gMuMEN7ISBZZUayudvXeB3m
=mWsT
-END PGP SIGNATURE-

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

Re: Access to manager webapp (JAAS exception)