December 2008 - jboss-user - Jboss List Archives

[JBoss Tools (users)] - Re: get stuck in deployment loop on eclipse redeploy - not s

by max.andersen＠jboss.com

which appserver are you running on ? I haven't seen it loop like you are describing. But I have seen it keep redeploying because files are still being deployed because of something is causing a change in the files...got anything running that might do/cause that ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199009#4199009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199009

15 years, 3 months

1
0
0 / 0

[JBoss Tools (users)] - Re: never seen this one before - debug page error with uncau

by max.andersen＠jboss.com

I dont see anything that relates specifically to jboss tools. Have you tried asking on seamframework.org ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199008#4199008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199008

15 years, 3 months

1
0
0 / 0

[JBoss Tools (users)] - Re: problem with deploy to jboss as 5.0 with new seam projec

by max.andersen＠jboss.com

All you xml snippets are missing. Did you misquote them ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199007#4199007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199007

15 years, 3 months

1
0
0 / 0

[JBoss Tools (users)] - Re: ganymede and jboss tool 3 problem with seam projet

by max.andersen＠jboss.com

I don't recall any issues with Seam 2.1.RC1 that should cause for missing manifest.mf files...weird. Thanks for letting us know it does not happen for you except for 2.1.RC1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199005#4199005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199005

15 years, 3 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Is perspective JMX considered to be

by max.andersen＠jboss.com

If there is an api (that is not just jmx) to introspect a live running instance then that would make sense. But I haven't looked into if there is such API besides JMX. Is there somethings you want to see you cant see via jmx ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199004#4199004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199004

15 years, 3 months

1
0
0 / 0

[Remoting] - Re: Socket keep alive with client EJB and RMI over HTTP

by ron.sigal＠jboss.com

Response on thread "Socket keep alive with client EJB", http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134089. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199003#4199003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199003

15 years, 3 months

1
0
0 / 0

[Remoting] - Re: Socket keep alive with client EJB

by ron.sigal＠jboss.com

"slimamar" wrote : | Using JBoss Remoting 2.4.0 with JBossAS 5.0.0Beta4, the parameter 'invokerDestructionDelay' is taken into account and the socket connection is reused for all client requests. | | But with JBossAS 5.0.0GA and JBoss Remoting 2.5.0SP2 embedded, the socket connection is closed, apparently by the server, after 60 seconds of inactivity. | The value of 'invokerDestructionDelay' is 28800000. | These two behaviors aren't really contradictory. There are two things going on. On the client side, setting "invokerDestructionDelay" allows the client invoker, with its connection pool, to stay alive longer than it would otherwise. Suppose you set "invokerDestructionDelay" to 10000 and you create, connect, invoke upon, and disconnect a new org.jboss.remoting.Client every five seconds. Since the client invoker stays alive for ten seconds, it will still be there when you create the next Client, and the existing connection will get reused. On the server side, the connection is managed by a worker thread which, when it is not executing an invocation, is waiting in a socket read(). When it times out, which it does in 60 seconds by default, the socket is closed and the worker thread is returned to the thread pool. If you make an invocation every five seconds, then the socket on the server side will never time out, and the same connection will be used every time. On the other hand, if you make an invocation every two minutes, then, even though you use the same client invoker with the same connection pool each time, you won't be able to reuse the old connection, which gets closed after sixty seconds, so each invocation will use a new connection. So the frequency of the invocations and the server side timeout determine if you get to reuse connections. Make sense? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199002#4199002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199002

15 years, 3 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Issue - âExpecting "jsp:param" standard action with "name"

by darshanparekh

I am facing a issue of âExpecting "jsp:param" standard action with "name" and "value" attributesâ in JBOSS 4.0.5 GA version of JBOSS. This issue is resolved only when i close the <jsp:forward> tag with "/" by removing the </jsp:forward> tag. Also i remove the comment tags given between the start <jsp:forward> tags and end <jsp:forward> tags. Example code that works <jsp:forward page="../resagentmode/findbooking.jsp"/> code that does not work <jsp:forward page="../resagentmode/findbooking.jsp"></jsp:forward> I am reluctant on changing the code as it is a jsp standard and JBOSS should allow any of the above mentioned codes. How can I resolve this issue without changing the code. Please reply ASAP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199001#4199001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199001

15 years, 3 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: virtual hosting in jboss

by jaikiran

anonymous wrote : 12:48:33,136 ERROR [Digester] Parse Fatal Error at line 165 column 9: The element type "Host" must be terminated by the matching end-tag "". | org.xml.sax.SAXParseException: The element type "Host" must be terminated by the matching end-tag "". | Going by this message, you have edited the xml incorrectly. Open the server.xml in a xml editor and fix the xml contents and then restart the server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198999#4198999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198999

15 years, 3 months

1
0
0 / 0

[Remoting] - Re: The invoker for locator (InvokerLocator [socket://xx.xx

by ron.sigal＠jboss.com

It looks like you're creating TransporterServers on the client side, right? I'm guessing each client has a TransporterServer to handle calls from the server to the client, right? So, when you recreate a client, you're also recreating a TransporterServer. The exception " The invoker for locator ... is already in use by another Connector." is thrown when you try to create a server (org.jboss.remoting.transport.Connector) with an InvokerLocator that is currently associated with a server in the InvokerRegistry. So, clearly, when your clients are shutting down, the TransporterServer's Connector is not shutting down. When you explicitly remove the InvokerLocator from the InvokerRegistry, you're just masking the problem: the server is still running and its ServerSocket is still bound. Now, I don't know why your TransportServer isn't getting closed. Check your code ... . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198997#4198997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198997

15 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2008