[Installation, Configuration & DEPLOYMENT] - Jboss 4.2.2GA shutdown always hangs under user load
by bitti1976
My Jboss process will not gracefully shutdown ocassionally.
I am using the "shutdown.sh -S" command first and then try to kill the parent process from a script. But the shutdown seems to stop at the following line (from server.log). Normal kill also doesn work, and then I have to do a kill -9 on both the parent and the child process (I start the run.sh in background), which is when the process eventually clears up, but without any logging in the server.log file. has anyone else observed tjis behavior, and is there a workaround/fix available for it. Thanks for your help in advance! -Yasha
2008-10-29 16:52:20,784 INFO [org.jboss.system.server.Server] Shutting down the server, blockingShutdown: false
2008-10-29 16:52:20,833 INFO [org.jboss.system.server.Server] Server exit(0) called
2008-10-29 16:52:20,836 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
2008-10-29 16:52:20,842 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
2008-10-29 16:52:20,842 INFO [org.jboss.web.tomcat.service.TomcatDeployer] undeploy, ctxPath=/solr, warUrl=.../tmp/deploy/tmp48792solr-exp.war/
2008-10-29 16:52:21,216 INFO [org.jboss.web.tomcat.service.TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
2008-10-29 16:52:21,227 INFO [org.jboss.ejb.EJBDeployer] Undeploying: file:/u01/jboss-4.2.2.GA/server/core/deploy/ejb-management.jar
2008-10-29 16:52:21,236 INFO [org.jboss.proxy.ejb.ProxyFactory] Unbind EJB Home 'MEJB' from jndi 'ejb/mgmt/MEJB'
2008-10-29 16:52:21,236 INFO [org.jboss.ejb.EjbModule] Undeployed MEJB
2008-10-29 16:52:21,238 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
2008-10-29 16:52:21,242 INFO [org.jboss.mq.server.jmx.Topic.testTopic] Unbinding JNDI name: topic/testTopic
2008-10-29 16:52:21,243 INFO [org.jboss.mq.server.jmx.Topic.securedTopic] Unbinding JNDI name: topic/securedTopic
2008-10-29 16:52:21,243 INFO [org.jboss.mq.server.jmx.Topic.testDurableTopic] Unbinding JNDI name: topic/testDurableTopic
2008-10-29 16:52:21,244 INFO [org.jboss.mq.server.jmx.Queue.testQueue] Unbinding JNDI name: queue/testQueue
2008-10-29 16:52:21,268 INFO [org.jboss.mq.server.jmx.Queue.A] Unbinding JNDI name: queue/A
2008-10-29 16:52:21,269 INFO [org.jboss.mq.server.jmx.Queue.B] Unbinding JNDI name: queue/B
2008-10-29 16:52:21,269 INFO [org.jboss.mq.server.jmx.Queue.C] Unbinding JNDI name: queue/C
2008-10-29 16:52:21,269 INFO [org.jboss.mq.server.jmx.Queue.D] Unbinding JNDI name: queue/D
2008-10-29 16:52:21,270 INFO [org.jboss.mq.server.jmx.Queue.ex] Unbinding JNDI name: queue/ex
2008-10-29 16:52:21,275 INFO [org.jboss.mq.server.jmx.Queue.DLQ] Unbinding JNDI name: queue/DLQ
2008-10-29 16:52:21,277 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS' - HANGS at this line, and never really shuts down
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185775#4185775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185775
17 years, 5 months
[JBossWS] - Stateless Session EJB Endpoint (JBossWS Native)
by tperrigo
JBoss 5.0.0.CR2, JBossWS Native (latest distribution). I've got a stateless session bean that I want to use as a web service endpoint. I created an Eclipse project using the (very handy!) ant tasks provided by the JBossWS Native distribution. I created my @Stateless-annotated implementation class, and specified (using @Remote) the remote interface for the class.
Using ant build file generated by the JBossWS ant tasks, I was able to build and deploy my jar file, although, both at app server startup and deployment time, I receive the following error:
| /usr/local/jboss-5.0.0.CR2/server/logos/deploy/jbossws-container-jboss-beans.xml -> java.lang.IllegalStateException: WSKernelLocator is already installed.
|
The web service appears in the list of deployed services in the jbossws console, but I thought for my first test I would simply try to invoke the service as an EJB (through the Remote interface). The JNDI lookup succeeds (it finds an object with the proper JNDI name), but when I try to cast it to the EJB's Remote Interface, I get a ClassCastException. When I print out the actual type of the object returned from the JNDI lookup, I find that it is an instance of javax.naming.Reference.
So my questions are:
(1) Does anyone know what the startup / deployment error means?
(2) Why can't I seem to get a reference to my RemoteInterface via a JNDI lookup? (Why the ClassCastException?)
Sorry for being so long-winded, I just wanted to include anything that might help. Any advice would be very much appreciated!
Tim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185771#4185771
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185771
17 years, 5 months
[JNDI/Naming/Network] - Re: MS SQL datasource error
by vitechinc2008
Thanks for advice...I will remember it next time:
Now that i have copy the jar file to lib directory. I am getting the following error:
Does it mean I have the wrong driver:
-----Error----
2008-10-30 11:23:41,012 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2008-10-30 11:23:41,012 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2008-10-30 11:23:41,012 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2008-10-30 11:23:41,012 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:190)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:619)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:264)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:575)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:347)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:330)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:402)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:849)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
at org.springframework.orm.hibernate.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:77)
at net.sf.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:73)
at net.sf.hibernate.cfg.Configuration.buildSettings(Configuration.java:1156)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:790)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:540)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:474)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1202)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:428)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:365)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$ConstructorResolverAdapter.findAutowireCandidates(AbstractAutowireCapableBeanFactory.java:1318)
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:472)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:153)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:800)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:720)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:387)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:247)
at org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:796)
at org.springframework.context.support.AbstractApplicationContext.registerListeners(AbstractApplicationContext.java:592)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:349)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185770#4185770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185770
17 years, 5 months
[Clustering/JBoss] - JMS Failover to Master node : SpyJMSException: Cannot authen
by vgiguere
Hi,
I have an application using JMS in a clustered JBOSS environment.
My JMS service and queues are deployed as a singleton (deploy-hasingleton/jms/***) on every node (3) in the cluster.
PLEASE NOTE : Each node in the server has been tested alone and successfully deployed the JMS service (as the master node).
My problem is:
When I launch all nodes in my cluster, everything works fine, but if I kill the master node, the new master node is unable to provide the JMS service.
I am getting the following error:
| org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.ConnectException: Connection refused)
| at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
| at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
| at org.jboss.mq.Connection.authenticate(Connection.java:1071)
| at org.jboss.mq.Connection.<init>(Connection.java:252)
| at org.jboss.mq.Connection.<init>(Connection.java:323)
| at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116)
| at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137)
| at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:98)
| at org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:188)
| at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:209)
| at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:197)
| at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:700)
| at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:682)
| at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:834)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.net.ConnectException: Connection refused
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
| at java.net.Socket.connect(Socket.java:519)
| at java.net.Socket.connect(Socket.java:469)
| at java.net.Socket.<init>(Socket.java:366)
| at java.net.Socket.<init>(Socket.java:180)
| at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:196)
| at org.jboss.mq.il.uil2.UILServerIL.createConnection(UILServerIL.java:497)
| at org.jboss.mq.il.uil2.UILServerIL.getSocketMgr(UILServerIL.java:390)
| at org.jboss.mq.il.uil2.UILServerIL.authenticate(UILServerIL.java:277)
| at org.jboss.mq.Connection.authenticate(Connection.java:1067)
| ... 12 more
|
Does anyone have an idea why JMS service is not deployed on the new master node when the cluster looses its master, even though each node can individually act as the master node?
Thanks in advance for your help.
Vincent Giguere
Environment information:
Jboss 4.2.3
Java 6 update 10
CENTOS 5.2
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185759#4185759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185759
17 years, 5 months