June 2007 - jboss-user - Jboss List Archives

[JCA/JBoss] - Re: Listening Database Failover

by adrian＠jboss.org

Interesting, there is a configuration property that lets you decide how the URL is selected, i.e. how it fails over. But it is not properly configured or documented. http://jira.jboss.com/jira/browse/JBAS-4490 Absent this configuration it uses the default org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory$URLSelector which does NOT the hook you are looking for. I guess you could override this strategy http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/connector/src/ma... to emit some form of notification when a new url is chosen. But where you would emit that notification to is a different question? ManagedConnectionFactorys are just "stateless" javabeans. They don't have references into the JMX system or any other part of JBoss. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055258#4055258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055258

18 years, 10 months

1
0
0 / 0

[JBossWS] - wsconsume ant task

by poyge394

Hi, i try to use wsconsume with ant, | <target name="target" description="Generates classes"> | <path id="wscon.classpath"> | <path path="${project.classpath}"/> | </path> | <taskdef name="wsconsume" classname="org.jboss.ws.tools.jaxws.ant.wsconsume"> | <classpath refid="wscon.classpath"/> | </taskdef> | <wsconsume | fork="true" | verbose="true" | destdir="output" | sourcedestdir="gen-src" | keep="true" | wsdl="http://api.tradera.com/v1/publicservice.asmx?WSDL"> | </wsconsume> | </target> | | I get: | [wsconsume] Command invoked: org.jboss.ws.tools.jaxws.command.wsconsume -k -o C:\workspace\ipl_tradera\output -s C:\workspace\ipl_tradera\gen-src -t http://api.tradera.com/v1/publicservice.asmx?WSDL | [wsconsume] Exception in thread "main" java.lang.NoClassDefFoundError: gnu/getopt/LongOpt | [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.parseArguments(wsconsume.java:82) | [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:75) | | anybody have using wsconsume ant task ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055257#4055257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055257

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: Configuring JBoss with Eclipse/Exadel

by dabd

"fady.matar" wrote : you don't even need to specify the JBoss home. It's referenced internally from within the project But isn't it necessary to start the server from Eclipse to be able to debug your code with breakpoints, etc.? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055255#4055255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055255

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: where to find errata for Seam book

by john135

I am also looking for such pages. I once confused but later realized that in several places in th book default component scopes are described incorrectly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055254#4055254 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055254

18 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: remote client cannot connect: detected failure on contro

by bartvh

I want to add that when is problem occurs, shutting down the server hangs. I did a stack trace dump and it shows: "JBoss Shutdown Hook" daemon prio=1 tid=0x08abc388 nid=0x2d94 waiting for monitor entry [0x85adb000..0x85adf030] | at org.jboss.remoting.ServerInvoker.removeCallbackHandler(ServerInvoker.java:1671) | - waiting to lock <0x911bbb28> (a java.util.HashMap) | at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1341) | at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:552) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:721) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1550) | at org.jboss.remoting.Client.invoke(Client.java:530) | at org.jboss.remoting.Client.removeListener(Client.java:1043) | at org.jboss.jms.client.remoting.JMSRemotingConnection.stop(JMSRemotingConnection.java:297) | at org.jboss.jms.client.container.ConnectionAspect.handleClose(ConnectionAspect.java:181) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.close(ClientConnectionDelegate.java) | at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:132) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStopDelivery(JMSContainerInvoker.java:944) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.stopService(JMSContainerInvoker.java:863) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) and "WorkerThread#2[127.1.0.1:48325]" prio=1 tid=0x080e0e10 nid=0xb97 in Object.wait() [0x82ada000..0x82adaeb0] | at java.lang.Object.wait(Native Method) | - waiting on <0x94f79fa0> (a java.util.HashSet) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.<init>(BisocketClientInvoker.java:206) | - locked <0x94f79fa0> (a java.util.HashSet) | at org.jboss.remoting.transport.bisocket.TransportClientFactory.createClientInvoker(TransportClientFactory.java:44) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.remoting.InvokerRegistry.loadClientInvoker(InvokerRegistry.java:419) | at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:320) | - locked <0x90b20338> (a java.lang.Object) | at org.jboss.remoting.Client.connect(Client.java:441) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.init(ServerInvokerCallbackHandler.java:167) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.<init>(ServerInvokerCallbackHandler.java:139) | at org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1655) | - locked <0x911bbb28> (a java.util.HashMap) | at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1336) | at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:552) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:721) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) | Looks like a thread is holding some lock and waiting to get notified of something... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055253#4055253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055253

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: Configuring JBoss with Eclipse/Exadel

by fady.matar

you don't even need to specify the JBoss home. It's referenced internally from within the project View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055252#4055252 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055252

18 years, 10 months

1
0
0 / 0

[JBoss Seam] - Seam 1.3alpha with Glassfish

by trouby

Hey, Just wanted to inform that Seam 1.3Alpha does not work with Glassfish running under Linux. I did some tests, it works fine with win32 GF distribution, not sure what could result such a difference, here are some info: 1) Tested against Linux RH Enterprise 4/Gentoo with JDK1.5/1.6 - did not work 2) Tested against win32 XP/2003 - with JDK1.6 - works fine all tests were done against GF V2 B51 When I say 'did not work' I mean that no action gets invoked and no jsf components get rendered, (Couldnt see any exception though) Everthing works fine if I replace seam's jars with version 1.2.x. n.b - also tried to download latest version(06-18-07) from CVS Thanks, Asaf. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055251#4055251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055251

18 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: Configuring JBoss with Eclipse/Exadel

by dabd

"fady.matar" wrote : Save your time this hassle an re-install the distribution and don't mess with the server libraries, future versions of the console will handle later versions of JBoss AS Are you using jbpm-jpdl-3.2.GA ? In the Servers View did you specify the JBoss AS Directory as C:\jbpm-jpdl-3.2.GA\server ? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055250#4055250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055250

18 years, 10 months

1
0
0 / 0

[JBoss Messaging] - remote client cannot connect: detected failure on control co

by bartvh

I have a remote client connecting to a clustered jboss-messaging server, using jboss 4.2.0. The JBM version is 1.3.0.GA. Because of some experimentation I frequently had restarted my client application. After a number of restarts, I get into a situation where the client is unable to reconnect to the JMS server. 6:02:28,612 WARN [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@1272332: detected failure on control connection Thread[control: Socket[addr=/127.1.0.1,port=3652,localport=34297],5,jboss]: requesting new control connection The client is retrying to connect to the server in case of failures. At everty retry this message is printed out. Restarting the client does not help to fix the problem, but restarting the server does. Note: this might be a pure remoting issue, but I'm not sure, so this is posted in the jbm forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055249#4055249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055249

18 years, 10 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: DurableSubscriber

by adrian＠jboss.org

"jp_ammu" wrote : | Even if able to configure the MDB succesfully, i still have DurableSubscriber() with same subscription name. My application( after restart) will get the duplicate subscription name exception and can't proceed further. ???? Restarting an MDB will close the previous connection so the client id/subscritpion name will not be a duplicate. The MDB uses only one connection with many sessions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055247#4055247 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055247

18 years, 10 months

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 June 2007