Madhu-
I can get this to work fine, by specifying something like the following in the
sample-bindings.xml:
| service-config name=jboss.messaging:service=Connector,transport=bisocket
|
delegateClass=org.jboss.services.binding.AttributeMappingDelegate
|
Tim/Team? Any feedback on this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041808#4041808
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041808
___
jboss-user mailing list
It seems at some time (not sure who/why) something changed (probably in
remoting) so the servicebindingmanager config for the remoting connector needs
to specified as a long string (see the JBAS 4.0.5 default config for more
details) rather than xml.
E.g.
| service-config
Tim, what about other attribtes, such as:
callbackStore
clientSocketClass
serverSocketClass
NumberOfCallRetries
etc..
Do you suggest we should supply these attributes same way as that long string?
Thanks
Madhu
View the original post :
I tried applying your fix Tim, but the conenctor is still startign on the port
specified in remoting-service.xml (at 4457 port instead of my defined one in
bindings file)
Also, the after ever poperty=value in the above string must be read as
(else will get a SAX exception)
View the original
Madhu-
Once I jave found out how/why the change was made I will get back to you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041864#4041864
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041864
Tim, here's my service-config def in bindings file:
| config
| invoker transport=bisocket
| attribute name=marshaller
isParam=trueorg.jboss.jms.server.remoting.JMSWireFormat/attribute
| attribute name=unmarshaller
Actually we do make use of service binding manager.
You just need to make sure the remoting config section exactly matches the one
in remoting-service.xml then make sure you start each server with the right
ports config e.g. ports01, ports02 etc.
This works fine for me.
View the original post
Thanks Clebert.
Any idea when is gonna go for implementation? Would please raise a JIRA request
on this issue?
Thanks
Madhu
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033913#4033913
Reply to the post :
What file is that?
For changing remoting properties, you have to change
jboss-messaging.sar/remoting-service.xml.
mbean code=org.jboss.remoting.transport.Connector
| name=jboss.messaging:service=Connector,transport=bisocket
| display-name=Bisocket transport Connector
Sorry clebert, I posted the wrong code (yes older version) by mistake by in
actual I am usign this one Clebert (which is the new one):
!-- * JBoss Messaging --
|
| service-config
name=jboss.messaging:service=Connector,transport=socket
|
Ah.. you mean the ServiceBindings from JBossAS... Hummm...
We don't make usage of that now... so.. you're right.. you have to define this
by hand on the XML for now.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033784#4033784
Reply to the post :
12 matches
Mail list logo