[Design of Messaging on JBoss (Messaging/JBoss)] - DuplicateDetectionTest::testNoPersistXA1 fails if libaio is
by jmesnil
The test DuplicateDetectionTest::testNoPersistXA1 passes when libaio is installed on the OS but fails when it is not installed.
I observed the failure on mac os x.
Then I ran the tests on Linux. it passes when I installed libaio but when I remove the lib it fails with the error:
| [main] 11:00:39,077 INFO [org.jboss.messaging.tests.util.UnitTestCase] ###### starting test org.jboss.messaging.tests.integration.DuplicateDetectionTest.testNoPersistXA1
| [main] 11:00:39,413 WARNING [org.jboss.messaging.core.management.impl.ManagementServiceImpl] It has been detected that the cluster admin user and password which are used to replicate management operation from one node to the other have not been changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [main] 11:00:39,626 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA3 (maggot, 104) started
| [main] 11:00:39,629 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA3 (maggot, 104) stopped
| [main] 11:00:39,637 WARNING [org.jboss.messaging.core.management.impl.ManagementServiceImpl] It has been detected that the cluster admin user and password which are used to replicate management operation from one node to the other have not been changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [main] 11:00:39,680 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager] AIO journal selected
| [main] 11:00:39,687 WARNING [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
| [main] 11:00:39,918 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA3 (maggot, 104) started
| [Thread-1 (group:JBM-server-threads15310053-3907502)] 11:00:40,127 SEVERE [org.jboss.messaging.core.server.impl.ServerSessionImpl] Failed to xa prepare
| java.lang.NullPointerException
| at org.jboss.messaging.core.journal.impl.JournalTransaction.syncPreviousFiles(JournalTransaction.java:224)
| at org.jboss.messaging.core.journal.impl.JournalImpl.appendPrepareRecord(JournalImpl.java:1171)
| at org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager.prepare(JournalStorageManager.java:411)
| at org.jboss.messaging.core.transaction.impl.TransactionImpl.prepare(TransactionImpl.java:166)
| at org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleXAPrepare(ServerSessionImpl.java:2160)
| at org.jboss.messaging.core.server.impl.ServerSessionImpl.handleXAPrepare(ServerSessionImpl.java:702)
| at org.jboss.messaging.core.server.impl.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:215)
| at org.jboss.messaging.core.remoting.impl.ChannelImpl.handlePacket(ChannelImpl.java:621)
| at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:399)
| at org.jboss.messaging.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:483)
| at org.jboss.messaging.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:136)
| at org.jboss.messaging.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
| at java.lang.Thread.run(Thread.java:613)
|
This is the only test in the class which fails if libaio is not installed. All the other tests pass where the lib is there or not.
Does someone see a relation between this test and the libaio installation?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241917#4241917
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241917
16 years, 6 months
[Design of JBoss ESB] - SFTP : auth fail
by oichris
Hi all,
I tried to configure an ftp listener using protocol "sftp", below is the snippet of my jboss-esb.xml :
<ftp-provider name="FTPprovider" hostname="myhost" >
<ftp-bus busid="my_ftp" >
<ftp-message-filter
username="userx"
password="userp"
directory="/home/ftpfolder"
input-suffix=".xml"
work-suffix=".esbWorking"
post-delete="false"
post-suffix=".COMPLETE"
error-delete="false"
error-suffix=".HAS_ERROR"
protocol="sftp"
passive="false"
/>
</ftp-bus>
</ftp-provider>
It keeps prompting me "Auth fail" error. So I tried to investigate into the code in : SecureFtpImpl.java . I used the same code in my testing client and found that this line is causing the problem :
session.setConfig("PreferredAuthentications", "password") ;
When I commented this line and compile, everything works fine. Could anyone guide me to any workaround or doc stating my problem? We would be more than happy that being no need to compile and package our own jboss-rosetta.jar
Thanks a lot.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241882#4241882
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241882
16 years, 6 months
[Design of JBossCache] - Re: Evolution of TcpDelegatingCacheLoaders/TcpCacheServers
by akluge
Hi,
I have taken a look into the Infinispan project, and it is interesting how much of it parallels what I am doing currently. Especially in light of my decision to use a server side hash to dispatch the remote cache requests from any server into the cluster of servers, rather than having each client maintain a connection to each server. However, at this point, it would disrupt an ongoing project to make the shift to Infinispan.
That said, I expect that a lot of what I have done can be applied to the Infinispan project as well - and indeed I have joined the project dev mailing list.
The current project is at a scale where significant data will be loaded into a single node, and there will be occasional writes to key/value pairs into the clustered far cache. When the write happens, the L1 (in process) cache will have to reload the altered data from the far cache. This just won't perform very well if it has to load the entire node every time. This actually seems to be working currently, except that it does reload the entire node. A slight alteration of the cache loader interceptor will load only the single effected key/value pair on a get request - I think I'll call it an L2 loader to avoid confusion with the current loader. It really will be a small, easy change, and won't be required to use the rest of the code.
Thanks,
Alex
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241881#4241881
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241881
16 years, 6 months