[Design of Messaging on JBoss (Messaging/JBoss)] - I got problem with running simple example!
by Kanat
I have installed jboss-messaging-1.2.0.GA to JBoss!
And after I connot run simple QueueExample.java example!
When I strat eith ant prints like this messages:
run:
[java] Queue /queue/testQueue exists
[java] The message was successfully sent to the testQueue queue
[java] 11:24:41,406 ERROR @WorkerThread#0[127.0.0.1:3029] [ServerThread] Wo
rker thread initialization failure
[java] java.io.EOFException
[java] at java.io.DataInputStream.readInt(DataInputStream.java:375)
[java] at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireForma
t.java:297)
[java] at org.jboss.remoting.transport.socket.ServerThread.versionedRea
d(ServerThread.java:641)
[java] at org.jboss.remoting.transport.socket.ServerThread.processInvoc
ation(ServerThread.java:523)
[java] at org.jboss.remoting.transport.socket.ServerThread.dorun(Server
Thread.java:363)
[java] at org.jboss.remoting.transport.socket.ServerThread.run(ServerTh
read.java:159) so on...
Anybody knows what 's a problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099533#4099533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099533
16 years, 11 months
[Design of JBossXB] - JBXB-114, model group issues
by scott.stark@jboss.org
What can we do with legacy documents that map to new model groups, but violate the group element ordering as is the case with the JBXB-114 and jboss_4_2.dtd environment reference model group?
The problem is that the jboss_4_2.dtd intermixes elements from the jboss_5_0.xsd jboss:jndiEnvironmentRefsGroup with other elements. For example, the security-identity element is in between service-ref and resource-ref:
| <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
| exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
| security-proxy? , ejb-ref* , ejb-local-ref* , service-ref*, security-identity? ,
| resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
| cluster-config?, method-attributes?, depends*,
| ior-security-config?, port-component*, ejb-timeout-identity?)>
|
This causes two different JBossEnvironmentRefsGroupMetaData instances to be created and when the second instance is set on the session bean it fails because the setter has a guard to validate the group is not being set more than once.
In reality we want to use the same group instance to collect the elements until the parent element end is seen. I'm sure this would make the parsing code even more of a mess though. This could be handled by the setJndiEnvironmentRefsGroup method merging the disparate groups into one. The binding code is not responsible for validation after all.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099525#4099525
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099525
16 years, 11 months