[JBoss Messaging] - Re: JBM deadlock cause by socket write
by lanceliao1
The memory dump,I hope it will helpful.
Why 287 serversessionEndpoint and 133 ServerConsumerEndpoint? We have about 10 client_end receive and send msg,each end have 19 topic.
| 2124 152928 org.jboss.jms.message.JBossObjectMessage
| 2277 54648 org.jboss.jms.destination.JBossTopic
| 287 36736 org.jboss.jms.server.endpoint.ServerSessionEndpoint
| 133 11704 org.jboss.jms.server.endpoint.ServerConsumerEndpoint
| 205 8200 org.jboss.jms.server.container.SecurityAspect
| 135 7560 org.jboss.jms.server.messagecounter.MessageCounter
| 64 6656 org.jboss.jms.server.endpoint.ServerConnectionEndpoint
| 196 6272 org.jboss.jms.server.remoting.ServerSocketWrapper
| 189 4536 org.jboss.jms.server.JMSCondition
| 282 4512 org.jboss.jms.server.endpoint.advised.SessionAdvised
| 48 4224 org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891
| 135 2160 org.jboss.jms.server.messagecounter.MessageCounter$DayCounter
| 133 2128 org.jboss.jms.server.endpoint.advised.ConsumerAdvised
| 48 1920 org.jboss.jms.wireformat.SessionSendRequest
| 47 1880 org.jboss.jms.wireformat.ClientDelivery
| 115 1840 org.jboss.jms.wireformat.JMSWireFormat
| 21 1680 org.jboss.jms.client.state.SessionState
| 19 1368 org.jboss.jms.server.destination.ManagedTopic
| 19 1216 org.jboss.jms.server.destination.TopicService
| 49 1176 org.jboss.jms.client.container.ClosedInterceptor
| 11 1056 org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886
| 64 1024 org.jboss.jms.server.endpoint.advised.ConnectionAdvised
| 11 880 org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588
| 18 864 org.jboss.jms.client.state.ProducerState
| 21 840 org.jboss.jms.client.delegate.ClientSessionDelegate
| 49 784 org.jboss.jms.client.container.DelegateIdentity
| 31 744 org.jboss.jms.client.remoting.ClientSocketWrapper
| 17 680 org.jboss.jms.asf.StdServerSession
| 13 624 org.jboss.jms.message.ObjectMessageProxy
| 18 576 org.jboss.jms.client.delegate.ClientProducerDelegate
| 31 496 org.jboss.jms.client.container.FailoverValveInterceptor
| 7 448 org.jboss.jms.client.state.ConnectionState
| 17 408 org.jboss.jms.tx.MessagingXAResource
| 17 408 org.jboss.jms.tx.ClientTransaction
| 7 336 org.jboss.jms.client.delegate.ClientConnectionDelegate
| 3 288 org.jboss.jms.client.container.ClientConsumer
| 18 288 org.jboss.jms.client.JBossSession
| 3 288 org.jboss.jms.server.connectionfactory.ConnectionFactory
| 18 288 org.jboss.jms.client.JBossMessageProducer
| 15 240 org.jboss.jms.tx.LocalTx
| 3 240 org.jboss.jms.client.delegate.ClientConsumerDelegate$receive_N8299950230150603585
| 1 232 org.jboss.jms.server.ServerPeer
| 7 224 org.jboss.jms.client.remoting.JMSRemotingConnection
| 3 192 org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint
| 3 192 org.jboss.jms.asf.StdServerSessionPool
| 3 192 org.jboss.jms.client.state.ConsumerState
| 7 168 org.jboss.jms.client.container.ConnectionAspect
| 7 168 org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener
| 3 168 org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate
| 2 160 org.jboss.jms.server.destination.ManagedQueue
| 3 144 org.jboss.jms.asf.StdServerSessionPool$MyPooledExecutor
| 3 144 org.jboss.jms.client.delegate.ClientConsumerDelegate
| 3 144 org.jboss.jms.client.JBossConnectionConsumer
| 2 144 org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702
| 2 128 org.jboss.jms.server.destination.QueueService
| 7 112 org.jboss.jms.client.remoting.CallbackManager
| 7 112 org.jboss.jms.client.JBossConnection
| 1 72 org.jboss.jms.server.endpoint.advised.ConsumerAdvised$close_N4742752445160157748
| 1 72 org.jboss.jms.server.plugin.JDBCJMSUserManagerService
| 1 72 org.jboss.jms.jndi.JMSProviderLoader
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect34
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect40
| 2 64 org.jboss.jms.delegate.DeliveryInfo
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect33
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect55
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect35
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect19
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect3
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect54
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect41
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect36
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect4
| 4 64 org.jboss.jms.server.security.SecurityMetadata$Role
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect21
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect18
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect37
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect1
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect5
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect53
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect42
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28
| 2 64 org.jboss.jms.tx.MessagingXid
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect32
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect38
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect52
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect17
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect6
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect2
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect47
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect43
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect39
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect51
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect22
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect7
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect27
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect16
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect31
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect50
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect44
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect23
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect15
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect8
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect45
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect9
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect26
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect49
| 2 64 org.jboss.jms.tx.ClientTransaction$SessionTxState
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect30
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect46
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect24
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect10
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect29
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect12
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect13
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect25
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect20
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect11
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect48
| 1 64 org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect56
| 1 56 org.jboss.jms.asf.ServerSessionPoolLoader
| 3 48 org.jboss.jms.server.security.CheckType
| 3 48 org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised
| 2 48 org.jboss.jms.destination.JBossQueue
| 1 40 org.jboss.jms.server.Bootstrap
| 1 40 org.jboss.jms.server.messagecounter.MessageCounterManager
| 1 40 org.jboss.jms.server.security.SecurityMetadataStore
| 1 32 org.jboss.jms.jndi.JNDIProviderAdapter
| 1 32 org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper
| 1 32 org.jboss.jms.server.connectionmanager.SimpleConnectionManager
| 1 32 org.jboss.jms.server.plugin.JDBCJMSUserManager
| 1 32 org.jboss.jms.message.MessageIdGenerator
| 2 32 org.jboss.jms.server.connectionfactory.JNDIBindings
| 2 32 org.jboss.jms.client.JBossConnectionFactory
| 4 32 org.jboss.jms.server.remoting.DirectThreadPool
| 1 24 org.jboss.jms.server.remoting.JMSServerInvocationHandler
| 1 24 org.jboss.jms.tx.ResourceManager
| 3 24 org.jboss.jms.asf.StdServerSessionPool$DefaultThreadFactory
| 1 24 org.jboss.jms.asf.StdServerSessionPoolFactory
| 1 24 org.jboss.jms.server.security.SecurityMetadata
| 1 24 org.jboss.jms.server.DestinationJNDIMapper
| 1 24 org.jboss.jms.message.MessageIdGeneratorFactory$Holder
| 1 24 org.jboss.jms.wireformat.CloseRequest
| 1 16 org.jboss.jms.wireformat.Dispatcher
| 1 16 org.jboss.jms.message.MessageIdGeneratorFactory
| 1 16 org.jboss.jms.server.container.ServerLogInterceptor
| 1 16 org.jboss.jms.client.ClientAOPStackLoader
| 1 16 org.jboss.jms.wireformat.SerializedPacket
| 1 16 org.jboss.jms.client.container.StateCreationAspect
| 1 16 org.jboss.jms.client.container.ProducerAspect
| 1 16 org.jboss.jms.client.container.SessionAspect
| 1 16 org.jboss.jms.tx.ResourceManagerFactory
| 1 16 org.jboss.jms.tx.ResourceManagerFactory$Holder
| 1 16 org.jboss.jms.server.connectormanager.SimpleConnectorManager
| 1 16 org.jboss.jms.server.endpoint.ServerSessionEndpoint$2
| 1 8 org.jboss.jms.server.container.SecurityActions$PrincipalInfoAction$1
| 1 8 org.jboss.jms.server.JMSConditionFactory
| 1 8 org.jboss.jms.server.selector.SelectorFactory
| 1 8 org.jboss.jms.client.container.ConsumerAspect
| 1 8 org.jboss.jms.server.endpoint.SecurityActions$PrincipalInfoAction$1
| 1 8 org.jboss.jms.server.security.SecurityActions$PrincipalInfoAction$2
| 1 8 org.jboss.jms.server.endpoint.SecurityActions$PrincipalInfoAction$2
| 1 8 org.jboss.jms.server.security.SecurityActions$PrincipalInfoAction$1
| 1 8 org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory
| 1 8 org.jboss.jms.server.container.SecurityActions$PrincipalInfoAction$2
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191594#4191594
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191594
17 years, 5 months
[Tomcat, HTTPD, Servlets & JSP] - Migrate web application from Weblogic to JBoss
by splram
Hi,
I am trying to migrate one web application currently running on Weblogic 8.1 application server.
The JSP content is separated from WAR and is placed at a specific folder location. Weblogic provides a feature called virtual-directory-mapping using which we can place the JSP content outside the WAR.
For example: In weblogic.xml i can define a virtual directory mapping as
<virtual-directory-mapping>
<local-path>c:/content/test-app</local-path>
<url-pattern>/pages/*</url-pattern>
<url-pattern>*.jsp</url-pattern>
</virtual-directory-mapping>
The above definition in weblogic.xml will enable all JSPs under /pages are served from c:/content/test-app/pages folder. All redirects/ forwards will pickup the JSPs from the configured folder.
I know this feature is a weblogic specific feature, and in Tomcat (assuming tomcat is the web server for Jboss) I tried achieving the same by configuring ajp13 connector to interface Apache webserver with Tomcat. I could successfully configure JSPs to be served from outside the WAR however if the same JSPs are forwarded by some controller I am getting a 404.
The reason for getting 404 is, i configured *.jsp pattern in apache's httpd.conf file to be served by Tomcat, but as these configurations are at apache level whenever i forward to any of these JSPs from controller Tomcat does not know that the JSPs need to be served via Apache so therefore it throws a 404 error.
Is there anyway to route the forwards through Apache from tomcat?
Thanks in advance.
Rammohan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191590#4191590
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191590
17 years, 5 months
[JBoss Messaging] - Re: JBM deadlock cause by socket write
by lanceliao1
Using auto_acknowledage mode create connection both on client and server side.
The similar codes are blow:
| TopicConnectionFactory topicFactory = (TopicConnectionFactory) ContextUtil.getContext() .lookup("ConnectionFactory");
| topicConn = topicFactory.createTopicConnection();
| //set connection exceptionlistener
| topicConn.setExceptionListener(new ExceptionListenerImpl());
|
| topicSession = topicConn.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
|
| channels = MsgRouterController.getInstance().findAllChannel();
|
| topicPublishers = new TopicPublisher[channels.length];
| for (int i = 0; i < topicPublishers.length; i++) {
| Topic topic = (Topic) ContextUtil.getContext().lookup(Const.Topic_Prefix+ channels);
| topicPublishers = topicSession.createPublisher(topic);
| log.debug("topicPublisher "+channels+" created!");
| }
if there is one client block receive jms due to network problem,I think the server should not block all receivers and senders.
My problem is waiting on socketwrite(),and blocking others thread to receive msg or send msg.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191588#4191588
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191588
17 years, 5 months