Its in :-
deploy\ejb3.deployer\META-INF\jboss-service.xml
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4264874#4264874
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4264874
___
For various reasons each EJB is in its own jar file, all the jar files are in
the ear file in the deploy directory. Strange thing is it dosnt always happen.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262105#4262105
Reply to the post :
Im getting this error from one of my EJBs (several hundred others deploy fine)
when I startup jboss 4.2.2
?
2009-10-22 12:10:52,177 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec
violation:
Bean : TimedFeeReport
Section: 22.2
Warning: The Bean Provider must specify the fully-qualified
We have 14 Jboss 4.2.2 systems running on the same server, at midnight they all
simultaneously update their runDate in the database (Oracle) and occasionally
(twice a week ?) they produce this error, any idea what might cause this ??
The only thing I can think is some kind of limit to number of
Does anyone know how to flush the AS CMP cache (without stopping/restarting the
AS)?
Since turning it on a lot of our unit tests are failing because they setup and
teardown data directly in the db before running, the good old AS knows nothing
about this and holds the test data from previous
Has anybody tried the caching of CMPs by the AS ? We examined our application
and discovered it was hitting the database thousands of times for each request,
this was due to the application developers use of findByBusinessKey methods, we
converted the code to use the findbyPrimaryKey method so
Are you sure you are actually retrieving something from the database. ie is
there some data that matches your primary key? Also, are you accessing the
retrieved data ? the AS only puts data into the cache when it is accessed ( not
when you do the findByPrimaryKey ).
View the original post :
This was due to the fact that the AS only caches data when its accessed, not
when findByPrimaryKey is called. One of the tests printed out the returned
entity (and hence it was cached) and the other didnt (and hence it wasnt
cached).
View the original post :
Is it possible to trace when transactions start and finish ? We have an
application that seems to be creating loads of new transactions but I need to
prove it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3996798#3996798
Reply to the post :
Cant I get all the benefits of caching by using cmps, accessing via their
primaryKey and letting the AS do the caching, without having to write container
specific code to put things into and take things out of a cache ?
View the original post :
OK, here goes :-
2006-12-20 11:01:46,269 DEBUG [javax.management.timer.Timer] start:
jboss.jmx:name=SnmpAgent,service=timer,type=heartbeat at Wed Dec 20 11:01:46
GMT 2006
2006-12-20 11:01:50,660 INFO [org.apache.catalina.startup.Embedded] Catalina
naming disabled
2006-12-20 11:01:50,738 INFO
This is definitely the first error message, the lines above the error message
are :-
...
2006-12-19 12:33:06,594 DEBUG [org.jboss.deployment.MainDeployer] Done with
create step of deploying synchronousinstructionprocessorEJB.jar
2006-12-19 12:33:06,594 DEBUG [org.jboss.deployment.MainDeployer]
We have two entity beans that are accessed via their findByPrimaryKey methods.
Both beans have the same container configuration and are executed 10 times
within a single transaction.
By turning on CMP tracing we can see that for the first bean one line of sql is
executed against the database
Does JBoss cache 'empty' beans ? ie beans that have no data in the database or
does it keep calling the select and getting nothing back ??
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3988814#3988814
Reply to the post :
Is it true that CMP entity beans are only cached in the appserver if they are
looked up by primary key ?
Is it possible to see the cache hits by the appserver ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986054#3986054
Reply to the post :
I have had exactly the same problem with Oracle, on following the instructions
above I discovered the file MQ.oracle-ds.xml as well as the oracle-ds.xml file.
Deleting the MQ.oracle-ds.xml file solved the problem but where it came from,
who knows ?
View the original post :
16 matches
Mail list logo