Geronimo 2.1.1 MDB Performance Question
hello, i have a question regarding MDBS in Geronimo 2.1.1 i bombard the server with a high amount of mdb requests, the mdbs write tuples to a database. so although my database connection pool maximum is 20 i realize that with mdbs the pool is just utilized with 10 connections to the database, no matter how many requests are coming in. does somebody have an idea what might be the reason for this behaviour? thanks a lot, mario -- View this message in context: http://www.nabble.com/Geronimo-2.1.1-MDB-Performance-Question-tp18483266s134p18483266.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Stateful Session Bean Problem Geronimo 2.1.1: "Passivation Failed"
hello, my old question about stateless session beans was posted here http://www.nabble.com/Re%3A-Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-td16144020s134.html#a16024338 it was concerned about the "passivation bug" in the geronimo 2.0.2 version. so i now installed the 2.1.1 version in order to test the stateful session bean performance of geronimo. unfortunately i still get the problem: "passivation failed" (see stack trace below)... Was this passivation issue ever solved? or is it still not working properly? i just can turn passivation off, what leads to an inferior performance. stack trace: [exec] 12:38:15,811 INFO [OpenEJB] Passivating to file /usr/local/geronimo/5.2.1.1/var/temp/11d1def534ea1be0=-49fa44bf=11b07642b72=-7fe7 [exec] 12:38:15,816 ERROR [OpenEJB] Passivation failed [exec] java.io.NotSerializableException: org.apache.openjpa.persistence.EntityManagerImpl [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) [exec] at org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:73) [exec] at org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:92) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager.passivate(StatefulInstanceManager.java:496) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager$BeanEntryQueue.add(StatefulInstanceManager.java:610) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager.poolInstance(StatefulInstanceManager.java:429) [exec] at org.apache.openejb.core.stateful.StatefulContainer.createEJBObject(StatefulContainer.java:314) [exec] at org.apache.openejb.core.stateful.StatefulContainer.invoke(StatefulContainer.java:267) [exec] at org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267) [exec] at org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:245) [exec] at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) [exec] at $Proxy22.create(Unknown Source) [exec] at org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:33) [exec] at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:150) [exec] at org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(IntraVmJndiReference.java:38) [exec] at org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40) [exec] at org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:118) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:603) [exec] at javax.naming.InitialContext.lookup(InitialContext.java:392) [exec] at vt.servlet.AddServlet.doGet(AddServlet.java:46) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
error writing tuple to database "the owning entity is not mapped" geronimo 2.1.1
hello, i am back again and hope someone can help me out with my new error in geronimo 2.1.1. my database scheme consists of a Person entity and a Director entity which is inherited from the Person entity. so i want to write a Person first, to keep it simple. unfortunately i get an error when i try to perform a write: org.apache.openjpa.persistence.ArgumentException: Attempt to map "vt.bean.entity.Person.id" failed: the owning entity is not mapped. i was successfully writing tuples of my application to database with geronimo version 2.0.2 and also did not change nothing in my .ear archive and application. i found a jira on a similar topic: https://issues.apache.org/jira/browse/OPENJPA-524 but i am not sure if this is the same problem, and the jira is in a fixed-solved status. the full debug view is: [exec] 10:51:04,196 INFO [OpenEJB] invoking method create on videothek.jar/WriteDataBean [exec] 10:51:04,268 INFO [OpenEJB] finished invoking method create [exec] 10:51:04,300 INFO [Transaction] TX Required: Started transaction [EMAIL PROTECTED] [exec] 10:51:04,304 INFO [Transaction] TX Required: Committing transaction [EMAIL PROTECTED] [exec] 10:51:04,305 INFO [Transaction] TX Required: Started transaction [EMAIL PROTECTED] [exec] 10:51:04,314 INFO [Runtime] Starting OpenJPA 1.0.2 [exec] 10:51:04,427 INFO [JDBC] Using dictionary class "org.apache.openjpa.jdbc.sql.PostgresDictionary". [exec] 10:51:05,734 INFO [Transaction] TX Required: setRollbackOnly() on transaction [EMAIL PROTECTED] [exec] 10:51:05,735 INFO [Transaction] TX Required: Rolling back transaction [EMAIL PROTECTED] [exec] javax.ejb.EJBException: The bean encountered a non-application exception.; nested exception is: [exec] org.apache.openjpa.persistence.ArgumentException: Attempt to map "vt.bean.entity.Person.id" failed: the owning entity is not mapped. [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:366) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:251) [exec] at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) [exec] at $Proxy23.writeToDB(Unknown Source) [exec] at vt.servlet.AddServlet.doGet(AddServlet.java:48) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) [exec] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) [exec] at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) [exec] at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) [exec] at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) [exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) [exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [exec] at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563) [exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) [exec] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) [exec] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) [exec] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) [exec] at java.lang.Thread.run(Thread.java:619) [exec] Caused by: org.apache.openjpa.persistence.ArgumentException: Attempt to map "vt.bean.entity.Person.id" failed: the owning entity is not mapped. [exec] at org.apache.openjpa.jdbc.meta.MappingInfo.assertTable(MappingInfo.java:544) [exec] at org.apache.openjpa.jdbc.meta.MappingInfo.createColumns(MappingInfo.java:496) [exec] at org.apache.openjpa.jdbc.meta.ValueMappingInfo.getColumns(ValueMappingInfo.java:143) [exec] at org.apache.openjpa.jdbc.meta.strats.PrimitiveFieldStrategy.map(PrimitiveFieldStrategy.java:83) [exec] at org.apache.openjpa.jdbc.meta.FieldMapping.setStrategy(FieldMapping.java:120) [exec] at org.apache.openjpa.jdbc.meta.RuntimeStrategyInstaller.installStrategy(RuntimeStrategyInstaller.java:80) [exec] at org.apache.openjpa.jdbc.meta.FieldM
fundamental question of understanding about pools and pool size
hello, i am using EJB 3.0 and was searching for some time now to change some kind of entity bean pool where i can change the container pool size for persistent entities. now i wanted to ask if there is an understanding problem.. could it be that, stateless and stateful entity bean pool sizes already include the associated persistent entities? that means that if stateless container "poolSize=100" for a stateless bean means 1 stateless bean and 99 associated persistent entity beans are possible? or does it merely mean (as i thought til now) that stateless container "poolSize=100" means that there is a pool for 100 stateless session beans. the confusion arose, because i did not find any way to configure how many persistent entity beans are possible concurrently. maybe someone can bring some clarification in this topic. thank you for your help, mario -- View this message in context: http://www.nabble.com/fundamental-question-of-understanding-about-pools-and-pool-size-tp16383168s134p16383168.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: MDB performance tuning, configuration
so sorry for the 1000 messages today.. just want to add something to this
topic once more:
i have my server up now again with the old behaviour (2.0.2):
mdbs get queued up til some point the performance increases (65 concurrent
users - transactions per second about 85 transactions/sec) then the
performance decreases again. in the end of my test i have to wait another 2
minutes til the messages in the queue are finished at the server.
your proposal:
the problem i have is that when i include the activation config as you told
me to do, like:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "maxSessions",
propertyValue = "32"),
@ActivationConfigProperty(propertyName = "destination",
propertyValue = "queue/videoupdate")})
the MDB stops delivering after some time and then i have the problem i
already mentioned above:
somehow there seem to be messages hanging in the queue and anytime i start
the server some more 10 messages are processed. but i cannot send messages
anymore to the server because it just works on some old "orphaned" messages
from the test-run before. the only solution i got from that point on is to
start with a fresh clean server as i dont knwo how to flush the queue or
something similar.
if i on the other hand dont change the "maxSessions" activation config and
just set the "MDB Container InstanceLimit" to "0" no significant performance
increase is experienced.
if someone can help more with this error i get i would be very happy.
thanks a lot in advance,
mario
the666pack wrote:
>
> ok as it is just a test server i had a quick "setup session" and got a
> clean server again. i hope i dont run into the problem anymore now.. i
> will keep some backup server just in case ;)
>
>
> the666pack wrote:
>>
>> hallo,
>>
>> it seems i completely messed up with my MDB application now. i tried the
>> "activation spec" that you mentioned and it worked fine. then i thought
>> ia lso try to set the InstanceLimit to 0. so i went to the config.xml
>> file and changed the "MDB\ Container\ InstanceLimit=0" wrong thing to do.
>> after that i did not receive the wanted updates anymore in the database.
>> i increased the value again to "maxPool" size.. and since that at startup
>> of the server or at deploy time i always realize that some messages are
>> delivered but then it stops again. i dont even send messages anymore, the
>> messages that are delivered are from a test 2 hours ago!
>>
>> i also tried to restart the database, restart the server, computer,
>> everything. and tried to start with an empty db. the only thing i realize
>> is that at startup or deploytime of my application it sends some 10
>> messages to the queue and after this it stops.
>>
>> by the way.. i already set the values back to their initial state.. but
>> no effect.. i keep having this error and not possible to deliver any new
>> messages.. just everytime i start i see more 10 values being changed in
>> the database.
>>
>> can anyone help me, please.
>>
>> thanks,
>>
>> mario
>>
>>
>> manucet wrote:
>>>
>>> You may have tried this out but increasing the maxMessagesPerSession
>>> activation config property will increase the prefetch size and
>>> generally speed it up a bit more. I assume u have already increased
>>> the maxSessions activation config property to increase the no of
>>> parallel Mdb instances. Here is a link for the properties that AMQ
>>> allows http://activemq.apache.org/activation-spec-properties.html. The
>>> configurable OpenEJB properties are given here
>>> http://openejb.apache.org/example-generated-documentation.html.
>>>
>>> Try setting the InstanceLimit property of the MdbContainer to 0 so
>>> that the no of instances created matches the no of AMQ sessions
>>> available. For setting this you need to set this as a system property.
>>> The property should be containerId.InstanceLimit where containerId is
>>> of the format .-
>>>
>>> eg: org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ
>>> RA-javax.jms.MessageListener
>>>
>>> ie = artifactId of the jms RA
>>> - The resource Group name u gave while creating
>>> the RA
>>> - javax.jms.MessageListener in this case
>>>
>>> So the property in this case can be s
info message at startup: "not defined set of persistent classes"
hello! so i switched back to 2.0.2. my favourite geronimo version so far :) i found out that at startup i get an info message at the console that looks like this: [exec] 15:31:08,338 INFO [Enhance] You have enabled runtime enhancement, but have not specified the set of persistent classes. OpenJPA must look for metadata for every loaded class, which might increase class load times significantly. may this be a performance issue for the server under load? the odd thing is also that i actually DO specify the set of my persistent classes in my persistence.xml file: http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"; version="1.0"> videothek org.apache.openjpa.persistence.PersistenceProviderImpl vt.bean.entity.Person vt.bean.entity.Actor vt.bean.entity.Director vt.bean.entity.Movie vt.bean.entity.Dvd jdbc/postgres jdbc/postgres i thank you for helping and i am sure soon i can make geronimo the best performing server of all :) regards, mario -- View this message in context: http://www.nabble.com/info-message-at-startup%3A-%22not-defined-set-of-persistent-classes%22-tp16253526s134p16253526.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: MDB performance tuning, configuration
ok as it is just a test server i had a quick "setup session" and got a clean server again. i hope i dont run into the problem anymore now.. i will keep some backup server just in case ;) the666pack wrote: > > hallo, > > it seems i completely messed up with my MDB application now. i tried the > "activation spec" that you mentioned and it worked fine. then i thought ia > lso try to set the InstanceLimit to 0. so i went to the config.xml file > and changed the "MDB\ Container\ InstanceLimit=0" wrong thing to do. after > that i did not receive the wanted updates anymore in the database. i > increased the value again to "maxPool" size.. and since that at startup of > the server or at deploy time i always realize that some messages are > delivered but then it stops again. i dont even send messages anymore, the > messages that are delivered are from a test 2 hours ago! > > i also tried to restart the database, restart the server, computer, > everything. and tried to start with an empty db. the only thing i realize > is that at startup or deploytime of my application it sends some 10 > messages to the queue and after this it stops. > > by the way.. i already set the values back to their initial state.. but no > effect.. i keep having this error and not possible to deliver any new > messages.. just everytime i start i see more 10 values being changed in > the database. > > can anyone help me, please. > > thanks, > > mario > > > manucet wrote: >> >> You may have tried this out but increasing the maxMessagesPerSession >> activation config property will increase the prefetch size and >> generally speed it up a bit more. I assume u have already increased >> the maxSessions activation config property to increase the no of >> parallel Mdb instances. Here is a link for the properties that AMQ >> allows http://activemq.apache.org/activation-spec-properties.html. The >> configurable OpenEJB properties are given here >> http://openejb.apache.org/example-generated-documentation.html. >> >> Try setting the InstanceLimit property of the MdbContainer to 0 so >> that the no of instances created matches the no of AMQ sessions >> available. For setting this you need to set this as a system property. >> The property should be containerId.InstanceLimit where containerId is >> of the format .- >> >> eg: org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ >> RA-javax.jms.MessageListener >> >> ie = artifactId of the jms RA >> - The resource Group name u gave while creating the >> RA >> - javax.jms.MessageListener in this case >> >> So the property in this case can be set as >> org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ\ >> RA-javax.jms.MessageListener.InstanceLimit=0 >> >> Regards >> Manu >> On Sun, Mar 23, 2008 at 4:49 PM, the666pack <[EMAIL PROTECTED]> >> wrote: >>> >>> hello, >>> >>> i am trying to test the performance of geronimo under load for message >>> driven beans. the observed behaviour is that i get a maximum of about >>> 85 >>> transactions per second. after this, tested with about 60 concurrent >>> users, >>> the performance drops again to about 45 tps. i hoped to increase the >>> performance somehow.. things i already tried: >>> >>> -increase the mdb pool size >>> -increase the thread pool size >>> -increase the connector-thread-pool-size >>> >>> unfortunately nothing helped, the performance situation remains the >>> same. >>> >>> another observed behaviour is that in the time of silence between tests >>> the >>> server needs some time to fulfill the requests sent before. so i see it >>> is >>> still working although i am not sending mdb-requests anymore. >>> >>> i suppose these are the requests that are still in the queue and have >>> to be >>> finished. i think this is the reason for the performance drop with more >>> concurrent users. i would like to see it perform without this >>> "aftertime-working" and handle the requests "in time". >>> >>> maybe someone can give me a hint which other values could be important >>> to >>> change for the performance of mdbs getting real good. i thank you very >>> much >>> for your help, >>> >>> greetings, >>> >>> mario >>> -- >>> View this message in context: >>> http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16234678.html >>> Sent from the Apache Geronimo - Users mailing list archive at >>> Nabble.com. >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16249640.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
setMaxResults()
hello, geronimo version: 2.1 the function "setMaxResults()" seems not to work fine. in my application i first execute an select query then try to limit the returned values via query.setMaxResults(10). after this i loop through the results list (which i got via query.getResultList()) and update some fields. unfortunately all the results of the Select query are updated, not just the ones selected by "query.setMaxResults()". This was working fine before in Geronimo 2.0.2 -- View this message in context: http://www.nabble.com/setMaxResults%28%29-tp16249488s134p16249488.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: MDB performance tuning, configuration
hallo, it seems i completely messed up with my MDB application now. i tried the "activation spec" that you mentioned and it worked fine. then i thought ia lso try to set the InstanceLimit to 0. so i went to the config.xml file and changed the "MDB\ Container\ InstanceLimit=0" wrong thing to do. after that i did not receive the wanted updates anymore in the database. i increased the value again to "maxPool" size.. and since that at startup of the server or at deploy time i always realize that some messages are delivered but then it stops again. i dont even send messages anymore, the messages that are delivered are from a test 2 hours ago! i also tried to restart the database, restart the server, computer, everything. and tried to start with an empty db. the only thing i realize is that at startup or deploytime of my application it sends some 10 messages to the queue and after this it stops. by the way.. i already set the values back to their initial state.. but no effect.. i keep having this error and not possible to deliver any new messages.. just everytime i start i see more 10 values being changed in the database. can anyone help me, please. thanks, mario manucet wrote: > > You may have tried this out but increasing the maxMessagesPerSession > activation config property will increase the prefetch size and > generally speed it up a bit more. I assume u have already increased > the maxSessions activation config property to increase the no of > parallel Mdb instances. Here is a link for the properties that AMQ > allows http://activemq.apache.org/activation-spec-properties.html. The > configurable OpenEJB properties are given here > http://openejb.apache.org/example-generated-documentation.html. > > Try setting the InstanceLimit property of the MdbContainer to 0 so > that the no of instances created matches the no of AMQ sessions > available. For setting this you need to set this as a system property. > The property should be containerId.InstanceLimit where containerId is > of the format .- > > eg: org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ > RA-javax.jms.MessageListener > > ie = artifactId of the jms RA > - The resource Group name u gave while creating the > RA > - javax.jms.MessageListener in this case > > So the property in this case can be set as > org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ\ > RA-javax.jms.MessageListener.InstanceLimit=0 > > Regards > Manu > On Sun, Mar 23, 2008 at 4:49 PM, the666pack <[EMAIL PROTECTED]> > wrote: >> >> hello, >> >> i am trying to test the performance of geronimo under load for message >> driven beans. the observed behaviour is that i get a maximum of about 85 >> transactions per second. after this, tested with about 60 concurrent >> users, >> the performance drops again to about 45 tps. i hoped to increase the >> performance somehow.. things i already tried: >> >> -increase the mdb pool size >> -increase the thread pool size >> -increase the connector-thread-pool-size >> >> unfortunately nothing helped, the performance situation remains the >> same. >> >> another observed behaviour is that in the time of silence between tests >> the >> server needs some time to fulfill the requests sent before. so i see it >> is >> still working although i am not sending mdb-requests anymore. >> >> i suppose these are the requests that are still in the queue and have to >> be >> finished. i think this is the reason for the performance drop with more >> concurrent users. i would like to see it perform without this >> "aftertime-working" and handle the requests "in time". >> >> maybe someone can give me a hint which other values could be important >> to >> change for the performance of mdbs getting real good. i thank you very >> much >> for your help, >> >> greetings, >> >> mario >> -- >> View this message in context: >> http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16234678.html >> Sent from the Apache Geronimo - Users mailing list archive at >> Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16248114.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
MDB performance tuning, configuration
hello, i am trying to test the performance of geronimo under load for message driven beans. the observed behaviour is that i get a maximum of about 85 transactions per second. after this, tested with about 60 concurrent users, the performance drops again to about 45 tps. i hoped to increase the performance somehow.. things i already tried: -increase the mdb pool size -increase the thread pool size -increase the connector-thread-pool-size unfortunately nothing helped, the performance situation remains the same. another observed behaviour is that in the time of silence between tests the server needs some time to fulfill the requests sent before. so i see it is still working although i am not sending mdb-requests anymore. i suppose these are the requests that are still in the queue and have to be finished. i think this is the reason for the performance drop with more concurrent users. i would like to see it perform without this "aftertime-working" and handle the requests "in time". maybe someone can give me a hint which other values could be important to change for the performance of mdbs getting real good. i thank you very much for your help, greetings, mario -- View this message in context: http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16234678.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
OptimisticLockException
Hello, so i try to test the server how it handles concurrent delete requests. i start quite low with 5 concurrent users trying to delete some values from the database. the problem is that i keep getting the error mentioned in the subject. the more concurrent users i schedule, the more errors i get until about 30 concurrent users the performance levels off quite low. the thing i do in my code is removing a persistent entity: // em.lock(director,LockModeType.WRITE); //optimistic lock exception?? em.remove(director); //em.flush(); //because of optimistic lock exception deleted++; i also tried with the help of the commented out lines, but without a significant performance increase, here is the error log, maybe someone could help, THANK YOU! [exec] Caused by: org.apache.openjpa.persistence.OptimisticLockException: An optimistic lock violation was detected when flushing object instance "vt.bean.entity.Director-1192302" to the data store. This indicates that the object was concurrently modified in another transaction. [exec] FailedObject: vt.bean.entity.Director-1192302 [exec] at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:101) [exec] at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:73) [exec] at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:162) [exec] at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89) [exec] at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89) [exec] at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72) [exec] at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:514) [exec] at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130) [exec] ... 42 more [exec] NestedThrowables: [exec] org.apache.openjpa.persistence.OptimisticLockException: An optimistic lock violation was detected when flushing object instance "vt.bean.entity.Director-1192302" to the data store. This indicates that the object was concurrently modified in another transaction. [exec] FailedObject: vt.bean.entity.Director-1192302 [exec] at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:101) [exec] at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:73) [exec] at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:162) [exec] at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89) [exec] at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89) [exec] at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72) [exec] at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:514) [exec] at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130) [exec] at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1946) [exec] at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1844) [exec] at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1615) [exec] at org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:973) [exec] at org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:488) [exec] at vt.bean.stateless.DeleteDataBean.removeDirectors(DeleteDataBean.java:115) [exec] at sun.reflect.GeneratedMethodAccessor175.invoke(Unknown Source) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:597) [exec] at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:146) [exec] at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:129) [exec] at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) [exec] at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:203) [exec] at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) [exec] at org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:223) [exec] at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invok
Re: Geronimo 2.0.2 - OpenEJB "Passivation Failed"
David Blevins wrote: > > > Nothing like that. Best you can do is bump your poolSize up much > higher. The settings we supply are very conservative and you could > likely have a much higher limit depending on the memory limits of your > vm. > > -David > > > ok, i overcame the issue now with editing /var/config/config.xml and setting BulkPassivate to 0: TimeOut=30 PoolSize=100 BulkPassivate=0 now the error is gone. i want to thank you for your help greetings, mario -- View this message in context: http://www.nabble.com/Re%3A-Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-tp15880469s134p16024338.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0.2 - OpenEJB "Passivation Failed"
David Blevins wrote: > > > You could implement serializable on your Entity beans, but it's ill > advised in almost any situation to have the data passivated with your > bean as you wind up with a private, detached, copy of the data that > may be outdated. The rare case may be that you're collecting data > that has yet to be persisted (never been attached) and therefore > doesn't live in the EntityManager's cache or database yet, but even > then you should really be using a transaction which would prevent your > bean from getting passivated at all so the issue should never arise. > > -David > > > > so this means i have to manually "turn off" the passivation of my SFSB via bean managed transactions. but i suppose this means a performance loss :(. is this problem another issue of the bug mentioned above and so the only solution is turning off the passivation mechanism? further, til now whenever i tried to make some kind of manual transaction in my beans i always got the error that the container is taking care of the transactions and bean managed control (transactions) is not allowed. maybe you can tell me what i have to change to be able to add transactions to my bean. and even further, is there the possibility to turn off the passivation for SFSB at all in geronimo? like some entry in a deployment descriptor "passivation=false" ? thanks a lot for helping, mario. -- View this message in context: http://www.nabble.com/Re%3A-Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-tp15880469s134p15950694.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0.2 - OpenEJB "Passivation Failed"
Jacek Laskowski wrote: > > > Hi, > > You should be concerned although the message level is too low I guess. > It happens when openejb attempts to passivate an instance so that > particular instance is in fact destroyed (the @PreDestroy method may > have been called). I think you may not have seen any troubles yet as > you didn't reuse the sfsbs and hence you didn't notice these > passivated instances were no longer active. Let's find out why the > bean is not capable of being passivated. How does it look like? I > guess it uses a logger instance or such with no transient keyword > specified, doesn't it? > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > hello jacek, the only thing i do in the @PreDestroy method is to explicitly close the entity manager via em.close() and then print a line to stdout that the entitymanager was closed. am i not supposed to close the em? thanks, mario -- View this message in context: http://www.nabble.com/Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-tp15663519s134p15668868.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Geronimo 2.0.2 - OpenEJB "Passivation Failed"
hello, i try to stress-test the geronimo application server version 2.0.2. so i try to call a jsp repeatedly, which validates against a stateless session bean and then creates a stateful session bean.. for the first few calls it starts fine but then after about 100 calls the server starts to throw the following error every now and then (means that inbetween there are calls which create the session beans successful): [exec] 13:04:31,854 INFO [OpenEJB] finished invoking method create [exec] 13:04:31,855 INFO [OpenEJB] finished invoking method create [exec] 13:04:31,857 INFO [OpenEJB] Passivating to file /usr/local/geronimo/5-2.0.2/var/temp/11d1def534ea1be0=-8cc2910=1184b52f0a4=-7e38 [exec] 13:04:31,865 INFO [OpenEJB] Passivation failed [exec] java.io.NotSerializableException: vt.bean.stateful.WriteDataBean [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) [exec] at org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:73) [exec] at org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:93) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager.passivate(StatefulInstanceManager.java:487) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager$BeanEntryQueue.add(StatefulInstanceManager.java:579) [exec] at org.apache.openejb.core.stateful.StatefulInstanceManager.poolInstance(StatefulInstanceManager.java:413) [exec] at org.apache.openejb.core.stateful.StatefulContainer.createEJBObject(StatefulContainer.java:291) [exec] at org.apache.openejb.core.stateful.StatefulContainer.invoke(StatefulContainer.java:241) [exec] at org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267) [exec] at org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:245) [exec] at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) [exec] at $Proxy22.create(Unknown Source) [exec] at org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:33) [exec] at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:150) [exec] at org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(IntraVmJndiReference.java:38) [exec] at org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40) [exec] at org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:118) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158) [exec] at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:603) [exec] at javax.naming.InitialContext.lookup(InitialContext.java:392) [exec] at vt.servlet.LoginServlet.doGet(LoginServlet.java:68) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [exec] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) [exec] at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectVa
performance tuning web-container in geronimo
hello! so this mailing list gave me good tips til now.. hope for this one too: i am performance testing the geronimo server. however i realized a low throughput for simultaneous client requests. so now i would like to know which possibilities i have to change this behaviour and increase performance. for performance tests i use the command line tool openwebload (http://openwebload.sourceforge.net), my jvm settings are fine now (-Xmx1024m) and i see the memory getting used up the more simultaneous client requests i send. however after about 160 simultaneous client requests the jvm is filled up and the server is going dead. this is too few for my taste. i need to keep the settings for tomcat (for example maxacceptrate,thread pool,...) and the jvm settings fixed, but i would anyway like to improve the performance. is there something i can do? are there possibilities of connection pooling or an improved garbage collection for the jvm so that it does not fill up the memory so fast? thanks in advance for help, greetings, mario -- View this message in context: http://www.nabble.com/performance-tuning-web-container-in-geronimo-tp15628903s134p15628903.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: JVM OutOfMemoryError: Java heap space
i have to reply to my own message.. somehow i realized that in the geronimo-console for the JVM is still written: Total Memory Allocated 63,56 MB and as soon as the size is reached the JVM hangs. so it seems that my environment settings (JAVA_OPTS or GERONIMO_OPTS) are not recognized? how can i set the jvm size according to my given values without these env variables? thanks for every help, greetings, mario the666pack wrote: > > hello, > > i try to performance test the geronimo applicatoin server but after 2 > minutes of testing the JVM hangs up and i get the following message on the > command line: > > java.lang.OutOfMemoryError: Java heap space > > my customized options for the jvm are: > > -server -Xms1280m -Xmx1280m -XX:PermSize=1280m -XX:MaxPermSize=1280m > > so this should be sufficient for the heap! unfortunately at 40 > simultaneous calls the JVM hangs and i just can kill it via the system > call! > > i also observed that the memory is not allocated, there is still plenty of > memory left (at least 3/4 of my 2048m) and it does not change the size > also not with more requests. but after 2 minutes->crash! > > also my call is fairly simple: it is a single call to a JSP page which > just returns the date. so this really should be possible. but i cannot see > the reason for the Exception anymore! > > so if anyone can help, PLEASE! > > thanks, > > mario. > -- View this message in context: http://www.nabble.com/JVM-OutOfMemoryError%3A-Java-heap-space-tp15532296s134p15535160.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
JVM OutOfMemoryError: Java heap space
hello, i try to performance test the geronimo applicatoin server but after 2 minutes of testing the JVM hangs up and i get the following message on the command line: java.lang.OutOfMemoryError: Java heap space my customized options for the jvm are: -server -Xms1280m -Xmx1280m -XX:PermSize=1280m -XX:MaxPermSize=1280m so this should be sufficient for the heap! unfortunately at 40 simultaneous calls the JVM hangs and i just can kill it via the system call! i also observed that the memory is not allocated, there is still plenty of memory left (at least 3/4 of my 2048m) and it does not change the size also not with more requests. but after 2 minutes->crash! also my call is fairly simple: it is a single call to a JSP page which just returns the date. so this really should be possible. but i cannot see the reason for the Exception anymore! so if anyone can help, PLEASE! thanks, mario. -- View this message in context: http://www.nabble.com/JVM-OutOfMemoryError%3A-Java-heap-space-tp15532296s134p15532296.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0: customize EJB-Container settings
another thing,
geronimo seems to cut out the parts of the config.xml file which i entered.
so i try to alter the properties:
PoolSize=100
StrictPooling=true
and after starting and shutting down geronimo i end up without the
"PoolSize" line.. same happens with "TimeOut" values and also in the
StatefulContainer gbean.
any idea?
thanks,
mario.
Gianny Damour wrote:
>
> Hello Mario,
>
> EJB Container properties along with their default values are defined
> by the resource META-INF/org.apache.openejb.embedded/service-jar.xml
> within the openejb-core.jar archive. Here is an URL pointing to this
> resource:
> http://svn.apache.org/repos/asf/openejb/trunk/openejb3/container/
> openejb-core/src/main/resources/META-INF/org.apache.openejb.embedded/
> service-jar.xml
>
> I believe you are after the TimeOut and PoolSize properties.
>
> Thanks,
> Gianny
>
> On 26/01/2008, at 10:28 PM, the666pack wrote:
>
>>
>> thanks,
>>
>> where can i get a full listing of the possible properties for the
>> openejb
>> container?
>>
>> in particular i would need properties like MaxCacheSize for how
>> many beans
>> can be kept at the same time by the ejb-container or a
>> RemoveTimeout which
>> defines the time after which the beans are removed from the pool
>> when not
>> needed.
>>
>> i didnt find a list where i can see the properties that are
>> possible for
>> openejb.
>>
>> thanks for helping,
>>
>> mario
>>
>>
>> Gianny Damour wrote:
>>>
>>> Hello,
>>>
>>> You can change these settings in var/config/config.xml. This file
>>> defines overrides for the GBeans, i.e. services such as EJB-
>>> Containers, running within Geronimo.
>>>
>>> EJB Containers are declared by the org.apache.geronimo.configs/
>>> openejb//car confiiguration and here are there default configuration:
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default Stateless Container
>>> STATELESS
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default Stateful Container
>>> STATEFUL
>>> PoolSize=1000
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default BMP Container
>>> BMP_ENTITY
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default CMP Container
>>> CMP_ENTITY
>>>
>>> OpenEjbSystem
>>>
>>>
>>>
>>> To override the PoolSize attribute of DefaultStatefulContainer, you
>>> need to update the org.apache.geronimo.configs/openejb//car
>>> confiiguration as follows in var/config/config.xm:
>>>
>>>
>>>
>>> ${OpenEJBPort + PortOffset}>> attribute>
>>> ${ServerHostname}
>>>
>>>
>>>
>>>PoolSize=100
>>>
>>>
>>>
>>>
>>> Properties declared there are passed "as-is" to OpenEJB; hence, you
>>> can use the same property names defined by OpenEJB.
>>>
>>> Thanks,
>>> Gianny
>>>
>>>
>>> On 25/01/2008, at 6:19 AM, the666pack wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> Can anybody tell me how i can customize the EJB-Container
>>>> settings in
>>>> Geronimo?
>>>>
>>>> I dont find an entry in the admin-console and i dont have an idea
>>>> which
>>>> files i can search for change.
>>>>
>>>> Basically i would like to set values like Bean-Pool Size or Maximum
>>>> Cache
>>>> Size as well as Timeout values.
>>>>
>>>> I hope someone can help,
>>>>
>>>> thank you,
>>>>
>>>> Mario
>>>> --
>>>> View this message in context: http://www.nabble.com/Geronimo-2.0%3A-
>>>> customize-EJB-Container-settings-tp15072400s134p15072400.html
>>>> Sent from the Apache Geronimo - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Geronimo-2.0%3A-
>> customize-EJB-Container-settings-tp15072400s134p15106943.html
>> Sent from the Apache Geronimo - Users mailing list archive at
>> Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Geronimo-2.0%3A-customize-EJB-Container-settings-tp15072400s134p15120164.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0: customize EJB-Container settings
hello,
thank you, these values are quite helpful already to specify important
performance values.
however i am missing some configuration settings.. in particular:
- container settings for entity beans (maximum pool size, commit option)
- cache settings (not pool-settings but merely what happens when the pool is
full)
is it possible to set such settings in geronimo or openejb?
thanks very much for helping,
mario.
Gianny Damour wrote:
>
> Hello Mario,
>
> EJB Container properties along with their default values are defined
> by the resource META-INF/org.apache.openejb.embedded/service-jar.xml
> within the openejb-core.jar archive. Here is an URL pointing to this
> resource:
> http://svn.apache.org/repos/asf/openejb/trunk/openejb3/container/
> openejb-core/src/main/resources/META-INF/org.apache.openejb.embedded/
> service-jar.xml
>
> I believe you are after the TimeOut and PoolSize properties.
>
> Thanks,
> Gianny
>
> On 26/01/2008, at 10:28 PM, the666pack wrote:
>
>>
>> thanks,
>>
>> where can i get a full listing of the possible properties for the
>> openejb
>> container?
>>
>> in particular i would need properties like MaxCacheSize for how
>> many beans
>> can be kept at the same time by the ejb-container or a
>> RemoveTimeout which
>> defines the time after which the beans are removed from the pool
>> when not
>> needed.
>>
>> i didnt find a list where i can see the properties that are
>> possible for
>> openejb.
>>
>> thanks for helping,
>>
>> mario
>>
>>
>> Gianny Damour wrote:
>>>
>>> Hello,
>>>
>>> You can change these settings in var/config/config.xml. This file
>>> defines overrides for the GBeans, i.e. services such as EJB-
>>> Containers, running within Geronimo.
>>>
>>> EJB Containers are declared by the org.apache.geronimo.configs/
>>> openejb//car confiiguration and here are there default configuration:
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default Stateless Container
>>> STATELESS
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default Stateful Container
>>> STATEFUL
>>> PoolSize=1000
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default BMP Container
>>> BMP_ENTITY
>>>
>>> OpenEjbSystem
>>>
>>>
>>> >> class="org.apache.geronimo.openejb.EjbContainer">
>>> Default CMP Container
>>> CMP_ENTITY
>>>
>>> OpenEjbSystem
>>>
>>>
>>>
>>> To override the PoolSize attribute of DefaultStatefulContainer, you
>>> need to update the org.apache.geronimo.configs/openejb//car
>>> confiiguration as follows in var/config/config.xm:
>>>
>>>
>>>
>>> ${OpenEJBPort + PortOffset}>> attribute>
>>> ${ServerHostname}
>>>
>>>
>>>
>>>PoolSize=100
>>>
>>>
>>>
>>>
>>> Properties declared there are passed "as-is" to OpenEJB; hence, you
>>> can use the same property names defined by OpenEJB.
>>>
>>> Thanks,
>>> Gianny
>>>
>>>
>>> On 25/01/2008, at 6:19 AM, the666pack wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> Can anybody tell me how i can customize the EJB-Container
>>>> settings in
>>>> Geronimo?
>>>>
>>>> I dont find an entry in the admin-console and i dont have an idea
>>>> which
>>>> files i can search for change.
>>>>
>>>> Basically i would like to set values like Bean-Pool Size or Maximum
>>>> Cache
>>>> Size as well as Timeout values.
>>>>
>>>> I hope someone can help,
>>>>
>>>> thank you,
>>>>
>>>> Mario
>>>> --
>>>> View this message in context: http://www.nabble.com/Geronimo-2.0%3A-
>>>> customize-EJB-Container-settings-tp15072400s134p15072400.html
>>>> Sent from the Apache Geronimo - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Geronimo-2.0%3A-
>> customize-EJB-Container-settings-tp15072400s134p15106943.html
>> Sent from the Apache Geronimo - Users mailing list archive at
>> Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Geronimo-2.0%3A-customize-EJB-Container-settings-tp15072400s134p15119677.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0: customize EJB-Container settings
thanks,
where can i get a full listing of the possible properties for the openejb
container?
in particular i would need properties like MaxCacheSize for how many beans
can be kept at the same time by the ejb-container or a RemoveTimeout which
defines the time after which the beans are removed from the pool when not
needed.
i didnt find a list where i can see the properties that are possible for
openejb.
thanks for helping,
mario
Gianny Damour wrote:
>
> Hello,
>
> You can change these settings in var/config/config.xml. This file
> defines overrides for the GBeans, i.e. services such as EJB-
> Containers, running within Geronimo.
>
> EJB Containers are declared by the org.apache.geronimo.configs/
> openejb//car confiiguration and here are there default configuration:
>
> class="org.apache.geronimo.openejb.EjbContainer">
> Default Stateless Container
> STATELESS
>
> OpenEjbSystem
>
>
> class="org.apache.geronimo.openejb.EjbContainer">
> Default Stateful Container
> STATEFUL
> PoolSize=1000
>
> OpenEjbSystem
>
>
> class="org.apache.geronimo.openejb.EjbContainer">
> Default BMP Container
> BMP_ENTITY
>
> OpenEjbSystem
>
>
> class="org.apache.geronimo.openejb.EjbContainer">
> Default CMP Container
> CMP_ENTITY
>
> OpenEjbSystem
>
>
>
> To override the PoolSize attribute of DefaultStatefulContainer, you
> need to update the org.apache.geronimo.configs/openejb//car
> confiiguration as follows in var/config/config.xm:
>
>
>
> ${OpenEJBPort + PortOffset} attribute>
> ${ServerHostname}
>
>
>
>PoolSize=100
>
>
>
>
> Properties declared there are passed "as-is" to OpenEJB; hence, you
> can use the same property names defined by OpenEJB.
>
> Thanks,
> Gianny
>
>
> On 25/01/2008, at 6:19 AM, the666pack wrote:
>
>>
>> Hello,
>>
>> Can anybody tell me how i can customize the EJB-Container settings in
>> Geronimo?
>>
>> I dont find an entry in the admin-console and i dont have an idea
>> which
>> files i can search for change.
>>
>> Basically i would like to set values like Bean-Pool Size or Maximum
>> Cache
>> Size as well as Timeout values.
>>
>> I hope someone can help,
>>
>> thank you,
>>
>> Mario
>> --
>> View this message in context: http://www.nabble.com/Geronimo-2.0%3A-
>> customize-EJB-Container-settings-tp15072400s134p15072400.html
>> Sent from the Apache Geronimo - Users mailing list archive at
>> Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Geronimo-2.0%3A-customize-EJB-Container-settings-tp15072400s134p15106943.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Error after sending Message via MDB
Hello, My application sends a message via a MDB to update some value in the database. The update is successful, yet after the update i get the error below at the console. Can anyone tell me how to get rid of this error? Thanks a lot for helping, Mario [exec] 20:20:07,077 ERROR [Transaction] Please correct the integration and supply a NamedXAResource [exec] java.lang.IllegalStateException: Cannot log transactions as [EMAIL PROTECTED] is not a NamedXAResource. [exec] at org.apache.geronimo.transaction.manager.TransactionImpl$TransactionBranch.getResourceName(TransactionImpl.java:697) [exec] at org.apache.geronimo.transaction.log.HOWLLog.prepare(HOWLLog.java:254) [exec] at org.apache.geronimo.transaction.log.HOWLLog$$FastClassByCGLIB$$7315be2e.invoke() [exec] at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) [exec] at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) [exec] at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) [exec] at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) [exec] at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) [exec] at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) [exec] at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) [exec] at org.apache.geronimo.transaction.manager.TransactionLog$$EnhancerByCGLIB$$65de4c27.prepare() [exec] at org.apache.geronimo.transaction.manager.TransactionImpl.internalPrepare(TransactionImpl.java:444) [exec] at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:316) [exec] at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:238) [exec] at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:139) [exec] at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) [exec] at org.apache.openejb.core.mdb.MdbContainer.afterDelivery(MdbContainer.java:375) [exec] at org.apache.openejb.core.mdb.EndpointHandler.afterDelivery(EndpointHandler.java:274) [exec] at org.apache.openejb.core.mdb.EndpointHandler.invoke(EndpointHandler.java:164) [exec] at $Proxy44.afterDelivery(Unknown Source) [exec] at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:126) [exec] at org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:65) [exec] at org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:216) [exec] at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751) [exec] at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:165) [exec] at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:290) [exec] at org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32) [exec] at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201) [exec] at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331) [exec] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [exec] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [exec] at java.lang.Thread.run(Thread.java:619) -- View this message in context: http://www.nabble.com/Error-after-sending-Message-via-MDB-tp15072505s134p15072505.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Geronimo 2.0: customize EJB-Container settings
Hello, Can anybody tell me how i can customize the EJB-Container settings in Geronimo? I dont find an entry in the admin-console and i dont have an idea which files i can search for change. Basically i would like to set values like Bean-Pool Size or Maximum Cache Size as well as Timeout values. I hope someone can help, thank you, Mario -- View this message in context: http://www.nabble.com/Geronimo-2.0%3A-customize-EJB-Container-settings-tp15072400s134p15072400.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
MDB - NameNotFound Error
hello all,
i am trying to make a message-driven-bean working on geronimo. after
configuration of the queue and connection factory i am stuck with a
[exec] javax.naming.NameNotFoundException: VideoConnectionFactory
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:163)
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
[exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
[exec] at
javax.naming.InitialContext.lookup(InitialContext.java:392)
i will try to post the relevant parts of my configuration files and client
here. hope someone can help.
the relevant parts of my client (the client is a jsp) with the line where
the error occurs:
Properties env = new Properties();
env.put(Context.PROVIDER_URL, "tcp://localhost:61616");
env.put("connectionFactoryNames", "VideoConnectionFactory");
env.put("queue.VideoQueue", "queue/videoupdate");
Context ctx = new InitialContext(env);
QueueConnectionFactory factory = (QueueConnectionFactory)
ctx.lookup("java:comp/env/VideoConnectionFactory"); //the
error occurs here
queue = (Queue) ctx.lookup("queue/videoupdate");
connection = factory.createQueueConnection();
System.out.println("Connection created to CONNECTIONFACTORY");
messageSession =
connection.createQueueSession(false,QueueSession.AUTO_ACKNOWLEDGE);
the "JMS-Resources" part of the web-console tells me however that the queue
and the connection factory are running:
jms-resources (default/videothek/1200600754675/ear)
Type NameDeployed
As State Actions
Connection Factory VideoConnectionFactory Application-scoped running
Queue queue/videoupdate Application-scoped
running
the relevant part of my openejb-jar.xml:
UpdateDataBean
jms-resources
do i have to write something into my web.xml deployment descriptor too
(because my client is a jsp)?
any help is highly appreciated,
thanks a lot,
mario
--
View this message in context:
http://www.nabble.com/MDB---NameNotFound-Error-tp14934912s134p14934912.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
ok, first of all the problem was the database connection with the geronimo-specific deployment descriptors. but after this was solved by help of your wiki i faced this No registered metadata for type "class vt.bean.entity.Director" error. so the problem was, that in my application (which was first deployed on jboss) i have a 1:n relation between Directors and Movies. this relation i was modelling by an @ManyToOne annotation in Movie and a @OneToMany relation in Director (i don't really know why). this was accepted by jboss but in geronimo i got some error and when i finally pinpointed the error to the annotation i simply commented out the annotation... leaving the Collection as attribute in the Director. that Collection was not annotated now, leading to the above mentioned error. while i was searching through deployment plans and descriptors over and over again changing values and attributes, i just realized the problem is in the app after i was modifying the "simple entity ejb" example from the documentation. thanks for your help, mario Jacek Laskowski wrote: > > On Jan 15, 2008 10:44 PM, the666pack <[EMAIL PROTECTED]> wrote: > > Wait. What was the attribute that stirred up the trouble? I must admit > I'm still unable to figure that out from the entire thread. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14873589.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
hello, problem solved. the last error where i spent a lot of time with, No registered metadata for type "class vt.bean.entity.Director" was in fact created by some attribute in the Director entity bean which should not have been there. i was just searching on the wrong side of the tracks for a long long time. thanks for your help with setting up the connection to postgresql, i come back for MDBs later ;) greetings, mario. the666pack wrote: > > ok, > > it seems to me that the only reason i got the "no No registered metadata > for type "class vt.bean.entity.Director"" error was because in my > persistence.xml file the following property was set: > > > > can you tell me what this property is good for? > > as soon as i dont set this property or set it to some other value (like in > your mdb-tutorial to > value="buildSchema(SchemaAction='add,deleteTableContents')")i get an error > again as soon as i call "emf.createEntityManager()": > > [exec] WAITING... to see if entitymanager is created successfully > [exec] 12:47:49,858 ERROR [OpenEJB] The bean instances business > method encountered a system exception: null > [exec] <1.0.0-r561970-r561970 nonfatal general error> > org.apache.openjpa.persistence.PersistenceException: null > [exec] at > org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:204) > [exec] at > org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142) > [exec] at > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:190) > [exec] at > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:143) > [exec] at > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:55) > [exec] at > vt.bean.stateful.WriteDataBean.writeToDB(WriteDataBean.java:89) > [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [exec] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [exec] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [exec] at java.lang.reflect.Method.invoke(Method.java:597) > [exec] at > org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:146) > [exec] at > org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:129) > [exec] at > org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) > [exec] at > org.apache.openejb.core.stateful.StatefulContainer._invoke(StatefulContainer.java:427) > [exec] at > org.apache.openejb.core.stateful.StatefulContainer.businessMethod(StatefulContainer.java:389) > [exec] at > org.apache.openejb.core.stateful.StatefulContainer.invoke(StatefulContainer.java:246) > [exec] at > org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:211) > [exec] at > org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:65) > [exec] at > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:244) > [exec] at > org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) > [exec] at $Proxy57.writeToDB(Unknown Source) > [exec] at > org.apache.jsp.addTool_jsp._jspService(addTool_jsp.java:108) > [exec] at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > [exec] at > javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > [exec] at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388) > [exec] at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) > [exec] at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) > [exec] at > javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > [exec] at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > [exec] at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > [exec] at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > [exec] at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > [exec]
Re: Geronimo 2.0/openejb/postgresql
java.lang.reflect.Method.invoke(Method.java:597) [exec] at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:146) [exec] at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:129) [exec] at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) [exec] at org.apache.openejb.core.stateful.StatefulContainer._invoke(StatefulContainer.java:427) [exec] at org.apache.openejb.core.stateful.StatefulContainer.businessMethod(StatefulContainer.java:389) [exec] at org.apache.openejb.core.stateful.StatefulContainer.invoke(StatefulContainer.java:246) [exec] at org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:211) [exec] at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:65) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:244) [exec] ... 25 more [exec] Caused by: java.lang.Exception: java.lang.NullPointerException [exec] at org.apache.openjpa.util.Exceptions.replaceNestedThrowables(Exceptions.java:242) [exec] at org.apache.openjpa.persistence.PersistenceException.writeObject(PersistenceException.java:100) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:597) [exec] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [exec] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [exec] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [exec] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [exec] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.copyObj(BaseEjbProxyHandler.java:503) [exec] at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:249) [exec] ... 25 more do you have an idea? i am getting crazy but i NEED to get this application running on geronimo. thanks A LOT, mario Jacek Laskowski wrote: > > On Jan 13, 2008 7:35 PM, the666pack <[EMAIL PROTECTED]> wrote: > >> for the messaging part of your tutorial i will return to the wiki at a >> later >> state, as it seems to be very helpful though written in polish language >> :) > > Let me know what article you're after and one day it could be > translated/written just for you ;-) > >> i found some files that were not supposed to be in my archive, you are >> right. yet the error remains also now after redeploying. the directory >> structure: > > Is the error the same as before? If so, I don't think we can fix it > without having such an application created to reproduce the issue (if > you stripped the application down from unnecessary bits and sent it > along here, it'd be helpful). > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14838249.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
hello, >> first thank you, with the help of your article i was able to deploy it >> and >> my application is able to create an entity manager. i did not have a geronimo-specific application.xml yet in my application. so i took the one from the polish wiki and modified it for my needs: left out any messaging parts and just added the "postgresql" connector part. i also slightly modified my openejb-jar.xml and added the "openjpa" dependency as suggested in the wiki. now the entity manager is created successfully. for the messaging part of your tutorial i will return to the wiki at a later state, as it seems to be very helpful though written in polish language :) but first i want my entity beans working. >> [exec] <1.0.0-r561970-r561970 nonfatal general error> >> org.apache.openjpa.persistence.PersistenceException: No registered >> metadata >> for type "class vt.bean.entity.Director". > I'd bet you've got the entity in another file that your > persistence.xml file is and hence the file is not processed. What is > needed to fix it would be to list the content of the files with jar > -tf. If your app could be attached and we looked at it, it'd be > helpful even more. i found some files that were not supposed to be in my archive, you are right. yet the error remains also now after redeploying. the directory structure: .ear: META-INF/ META-INF/MANIFEST.MF META-INF/application.xml META-INF/geronimo-application.xml videothek.jar videothek.war .jar: META-INF/ META-INF/MANIFEST.MF META-INF/ejb-jar.xml META-INF/openejb-jar.xml META-INF/persistence.xml vt/ vt/bean/ vt/bean/entity/ vt/bean/entity/Actor.class vt/bean/entity/Director.class vt/bean/entity/Dvd.class vt/bean/entity/Movie.class vt/bean/entity/Person.class vt/bean/stateful/ vt/bean/stateful/WriteData.class vt/bean/stateful/WriteDataBean.class vt/bean/stateless/ vt/bean/stateless/Login.class vt/bean/stateless/LoginBean.class vt/bean/stateless/LoginLocal.class .war: META-INF/ META-INF/MANIFEST.MF WEB-INF/ WEB-INF/web.xml WEB-INF/geronimo-web.xml WEB-INF/classes/ WEB-INF/classes/vt/ WEB-INF/classes/vt/servlet/ WEB-INF/classes/vt/servlet/LoginServlet.class addTool.jsp error.jsp index.jsp login.jsp removeTool.jsp search.jsp updateTool.jsp thanks again, your help is very much appreciated, greetings, mario. -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14789262.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
hello, first thank you, with the help of your article i was able to deploy it and my application is able to create an entity manager. unfortunately i am stuck with another error now when i want to persist an entity bean to the database: [exec] <1.0.0-r561970-r561970 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: No registered metadata for type "class vt.bean.entity.Director". my persistence.xml now looks like this: http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"; version="1.0"> videothek org.apache.openjpa.persistence.PersistenceProviderImpl videothek.jar vt.bean.entity.Person vt.bean.entity.Actor vt.bean.entity.Director vt.bean.entity.Movie vt.bean.entity.Dvd -> jdbc/postgres jdbc/postgres according to this in my opinion the "Director" entity bean should be registered. or do i have to mention it in another deployment descriptor too (e.g. openejb-jar.xml?) thanks for your help, mario Jacek Laskowski wrote: > > On Jan 10, 2008 7:59 PM, the666pack <[EMAIL PROTECTED]> wrote: > >> also tried to put the and the >> element >> after the properties and also to spare out all properties.. same error >> message :( > > Here's the complete article about running MDB with JPA in JTA mode and > PostgreSQL - > http://www.jaceklaskowski.pl/wiki/Aplikacja_Java_EE_5_z_MDB_z_JPA_w_trybie_JTA_i_PostgreSQL_w_Apache_Geronimo_2. > It's in Polish, but you may want to look at the configuration files > only. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14784297.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
hello, "valhalla" is just the name of my persistence-unit, the actual name of the database is "video": jdbc.ConnectionURL: jdbc:postgresql://localhost:5432/video nevertheless i tried to change the names of the and elements and also of the persistence-unit to "video" or to "valhalla", yet without an effect, the error message remains the same. my persistence.xml is found in the reply to Jacek Laskowski's post thanks, mario Jay D. McHugh-2 wrote: > > Hello, > > Instead of using the reference name of your database pools - try using > the actual names in the persistence.xml. > > ie: > valhalla > valhalla2 > > Jay > > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14741285.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
ok, sorry, persistence.xml: http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"; version="1.0"> videothek org.apache.openjpa.persistence.PersistenceProviderImpl videothek.jar DefaultDS DefaultNoTxDS also tried to put the and the element after the properties and also to spare out all properties.. same error message :( thanks, mario Jacek Laskowski wrote: > > On Jan 10, 2008 5:02 PM, the666pack <[EMAIL PROTECTED]> wrote: > >> so i set up the second datasource as recommended and the pool is also >> running according to startup info: >> >> [exec] RAR: console.dbpool/DefaultDS/1.0/rar >> [exec] RAR: console.dbpool/DefaultNoTxDS/1.0/rar >> >> unfortunately i get an error at deploy time now: >> >> [exec] 16:51:41,504 ERROR [DirectoryHotDeployer] Unable to deploy: >> Unable to resolve reference "NonJtaDataSourceWrapper" in gbean > > Show the plan and persistence.xml. It becomes much easier to suggest a > solution. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14741179.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.0/openejb/postgresql
hello, so i set up the second datasource as recommended and the pool is also running according to startup info: [exec] RAR: console.dbpool/DefaultDS/1.0/rar [exec] RAR: console.dbpool/DefaultNoTxDS/1.0/rar unfortunately i get an error at deploy time now: [exec] 16:51:41,504 ERROR [DirectoryHotDeployer] Unable to deploy: Unable to resolve reference "NonJtaDataSourceWrapper" in gbean default/videothek/1199980300389/car?EJBModule=videothek.jar,J2EEApplication=default/videothek/1199980300389/car,PersistenceUnitModule=videothek.jar,j2eeType=PersistenceUnit,name=valhalla to a gbean matching the pattern [?name=DefaultNoTxDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource]due to: No matches for referencePatterns: [?name=DefaultNoTxDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource] [exec] Unable to resolve reference "JtaDataSourceWrapper" in gbean default/videothek/1199980300389/car?EJBModule=videothek.jar,J2EEApplication=default/videothek/1199980300389/car,PersistenceUnitModule=videothek.jar,j2eeType=PersistenceUnit,name=valhalla to a gbean matching the pattern [?name=DefaultDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource]due to: No matches for referencePatterns: [?name=DefaultDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource] [exec] org.apache.geronimo.common.DeploymentException: Unable to resolve reference "NonJtaDataSourceWrapper" in gbean default/videothek/1199980300389/car?EJBModule=videothek.jar,J2EEApplication=default/videothek/1199980300389/car,PersistenceUnitModule=videothek.jar,j2eeType=PersistenceUnit,name=valhalla to a gbean matching the pattern [?name=DefaultNoTxDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource]due to: No matches for referencePatterns: [?name=DefaultNoTxDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource] [exec] Unable to resolve reference "JtaDataSourceWrapper" in gbean default/videothek/1199980300389/car?EJBModule=videothek.jar,J2EEApplication=default/videothek/1199980300389/car,PersistenceUnitModule=videothek.jar,j2eeType=PersistenceUnit,name=valhalla to a gbean matching the pattern [?name=DefaultDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource]due to: No matches for referencePatterns: [?name=DefaultDS#org.apache.geronimo.connector.outbound.ConnectionFactorySource] [exec] at org.apache.geronimo.deployment.DeploymentContext.getConfigurationData(DeploymentContext.java:516) [exec] at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:307) [exec] at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:126) [exec] at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke() [exec] at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) [exec] at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) [exec] at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) [exec] at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) [exec] at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) [exec] at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) [exec] at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) [exec] at java.lang.Thread.run(Thread.java:619) [exec] [exec] 16:51:43,719 ERROR [DirectoryHotDeployer] Unable to undeploy [exec] java.lang.NullPointerException [exec] at org.apache.geronimo.deployment.plugin.ConfigIDExtractor.identifyTargetModuleIDs(ConfigIDExtractor.java:174) [exec] at org.apache.geronimo.deployment.hot.DirectoryHotDeployer.fileRemoved(DirectoryHotDeployer.java:350) [exec] at org.apache.geronimo.deployment.hot.DirectoryMonitor.scanDirectory(DirectoryMonitor.java:325) [exec] at org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMonitor.java:216) [exec] at java.lang.Thread.run(Thread.java:619) this error i already got before whenever i tried versions of persistence.xml using the "" element. any help is much appreciated, thanks a lot, mario djencks wrote: > > I recommend you set up a second postgres datasource with no tx > support, say DefaultNoTxDS (pointing to the same postgres db as > DefaultDS) > > Then in persistence.xml > > DefaultDS > DefaultNoTxDS > > and leave out > >value="org.postgresql.Driver" /> > > >value="jdbc:postgresql://localhost:5432/video" /> > > and tell us what problems if any you get. > > thanks > david jencks > -- View this message in context: http://www.nabble.com/Geronimo-2.0-openejb-postgresql-tp14710209s134p14737013.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
