[Resin-interest] resin (non-pro) 3.2.0.x won't start.... error w/ watchdog:

[Vic Cekvenich]

[EMAIL PROTECTED] bin]# ./resin.sh start
Resin/3.2.0 can't start -server '' for watchdog at 127.0.0.1:6600.
com.caucho.config.ConfigException: user-name requires compiled JNI.
Check the $RESIN_HOME/libexec or $RESIN_HOME/libexec64 directory for
libresin_os.so.
[EMAIL PROTECTED] bin]#

help?


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] resin (non-pro) 3.2.0.x won't start.... error w/ watchdog:

[Rob Lockstone]

On Dec 10, 2008, at 11:31, Vic Cekvenich wrote:

 [EMAIL PROTECTED] bin]# ./resin.sh start
 Resin/3.2.0 can't start -server '' for watchdog at 127.0.0.1:6600.
 com.caucho.config.ConfigException: user-name requires compiled JNI.
 Check the $RESIN_HOME/libexec or $RESIN_HOME/libexec64 directory for
 libresin_os.so.
 [EMAIL PROTECTED] bin]#

 help?

Open your resin.xml file and search for user-name. Comment that  
section out or bracket with:

resin:if test=${resin.professional}
 ...
/resin:if

Rob



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] thread dump from StatService

[Scott Ferguson]

On Dec 10, 2008, at 2:19 PM, Vinny wrote:

 Running Resin 3.1.6 on centos linux 5,  2.0ghz proc , 2G ram.
 I have a box that is running a bunch of virtual hosts configured in  
 resin and also connects to Apache 2.2.3 via mod_caucho.

 I am getting these in the logs and I'm wondering how I can read this  
 in order to figure out why my cpu load is being pegged so high

Can you do a 'ps' or 'top' to make sure that Resin is the overloading  
process?  Since that thread dump doesn't show any active threads, if  
the Resin JVM has a high CPU, then something odd is happening.

With the exception of the CMS thread, those are all idle Resin  
threads.  So the load due to Resin should be zero based on that thread  
dump.

-- Scott


 Thanks in advance:

 == /usr/local/resin/log/jvm-default.log ==
 [21:36:00.000] StatService[] cpu-load=11.57
 [21:36:00.001] StatService[] dumping threads due to cpu load=11.57
 [21:36:00.003] Thread Dump:
 [21:36:00.003]
 [21:36:00.003] Signal Dispatcher id=5 RUNNABLE
 [21:36:00.003]
 [21:36:00.003] Surrogate Locker Thread (CMS) id=4 RUNNABLE
 [21:36:00.003]
 [21:36:00.003] resin-pro-statistics id=27 RUNNABLE
 [21:36:00.003]   at sun.management.ThreadImpl.getThreadInfo0  
 (ThreadImpl.java) (native)
 [21:36:00.003]   at sun.management.ThreadImpl.getThreadInfo  
 (ThreadImpl.java:147)
 [21:36:00.003]   at  
 com.caucho.server.admin.ThreadDump.threadDumpImpl (ThreadDump.java:46)
 [21:36:00.003]   at com.caucho.server.admin.ThreadDump.dumpThreads  
 (ThreadDump.java:38)
 [21:36:00.003]   at com.caucho.server.admin.StatService.run  
 (StatService.java:135)
 [21:36:00.003]   at java.lang.Thread.run (Thread.java:619)
 [21:36:00.003]
 [21:36:00.003] RMI TCP Accept-0 id=10 RUNNABLE (in native)
 [21:36:00.003]   at java.net.PlainSocketImpl.socketAccept  
 (PlainSocketImpl.java) (native)
 [21:36:00.003]   at java.net.PlainSocketImpl.accept  
 (PlainSocketImpl.java:384)
 [21:36:00.003]   at java.net.ServerSocket.implAccept  
 (ServerSocket.java:453)
 [21:36:00.003]   at java.net.ServerSocket.accept (ServerSocket.java: 
 421)
 [21:36:00.003]   at sun.rmi.transport.tcp.TCPTransport 
 $AcceptLoop.executeAcceptLoop (TCPTransport.java:369)
 [21:36:00.003]   at sun.rmi.transport.tcp.TCPTransport 
 $AcceptLoop.run (TCPTransport.java:341)
 [21:36:00.003]   at java.lang.Thread.run (Thread.java:619)
 [21:36:00.003]
 [21:36:00.003] hmux-127.0.0.1:6802-105 id=1859 RUNNABLE (in native)
 [21:36:00.003]   at com.caucho.vfs.JniSocketImpl.readNative  
 (JniSocketImpl.java) (native)
 [21:36:00.003]   at com.caucho.vfs.JniSocketImpl.read  
 (JniSocketImpl.java:279)
 [21:36:00.003]   at com.caucho.vfs.JniStream.readTimeout  
 (JniStream.java:87)
 [21:36:00.003]   at com.caucho.vfs.ReadStream.fillWithTimeout  
 (ReadStream.java:982)
 [21:36:00.003]   at  
 com.caucho.server.port.TcpConnection.waitForKeepalive  
 (TcpConnection.java:208)
 [21:36:00.003]   at com.caucho.server.port.TcpConnection.run  
 (TcpConnection.java:691)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.runTasks  
 (ThreadPool.java:721)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.run  
 (ThreadPool.java:643)
 [21:36:00.003]   at java.lang.Thread.run (Thread.java:619)
 [21:36:00.003]
 [21:36:00.003] hmux-127.0.0.1:6802-107 id=1881 RUNNABLE (in native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.nativeAccept  
 (JniServerSocketImpl.java) (native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.accept  
 (JniServerSocketImpl.java:199)
 [21:36:00.003]   at com.caucho.server.port.Port.accept (Port.java: 
 1176)
 [21:36:00.003]   at com.caucho.server.port.TcpConnection.run  
 (TcpConnection.java:655)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.runTasks  
 (ThreadPool.java:721)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.run  
 (ThreadPool.java:643)
 [21:36:00.003]   at java.lang.Thread.run (Thread.java:619)
 [21:36:00.003]
 [21:36:00.003] hmux-127.0.0.1:6802-108 id=1871 RUNNABLE (in native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.nativeAccept  
 (JniServerSocketImpl.java) (native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.accept  
 (JniServerSocketImpl.java:199)
 [21:36:00.003]   at com.caucho.server.port.Port.accept (Port.java: 
 1176)
 [21:36:00.003]   at com.caucho.server.port.TcpConnection.run  
 (TcpConnection.java:655)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.runTasks  
 (ThreadPool.java:721)
 [21:36:00.003]   at com.caucho.util.ThreadPool$Item.run  
 (ThreadPool.java:643)
 [21:36:00.003]   at java.lang.Thread.run (Thread.java:619)
 [21:36:00.003]
 [21:36:00.003] hmux-127.0.0.1:6802-57 id=1897 RUNNABLE (in native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.nativeAccept  
 (JniServerSocketImpl.java) (native)
 [21:36:00.003]   at com.caucho.vfs.JniServerSocketImpl.accept  
 (JniServerSocketImpl.java:199)
 [21:36:00.003]   at com.caucho.server.port.Port.accept (Port.java: 
 1176)
 [21:36:00.003]   at com.caucho.server.port.TcpConnection.run  

Re: [Resin-interest] Using php views in Spring framework - can one benefit from resin Pro compilation features?

[Emil Ong]

Hi Huima,

I just gave a talk at Devoxx about Quercus and I mentioned that you were
using Spring MVC and Quercus in this way.  I got a couple of questions
about details and code samples.  Any chance you can share some with us?

Thanks!
Emil



- Original Message 
 From: Heimo Laukkanen [EMAIL PROTECTED]
 To: resin-interest@caucho.com
 Sent: Thursday, December 4, 2008 7:07:46 PM
 Subject: [Resin-interest] Using php views in Spring framework - can one 
 benefit from resin Pro compilation features?
 
 Hi all,
 
 I'm using Quercus views in out project as Spring Framework MVC views
 with in similar way as is done in Resin's quercus servlet.
 
 I was just wondering whether we could benefit from or use Caucho Pro's
 capabilities to compile php code into javacode in our project somehow
 - even when we are not using QuercusServlet?
 
 Is there a source-code available for QuercusServlet in the pro-version
 that could be used as a base, if we would like to use the pro version
 of the appserver and quercus?
 
 -huima
 
 
 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest