[JBoss Messaging] - Server closes connection even if the Client is alive.
by jbmuser
Hi,
I am using JBM 2.0.0.BETA4. I am trying to migrate ActiveMQ to JBM in our product. But I have been hitting this issue of loosing connections regularly after sending some messages to the server. I have been debugging on this issue for a while now. Finally, today, I was able to reproduce this issue with a simple JMS sender class. The issue is that the server closes client connection and clears the resources even if the client is alive. Please see the server message below.
[main] 17:49:54,850 WARNING [org.jboss.messaging.jms.server.impl.JMSServerManagerImpl] Binding for java:/XAConnectionFactory already exists
| [main] 17:49:54,949 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA4 (maggot, 104) started
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,158 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p
| lient. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4
| ba-11de-93a5-001aa035dde5
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session 4dd07287-81ba-11de-93a5-001a
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p
| lient. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4
| ba-11de-93a5-001aa035dde5
| [Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,415 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session 4dae6b96-81ba-11de-93a5-001a
As per the JBM documentation, if a client is idle (i.e. not sending/receiving any message), it will automatically send "ping" packets periodically to prevent the server from closing it down. So my understanding is that, the server should not close the connection as long as client program is running (even though it is not sending/receiving any messages). Please confirm. If yes, It seems this pinging is not happening always. Because, in my case, client program is sitting idle for 5 min after sending some messages and after 2-3 minutes, server closes the connection saying "no ping received".
Please find the test class and instructions in JIRA - https://jira.jboss.org/jira/browse/JBMESSAGING-1701
Thanks
Bijith
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248126#4248126
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248126
16 years, 8 months
[JBoss Portal] - cms failover in portal using filesystem
by henderson_mk
Hi,
We're having some issues with the supplied cms on portal 2.7.2. In a clustered environment with the cms configured to use the filesystem storage method the failover from one node to the other doesn't seem to work.
The behaviour observed is when the master node goes down, any content that had previously been uploaded is not available on the node that takes up the master role. Just the default content is available.
Is this how this is supposed to behave? If so, is there a way to make the master node transfer the contents of its cms to the node that is taking up the master role?
Using the db as storage for the cms seems to have correct behaviour, but is un-useable as it doesn't work correctly with oracle and concurrent uploads seem to break the cms.
Hope you can give some clarification.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248125#4248125
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248125
16 years, 8 months
[JBoss OSGi] - Re: OSGi and MicroContainer
by alesj
"speleomaniac" wrote :
| Or I am wrong and this would not occur in JBoss MicroContainer....
|
It all depends on how you would configure your classloading.
e.g. by default - as you might probably know - in JBossAS everything is flat,
meaning everything can see everything, and it's the first-loaded rule on which class gets loaded
While this is pretty nice/useful for most of the time
- I personally liked this very much while I was still a plain user of JBossAS :-) -
but of course it can be a pita sometimes.
But that's why you have classloading isolation.
While in JBossAS itself you have those custom and easy to configure files to apply cl isolation
* jboss-app.xml for .ear
* jboss-web.xml for .war
* jboss.xml for the rest
these can be called legacy with the new Microcontainer as the kernel.
As part of MC, we completely changed our classloading and deployers layer, making it a lot richer.
For classloading, OSGi model was definitely something we looked to support (among other potential new cl models).
You can already do most of the OSGi kind of features, only missing on some corner cases.
The new syntax is currently supported in jboss-classloading.xml files,
while we're already working on making this portable to plain OSGi manifest.mf files.
Unfortunately the docs are not that comprehensive:
* http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159343
but I do try to answer all of the question releated with MC and therefore its new cl layer in our MC user forum:
* http://www.jboss.org/index.html?module=bb&op=viewforum&f=228
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248124#4248124
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248124
16 years, 8 months
[JNDI/Naming/Network] - You are trying to use a connection factory that has been sh
by rajika
hi,
I am trying to use xa-datasource configuration for derby with my application deployed on JBoss 5.0.0GA(on Linux with jdk version 1.5). I asked this question from JCA forum and now since this looks like a JNDI problem, I am posting here as well. Sorry for the cross post.
Once deployed the below xa-configuration I am getting the exception: You are trying to use a connection factory that has been shut down (full stack trace is available below.).
Any help to fix the problem will be highly appreciated. Thanks in advance.
| <datasources>
| <xa-datasource>
| <jndi-name>XADerbyDS</jndi-name>
|
| <!-- uncomment to enable interleaving <interleaving/> -->
|
| <isSameRM-override-value>false</isSameRM-override-value>
| <xa-datasource-class>org.apache.derby.jdbc.EmbeddedXADataSource</xa-datasource-class>
|
| <!-- path to the database. (${jboss.server.data.dir}${/}derby${/}default didn't work on win) -->
| <xa-datasource-property name="DatabaseName">derby/esb</xa-datasource-property>
| <xa-datasource-property name="User">esb</xa-datasource-property>
| <xa-datasource-property name="Password">esb</xa-datasource-property>
| <xa-datasource-property name="CreateDatabase">create</xa-datasource-property>
|
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
| <metadata>
| <type-mapping>Derby</type-mapping>
| </metadata>
| </xa-datasource>
| </datasources>
|
The exception when using the above defined data source(I don't get any error while sever start up) as follows.
| org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
| at org.apache.synapse.mediators.db.AbstractDBMediator.getPreparedStatement(AbstractDBMediator.java:177)
| at org.apache.synapse.mediators.db.DBReportMediator.processStatement(DBReportMediator.java:40)
| at org.apache.synapse.mediators.db.AbstractDBMediator.mediate(AbstractDBMediator.java:102)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.filters.OutMediator.mediate(OutMediator.java:55)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:115)
| at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:131)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:339)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:135)
| at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178)
| at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:230)
| at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:487)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
| ... 16 more
| 18:25:27,427 INFO [STDOUT] 18:25:27,427 ERROR [SERVICE_LOGGER] Error execuring insert statement : update company set price=? where name =? against DataSource : localhost:1099
| org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
| at org.apache.synapse.mediators.db.AbstractDBMediator.getPreparedStatement(AbstractDBMediator.java:177)
| at org.apache.synapse.mediators.db.DBReportMediator.processStatement(DBReportMediator.java:40)
| at org.apache.synapse.mediators.db.AbstractDBMediator.mediate(AbstractDBMediator.java:102)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.filters.OutMediator.mediate(OutMediator.java:55)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:115)
| at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:131)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:339)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:135)
| at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178)
| at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:230)
| at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:487)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
| ... 16 more
| 18:25:27,428 INFO [STDOUT] 18:25:27,428 WARN [FaultHandler] ERROR_CODE : 0
| 18:25:27,428 INFO [STDOUT] 18:25:27,428 WARN [FaultHandler] ERROR_MESSAGE : Error execuring insert statement : update company set price=? where name =? against DataSource : localhost:1099
| 18:25:27,428 INFO [STDOUT] 18:25:27,428 WARN [FaultHandler] ERROR_DETAIL : org.apache.synapse.SynapseException: Error execuring insert statement : update company set price=? where name =? against DataSource : localhost:1099
| at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:275)
| at org.apache.synapse.mediators.db.DBReportMediator.processStatement(DBReportMediator.java:61)
| at org.apache.synapse.mediators.db.AbstractDBMediator.mediate(AbstractDBMediator.java:102)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.filters.OutMediator.mediate(OutMediator.java:55)
| at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
| at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:115)
| at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:131)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:339)
| at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:135)
| at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178)
| at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:230)
| at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
| at org.apache.synapse.mediators.db.AbstractDBMediator.getPreparedStatement(AbstractDBMediator.java:177)
| at org.apache.synapse.mediators.db.DBReportMediator.processStatement(DBReportMediator.java:40)
| ... 14 more
| Caused by: javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:487)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
| ... 16 more
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248121#4248121
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248121
16 years, 8 months
[JCA/JBoss] - problem parsing datasources
by Smin3r
Using JBOSS 5.1 and trying to parametrize e.g. datasource name, I get this log:
21:25:16,455 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=${jboss.ds.name}' to JNDI name 'java:${jboss.ds.name}'
I've configured a mysql-ds.xml file in this way:
<local-tx-datasource>
<jndi-name>${jboss.ds.name}</jndi-name>
<connection-url>jdbc:mysql://127.0.0.1:3306/jbossdb</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>admin</user-name>
admin
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<type-mapping>mySQL</type-mapping>
</local-tx-datasource>
and I start jboss instance with this line:
./run.sh -c all -Djboss.ds.name=mydatasourcename
thanks all
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248115#4248115
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248115
16 years, 8 months