November 2006 - jboss-user - Jboss List Archives

[Installation, Configuration & Deployment] - URLDeploymentScanner fails in 4.0.5.GA

by Stefan Arentz

I have a strange problem. When I add a remote URL to the URLs section of the URLDeploymentScanner mbean definition in server/default/conf/jboss-service.xml, I get the following error during startup: | 18:04:14,496 WARN [ServiceController] Problem starting service jboss.deployment:type=DeploymentScanner,flavor=URL | java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpException | at java.lang.Class.getDeclaredConstructors0(Native Method) | at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328) | at java.lang.Class.getConstructor0(Class.java:2640) | at java.lang.Class.newInstance0(Class.java:321) | at java.lang.Class.newInstance(Class.java:303) | at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.java:70) | at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.java:53) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:494) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:613) | 18:04:14,594 ERROR [Server] Root deployment has missing dependencies; continuing | Incomplete Deployment listing: | | --- MBeans waiting for other MBeans --- | ObjectName: jboss.deployment:type=DeploymentScanner,flavor=URL | State: FAILED | Reason: java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpException | I Depend On: | jboss.system:service=MainDeployer | | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.deployment:type=DeploymentScanner,flavor=URL | State: FAILED | Reason: java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpException | I Depend On: | jboss.system:service=MainDeployer | | | at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:613) | The URLs section looks like this: | <attribute name="URLs"> | http://localhost/deploy/ | deploy/ | </attribute> | Is this supposed to work like this? Or should I create a completely different profile for JBoss when I want to do this? S. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982718#3982718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982718

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: Commit after component method is called

by chuckadams

It's running inside a transaction, yes, and that's part of the EJB spec unless you mark the business method @TransactionAttribute(NOTSUPPORTED) but that doesn't explain where the update is coming from. Since it's probably due to a flush, you can just keep it from flushing by setting flushMode=MANUAL if you're starting an existing conversation or bu calling Conversation.instance.changeFlushMode(FlushModeType.MANUAL) if you're just in a temporary conversation. I just discovered this myself, so maybe I'm suggesting the wrong approach, but you can always try it out. Probably not related, but it also looks strange that you're using createNamedQuery and passing it HQL. You should be using createQuery instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982717#3982717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982717

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Recording user logins/logouts

by free1000

My first thought is that I like the idea of the custom valve for Tomcat. I'll take a look at it. I was thinking of the AOP approach but I'm not familiar with how that would be hooked in to the portal. Thanks for the ideas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982716#3982716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982716

19 years, 6 months

1
0
0 / 0

[Clustering/JBoss] - Re: TCP Clustering problem

by somejunk

This is what I am getting on node2. 2006-11-02 11:56:55,294 WARN [org.jgroups.protocols.TCP] discarded message from different group (tomcat-%JBOSS_CLUSTER_NAME%). Sender was APP1:7810 2006-11-02 11:57:01,138 WARN [org.jgroups.protocols.TCP] discarded message from different group (%JBOSS_CLUSTER_NAME%). Sender was APP1:7800 (additional data: 20 bytes) 2006-11-02 11:57:06,669 WARN [org.jgroups.protocols.TCP] discarded message from different group (tomcat-%JBOSS_CLUSTER_NAME%). Sender was APP1:7810 2006-11-02 11:57:12,528 WARN [org.jgroups.protocols.TCP] discarded message from different group (%JBOSS_CLUSTER_NAME%). Sender was APP1:7800 (additional data: 20 bytes) 2006-11-02 11:57:19,325 WARN [org.jgroups.protocols.TCP] discarded message from different group (tomcat-%JBOSS_CLUSTER_NAME%). Sender was APP1:7810 2006-11-02 11:57:22,529 WARN [org.jgroups.protocols.TCP] discarded message from different group (%JBOSS_CLUSTER_NAME%). Sender was APP1:7800 (additional data: 20 bytes) 2006-11-02 11:57:29,873 WARN [org.jgroups.protocols.TCP] discarded message from different group (tomcat-%JBOSS_CLUSTER_NAME%). Sender was APP1:7810 2006-11-02 11:57:32,185 WARN [org.jgroups.protocols.TCP] discarded message from different group (%JBOSS_CLUSTER_NAME%). Sender was APP1:7800 (additional data: 20 bytes) TCP stack in cluster-service.xml is: <TCP bind_addr="192.168.224.123" start_port="7800" loopback="true"/> <TCPPING initial_hosts="192.168.224.123[7800],192.168.224.122[7800]" port_range="3" timeout="3500" num_initial_members="3" up_thread="true" down_thread="true"/> <MERGE2 min_interval="5000" max_interval="10000"/> <FD shun="true" timeout="2500" max_tries="5" up_thread="true" down_thread="true" /> <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false" /> <pbcast.NAKACK down_thread="true" up_thread="true" gc_lag="100" retransmit_timeout="3000"/> <pbcast.STABLE desired_avg_gossip="20000" down_thread="false" up_thread="false" /> <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="false" print_local_addr="true" down_thread="true" up_thread="true"/> <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/> In tc5-cluster-service.xml, I am using port 7810. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982715#3982715 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982715

19 years, 6 months

1
0
0 / 0

[Clustering/JBoss] - Re: TCP Clustering problem

by bela＠jboss.com

"somejunk" wrote : I tried procedure given in the link. On node1 which I started first I get | GMS: address is App2:7800 | ** New View: [App2:7800|0] [App2:7800] | | When node2 on other machine is started, I get ChannelException: unable to setup protocol stack. | | Please help me on this further. Thanks There should be a stack trace on node2, can you post it ? Also, if you enable logging at the trace level for org.jgroups, you will see what the problem is. I suspect an incorrect bind_addr. Any chance you're using IPv6 ? Then disable it as detailed in http://wiki.jboss.org/wiki/Wiki.jsp?page=IPv6 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982712#3982712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982712

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Recording user logins/logouts

by sohil.shah＠jboss.com

Since Portal uses JAAS based authentication, you could also integrate a custom Tomcat Valve and monitor a user's authenticated session. Tomcat Valve would hook in from your web app's context.xml View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982711#3982711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982711

19 years, 6 months

1
0
0 / 0

[JBoss jBPM] - Job Offer - Paris

by Alkero

Hello all, I'm looking for a jbpm developer for a job in Paris. If you are interested please send me a mail: dloiseau [at] yahoo.com Regards, David View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982710#3982710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982710

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Recording user logins/logouts

by PeterJ

Just a thought. Have you looked into using AOP to accomplish this? Writing an aspect for the appropriate methods should do the trick. (And before you ask, no I have not done this.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982709#3982709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982709

19 years, 6 months

1
0
0 / 0

[JBoss/Spring Integration] - Re: SpringDeployer compatible with Spring2.0 final

by Stefan Arentz

Hi Ales. I got it working now. Excellent. But, I realized that this is not working like I want to. I would like a .spring archive be much like an ear; I need to be able to bundle my Spring app togehter with all it's dependend jar files in one .spring file and then deploy that as a whole. Guess I'll have a little project to work on :-) S. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982708#3982708 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982708

19 years, 6 months

1
0
0 / 0

[JBoss jBPM] - Re: new JPDL designer feature : forms generation

by matthieugd

"kukeltje" wrote : | - used by the webapp | Thanks for yor answer. But when I deploy the process defintion with a task (including the forms.xml file and the task1.xhtml file) on the jbpm console and I start a new instance, the form UI for the task is the default one. There's another setting to change ? Matthieu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982707#3982707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982707

19 years, 6 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 November 2006