[JBoss Remoting] - jms over http - [JBossConnectionFactory] Failed to download and/or install client side AOP stack
by Kobi Ianko
Kobi Ianko [http://community.jboss.org/people/kobiianko] created the discussion
"jms over http - [JBossConnectionFactory] Failed to download and/or install client side AOP stack"
To view the discussion, visit: http://community.jboss.org/message/549279#549279
--------------------------------------------------------------
following the wiki page: http://community.jboss.org/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker http://community.jboss.org/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker
tring this line at the client side:
conFactory = (ConnectionFactory)initialContext.lookup(connectionFactoryName)
throws an exception:
12:24:14,059 ERROR [JBossConnectionFactory] Failed to download and/or install client side AOP stack
org.jboss.jms.exception.MessagingNetworkFailureException
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:240)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:205)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$getClientAOPStack$aop(ClientConnectionFactoryDelegate.java:237)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPStack(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:75)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:192)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
at com.allot.nms.common.messaging.client.MessagingManager.setupSub(MessagingManager.java:69)
at com.allot.nms.common.messaging.client.MessagingManager.setMessageListener(MessagingManager.java:87)
at com.allot.nms.common.messaging.client.MessagingHelper.setMessageListener(MessagingHelper.java:101)
at com.allot.nms.client.model.alarms.AlarmsModelController.reload(AlarmsModelController.java:128)
at com.allot.nms.client.ui.frm.Controller.reloadAllDataFromServer(Controller.java:485)
at com.allot.nms.client.ui.frm.Controller.access$200(Controller.java:95)
at com.allot.nms.client.ui.frm.Controller$DataLoader.run(Controller.java:1260)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:249)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:161)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.remoting.Client.invoke(Client.java:617)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
... 15 more
Caused by: java.lang.IllegalArgumentException: Invalid packet type: 1013478509
at org.jboss.jms.wireformat.PacketSupport.createPacket(PacketSupport.java:379)
at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:290)
at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:570)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:369)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231)
... 21 more
any ideas?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549279#549279]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JNDI and Naming] - timeouts on jndi calls (jnp.timeout & jnp.sotimeout)
by Andy Taylor
Andy Taylor [http://community.jboss.org/people/ataylor] created the discussion
"timeouts on jndi calls (jnp.timeout & jnp.sotimeout)"
To view the discussion, visit: http://community.jboss.org/message/549274#549274
--------------------------------------------------------------
Ive been playing around with the time outs on client jndi lookups (we want to set these for HornetQ JMS bridges) and have found that the timeouts i was setting weren't being used. After debugging i found that the following was happening
//psuedo code
1. Create socket
2. socket.setsotimeout(sotimeout)
3. socket.connect(timeout)
4. marshall Naming Server stub
5. cache server
6. invoke lookup on server using RMI
subsequent calls use the cached server which means that the timeouts are only actually used in the initial marshalling of the server stub, all subsuquent calls to the naming server will use what ever default timeouts are set on the RMI implementation.
My question is this, should the jndi code handle setting these same parameters on the rmi layer or is it up to the client code to do it. I actually tried setting the sun rmi params but it had no effect.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549274#549274]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Portal] - Jboss Cluster on same network does not identify each other
by Sasi Kanth
Sasi Kanth [http://community.jboss.org/people/sasidev] created the discussion
"Jboss Cluster on same network does not identify each other"
To view the discussion, visit: http://community.jboss.org/message/549273#549273
--------------------------------------------------------------
Hi all,
I'm trying to setup a cluster with two Jboss 5.0.1.GA instances (initially) on two different machines sharing same network and have STATIC IP been assigned. When I start those instances using:
./run.sh -c all -g MyPartition -u 239.127.11.11 -b <IP address> -Djboss.messaging.ServerPeerID=<1/2>
both start properly but seldom identify each other. Here are some Observations:
1. Second Instance shows "No. Of members in Cluster: 1". Which means that it did not identify first one.
2. First instance *use to show* "discarded message from non-member [<second instance's ip>]" message.
3. Tested multi-cast using *McastReceiverTest and McastSenderTest*. This *FAILED* as first instance is not sending any message.
When second instance isn't able to identify how is first recieving message from it?
*MCast FAILED*. Does it mean I need to check Network Configuration? If so what configuration could it be?
Looking forward for response on this issue :) .
Sasi.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549273#549273]
Start a new discussion in JBoss Portal at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years