[JBoss-user] [Messaging, JMS JBossMQ] - Remote messaging fails with EXCEPTION_ACCESS_VIOLATION
I have two JBosses running on two machines. They are configured in way one uses messaging on other machine (no application is running there). After some time of running at least one of JBosses fails. This failure also happens nearly every time I stop JBoss with runnnig application by pressing CTR+C. | An unexpected exception has been detected in native code outside the VM. | Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc005) occurred at PC=0x77F | 85C41 | Function=RtlpWaitForCriticalSection+0x60 | Library=C:\WINNT\System32\ntdll.dll | | Current Java thread: | at java.net.SocketInputStream.socketRead0(Native Method) | at java.net.SocketInputStream.read(SocketInputStream.java:129) | at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) | at java.io.BufferedInputStream.read(BufferedInputStream.java:201) | - locked 0x11c341d8 (a org.jboss.util.stream.NotifyingBufferedInputStr | eam) | at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBuff | eredInputStream.java:67) | at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java | :2133) | at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Object | InputStream.java:2313) | at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStre | am.java:2380) | at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream | .java:2452) | at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputSt | ream.java:2601) | at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845) | at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:28 | 1) | at java.lang.Thread.run(Thread.java:534) | | Dynamic libraries: | 0x0040 - 0x00406000 c:\win32app\java\j2sdk1.4.2\bin\java.exe | 0x77F8 - 0x77FFB000 C:\WINNT\System32\ntdll.dll | 0x77DB - 0x77E0D000 C:\WINNT\system32\ADVAPI32.dll | 0x77E8 - 0x77F36000 C:\WINNT\system32\KERNEL32.DLL | 0x77D3 - 0x77DA1000 C:\WINNT\system32\RPCRT4.DLL | 0x7800 - 0x78046000 C:\WINNT\system32\MSVCRT.dll | 0x002D - 0x002F1000 C:\Program Files\Webroot\Spy Sweeper\sis.dll | 0x77E1 - 0x77E75000 C:\WINNT\system32\user32.dll | 0x77F4 - 0x77F7C000 C:\WINNT\system32\GDI32.DLL | 0x779B - 0x77A4B000 C:\WINNT\system32\oleaut32.dll | 0x77A5 - 0x77B45000 C:\WINNT\system32\ole32.dll | 0x0800 - 0x08136000 c:\win32app\java\j2sdk1.4.2\jre\bin\client\jvm.d | ll | 0x7757 - 0x775A C:\WINNT\System32\WINMM.dll | 0x6BD0 - 0x6BD0D000 C:\WINNT\System32\SYNCOR11.DLL | 0x1000 - 0x10007000 c:\win32app\java\j2sdk1.4.2\jre\bin\hpi.dll | 0x00D5 - 0x00D5E000 c:\win32app\java\j2sdk1.4.2\jre\bin\verify.dll | 0x00D6 - 0x00D78000 c:\win32app\java\j2sdk1.4.2\jre\bin\java.dll | 0x00D8 - 0x00D8D000 c:\win32app\java\j2sdk1.4.2\jre\bin\zip.dll | 0x184B - 0x184BF000 C:\win32app\java\j2sdk1.4.2\jre\bin\net.dll | 0x7503 - 0x75043000 C:\WINNT\System32\WS2_32.dll | 0x7502 - 0x75028000 C:\WINNT\System32\WS2HELP.DLL | 0x782C - 0x782CC000 C:\WINNT\System32\rnr20.dll | 0x7798 - 0x779A4000 C:\WINNT\System32\DNSAPI.DLL | 0x7505 - 0x75058000 C:\WINNT\System32\WSOCK32.DLL | 0x7734 - 0x77353000 C:\WINNT\System32\iphlpapi.dll | 0x7752 - 0x77525000 C:\WINNT\System32\ICMP.DLL | 0x7732 - 0x77337000 C:\WINNT\System32\MPRAPI.DLL | 0x7515 - 0x7516 C:\WINNT\System32\SAMLIB.DLL | 0x7517 - 0x751BF000 C:\WINNT\System32\NETAPI32.DLL | 0x77BE - 0x77BEF000 C:\WINNT\System32\SECUR32.DLL | 0x751C - 0x751C6000 C:\WINNT\System32\NETRAP.DLL | 0x7795 - 0x7797A000 C:\WINNT\system32\WLDAP32.DLL | 0x773B - 0x773DE000 C:\WINNT\System32\ACTIVEDS.DLL | 0x7738 - 0x773A2000 C:\WINNT\System32\ADSLDPC.DLL | 0x7783 - 0x7783E000 C:\WINNT\System32\RTUTILS.DLL | 0x7788 - 0x7790D000 C:\WINNT\System32\SETUPAPI.DLL | 0x77C1 - 0x77C6E000 C:\WINNT\System32\USERENV.DLL | 0x774E - 0x77512000 C:\WINNT\System32\RASAPI32.DLL | 0x774C - 0x774D1000 C:\WINNT\System32\RASMAN.DLL | 0x7753 - 0x77552000 C:\WINNT\System32\TAPI32.DLL | 0x7171 - 0x71794000 C:\WINNT\system32\COMCTL32.DLL | 0x70BD - 0x70C35000 C:\WINNT\system32\SHLWAPI.DLL | 0x7736 - 0x77379000 C:\WINNT\System32\DHCPCSVC.DLL | 0x777E - 0x777E8000 C:\WINNT\System32\winrnr.dll | 0x777F - 0x777F5000 C:\WINNT\System32\rasadhlp.dll | 0x20B0 - 0x20B3F000
[JBoss-user] [Messaging, JMS JBossMQ] - Re: JMS with Derby
Thank you for your response Mike. I cannot use RC in my setup, because we are near to release, but at least I can check it for details of configuration (I hope it was not changed totally). Thanks, Pavol View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859601#3859601 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859601 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - JMS with Derby
I tried to use Derby DB 10.0.2.1 as store for JMS messages. Because it is not nativelly supported by JBoss 3.2.6 I am using (on Win 2000, JDK 1.5) I made my own jms services (after removing original hsqldb-jdbc2-service.xml and hsqldb-jdbc-state-service.xml). My files follow (they are basicaly modified from existing examples): derby-service.xml | ?xml version=1.0 encoding=UTF-8? | | !-- $Id: derby-service.xml,v 1.1.2.8 2004/08/20 09:52:22 ejort Exp $ -- | | server | | !-- -- | !-- Persistence and caching using HSQLDB -- | !-- See docs/examples/jms for other configurations -- | !-- -- | | !-- | | The destination manager is the core service within JBossMQ | -- | mbean code=org.jboss.mq.server.jmx.DestinationManager name=jboss.mq:service=DestinationManager | depends optional-attribute-name=MessageCachejboss.mq:service=MessageCache/depends | depends optional-attribute-name=PersistenceManagerjboss.mq:service=PersistenceManager/depends | depends optional-attribute-name=StateManagerjboss.mq:service=StateManager/depends | /mbean | | !-- | | The MessageCache decides where to put JBossMQ message that | | are sitting around waiting to be consumed by a client. | | | | The memory marks are in Megabytes. Once the JVM memory usage hits | | the high memory mark, the old messages in the cache will start getting | | stored in the DataDirectory. As memory usage gets closer to the | | Max memory mark, the amount of message kept in the memory cache aproaches 0. |-- | mbean code=org.jboss.mq.server.MessageCache | name=jboss.mq:service=MessageCache | attribute name=HighMemoryMark50/attribute | attribute name=MaxMemoryMark60/attribute | attribute name=CacheStorejboss.mq:service=PersistenceManager/attribute | /mbean | | !-- | | The jdbc2 PersistenceManager is the new improved JDBC implementation. | | This implementation allows you to control how messages are stored in | | the database. | | | | Use this PM if you want the reliablity a relational database can offer | | you. The default configuration is known to work with hsqldb, other | | databases will requrie teaking of the SqlProperties e.g. changing table | | colum definitions to database supported types. | | | | Take care that the selected blob column type in jms_messages can store | | all message data. Some databases (e.g. mySQL) offer blob types with | | different maximum capacity (e.g. mySQL-type BLOB=64K, LONGBLOB=2G). | | | | If you encouter problems with the configured BLOB_TYPE try a different | | setting. Valid settings are OBJECT_BLOB, BINARYSTREAM_BLOB and BYTES_BLOB. |-- | mbean code=org.jboss.mq.pm.jdbc2.PersistenceManager | name=jboss.mq:service=PersistenceManager | depends optional-attribute-name=ConnectionManagerjboss.jca:service=LocalTxCM,name=MyDS/depends | attribute name=SqlProperties | BLOB_TYPE=BYTES_BLOB | INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?) | INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?) | SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS | SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES | SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=? | SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=? | MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=? | UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=? | UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? | UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=? | DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) | DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ? | DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=? | DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T' | DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=? | CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ | DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ | MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) |
