Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems

2010-01-30 Thread fatzopilot

Hi Chris,

Thank you for your response and time.
 Okay. Generally, it's considered polite to ask a single question in a
 single thread. Next time, just post them separately.
You are right and I would have done that but thought the issues might be
connected and caused by some low level system problem (firewall etc.) thence
I bundled them.
Luckily, meanwhile all issues are gone. Not sure what actually caused them
but I will post my assumptions.

 1st issue: I cannot connect to a socket server embedded in a webapp and
 listening on port 1 any more in all cases. If I do it from a mobile
 device, it works, if i do it from my laptop over a dsl connection (router
 in
 between), a channel is opened and instantly closed.
This seemed to be caused by connecting too fast to the socket server.
Lowering the sending frequency solved the issue.

 2nd issue: mod_jk does not work. I think I replayed multiple instructions
 to
 set it up multiple times but in all cases it finally says Could not find
 a
 worker for worker name=myWorker

Solved by using the procedure described here (till item 11):
http://ubuntuforums.org/showthread.php?t=971517

I now use (for worker.properties):
workers.tomcat_home=/usr/share/tomcat5.5
workers.java_home=/usr/lib/jvm/java-1.5.0-sun
ps=/
worker.list=myWorker
worker.myWorker.port=8009
worker.myWorker.host=localhost
worker.myWorker.type=ajp13
worker.myWorker.lbfactor=1

which before was
workers.list=myWorker,ajp13
workers.myWorker.type=ajp13
workers.myWorker.host=localhost
workers.myWorker.port=8009

 3rd issue: GWT-RPC calls do not get delivered any more to the browser on
 my
 laptop.
After having solved 1) I switched back to IPV6. Not sure if exactly this
caused the calls to work again but now they work :)

Cheers and sorry for bugging
fatzopilot


-- 
View this message in context: 
http://old.nabble.com/Tomcat-on-Ubuntu-8.04-VPS-and-presumably-multiple-socket-problems-tp27332135p27385269.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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



Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems

2010-01-30 Thread Rainer Jung

On 30.01.2010 17:41, fatzopilot wrote:

2nd issue: mod_jk does not work. I think I replayed multiple instructions
to
set it up multiple times but in all cases it finally says Could not find
a
worker for worker name=myWorker


Solved by using the procedure described here (till item 11):
http://ubuntuforums.org/showthread.php?t=971517

I now use (for worker.properties):
workers.tomcat_home=/usr/share/tomcat5.5


This attribute doesn't do anything, the line can be deleted.


workers.java_home=/usr/lib/jvm/java-1.5.0-sun


This attribute doesn't do anything, the line can be deleted.


ps=/


This attribute doesn't do anything, the line can be deleted.


worker.list=myWorker
worker.myWorker.port=8009
worker.myWorker.host=localhost
worker.myWorker.type=ajp13
worker.myWorker.lbfactor=1


OK, ver ybasic but should work.


which before was
workers.list=myWorker,ajp13
workers.myWorker.type=ajp13
workers.myWorker.host=localhost
workers.myWorker.port=8009


The problem was the plural workers, which was wrong. After fixing this 
your original configuration should have worked, at least after dropping 
the non-defined worker ajp13 from worker.list.


Regards,

Rainer

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



Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems

2010-01-30 Thread fatzopilot

Rainer,

Thanks for clarification. There are a lot of misleading configuration
'tweaks' roaming around which do not seem to have any effect (or at least
not in recent versions). The minimal config now works well for me.

Cheers
fatzopilot


Rainer Jung-3 wrote:
 
 On 30.01.2010 17:41, fatzopilot wrote:
 2nd issue: mod_jk does not work. I think I replayed multiple
 instructions
 to
 set it up multiple times but in all cases it finally says Could not
 find
 a
 worker for worker name=myWorker

 Solved by using the procedure described here (till item 11):
 http://ubuntuforums.org/showthread.php?t=971517

 I now use (for worker.properties):
 workers.tomcat_home=/usr/share/tomcat5.5
 
 This attribute doesn't do anything, the line can be deleted.
 
 workers.java_home=/usr/lib/jvm/java-1.5.0-sun
 
 This attribute doesn't do anything, the line can be deleted.
 
 ps=/
 
 This attribute doesn't do anything, the line can be deleted.
 
 worker.list=myWorker
 worker.myWorker.port=8009
 worker.myWorker.host=localhost
 worker.myWorker.type=ajp13
 worker.myWorker.lbfactor=1
 
 OK, ver ybasic but should work.
 
 which before was
 workers.list=myWorker,ajp13
 workers.myWorker.type=ajp13
 workers.myWorker.host=localhost
 workers.myWorker.port=8009
 
 The problem was the plural workers, which was wrong. After fixing this 
 your original configuration should have worked, at least after dropping 
 the non-defined worker ajp13 from worker.list.
 
 Regards,
 
 Rainer
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Tomcat-on-Ubuntu-8.04-VPS-and-presumably-multiple-socket-problems-tp27332135p27386170.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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



Re: Tomcat on Ubuntu 8.04 VPS and presumably multiple socket problems

2010-01-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Fatzopilot,

On 1/26/2010 7:16 PM, fatzopilot wrote:
 I switched from a Windows XP based VPS to a Ubuntu 8.04 linux machine.

Good choice! Are you still on a virtualized platform?

 Both run Tomcat 6.0.18 and 2.2.8 on tcp4.

Could that mean Apache httpd 2.2.8 on IPv4?

 I now face several problems that might
 be related to some low level socket issue but do not necessarily need to. I
 am already glad to receive some hints to further boil down the issues.

Okay. Generally, it's considered polite to ask a single question in a
single thread. Next time, just post them separately.

 1st issue: I cannot connect to a socket server embedded in a webapp and
 listening on port 1 any more in all cases. If I do it from a mobile
 device, it works, if i do it from my laptop over a dsl connection (router in
 between), a channel is opened and instantly closed.

Hmm... so, on the Linux install, mobile devices (presumably through the
wireless provider's network) connect correctly, but non-mobile devices fail?

This sounds like it might be a firewall issue. Does your laptop allow
outgoing connections to port 1? How about your router? Are you on a
corporate network with IT Nazis preventing you from doing anything but
using ports 80 and 443? You can use traceroute or other tools to confirm
connectivity independently of the server software. Telnet also helps,
sometimes, too.

 2nd issue: mod_jk does not work. I think I replayed multiple instructions to
 set it up multiple times but in all cases it finally says Could not find a
 worker for worker name=myWorker

Please post the relevant parts of your httpd.conf and
jk_workers.properties. Most often, I've seen configurations where the
JkWorkersFile directive is in the wrong place. Also, please post as much
error information as mod_jk provides in your mod_jk.log file.

 3rd issue: GWT-RPC calls do not get delivered any more to the browser on my
 laptop.

This is probably due to issue #1 above, no?

 IPtables is turned off. 

On your laptop, on the server, or both?

 tcp0  0 127.0.0.1:8009  0.0.0.0:*   LISTEN
  
 29931/jsvc 

So, Tomcat is listening on port 8009, which is the default AJP port in
server.xml. Tomcat looks like it's expecting to receive requests from
httpd via AJP (provided by mod_jk).

 tcp0  0 0.0.0.0:1   0.0.0.0:*   LISTEN
  
 29931/jsvc 

Also good: Tomcat is listening to port 1. This means that your
Tomcat configuration appears to be correct in terms of SecurityManager
(if present), socket binding rights, etc.

 tcp0  0 0.0.0.0:80800.0.0.0:*   LISTEN
  
 29931/jsvc 

Note that Tomcat is also listening to port 8080, which is the default
HTTP port in server.xml. If you don't want connections to circumvent
httpd, you might want to disable this connector.

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

iEYEARECAAYFAktgjyEACgkQ9CaO5/Lv0PCO3ACfU1bRXkSPB6Ra3WiepoMMmdUN
V1wAoJuA6cOFHCG1EQnBxH9Ex30ADjMM
=XGBZ
-END PGP SIGNATURE-

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