[Beginners Corner] - Exiting on IOE
by teodoro21
JBOSSMQ java.io.EOFException
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
when I send text message to my topic i see inside the server.log file
the following exception:
2007-07-20 10:48:40,466 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2007-07-20 10:48:40,467 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2007-07-20 10:48:40,467 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2007-07-20 10:48:40,724 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2007-07-20 10:48:40,756 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the UILClientIL Connection
2007-07-20 10:48:40,756 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL Connection is set up
2007-07-20 10:48:40,957 INFO [STDOUT] ->SpyTextMessage {
Header {
jmsDestination : TOPIC.myTopic.DurableSubscription[clientId=DurableSubscriberExample name=DurableSubscriberExample selector=null]
jmsDeliveryMode : 2
jmsExpiration : 0
jmsPriority : 4
jmsMessageID : ID:3-11849213209421
jmsTimeStamp : 1184921320942
jmsCorrelationID: null
jmsReplyTo : null
jmsType : null
jmsRedelivered : false
jmsProperties : {}
jmsPropReadWrite: false
msgReadOnly : true
producerClientId: ID:3
}
Body {
text :test message..
}
}
2007-07-20 10:48:41,545 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2666)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
at java.lang.Thread.run(Thread.java:595)
2007-07-20 10:48:41,546 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2007-07-20 10:48:41,547 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
What means?
thanks Teo.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066078#4066078
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066078
18Â years, 9Â months
[JBoss Seam] - Re: Help: Seam on Weblogic 10
by lisaanm
Hi Guys,
No one replied for my post yet.
Please help me and share your comments about this error on deploying
SEAM 1.2.1 JPA example on Weblogic 10.
| ####<12.07.2007 13.30 Uhr CEST> <Error> <J2EE> <toms-2000> <examplesServer> <[ACTIVE] ExecuteThread: '0' for queue:
| 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1184239814906> <BEA-160197>
|
| <Unable to load descriptor weblogic.utils.classloaders.ChangeAwareClassLoader@1df0959 finder: weblogic.utils.classloaders.CodeGenClassFinder@19f58a
| annotation: consoleapp@console/WEB-INF/lib/jboss-seam
| -jpa.jar!/META-INF/persistence.xml of module jboss-seam-jpa.war.
| The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
| ....
| ....
| Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=persistence at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
|
|
I already posted on BEA DEV forum and waiting for reply.
Hope SEAM guys will help me.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066077#4066077
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066077
18Â years, 9Â months
[JBoss Messaging] - Re: problem when testing multiple failovers in a cluster
by chatzi
Hi
Thanks for the reply.
Initially I did the following (all locally on my machine, Windows XP, SQLServer 2005).
1) Start the Cluster.
2) Wait for it to completely come up.
3) Start my 'test' tool
- The test simply sends messages as quickly as possible to a distributed topic, while additionally (in another thread) receiving them again.
- At this point in time both JBoss instances start consuming CPU.
4) Shutdown one JBoss instance (through CTRL-C in its command window).
- There are now some exceptions thrown in the background, but the test continues to run.
- There is no 're-initialisation' of any JMS recources whatsoever from my side (the cluster should be transparent to me).
5) Wait for 'my' test to finish.
- The test in the end reports the number of 'send' and received messages. Some have gone lost, but ok, not too many.
Now I did the test again,with the following differences:
1) Extend the duration of the test.
2) Start everything again.
3) Shutdown JBoss instance 'A' (as above)
4) Re-start JBoss instance 'A'
5) Wait for it to come up again.
6) Shutdown JBoss instance 'B'
- THE PROBLEM: At this point in time exceptions start to pour in, the test fails. 'Failover', i.e. the sender connection previously using 'B' now using 'A' did not happen for me.
Regards
Alex
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066075#4066075
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066075
18Â years, 9Â months