Bugs item #634591, was opened at 2002-11-06 11:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634591&group_id=22866
Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: ryan sonnek (wireframe6464) Assigned to: Nobody/Anonymous (nobody) Summary: netboot failure Initial Comment: server specs: suse linux 7.3 sun 1.3.1 jdk apache web server 2.x jboss 3.0.2 config files client specs: win2k sun 1.4.0 jdk jboss 3.0.2 netboot files. can view the files correctly through a webbrowser, but when client executes run.bat, no files are pulled down. apache's server log shows the client trying to download crimson.jar. both the server and client are unresponsive, and no error messages are thrown. run.bat -netboot http://<servername> -c custom ---------------------------------------------------------------------- >Comment By: Jeremy Boynes (jboynes) Date: 2003-02-07 08:53 Message: Logged In: YES user_id=378919 In version 3.0 all files needed by the client config must be listed explicitly, or you must configure the server-side helper app. This is covered in the page Sacha referred to. Be aware this has changed significantly in 3.2 - see the change note on SF ---------------------------------------------------------------------- Comment By: ryan sonnek (wireframe6464) Date: 2003-02-07 08:40 Message: Logged In: YES user_id=552776 i've updated to the default installation of jboss 3.0.6 and have continued to try and get this working. i have gotten past the previous errors, but am getting a new error when starting up: 10:28:47,094 INFO [MainDeployer] Starting deployment of package: http://172.16.1.40/jboss/server/local/conf/jboss-service.xml 10:28:47,915 ERROR [Server] start failed org.jboss.deployment.DeploymentException: No wildcard permitted in non-file URL deployment you must specify individual jars at org.jboss.deployment.SARDeployer.parseXMLClasspath(SARDeployer.java:3 75) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:132) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:679) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea nDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222) at org.jboss.Main.boot(Main.java:148) at org.jboss.Main$1.run(Main.java:381) at java.lang.Thread.run(Thread.java:536) org.jboss.deployment.DeploymentException: No wildcard permitted in non-file URL deployment you must specify individual jars at org.jboss.deployment.SARDeployer.parseXMLClasspath(SARDeployer.java:3 75) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:132) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:679) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea nDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222) at org.jboss.Main.boot(Main.java:148) at org.jboss.Main$1.run(Main.java:381) at java.lang.Thread.run(Thread.java:536) 10:28:47,985 INFO [Server] Undeploying all packages if the wildcard can not be used in jboss-service, what can i use to load the required jars? ---------------------------------------------------------------------- Comment By: ryan sonnek (wireframe6464) Date: 2002-11-07 07:23 Message: Logged In: YES user_id=552776 here's the structure of the website: http://172.xxx.xxx.xxx/jboss/server/custom inside the custom directory is pretty much a straight copy of the "default" folder with all of the conf, lib, and deploy folders. i've tried to follow the netboot instructions on the website as much as possible, but it's still not working, and i'm not getting any responses or error messages when i try and run the netboot client. my last post had an incorrect posting of the command i use to startup the client. here's the command i run from my JBOSS_HOME directory: bin/run.bat --netboot http://172.xxx.xxx.xxx/jboss --config custom ---------------------------------------------------------------------- Comment By: Sacha Labourey (slaboure) Date: 2002-11-07 03:10 Message: Logged In: YES user_id=95900 What is the structure that is available on your web site? You need to make sure that the first available directory is "server" and, below, the different configuration directories, etc. For an example, see here: http://www.jboss.org/demos/netboot.jsp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634591&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
