[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-20 Thread [EMAIL PROTECTED]
I have a few observations: - The JVM 1.6 you have seems a bit old: Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b06 mixed mode) I see at Sun's website they are at "Java SE 6 Update 10 Beta (Build 25)" right now. - JBoss 4 and JBM 1.4 is JVM 1.5 JBoss4 itself doesn't support JVM 1.5 yet. There

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-20 Thread PeterJ
Given that the crash happened in socket code, you should also ensure that you have the latest drivers for your network card. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159668#4159668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=postin

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-23 Thread bodrin
Ok, I can start the JBoss with JBM on 1.5. But does it mean that my standalone jms clients should also run on 1.5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159819#4159819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=repl

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-23 Thread [EMAIL PROTECTED]
In commercial terms (don't know if you have a support contract) At the moment we are supporting JVM 1.5... JVM 1.6 should come soon. In technical terms, this error shouldn't be happening. The crash happened because your old JVM, or as PeterJ also said, something not updated at your windows (dri

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-23 Thread PeterJ
Another possibility is the age of JDK 6u2. Not sure when that came out (I don't have 6u2, but I do have 6u3 and it is dated Sept '07, you could look at the dates on the files in the bin directory), but when Vista first came out it played havoc with the 1.5 and 1.6 versions of the JDK on the mark

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-23 Thread [EMAIL PROTECTED]
anonymous wrote : Another possibility is the age of JDK 6u2 This is what I mentioned few posts ago: "Clebert" wrote : | - The JVM 1.6 you have seems a bit old: | Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b06 mixed mode) | | I see at Sun's website they are at "Java SE 6 Update 10 Bet

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-24 Thread bodrin
I have just updated to the latest jdk and the problem is reproducible again View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160180#4160180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160180 ___

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-24 Thread [EMAIL PROTECTED]
Hmm: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5040096 Can you tell me what Windows version and updates you have now? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160294#4160294 Reply to the post : http://www.jboss.com/index.html?module=bb&o

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-24 Thread timfox
There is a simple solution here: Don't use windows ;) *** ducks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160295#4160295 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160295 _

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-25 Thread bodrin
jdk1.6.0_06 windows XP professional version 2002 service pack 2 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160441#4160441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160441 ___

[jboss-user] [JBoss Messaging] - Re: EXCEPTION_ACCESS_VIOLATION [ntdll.dll+0x18fea]

2008-06-25 Thread [EMAIL PROTECTED]
Can you please do a last test with Windows SP3? That would help us a lot. It seems this is a bug on Windows/malloc from what I saw on the Sun's bug at jdk 1.5.someversion. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160628#4160628 Reply to the post : htt