I suggest to post such problems in a java forum... it's not EJB related if you
can't get your main running...
1) cd C:\TEST\EJB\
2) %JAVA_HOME%\bin\java -classpath
.;C:\jboss-4.0.2\client\jboss-j2ee.jar;C:\TEST\EJB\FirstEJB\Fir
stEJB.jar FirstEJBClient
View the original post :
You can use the Timer Service provided by JBoss:
1) Just implement the org.jboss.varia.scheduler.Schedulable Interface
2) and configure the MBean
3) and deploy the SAR.
that's it...
more infos:
http://docs.jboss.org/jbossas/jboss4guide/r1/html/ch10.html#ch10.sched.sect
View the original post
to find out which LWPID corresponds to which Java thread you can run kill
-QUIT (in your case is the PID 24187) which will trigger a jvm dump with all
thread stacktraces. look for the nid (10=0xA) which corresponds to your LWPID
to find out which this guy is doing...
Dirk
View the original
My guess is that JBoss can't find this exception class during EJB deployment
even though it is in your WAR file. (btw: jars are deployed before wars)
Solution: pull out your Exception class and all other classes which are used in
both war and jar into a separate jar file which you include in
I finally found the problem after debugging JBoss:
the deployment descriptor (ejb-jar.xml) generated by xdoclet v1.2.3 spit out a
method signature with a param of an inner class which had an incorrect format
of CLASS.INNERCLASS insteand of CLASS$INNERCLASS
This is why JBoss ignored the TX type
hi,
to 2) there is one way i can think of but don't know if this would meet your
requirements, it's actually more of a hack:
by putting your jars in your jboss root lib folder all of your business classes
become available from all deployed apps. this means you're moving your jars
(classes)
Hi everybody,
I have a problem with TX handling of CMT in particular with RequiresNew types:
Following scenario:
I have a session bean here where all remote interface methods are declared with
an transaction type Required - means per definition all method calls to it
will open transactions.
Thanks for the reply.
i'm currently involved in migrating an enterprise application from weblogic to
jboss whereby it is necessary to ensure that certain ejb modules are deployed
before others.
The problem is to make sure that after a server startup jms messages which were
not delivered yet
Hi everybody,
I just wonder whether there are other options in JBoss4 of how to specify the
deployment order of jars, wars and so on than the one of prefixing the archives?
(other options than the usage of PrefixDeploymentSorter in the
jboss-service.xml!!!)
I have an enterprise archive (ear)
