December 2006 - jboss-user - Jboss List Archives

[Remoting] - Re: InvokerLocator already exists for listener

by ron_sigal

The following change has been made to the behavior of reused InvokerCallbackHandlers: anonymous wrote : ServerInvoker stores the client side InvokerCallbackHandler using a key consisting of the sessionId of the Client that is registering the InvokerCallbackHandler concatenated with the InvokerCallbackHandler's listenerId. When ServerInvoker is asked to unregister a client side InvokerCallbackHandler X, it looks for X based on the sessionId of the Client making the request concatenated with the listenerId of X. When a Client other than the one that registered InvokerCallbackHandler X tries to unregister X, the ServerInvoker can't find X. It follows that a Client can unregister only those InvokerCallbackHandlers that it has registered. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991856#3991856 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991856

19 years, 4 months

1
0
0 / 0

[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

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: trace logging for jboss

by weston.price＠jboss.com

Can I see the definition of anonymous wrote : | JBOSSLOG | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991853#3991853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991853

19 years, 4 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: Jboss Operation Network

by visolvejboss

Hello, JBoss ON available for Gold and Platinum Subscribers. Refer these links. http://www.jboss.com/services/profsupport https://network.jboss.com/jbossnetwork/login.html;jsessionid=Gag4WXhRqDX-... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991852#3991852 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991852

19 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: trace logging for jboss

by btogo

Thanks for your reply. But it is a typo in my posting. I do have Pool in the log4j.xml file. Anything else you may think of? Thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991851#3991851 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991851

19 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Understanding the deploy directory

by weston.price＠jboss.com

Best place to start with something like this is the Slimming JBoss page on the Wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossASTuningSliming Also, the JBossAS documentation gives a fairly decent explanation of the deployment directory. http://docs.jboss.org/jbossas/jboss4guide/r5/html/ch01.html#d0e523 The book JBoss 4.0 The Offical Guide provides a bit more in depth treatment of this subject as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991850#3991850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991850

19 years, 4 months

1
0
0 / 0

[JBoss Portal] - Re: UserPortlet

by PeterJ

The user portlet is at ./core/src/main/org/jboss/portal/core/portlet/user/UserPortlet.java in the source and the class file is in jboss-portal.sar\lib\portal-core-lib.jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991849#3991849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991849

19 years, 4 months

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shared classpath within an EAR?

by lightbulb432

Thanks for that answer, I've got a few more questions on this topic: 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? Because (based on what I figure from reading the JBoss ClassLoading wikis) the class would first look in its own UCL, then would look at the EAR's UCL (which would contain the JARs in EAR/lib...is my reasoning not correct here? 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? How would this JAR in the deploy directory fit into the ClassLoader "hierarchy" explained at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases? What would it be visible to? 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? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991845#3991845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991845

19 years, 4 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 December 2006