[Installation, Configuration & Deployment] - Re: JEMS Installer 1.2.0.CR1: Errors when starting JBoss
by chbussler
Hi,
today I installed 4.0.4 with the corresponding JEMS installer: I also get the following errors:
20:17:34,975 INFO [[/web-console]] MonitorsFolder: Failed to init plugin, null
20:17:34,980 INFO [[/web-console]] UCLs: Failed to init plugin, null
20:17:35,002 INFO [[/web-console]] JMS Message: Failed to init plugin, null
20:17:35,006 INFO [[/web-console]] JSR77 WebModule: Failed to init plugin, null
20:17:35,011 INFO [[/web-console]] J2EEFolder: Failed to init plugin, null
20:17:35,019 INFO [[/web-console]] AOPFolder: Failed to init plugin, null
20:17:35,020 INFO [[/web-console]] SystemFolder: Failed to init plugin, null
20:17:35,046 INFO [[/web-console]] MBeans: Failed to init plugin, null
20:17:35,051 INFO [[/web-console]] JSR77 Domains and Servers: Failed to init plugin, null
20:17:35,055 INFO [[/web-console]] JSR77 EJBModules and EJBs: Failed to init plugin, null
20:17:35,059 INFO [[/web-console]] JSR77 J2EE Apps: Failed to init plugin, null
Not sure if the solution to that was posted, does anybody have any hint?
Thanks,
Christoph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991855#3991855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991855
19 years, 4 months
[Installation, Configuration & Deployment] - Re: Shared classpath within an EAR?
by weston.price@jboss.com
anonymous wrote :
| 1) In the case with the EAR/lib directory containing JARs that you mentioned, wouldn't an archive within the EAR still look at EAR/lib JARs even with Java2ParentDelegation set to true?
|
Yes, and this is quite often the cause of issues. A good example is wanting to use Hibernate/Xalan/Xerces jars that conflict with thirdparty jars that exist in JBoss. One of the major reasons for classloader isolation is when you want to use a different version of jar offered in your application environment.
anonymous wrote :
| 2) I read that you can have, in the deploy directory itself, a regular JAR file (i.e. I don't mean EJB-JAR, but a regular JAR containing utility or other classes that you may want on your classpath)...is this really possible?
|
Yes, the classes will be added to the LoaderRepository and a UCL created. However, this can create versioning issues rather quickly. Classic example is a jar file that an EJB and WAR depend on. Simply deploying the jar in a hot deployment environment will not work in this case and both the deployment units (WAR/EJB) would have to be redeployed as well. This can get real messy, real quick no matter how much you may think your build/release process can do to help you manage this.
anonymous wrote :
| What would it be visible to?
|
Everything ;-)
anonymous wrote :
| 3) Why should we not use the java module approach? Are there reasons that'd make it difficult to manage (like having to add them all to application.xml) or is it just not the way things are done?
|
Largely because this was a mistaken implementation to begin with and was added prior to the J2EE spec defining an well defined Classloading model for utility jars. Technically the
| <module>
| <java>somejar.jar</module>
| </module>
|
is for J2EE ApplicationClient deployments and should only be used a such.
There is no guarantee that this approach will not be removed in the furture. In fact, I can pretty much guarantee you that it will be.
While JBoss allows a 'flexible' approach to deployments (and in many ways allows things that it really shouldn't), sometimes this can cause serious deployment/management headachese. Sticking with a standard well know mechanism can often pay dividends in the long run.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991848#3991848
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991848
19 years, 4 months
[Installation, Configuration & Deployment] - Understanding the deploy directory
by lightbulb432
I'd like to get a better understanding of the actual files within the deploy directory, so that (among other reasons, of course) I can delete unnecessary files/folders to decrease startup time and memory consumption.
Is there any place that lists what each of the files that I see there actually do? That way I can know what to safely delete without creating any problems that may pop up later because of it?
Right now, the only thing I know is that if I am using EJB3, JSF, and Seam, I can delete all the *-ds.xml files except for the one I am using in my application. I also know, of course, that the deployed application itself must remain. But that's all I know.
But I see a lot of folders, XML files, and a couple of RAR files...how can I learn about what these do?
There's also an issue of dependencies...for example, if I guess that the jbossweb-tomcat55.sar folder is for JBoss Web and I delete it, how do I know that some other functionality (like JSPs/Servlets) doesn't depend on it somewhere down the road?
Where might I find such info? I truly hope it has been documented. Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991846#3991846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991846
19 years, 4 months