[Installation, Configuration & DEPLOYMENT] - JBoss deployment on XP loops
by iyerji2
Hi
I have a jboss app (that is copied off of default.)
It runs fine on my desktop (windows XP)
when I try running it on another XP box it
starts up and immediately ends up w/ the socket exception below
which loops and makes a big server.log file.
conf/jboss-service.xml file looks fine. There are no differences
(i'm zipping up the server/myApp directory and deploying to the
other machine)
Something is different on the new machine.
Any clues would help
-Thanks
| 2007-08-28 14:56:13,328 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
| 2007-08-28 14:56:13,328 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 21s:500ms
| 2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
| 2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
| 2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
| 2007-08-28 14:56:14,031 ERROR [org.jboss.naming.Naming] Naming accept handler stopping
| java.net.SocketException: socket closed
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| at java.net.ServerSocket.implAccept(ServerSocket.java:450)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.jnp.server.Main$AcceptHandler.run(Main.java:481)
| at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| 2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
| 2007-08-28 14:56:14,046 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:3873] failed to handle socket
| java.net.SocketException: socket closed
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| at java.net.ServerSocket.implAccept(ServerSocket.java:450)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
| at java.lang.Thread.run(Thread.java:595)
| 2007-08-28 14:56:14,046 ERROR [org.jboss.invocation.pooled.server.PooledInvoker] Failed to accept socket connection
| java.net.SocketException: socket closed
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| at java.net.ServerSocket.implAccept(ServerSocket.java:450)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.jboss.invocation.pooled.server.PooledInvoker.run(PooledInvoker.java:262)
| at java.lang.Thread.run(Thread.java:595)
| 2007-08-28 14:56:14,046 ERROR [org.apache.tomcat.util.net.JIoEndpoint] Socket accept failed
| java.net.SocketException: socket closed
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| at java.net.ServerSocket.implAccept(ServerSocket.java:450)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
| at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
| at java.lang.Thread.run(Thread.java:595)
| 2007-08-28 14:56:14,046 ERROR [org.jboss.naming.Naming] Naming accept handler stopping
| java.net.SocketException: socket closed
| at java.net.PlainSocketImpl.socketAccept(Native Method)
| at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
| at java.net.ServerSocket.implAccept(ServerSocket.java:450)
| at java.net.ServerSocket.accept(ServerSocket.java:421)
| at org.jnp.server.Main$AcceptHandler.run(Main.java:481)
| at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| 2007-08-28 14:56:14,046 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
| 2007-08-28 14:56:14,046 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:3873] failed to handle socket
| java.net.SocketException: socket closed
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079744#4079744
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079744
19Â years
Portal CMS
by Boudreau Luc
Hello,
I've installed JBoss portal 2.6.1-CR1 on JBoss AS 4.0.5. When erasing
the portal DB on MySQL 5.0.45 and starting the AS, all the tables get
created. I can then access the CMS content, but every time I change
something in the repository, once I restart, it's not there anymore. The
CMS jboss-service file is configured properly for RDBMS storage and the
datasource has the 'jdbcCompliantTruncation' parameter set to false to
solve the famous MySQL 5 truncation error.
Also, changing the access rights on the CMS content has no effect, thus
enforcing my theory which is this : the CMS doesn't use the database at
all. Also, the table jbp_cms_cmsentry is empty. Is that normal ?
The only error included in the log is concerning JBoss cache :
==========================================
2007-08-30 14:45:09,073 WARN
[org.jboss.cache.interceptors.CacheLoaderInterceptor] CacheLoader.get()
should return an empty Map if the node does exist but doesn't have any
attributes.
2007-08-30 14:45:09,174 WARN
[org.jboss.cache.interceptors.CacheLoaderInterceptor]
CacheLoader.get(Fqn) returned a null; assuming the node nodes not exist.
2007-08-30 14:45:09,174 WARN
[org.jboss.cache.interceptors.CacheLoaderInterceptor] The CacheLoader
interface has changed since JBossCache 1.3.x
2007-08-30 14:45:09,174 WARN
[org.jboss.cache.interceptors.CacheLoaderInterceptor] Please see
http://jira.jboss.com/jira/browse/JBCACHE-118
============================================
I don't know if this is related nor how to fix this. Please help.
19Â years