May 2008 - jboss-user - Jboss List Archives

[Tomcat, HTTPD, Servlets & JSP] - Re: Problem with Jboss/Tomcat when using Apache Loadbalancer

by ryousure2000

Did you find any solution for the issue u mentioned. We are having same issue. Thanks Urvish Amin urvishamin(a)hotmail.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148110#4148110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148110

18 years, 1 month

1
0
0 / 0

[JBoss Getting Started Documentation] - Re: Documentation for jboss-5.0.0

by sunnyDev

Sorry, I ask the quesiotn hastily, I find I should refer to JBoss Messaging Document. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148108#4148108 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148108

18 years, 1 month

1
0
0 / 0

[Clustering/JBoss] - Re: Failover is taking 15 seconds to recognize by other node

by bstansberry＠jboss.com

You're shutting node2 down gracefully? How are you doing it? Your symptoms sound more like a hard kill, where it's taking 15 secs for the other node to recognize missed heartbeats and suspect the dead node. To fix that you can add the FD_SOCK protocol to the JGroups config in the tc5-cluster-service.xml file. See http://wiki.jboss.org/wiki/FDVersusFD_SOCK for details. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148105#4148105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148105

18 years, 1 month

1
0
0 / 0

[Clustering/JBoss] - Re: Buddy Replication: Memory usage with Tomcat Session Repl

by bstansberry＠jboss.com

Node a2 becoming the buddy of both a1 and a3 sounds broken; it's not meant to be that way. There have been a lot of improvements in JBoss Cache related to buddy replication since AS 4.0.5 came out. Can you try replacing the server/all/lib/jboss-cache.jar with the jboss-cache-jdk50.jar that comes with the JBC 1.4.1.SP9 release? For that to work you'll need to replace jgroups.jar, either with the one that comes with the JBC 1.4.1.SP9 download. or even better with the one from the JGroups 2.4.1.SP4 release. That may help your session.invalidate() issue as well. I've never heard of a problem like that before; will investigate more. Re: setting up eviction, normally I say don't do that, but it may be a valid workaround for now. If you do it, set it up for the _default_ region (i.e. the whole cache) so it also covers the internal buddy replication backup areas. Use LRUPolicy, and configure maxNodes=0 (disabling eviction based on # of nodes). The timeToLiveSeconds value must be greater than the session expiration timeout. I'd say make it a couple minutes greater -- idea is to make sure that the normal JBossWeb session cleanup process gets a chance to flush things out first, with the JBC eviction only cleaning out stuff that gets left behind. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148104#4148104 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148104

18 years, 1 month

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Tomcat Virtual Hosts/Hostname

by lovelyliatroim

Thanks jaikiran, that works a treat!! Much appreciated!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148101#4148101 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148101

18 years, 1 month

1
0
0 / 0

[JBoss Portal] - Re: A4J and UserModule in a portlet

by wesleyhales

This is normal for RichFaces ResourceLifecycle class. The fix to not show this exception is in Richfaces trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148100#4148100 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148100

18 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: MQ migration help

by tnine

One quick note, I only get this when running in a cluster with 2 nodes. Both nodes share a DB, and I have set the ServerPeerID to 0 and 1 for nodes 1 and 2 respectively. I have also changed the queue/DLQ definition to the following. | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=DLQ" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <depends optional-attribute-name="ServerPeer"> | jboss.messaging:service=ServerPeer | </depends> | <depends>jboss.messaging:service=PostOffice</depends> | <attribute name="Clustered">true</attribute> | </mbean> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148099#4148099 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148099

18 years, 1 month

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Getting data from a node

by manik.surtani＠jboss.com

Sadly, 2.1.1 is in QA right now and very close to being released. If there was no workaround, I would have "stopped the presses" for this, but since there is a workaround I'd prefer not to do that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148098#4148098 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148098

18 years, 1 month

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Getting data from a node

by FredrikJ

Cheers. The JIRA issue is currently due for 2.2.0, is this correct or do you think it might be included in 2.1.1? If the fix is likely to be included in 2.1.1 then we wont bother with implementing a workaround but rather wait for 2.1.1 =) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148097#4148097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148097

18 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Need help : JBossWS Security!

by xinhua

ok, i see, maybe jboss-wsse-client.xml or standard-jaxws-client-config.xml not loaded ,so i copied the both xml into META-INF and also changed the client code like this: | | Service s = Service.create(url, qn); | Test port = s.getPort(Test.class); | | URL securityURL = new File("META-INF/jboss-wsse-client.xml").toURL(); | URL securityConfig= new File("META-INF/standard-jaxws-client-config.xml").toURL(); | ((StubExt) port).setSecurityConfig(securityURL.toExternalForm()); | ((StubExt) port).setConfigName("Standard WSSecurity Client",securityConfig.toExternalForm()); | | | ((BindingProvider) port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "kermit"); | ((BindingProvider) port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "thefrog"); | ((BindingProvider) port).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:4040/miguoWS/TestBean"); but in soap monitor i found <wsse: Security> is still missing in request. (jboss4.2.1GA, jbossws-3.0.1-native-2.0.4.GA, jdk1.5 update 15) Really nobody can help me out here ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148096#4148096 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148096

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user May 2008