Re: Error in starting Server! Please Help
I guess it's because of the firewall in Vista. You can try it again after turning off the firewall in Vista. Hope it helps. -- Yun Feng Olakara wrote: Hi, I am trying to start the server on a Vista Home OS. I get the following error: Using GERONIMO_BASE: C:\Program Files\geronimo Using GERONIMO_HOME: C:\Program Files\geronimo Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:C:\Java\jdk1.5.0_14\jre Booting Geronimo Kernel (in Java 1.5.0_14)... Starting Geronimo Application Server v2.1.1 [*** ] 58% 14s Loading org.apache.ger...23:25:22,409 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for [EMAIL PROTECTED] javax.resource.spi.ResourceAdapterInternalException: Unable to obtain physical connection to [EMAIL PROTECTED] at org.tranql.connector.jdbc.AbstractLocalDataSourceMCF.getPhysicalConnection(AbstractLocalDataSourceMCF.java:72) at org.tranql.connector.jdbc.AbstractLocalDataSourceMCF.createManagedConnection(AbstractLocalDataSourceMCF.java:64) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.LocalXAResourceInsertionInterceptor.getConnection(LocalXAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:70) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:94) at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:87) at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56) at org.apache.geronimo.connector.DatabaseInitializationGBean.init(DatabaseInitializationGBean.java:50) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at
Re: Re: JCA Connector and hidden-classes
I'm not sure exactly what you are trying to do but have you looked at http://cwiki.apache.org/GMOxDOC21/configuring-application-specific-logging-with-log4j.html to see if it would help? thanks david jencks Alas, I'm using geronimo 2.0.2... I don't feel I'm trying to do something special. I'm deploying a Resource Adapter packaged in a rar file. I want this adapter to use the commons-logging.jar and log4j.jar (with their corresponding commons-logging.properties and log4j.xml) that are in the rar, in order to have total control on the log level Thanks Jean-Noël On Jul 9, 2008, at 2:44 AM, johnxmas wrote: Kevan, I corrected my geronimo.bat, by suppressing the quotes as you stated, and, yes, it succeeded: the commons-logging.jar used is the one from my application Thanks for that BUT, that is not a full success: as expected, the LogFactory gives me a Log4JLogger MockAdapter setting hostName - Log is org.apache.commons.logging.impl.Log4JLogger - loaded from file:/D:/ geronimo-tomcat6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/ MockAdapter-1.0.rar/rar/commons-logging-1.1.jar Alas, the following line MockAdapter - embedded Log is org.apache.log4j.Logger - loaded from file:/D:/geronimo-tomcat6-jee5-2.0.2/lib/log4j-1.2.14.jar shows that my applications log4j.jar is not used. So, my local log4j.xml is ignored and I get a default INFO trace level instead of the ones I specified Jean-Noël On Jul 8, 2008, at 9:24 AM, johnxmas wrote: David, Hmm. The MPCLSearchOption is working for me. I set as follows: set JAVA_OPTS=- DXorg.apache.geronimo.kernel.config.MPCLSearchOption=safe I verified that this works on Windows (and Mac OS X). I had Jetty installed. Don't see how a Tomcat install could behave differently. Here's the output during deploy: MockAdapter setting hostName - Log factory is org.apache.commons.logging.LogFactory - loaded from file:/C:/ geronimo- jetty6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/ MockAdapter-1.0.rar/rar/commons-logging.jar Doh... I bet the 's that you used are wrong... If you update your GERONIMO_OPTS setting in geronimo.bat and remove the quotation mark characters, I bet it works... Still need to fix this properly... --kevan
Re: Error in starting Server! Please Help
There's also this: IOException occurred while saving attributes java.io.IOException: Unable to rename C:\Program Files\geronimo\var\config\config.xml to C:\Program Files\geronimo\var\config\config.xml.bak in order to back up manageable attribute save file I'm guessing you have an access issue in Program Files? Have you tried starting the server from one of your directories like somewhere in the Users (Documents and Settings) folder. I believe applications are not supposed to write files in Program Files on Vista. Trygve 2008/7/16 YunFeng Ma [EMAIL PROTECTED]: I guess it's because of the firewall in Vista. You can try it again after turning off the firewall in Vista. Hope it helps. -- Yun Feng Olakara wrote: Hi, I am trying to start the server on a Vista Home OS. I get the following error: Using GERONIMO_BASE: C:\Program Files\geronimo Using GERONIMO_HOME: C:\Program Files\geronimo Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:C:\Java\jdk1.5.0_14\jre Booting Geronimo Kernel (in Java 1.5.0_14)... Starting Geronimo Application Server v2.1.1 [*** ] 58% 14s Loading org.apache.ger...23:25:22,409 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for [EMAIL PROTECTED] javax.resource.spi.ResourceAdapterInternalException: Unable to obtain physical connection to [EMAIL PROTECTED] at org.tranql.connector.jdbc.AbstractLocalDataSourceMCF.getPhysicalConnection(AbstractLocalDataSourceMCF.java:72) at org.tranql.connector.jdbc.AbstractLocalDataSourceMCF.createManagedConnection(AbstractLocalDataSourceMCF.java:64) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.LocalXAResourceInsertionInterceptor.getConnection(LocalXAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:70) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:94) at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:87) at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56) at org.apache.geronimo.connector.DatabaseInitializationGBean.init(DatabaseInitializationGBean.java:50) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) at
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.
Re: Geronimo 2.1.1 MDB Performance Question
Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to send the JMS message? DefaultActiveMQConnectionFactory configures a single-pool with default max-size 10. I'm not sure whether this can explain what you saw in your scenario, but I think you can try to create a new ActiveMQ RA (you can do this via admin console) with a larger size single-pool and rerun your scenario. Hope this helps. -- Yun Feng the666pack wrote: 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
Re: Geronimo 2.1.1 MDB Performance Question
actually i deployed a geronimo-application.xml deployment plan, defining the connection factory: ext-module connectorjms-resources/connector external-path xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:groupIdorg.apache.geronimo.modules/dep:groupId dep:artifactIdgeronimo-activemq-ra/dep:artifactId dep:version2.1.1/dep:version dep:typerar/dep:type /external-path connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:dependencies dep:dependency dep:groupIdorg.apache.geronimo.configs/dep:groupId dep:artifactIdactivemq-broker/dep:artifactId dep:version2.1.1/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies /dep:environment resourceadapter resourceadapter-instance resourceadapter-namejms-resources/resourceadapter-name workmanager xmlns=http://geronimo.apache.org/xml/ns/naming-1.2; gbean-linkDefaultWorkManager/gbean-link /workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameVideoConnectionFactory/name implemented-interfacejavax.jms.QueueConnectionFactory/implemented-interface implemented-interfacejavax.jms.TopicConnectionFactory/implemented-interface connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size200/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes5/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter adminobject adminobject-interfacejavax.jms.Queue/adminobject-interface adminobject-classorg.apache.activemq.command.ActiveMQQueue/adminobject-class adminobject-instance message-destination-namequeue/videoupdate/message-destination-name config-property-setting name=PhysicalNamequeue/videoupdate/config-property-setting /adminobject-instance /adminobject /connector but maybe it ignores these settings and it takes the default settings. i will give it a try, thanks for helping, mario. 2008/7/16 YunFeng Ma [EMAIL PROTECTED]: Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to send the JMS message? DefaultActiveMQConnectionFactory configures a single-pool with default max-size 10. I'm not sure whether this can explain what you saw in your scenario, but I think you can try to create a new ActiveMQ RA (you can do this via admin console) with a larger size single-pool and rerun your scenario. Hope this helps. -- Yun Feng the666pack wrote: 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
Re: Geronimo 2.1.1 MDB Performance Question
my connection factory is successfully deployed on the server and the queue is using it as far as i can say. nevertheless, not more than 10 connections are made to the database. does the connection factory pool size always have to be the amount of data source connections? i already tried with 20 but still no difference, just 10 database connections open at one time. is there a possibility to adjust the message-queue size somehow? thanks a lot for the answers, greetings, mario. 2008/7/16 Mario Kofler [EMAIL PROTECTED]: actually i deployed a geronimo-application.xml deployment plan, defining the connection factory: ext-module connectorjms-resources/connector external-path xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:groupIdorg.apache.geronimo.modules/dep:groupId dep:artifactIdgeronimo-activemq-ra/dep:artifactId dep:version2.1.1/dep:version dep:typerar/dep:type /external-path connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:dependencies dep:dependency dep:groupIdorg.apache.geronimo.configs/dep:groupId dep:artifactIdactivemq-broker/dep:artifactId dep:version2.1.1/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies /dep:environment resourceadapter resourceadapter-instance resourceadapter-namejms-resources/resourceadapter-name workmanager xmlns=http://geronimo.apache.org/xml/ns/naming-1.2; gbean-linkDefaultWorkManager/gbean-link /workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameVideoConnectionFactory/name implemented-interfacejavax.jms.QueueConnectionFactory/implemented-interface implemented-interfacejavax.jms.TopicConnectionFactory/implemented-interface connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size200/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes5/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter adminobject adminobject-interfacejavax.jms.Queue/adminobject-interface adminobject-classorg.apache.activemq.command.ActiveMQQueue/adminobject-class adminobject-instance message-destination-namequeue/videoupdate/message-destination-name config-property-setting name=PhysicalNamequeue/videoupdate/config-property-setting /adminobject-instance /adminobject /connector but maybe it ignores these settings and it takes the default settings. i will give it a try, thanks for helping, mario. 2008/7/16 YunFeng Ma [EMAIL PROTECTED]: Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to send the JMS message? DefaultActiveMQConnectionFactory configures a single-pool with default max-size 10. I'm not sure whether this can explain what you saw in your scenario, but I think you can try to create a new ActiveMQ RA (you can do this via admin console) with a larger size single-pool and rerun your scenario. Hope this helps. -- Yun Feng the666pack wrote: 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
Re: Geronimo 2.1.1 MDB Performance Question
I think there's a setting for the mdb pool size in the activation spec. Also it looks like the DefaultWorkManager only has 30 threads which is pretty low but I don't see offhand how this would result in only 10 worker threads. thanks david jencks On Jul 16, 2008, at 3:38 AM, Mario Kofler wrote: my connection factory is successfully deployed on the server and the queue is using it as far as i can say. nevertheless, not more than 10 connections are made to the database. does the connection factory pool size always have to be the amount of data source connections? i already tried with 20 but still no difference, just 10 database connections open at one time. is there a possibility to adjust the message-queue size somehow? thanks a lot for the answers, greetings, mario. 2008/7/16 Mario Kofler [EMAIL PROTECTED]: actually i deployed a geronimo-application.xml deployment plan, defining the connection factory: ext-module connectorjms-resources/connector external-path xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:groupIdorg.apache.geronimo.modules/dep:groupId dep:artifactIdgeronimo-activemq-ra/dep:artifactId dep:version2.1.1/dep:version dep:typerar/dep:type /external-path connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:dependencies dep:dependency dep:groupIdorg.apache.geronimo.configs/dep:groupId dep:artifactIdactivemq-broker/dep:artifactId dep:version2.1.1/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies /dep:environment resourceadapter resourceadapter-instance resourceadapter-namejms-resources/resourceadapter-name workmanager xmlns=http://geronimo.apache.org/xml/ns/naming-1.2 gbean-linkDefaultWorkManager/gbean-link /workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory- interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameVideoConnectionFactory/name implemented-interfacejavax.jms.QueueConnectionFactory/ implemented-interface implemented-interfacejavax.jms.TopicConnectionFactory/ implemented-interface connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size200/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes5/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter adminobject adminobject-interfacejavax.jms.Queue/adminobject- interface adminobject- classorg.apache.activemq.command.ActiveMQQueue/adminobject-class adminobject-instance message-destination-namequeue/videoupdate/message- destination-name config-property-setting name=PhysicalNamequeue/videoupdate/config-property-setting /adminobject-instance /adminobject /connector but maybe it ignores these settings and it takes the default settings. i will give it a try, thanks for helping, mario. 2008/7/16 YunFeng Ma [EMAIL PROTECTED]: Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to send the JMS message? DefaultActiveMQConnectionFactory configures a single-pool with default max-size 10. I'm not sure whether this can explain what you saw in your scenario, but I think you can try to create a new ActiveMQ RA (you can do this via admin console) with a larger size single-pool and rerun your scenario. Hope this helps. -- Yun Feng the666pack wrote: 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
EJB Injection in Managed Bean
Good evening, I've got two managed beans in a JSF 1.2 webapp. Both beans are quite equal. I try to inject a stateless session bean (EJB3) into the managed beans. @EJB(name = java:comp/env/ejb/CredentialData) private CredentialData credentialData; In the first managed bean the EJB is injected correctly. The second bean with exactly the same injection code does not get the EJB. There is no error but at runtime credentialData is null. I get messages like WARN [startup] Unresolved ejb reference ejb/CredentialData in bean GeronimoEnc. Will attempt resolution again at runtime. but injection works on the first managed bean. I tried to debug through the code but failed because I didn't understand it completely and may be didn't find the right peace. Can anyone give me an advice? Thanks Matthias Berndt
Re: javax.jms.JMSException: Failed to build body from bytes
Kevan, Your assumption is correct. I've moved the jms connector into my ear deployment plan as you suggested. JMS is now happy. I'll see if I can mock up some artifacts for you. In the meantime, here is what I had before with jms connector as a separate module hopefully will help you determine if it's a bug indeed. geronimo2.1.2 repository apps myApp 1.0 myApp-1.0.car META-INF appweb.war appDataSource 1.0 appDataSource-1.0.rar META-INF rar META-INF appJMS 1.0 appJMS-1.0.rar META-INF rar META-INF NOTE: There is no longer appJMS module, I have moved it into the ear deployment plan. Kevan Miller wrote: On Jul 15, 2008, at 9:56 AM, jklcom99 wrote: The app was running on G1.1.1. I've recently upgraded to G2.1.2- SNAPSHOT. I believe I'm on G2.1.2-SNAPSHOT 07/03 build. Test case: Whenever a scheduled Quartz job kicks off, the server would send a JMS message to update the UI. Could this be a bug? Please let me know if you need more information. Thanks. Assuming that the contents of your EAR are correct (i.e. lib/ contains a jar file which contains the required Classes for the ObjectMessage), I think this is a bug. I was hoping you could prepare some deployable artifacts that we could be used to recreate, test and diagnose the problem. It will take a bit of work to set up your scenario. Anything that you can do to make it easier to recreate your problem will increase the chances of somebody looking at it... If I understand correctly, you are separately deploying a JMS 'module' and an EAR with your MDB. I don't think Quartz is needed to recreate the problem, just some JMS ObjectMessage with an object from your EAR's lib/ We may be able to figure this out without a test case, but it would definitely help... --kevan Thank you Kevan Miller wrote: Thanks. Is it possible for you to provide a test case that can illustrate the problem? Which version of Geronimo were you using previously? If you want to try a work-around, you could try moving your connector deployment into your ear deployment plan. --kevan -- View this message in context: http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18465908.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18498003.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: EJB Injection in Managed Bean
I'm not sure why this happened, but it will be easer to debug if you can attach your sample. :-) -- Yun Feng Matthias Berndt wrote: Good evening, I've got two managed beans in a JSF 1.2 webapp. Both beans are quite equal. I try to inject a stateless session bean (EJB3) into the managed beans. @EJB(name = java:comp/env/ejb/CredentialData) private CredentialData credentialData; In the first managed bean the EJB is injected correctly. The second bean with exactly the same injection code does not get the EJB. There is no error but at runtime credentialData is null. I get messages like WARN [startup] Unresolved ejb reference ejb/CredentialData in bean GeronimoEnc. Will attempt resolution again at runtime. but injection works on the first managed bean. I tried to debug through the code but failed because I didn't understand it completely and may be didn't find the right peace. Can anyone give me an advice? Thanks Matthias Berndt
