[Installation, Configuration & Deployment] - Disabling Clustering in Jboss Application Server
by Craig2007
Hi
I am using jboss-4.0.4.GA for JBoss Messaging.
If any other server is started ,it automatically joins the cluster environment.
I want to disable the joing of new server with my server( Server on which JBoss Messaging is running).
Please tell me a way to disable to cluster participation of JBoss App Servers.
I have pasted the log which i get when another Jboss Server pariciaptes the cluster
14:00:47,626 INFO [DefaultPartition] Suspected member: ABC044690:2301 (additional data: 19 bytes)
14:00:47,626 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 39, delta: -1) : [192.168.251.101:1099]
14:00:47,658 INFO [DefaultPartition] I am (192.168.251.101:1099) received membershipChanged event:
14:00:47,658 INFO [DefaultPartition] Dead members: 1 ([192.168.251.36:1099])
14:00:47,658 INFO [DefaultPartition] New Members : 0 ([])
14:00:47,658 INFO [DefaultPartition] All Members : 1 ([192.168.251.101:1099])
14:03:17,706 INFO [DefaultPartition] New cluster view for partition DefaultPartition: 40 ([192.168.251.36:1099, 192.168.251.101:1099] delta: 1)
14:03:17,706 ERROR [NAKACK] sender at index 1 in digest is null
14:03:17,738 INFO [DefaultPartition] Merging partitions...
14:03:17,738 INFO [DefaultPartition] Dead members: 0
Please do reply me back
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022319#4022319
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022319
19Â years, 1Â month
[JBoss Seam] - Re: concurrent access to SFSB using SEAM Remoting
by zdaler
Thanks for you answer.
Looking at the code inside the Conversation Manager we saw that if there is a concurrent call to a locked conversation context : a new temporary one is created :
log.debug("No stored conversation, or concurrent call to the stored conversation");
| initializeTemporaryConversation();
|
This lead to our problem since the concurrent-request-timeout is set to 1 sec by default. Setting this parameter to 20s did the trick : each request would wait enough time for the previous request to be completed.
in components.xml :
<core:manager concurrent-request-timeout="20000" ...
Maybe you could add a note in section "3.1.10. Concurrency model" mentioning this parameter ...
In our case, it was really strange to have a new temporary (and empty !) conversation created to handle requests from a long running conversation ... maybe it solves some of your use-cases (?) ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022318#4022318
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022318
19Â years, 1Â month
[JBoss Messaging] - java.lang.IllegalAccessError in 1.2.0.CR1
by bnarayan
Hi,
I have been trying to setup 1.2.0.CR1.
While deploying the my MDBs i am getting the following exception
| 15:23:26,554 WARN [JMSContainerInvoker] JMS provider failure detected for MyMDB
| java.lang.IllegalAccessError: tried to access class org.jboss.aop.ClassAdvisor$1 from class org.jboss.aop.ClassAdvisor
| at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271)
| at org.jboss.aop.AspectManager.initialiseClassAdvisor(AspectManager.java:587)
| at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:575)
| at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.<clinit>(ClientClu
| steredConnectionFactoryDelegate.java)
| at sun.misc.Unsafe.ensureClassInitialized(Native Method)
| at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:2
| 5)
| at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
| at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
| at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
| at java.lang.reflect.Field.getLong(Field.java:527)
| at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1559)
| at java.io.ObjectStreamClass.access$600(ObjectStreamClass.java:47)
| at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:381)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:373)
| at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:268)
| at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:504)
| at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546)
| at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
| at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
| at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
| at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)
|
Not able to figure why i am getting this.
Any pointers are appreciated
Thanks,
Bharath
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022316#4022316
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022316
19Â years, 1Â month
[Remoting] - Re: SocketTimeout in client
by maheshp
Hello Mr. Tom,
i am using following code to get the remote objects,
Hashtable<Object,String> props = new Hashtable<Object,String> ();
props.put(
InitialContext.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(InitialContext.PROVIDER_URL, "jnp://127.0.0.1:1099");
props.put("java.naming.factory.url.pkgs", "org.jboss.naming");
InitialContext ctx = new InitialContext(props);
objSecurity = (Security) ctx.lookup(SecurityRemote.class.getName());
after setting the timeout attribute in invoker-service.xml to 120,000 it is taking the 60000 milli sec as default and it throwing timeout exception after 60000 ms.
please let me know any other options to get the remote objects, so i can avoid the timeout exception.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022315#4022315
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022315
19Â years, 1Â month