If I may guess from the above stacktrace, it is an 5.0.0 BETA JBoss.
I would hint at a misspelled entry and / or the usage of a wrong JBoss runtime
installation, when the index page is still coming up, although the ROOT.war has
been removed. Did you delete the tmp and work directories? Perhaps t
Hi,
it depends on what you want to do on the client. In most cases it is sufficient
to add the jbossall-client.jar to the client classpath. You can find that jar
under JBOSS_HOME/client.
If you already did add this library, you have to give more information about
what you are doing on the cli
Hi,
I've never tried to get JBoss via a package system, but maybe Red Hat offers
that (look to the upper left corner -> JBoss - a division of Red Hat :) ).
But why do you want to get it via a package system? You just have to unzip te
folder with the jboss installation to get it installed. Chan
Hi,
it looks like you pointed to a JRE instead of an JDK. Tomcat needs a JDK to be
able to compile the JSPs into Servlets.
So I think you have not pointed JAVA_HOME to the SDK (btw, what is SDK 5.5?),
but to a JRE.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op
Hi,
you could use the following packaging:
- bean classes and bean resources in YOUR_EJB.jar
- home and component interfaces in YOUR_EJB_client.jar
Then you can put the client.jar into your ear, add the reference to the
manifest.mf of your web-application (or give it to any other client you wis
Hi,
put the helper-jar in the ear and fill the Classpath-element in META-INF of the
war and ejb-jar with this entry.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012928#4012928
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
Hi,
either you define n *-ds.xml files, each defining one database connection, or
you use one -ds.xml file that defines the n connections to the database. Inside
the datasources tag you can define n datasources.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
Hi,
you have to get the information where the leak is located and then fix it. If
it is in an external software component that you cannot fix the provider has to
fix it. Getting more RAM is not the solution, because it will just last longer
until you get the error.
If you have incredible pain
Hi there!
I have a JBoss 4.0.3 SP1 that does JMS with MDBs. The persistance is done with
DB2. There is a message sent to a topic, an MDB reacts and - as a result -
sends another message to a Queue. The first message is being sent and received,
it is being saved in the database (jms_messages). W
Hi,
you could look at the modified date of the log4j.xml and on the server date. I
had this problem when the server date was behind the date of the computer where
I changed the log4j.xml. Then jboss compares the system date with the last
modified date and realizes a modification on the file. I
Hi Hans-Martin,
maybe I'm not understanding your problem correctly, but here is what I would
do:
1. You have a jsp with a form that has an action that points to a servlet.
2. In this servlet you are handling the request. You could have one servlet for
each button or one servlet for all and th
Hi,
you could use the Scheduler MBean to schedule a little module that gets this
data and puts it in the JBoss Cache. Information on how to do this is offered
in the JBoss documentation. From your System code you could then lookup the
cache and get the information you need. If you don't like u
Hi!
I think there are two possibilities:
1. You finde the one that does develop your applications and ask him.
2. You change the logging level and hope that under a more talkful level you
will get the information you need. You can change the logging level under
jboss/server//conf/log4j.xml. Th
Hi,
you could look at the jmx-console (http://localhost:8080/jmx-console) and there
in the domain jboss under "name=SystemProperties,type=Service". There is an
operation showAll() that displays the SystemProperties.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op
Hi Ramdas,
the configuration is not different from the server.log at all.
What messages are given out on the console that do not appear in the server.log
(if you have the same threshold defined)? I haven't noticed anything different
yet.
Peter
View the original post :
http://www.jboss.com
Hi Ramdas,
there are some errors in your configuration. First you finish the opening
appender tag with "/>". That brings a SaxParseException. Then you have the
param "Target" that is not possible for the FileAppender.
Apart from that your configuration works for me.
Peter
View the original
Hi Gabriel,
may be that I misunderstand you, but you seem to mix MBean with Message Driven
Bean. An MBean is a Managed Bean in the jmx server. The Message Driven Bean is
an EJB used for message based communication.
You should lookup your MBean with something like this:
http://wiki.jboss.org/w
Hi Ramdas,
I'm not sure if I understand you right. But if you want to capture the output
to the console in your file, why don't you change the "CONSOLE" appender in
log4j.xml to use a RollingFileAppender like the "FILE" appender? Then you could
remove the redirect from the shell to console.log
Hi!
It seems there has been an error unzipping the archive, just as Peter (with 'J'
:) ) suggested. If you open the zip-file you should see there are several files
in conf.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971198#3971198
Reply to the p
Hi Ramdas,
what does not work when changing the configuration of log4j.xml. Normally this
is the place where you put your configuration. What have you changed and what
doesn't work?
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970970#3970970
Reply
Hi Carlos,
which version of JBoss did you download and where from? The jboss-service.xml
ist an important part of the JBoss configuration and has to be shipped with the
application server. Could it be that this exists and is not accessible for the
user starting the server?
Peter
View the ori
Hi,
Look in deploy/jbossweb-tomcat55.sar/conf/web.xml from line 224 on and
uncomment the following:
I hope that helps.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967780#3967780
Reply to the post :
http://www.jboss.com/index.html?modul
Hi,
you could begin with downloading the JBossIDE for Eclipse or Eclipse with WTP.
Both make the work with XDoclet possible and quite easy. I have not worked with
XDoclet for a while, but for little examples it is working fine. The wizards of
both systems and the tutorial for the JBossIDE show
Hi!
You can try to package your web application and to deploy it as a packaged .war
instead of an exploded one. This works for me.
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967233#3967233
Reply to the post :
http://www.jboss.com/index.html?modu
Yes.
Perhaps you could give us a bit more detail information of what you are trying
to do. Do you want to generate the deployment descriptors for J2EE
applications? If yes, you could try XDoclet
(http://sourceforge.net/projects/xdoclet/). That generates these files from
comments in the source
25 matches
Mail list logo
