Re: [jboss-user] [JBoss Remoting] - Which Library for 4.2.3.GA
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"Which Library for 4.2.3.GA"
To view the discussion, visit: http://community.jboss.org/message/535526#535526
--------------------------------------------------------------
Hi BJ.
> What should I be using?
I always recommend using the latest combination of Remoting and JBossMessaging jars, because we've fixed quite a few issues over time. The 2.2.2.x generation of Remoting releases evolved into the 2.2.3 releases, the newest of which is 2.2.3.SP1. Actually, version 2.2.3.SP2 is tagged, but I haven't uploaded it to the download site yet. I believe the appropriate version of JBossMessaging is 1.4.0.SP3_CP10, but I don't see it on the JBM download page. Of course, the beauty of open source is that you can build the jars yourself.
> How does one install this in 4.2.3 ? Is it simply (he asks hopefully) a matter of replacing the jars in the library?
It is indeed. The server uses jboss-remoting.jar from the $JBOSS_HOME/server/$CONFIG/lib. Also, the jars in the $JBOSS_HOME/client directory are intended for use by clients, so you should update jboss-remoting.jar in that directory as well.
> found the jar, looked in the Manifest
>
jboss-remoting.jar has the property that if you type
java -jar jboss-remoting.jar
it will print the version.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535526#535526]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Remoting] - Detection failure delay for JMS bisocket connection
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"Detection failure delay for JMS bisocket connection"
To view the discussion, visit: http://community.jboss.org/message/535525#535525
--------------------------------------------------------------
Hi Amar,
Remoting detects an apparent network problem by sending pings from the client to the server and waiting for a reply. If the reply doesn't arrive within the configured time frame, Remoting informs JBossMessaging. The relevant configuration parameters are
> + <attribute name="validatorPingPeriod" isParam="true">60000</attribute>
> <attribute name="validatorPingTimeout" isParam="true">30000</attribute>+
>
"validatorPingPeriod" determines how often the ping is sent, and "validatorPingTimeout" determines the window within which the response must arrive. So the ping could get sent anywhere from 0 to 60 seconds after the plug is pulled, and the problem detected anywhere from 30 to 90 seconds after the plug is pulled. So, I can explain why the problem detection could take up to 90 seconds. I can't explain how it could happen within 5 seconds, unless some other problem had prevented the server from sending a response to a ping that had already been sent, say 25 seconds before you pulled the plug. Just a stab in the dark.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535525#535525]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Remoting] - JBoss Remoting in AS Cluster
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"JBoss Remoting in AS Cluster"
To view the discussion, visit: http://community.jboss.org/message/535521#535521
--------------------------------------------------------------
Hi Wolfgang,
To tell you the truth, I don't know enough about clustering to give a definitive answer, but I would say that an important consideration is whether the application is stateful. Clustering uses caching to share state among machines, so, if you need to share state, I think you would have a lot of work to reach your goal. In that case, I think you might want to adapt your client to use EJBs, with all of their built in infrastructure, instead of invoking Remoting directly. If you don't have shared state, then I guess you could just start up a Remoting server in each AS instance, but that still doesn't give you load balancing. Again, you might be better off using the built in EJB mechanisms.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535521#535521]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [jBPM] - task for multiple users
by Huisheng Xu
Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion
"task for multiple users"
To view the discussion, visit: http://community.jboss.org/message/535520#535520
--------------------------------------------------------------
Hi Alexei,
I think it is some different from Task and Execution in the jPDL. Task is more likely a notification service to Human being. The Execution is the actually a part of Graph Oriented Language. If you use Discriminator Pattern, you may find it is difficult to implement it, but in our country, this scenario is very commonly. People want to have a most flexible human task service, so they want to decision who and could receive the task, you have to decide to create how much task may be created in the runtime. The different time you execute the process, the difference tasks may be created and assigned to different person.
It may sounds strange, but it is the real user requirement. I hope jBPM could support more powerful feature like this in future.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535520#535520]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Remoting] - Application ClassNotFound within InvocationHandler.invoke() on AS6 M2
by fatbatman
fatbatman [http://community.jboss.org/people/fatbatman] created the discussion
"Application ClassNotFound within InvocationHandler.invoke() on AS6 M2"
To view the discussion, visit: http://community.jboss.org/message/535513#535513
--------------------------------------------------------------
Hi,
I'm in the process of upgrading the JBoss 6 M2 and I'm getting a ClassNotFound error within MyRemotingInvocationHandler.invoke(InvocationRequest invocation) when an applications class object is received by the server side invocation handler.
I create my connector programmatically using the code below on a socket transport.
The class is in the same application jar that the connector is created from, which is within deploy/myapp.ear/myapp.jar.
The connectors are created when the application is started as an mbean from deploy/myapp.ear/myserver-service.xml
This worked fine on JBoss 4 & 5 so I assume there's something different in the Class Loading from the remoting thread pool threads on JBoss 6 M2?
Does anyone have any suggestions?
Thanks in advance
James
Server side connector set up is;
Map<String, String> connectorConfig = new HashMap<String, String>();
connectorConfig.put("callbackStore", "org.jboss.remoting.callback.BlockingCallbackStore"); //will block the thread trying to send it if memory is low.
connectorConfig.put("return-exception","true"); //Make sure the original Exception is returned to client when using servlet
connectorConfig.put("numAcceptThreads", "20");
connectorConfig.put("maxPoolSize", "500");
Map<String, String> locatorConfig = new HashMap<String, String>();
locatorConfig.put("force_remote", "true");
locatorConfig.put("leasing", "true"); //The client will establish a lease with the server so the server can check it's still connected
locatorConfig.put("lease_period", GlobalConstants.LEASE_PERIOD+""); //The period in which the server check the client is still there
String uri = protocol + "://" + server + ":" + port + path;
ServerConfiguration serverConfig = new ServerConfiguration(protocol);
serverConfig.setInvokerLocatorParameters(locatorConfig);
Connector connector1 = new Connector(connectorConfig);
connector1.setInvokerLocator(uri); //new InvokerLocator(protocol, server, port, path, locatorConfig);
connector1.setServerConfiguration(serverConfig);
connector1.setLeasePeriod(GlobalConstants.LEASE_PERIOD);
connector1.create();
connector1.getServerInvoker().setMaxNumberOfOnewayThreads(100);
connector1.getServerInvoker().setSerializationType(GlobalConstants.JBOSS_REMOTING_SERIALIZATION_TYPE);
MyRemotingInvocationHandler invocationHandler = new MyRemotingInvocationHandler();
connector1.addInvocationHandler(MyConstants.REMOTING_SYSTEM, invocationHandler);
connector1.addConnectionListener(new MyRemotingConnectionListener());
connector1.start();
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535513#535513]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years