[JBoss AS7 Development] - EJB3/JPA 2.0 support for AS-7
by Scott Marlow
Scott Marlow [http://community.jboss.org/people/smarlow%40redhat.com] created the document:
"EJB3/JPA 2.0 support for AS-7"
To view the document, visit: http://community.jboss.org/docs/DOC-16271
--------------------------------------------------------------
This is about how the AS-7 JPA layer and related concerns.
1. Container-managed persistence context
1. Transaction scope (JPA 7.6.1)
1. Transaction active invocation
1. Persistence context is created …
[View More] if none already associated with transaction
2. Created persistence context ends when transaction ends
3. An extended persistence context can also be used, which survives when transaction ends.
2. No transaction invocation
1. Loaded entities are detached at end of method call.
2. Extended scope (JPA 7.6.2)
1. Only supported for stateful session beans.
2. Entity modifications can be made outside of a transaction and are applied on the next joined transaction (anywhere on the cluster).
3. Extended persistence context (XPC) is created when stateful bean that depends on a XPC is created.
4. XPC is closed when dependent session bean(s) are closed (via @remove method).
5. Inheritance
1. Stateful beans that create other (local) stateful beans, share the same XPC.
3. Persistence context propagation (JPA 7.6.3)
1. A persistence context will be propagated to multiple entity managers (instances) within the same local transaction.
2. Remote invocations do not propagate the persistence context.
4. Persistence context propagation requirements for component invocations (JPA 7.6.3.1)
1. no propagation if component is invoked without a JTA transaction or without the JTA transaction propagating:
1. Transaction scoped entity manager used within the invoked component, will create a new persistence context.
2. Extended scoped entity manager used within the invoked component, will use the XPC already bound to the (invoked stateful) bean.
3. If the entity manager is invoked within a JTA transaction, the persistence context is bound to the JTA transaction.
2. If a component is invoked and the JTA transaction is propagated into the component:
1. If (SFSB) component has a XPC and the transaction already has a different persistence context associated with it, an EJBException is thrown by the container.
2. If a persistence context is bound to the JTA transaction, it is propagated into any entity managers used in the invocation.
2. Container requirements review
1. Application-managed persistence context (JPA 7.8.1)
1. Container needs to inject entity manager factory into jndi for application use.
2. Must use PersistenceProvider.createContainerEntityManagerFactory method for 3^rd^ party support. Internal APIs are fine for our persistence provider.
3. Must use EntityManagerFactory.close method to close the entity manager factory prior to shutdown (again for 3^rd^ party support).
2. Container-managed persistence context (JPA 7.9.1)
1. For 3^rd^ party support, use EntityManagerFactory.createEntityManager . Consider using for our persistence provider as well.
2. May pass (PersistenceProperty (http://download.oracle.com/javaee/6/api/javax/persistence/PersistenceProp... PersistenceContext.properties to EntityManagerFactory.createEntityManager(Map map) .
3. Container EM wrapper could implement some EntityManager.unwrap(Class<T> cls) calls but should default to underlying EM for unhandled classes.
3. Deployment
1. Extract persistence metadata from persistence.xml
2. Determine the PersistenceProvider classname for each persistence unit (PU). The default class is currently org.hibernate.ejb.HibernatePersistence.
3. Invoke the PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) to create the EMF that will be used to create all EntityManager's for the PU. The properties read from the PU are passed as the second parameter.
4. Also pass the “javax.persistence.validation.factory ” property if validation mode is not set to NONE. The validator factory value appears to be org.hibernate.validator.engine.ValidatorFactoryImpl. Consult ValidatorFactoryProvider which is currently used to bootstrap the validator factory in AS6.
5. The PU classes shouldn't be loaded until after the EMF is created.
6. The EntityManagerFactory is closed at undeploy time, which also closes all EntityManager's opened by each factory.
7. Switchboard changes for PU + PC???
4. Clustering
1. Determine impact on http://community.jboss.org/docs/DOC-13822 http://community.jboss.org/wiki/OptimizingentityandXPCreplication which may need to be tweaked for clustering other persistence providers. Judging by the jira status, this optimization is not in place yet (although the Hibernate persistence provider jira HHH-2762 is done).
2. Determine impact on http://community.jboss.org/docs/DOC-9565 http://community.jboss.org/wiki/DevEJB3NewSFSBCache (consider support for other persistence providers).
5. Weld integration (JpaInjectionServices implementation is wired in at boot time)
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16271]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[IronJacamar Development] - TestSuite - mapping test cases for AS6 and IronJacamar
by Stefano Maestri
Stefano Maestri [http://community.jboss.org/people/maeste] modified the document:
"TestSuite - mapping test cases for AS6 and IronJacamar"
To view the document, visit: http://community.jboss.org/docs/DOC-16266
--------------------------------------------------------------
h1. 1. General Note
1. Every deployment related test should be written with Arquillian
2. Every test that depends on some external deployment into the environment (for example jdbc driver) should be carefully evaluated to …
[View More]consider possible difference in AS7 env
3. Stress tests are not reported in this list because they are out of our unit test suite scope. It easy to keep track of them because all class names of this kind o tests contain the word "Stress" :)
4. InFlow test should be carefully evaluated too.
5. Also some integration tests are out of unit tests suite scope, but they are listed and commented here to keep track of them and open a discussion about integration tests.
*2. Test List*
|| Stressed condition || AS6 Implementation
(ClassName.methodName)
package is always
org.jboss.test.jca.test || IronJacamar Implementation
(packageName.ClassName.methodName)
||
| verify AdminObject deployment, obj types and properties | AdminObjectUnitTestCase.testAdminObject() | TODO. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase.
testProcessAdministeredObject. |
| Test for connection background validation | BackgroundValidationUnitTestCase | To be evaluated: we are testing our Validation mechanism directly, but this test should be ported to stress Validation framework indirectly at deploy time. IOW we can verify with this test if and when validation should stop the deployment. |
| stress various condition on CM (changing config and/or using it to get connection and so on) | BaseConnectionManagerUnitTestCase | TODO |
| | CachedConnectionErrorUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| | CachedConnectionSessionUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| verify cf (datasource) correct serialization/deserialization | ConnectionFactorySerializationUnitTestCase | TODO |
| verify dependency define in jboss-ra.xml | DependsRARUnitTestCase | Does not make sense for ironjacamar |
| Check deployment of a -ds | DeploymentUnitTestCase | /ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
NOTE: here we are just testing that deployment is working, while in old test suite also some properties setting are verified |
| Test HA connection both Local and XA | HAConnectionFactoryUnitTestCase | Does not make sense since we are not supporting HA connection right now. |
| test in flow RA using a Message Driven Bean | InflowUnitTestCase | TODO. We need to set up a messaging system in our test suite to do that |
| test correct behavior of ConnectionPool | InternalManagedConnection
PoolStatUnitTestCase | TODO |
| test that calling .close() 2 times on rs, statement, and connection does not throw Exception | JDBCComplianceUnitTestCase | To be evaluated, it's a jdbc compliance test, not directly related to JCA |
| test that after -ds redeployment connection are obtainable. | JDBCDriverRedeployUnitTestCase | TODO: extending/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
and
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
Note: the old test suite is redeploying driver too. It have to be evaluated in our new environment if it make sense and if AS7 would permit driver hot redeployment |
| test various jdbc statement method | JDBCStatementTestsConnectionUnitTestCase | It's a JDBC test, not a JCA test. To be evaluated |
| test Local transaction states | LocalTransactionTidyupUnitTestCase | TODO: byteman to be evaluated. Probably not needed here |
| test Local transaction commits and rollbacks | LocalWrapperCleanupUnitTestCase | TODO: byteman to be evaluated. Maybe useful here. |
| test marsha/unmarshal of ManagedConnectionFactory and some deployment injection for it | ManagedDeploymentUnitTestCase.java | TODO: the marshal/unmarshal part. The injection is already covered |
| Verify multi thread correct behavior for DS and JCA adapter in a Tx context | MultiThreadedTxDsUnitTestCase
MultiThreadedTxUnitTestCase | TODO for sure, but we have to postpone this after other unit tests porting/implementation, since we need to understand if the AS6 tests in this classes are enough (probably not) or if we need to stress other condition in a mutithread env. Probably we could use for all (or at least almost) of this test the Tx fake implementation we have. If we need (or decite to) use the real arjuna one we probably would need Byteman here, but it have to be carefully evaluated since we are writing pure JCA tests that should not depend on Tx framework used. The best solution frm a Unit test point of view would be to use our fake implementation for every test, but we need to verify if it is possible. |
| Verify pooling behaviours< | PoolingUnitTestCase.java
PreFillPoolingUnitTestCase.java
PoolingUnitTestCase
PreFillPoolingUnitTestCase.java | TODO: we have 2 classes that should do that in package org.jboss.jca.core.connectionmanager.unit.pool named PoolingTestCase and PreFillPoolingTestCase but all test methods are empty |
| Test case for resource adapters with primitive config-property definitions | PrimitiveUnitTestCase.java | ConnectionFactories does not make sense anymore. Moreover we are verifying config-property settings and mainly mandatory ones in parser's test cases |
| ests of the prepared statement cache | PSCacheUnitTestCase.java | TODO, but Not a pure JCA. It's a JDBC tests we have to evaluate if we are going to provide JDBC tests too. |
| tests if CachedConnectionManager works with reentrant ejbs | ReentrantUnitTestCase.java | It's a JCA/EJB test. It's more an integration test. It would make sense to have it into AS7, but not ironjacamar standalone because we need an EJB environment to do that. |
| Tests of remote access to a jdbc datasource. | RemoteDSUnitTestCase.java | It would be implemented as integration test, not as part of our unit test suite. Like stress tests. |
| Unit test for the RetryableResourceException | RetryableResourceUnitTestCase.java | does not make sense we haven't this exception in ironjacamar impl |
| RollbackOnlyReleaseConnectionUnitTestCase | RollbackOnlyReleaseConnectionUnitTestCase.java | TODO. Our Tx fake implementation should be enough here |
| tests scoped rar inside ear | ScopedRARNoJBossAppUnitTestCase.java
ScopedRARUnitTestCase.java | Integration tests. Suitable for AS7, ironjacamar standalone does not support ear |
| Tests of how security context interact with the JCA layer. | SecurityContextUnitTestCase | TODO after security integration :) |
| StaleConnectionCheckerUnitTestCase | StaleConnectionCheckerUnitTestCase.java | org/jboss/jca/adapters/jdbc/spi/StaleConnectionCheckerTestCase |
| StatisticsFormatterUnitTestCase | StatisticsFormatterUnitTestCase.java
StatisticsReporterUnitTestCase.java | Does not make sense. It will be covered by RHQ integration tests |
| Unit test for the TestConnection method | TestConnectionUnitTestCase.java | does not make sense is a jmx sever method |
| Transaction Active test | TransactionActiveUnitTestCase.java | TODO. AS6' one is based on a jms queue. Maybe it should be redefined in another way. To be evaluated. |
| Unit test for class TxConnectionManager | Unit test for class TxConnectionManager | TODO. Probably we could use for all (or at least almost) of this test the Tx fake implementation we have. If we need (or decite to) use the real arjuna one we probably would need Byteman here, but it have to be carefully evaluated since we are writing pure JCA tests that should not depend on Tx framework used. The best solution from a Unit test point of view would be to use our fake implementation for every test, but we need to verify if it is possible. |
| Tests unshared connections | UnsharedConnectionUnitTestCase.java | TODO |
| Test correct deployment of UserTx | UserTxUnitTestCase.java | Doable extending deployers' tes cases. |
| Inflow unit tests | WorkManagerUnitTestCase.java
TimerUnitTestCase.java
TxInflowUnitTestCase.java | TO be evaluated |
| XADSUnitTestCase.java | XADSUnitTestCase.java | done on H2XATestCase |
| verify correct thrown of XAException | XAExceptionUnitTestCase.java | TODO |
| Unit test for class XATxConnectionManager | XATxConnectionManagerUnitTestCase.java | TODO. Probably we could use for all (or at least almost) of this test the Tx fake implementation we have. If we need (or decite to) use the real arjuna one we probably would need Byteman here, but it have to be carefully evaluated since we are writing pure JCA tests that should not depend on Tx framework used. The best solution from a Unit test point of view would be to use our fake implementation for every test, but we need to verify if it is possible. |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16266]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[IronJacamar Development] - TestSuite - mapping test cases for AS6 and IronJacamar
by Stefano Maestri
Stefano Maestri [http://community.jboss.org/people/maeste] modified the document:
"TestSuite - mapping test cases for AS6 and IronJacamar"
To view the document, visit: http://community.jboss.org/docs/DOC-16266
--------------------------------------------------------------
h1. 1. General Note
1. Every deployment related test should be written with Arquillian
2. Every test that depends on some external deployment into the environment (for example jdbc driver) should be carefully evaluated to …
[View More]consider possible difference in AS7 env
*2. Test List*
|| Stressed condition || AS6 Implementation
(ClassName.methodName)
package is always
org.jboss.test.jca.test || IronJacamar Implementation
(packageName.ClassName.methodName)
||
| verify AdminObject deployment, obj types and properties | AdminObjectUnitTestCase.testAdminObject() | TODO. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase.
testProcessAdministeredObject. |
| Test for connection background validation | BackgroundValidationUnitTestCase | To be evaluated: we are testing our Validation mechanism directly, but this test should be ported to stress Validation framework indirectly at deploy time. IOW we can verify with this test if and when validation should stop the deployment. |
| stress various condition on CM (changing config and/or using it to get connection and so on) | BaseConnectionManagerUnitTestCase | TODO |
| | CachedConnectionErrorUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| | CachedConnectionSessionUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| verify cf (datasource) correct serialization/deserialization | ConnectionFactorySerializationUnitTestCase | TODO |
| verify dependency define in jboss-ra.xml | DependsRARUnitTestCase | Does not make sense for ironjacamar |
| Check deployment of a -ds | DeploymentUnitTestCase | /ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
NOTE: here we are just testing that deployment is working, while in old test suite also some properties setting are verified |
| Test HA connection both Local and XA | HAConnectionFactoryUnitTestCase | Does not make sense since we are not supporting HA connection right now. |
| test in flow RA using a Message Driven Bean | InflowUnitTestCase | TODO. We need to set up a messaging system in our test suite to do that |
| test correct behavior of ConnectionPool | InternalManagedConnection
PoolStatUnitTestCase | TODO: we have 2 classes that should do that in package org.jboss.jca.core.connectionmanager.unit.pool named PoolingTestCase and PreFillPoolingTestCase but all test methods are empty |
| test that calling .close() 2 times on rs, statement, and connection does not throw Exception | JDBCComplianceUnitTestCase | To be evaluated, it's a jdbc compliance test, not directly related to JCA |
| test that after -ds redeployment connection are obtainable. | JDBCDriverRedeployUnitTestCase | TODO: extending/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
and
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
Note: the old test suite is redeploying driver too. It have to be evaluated in our new environment if it make sense and if AS7 would permit driver hot redeployment |
| test various jdbc statement method | JDBCStatementTestsConnectionUnitTestCase | It's a JDBC test, not a JCA test. To be evaluated |
| test Local transaction states | LocalTransactionTidyupUnitTestCase | TODO: byteman to be evaluated. Probably not needed here |
| test Local transaction commits and rollbacks | LocalWrapperCleanupUnitTestCase | TODO: byteman to be evaluated. Maybe useful here. |
| test marsha/unmarshal of ManagedConnectionFactory and some deployment injection for it | ManagedDeploymentUnitTestCase.java | TODO: the marshal/unmarshal part. The injection is already covered |
| | | |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16266]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[IronJacamar Development] - TestSuite - mapping test cases for AS6 and IronJacamar
by Stefano Maestri
Stefano Maestri [http://community.jboss.org/people/maeste] modified the document:
"TestSuite - mapping test cases for AS6 and IronJacamar"
To view the document, visit: http://community.jboss.org/docs/DOC-16266
--------------------------------------------------------------
h1. 1. General Note
1. Every deployment related test should be written with Arquillian
2. Every test that depends on some external deployment into the environment (for example jdbc driver) should be carefully evaluated to …
[View More]consider possible difference in AS7 env
*2. Test List*
|| Stressed condition || AS6 Implementation
(ClassName.methodName)
package is always
org.jboss.test.jca.test || IronJacamar Implementation
(packageName.ClassName.methodName)
||
| verify AdminObject deployment, obj types and properties | AdminObjectUnitTestCase.testAdminObject() | TODO. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase.
testProcessAdministeredObject. |
| Test for connection background validation | BackgroundValidationUnitTestCase | To be evaluated: we are testing our Validation mechanism directly, but this test should be ported to stress Validation framework indirectly at deploy time. IOW we can verify with this test if and when validation should stop the deployment. |
| stress various condition on CM (changing config and/or using it to get connection and so on) | BaseConnectionManagerUnitTestCase | TODO |
| | CachedConnectionErrorUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| | CachedConnectionSessionUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| verify cf (datasource) correct serialization/deserialization | ConnectionFactorySerializationUnitTestCase | TODO |
| verify dependency define in jboss-ra.xml | DependsRARUnitTestCase | Does not make sense for ironjacamar |
| Check deployment of a -ds | DeploymentUnitTestCase | /ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
NOTE: here we are just testing that deployment is working, while in old test suite also some properties setting are verified |
| Test HA connection both Local and XA | HAConnectionFactoryUnitTestCase | Does not make sense since we are not supporting HA connection right now. |
| test in flow RA using a Message Driven Bean | InflowUnitTestCase | TODO. We need to set up a messaging system in our test suite to do that |
| test correct behavior of ConnectionPool | InternalManagedConnection
PoolStatUnitTestCase | TODO: we have 2 classes that should do that in package org.jboss.jca.core.connectionmanager.unit.pool named PoolingTestCase and PreFillPoolingTestCase but all test methods are empty |
| test that calling .close() 2 times on rs, statement, and connection does not throw Exception | JDBCComplianceUnitTestCase | To be evaluated, it's a jdbc compliance test, not directly related to JCA |
| test that after -ds redeployment connection are obtainable. | JDBCDriverRedeployUnitTestCase | TODO: extending /ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
and
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
Note: the old test suite is redeploying driver too. It have to be evaluated in our new environment if it make sense and if AS7 would permit driver hot redeployment |
| | | |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16266]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[IronJacamar Development] - TestSuite - mapping test cases for AS6 and IronJacamar
by Stefano Maestri
Stefano Maestri [http://community.jboss.org/people/maeste] modified the document:
"TestSuite - mapping test cases for AS6 and IronJacamar"
To view the document, visit: http://community.jboss.org/docs/DOC-16266
--------------------------------------------------------------
|| Stressed condition || AS6 Implementation
(ClassName.methodName)
package is always
org.jboss.test.jca.test || IronJacamar Implementation
(packaheName.ClassName.methodName)
||
| verify AdminObject deployment, obj types …
[View More]and properties | AdminObjectUnitTestCase.testAdminObject() | TODO. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase.
testProcessAdministeredObject. |
| Test for connection background validation | BackgroundValidationUnitTestCase.* | To be evaluated: we are testing our Validation mechanism directly, but this test should be ported to stress Validation framework indirectly at deploy time. IOW we can verify with this test if and when validation should stop the deployment. |
| stress various condition on CM (changing config and/or using it to get connection and so on) | BaseConnectionManagerUnitTestCase.* | TODO |
| | CachedConnectionErrorUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| | CachedConnectionSessionUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| verify cf (datasource) correct serialization/deserialization | ConnectionFactorySerializationUnitTestCase | TODO |
| verify dependency define in jboss-ra.xml | DependsRARUnitTestCase | Does not make sense for ironjacamar |
| Check deployment of a -ds | DeploymentUnitTestCase | /ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2TestCase
/ironjacamar-adapters/src/test/java/org/jboss/jca/adapters/jdbc/unit/H2XATestCase
NOTE: here we are just testing that deployment is working, while in old test suite also some properties setting are verified |
| Test HA connection both Local and XA | HAConnectionFactoryUnitTestCase | Does not make sense since we are not supporting HA connection right now. |
| test in flow RA using a Message Driven Bean | InflowUnitTestCase | TODO. We need to set up a messaging system in our test suite to do that |
| test correct behavior of ConnectionPool | InternalManagedConnectionPoolStatUnitTestCase | TODO: we have 2 classes that should do that in package org.jboss.jca.core.connectionmanager.unit.pool named PoolingTestCase and PreFillPoolingTestCase but all test methods are empty |
| | | |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16266]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[IronJacamar Development] - TestSuite - mapping test cases for AS6 and IronJacamar
by Stefano Maestri
Stefano Maestri [http://community.jboss.org/people/maeste] modified the document:
"TestSuite - mapping test cases for AS6 and IronJacamar"
To view the document, visit: http://community.jboss.org/docs/DOC-16266
--------------------------------------------------------------
|| Stressed condition || AS6 Implementation
(ClassName.methodName)
package is always
org.jboss.test.jca.test || IronJacamar Implementation
(packaheName.ClassName.methodName)
||
| verify AdminObject deployment, obj types …
[View More]and properties | AdminObjectUnitTestCase.testAdminObject() | TODO. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase.
testProcessAdministeredObject. |
| Test for connection background validation | BackgroundValidationUnitTestCase.* | To be evaluated: we are testing our Validation mechanism directly, but this test should be ported to stress Validation framework indirectly at deploy time. IOW we can verify with this test if and when validation should stop the deployment. |
| stress various condition on CM (changing config and/or using it to get connection and so on) | BaseConnectionManagerUnitTestCase.* | TODO |
| | CachedConnectionErrorUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| | CachedConnectionSessionUnitTestCase | To be analysed. Maybe it don't make sense as is for ironjacamar |
| verify cf (datasource) correct serialization/deserialization | ConnectionFactorySerializationUnitTestCase | TODO |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16266]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
[View Less]
14 years, 2 months
[JBoss AS7 Development] - AS7 Alpha 1 - No such file or directory error on start
by Vladimir Ralev
Vladimir Ralev [http://community.jboss.org/people/vladimir.ralev%40jboss.com] created the discussion
"AS7 Alpha 1 - No such file or directory error on start"
To view the discussion, visit: http://community.jboss.org/message/577759#577759
--------------------------------------------------------------
16:22:11,492 ERROR [org.jboss.as.process.Server:server-two.status] (pool-2-thread-2) Failed to start process 'Server:server-two': java.io.IOException: Cannot run program "/Users/vladimirralev/…
[View More]Downloads/jboss-7.0.0.Alpha1/java" (in directory "/Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) [:1.6.0_22]
at org.jboss.as.process.ManagedProcess.doStart(ManagedProcess.java:151)
at org.jboss.as.process.ManagedProcess.start(ManagedProcess.java:129)
at org.jboss.as.process.ProcessManager.startProcess(ProcessManager.java:143)
at org.jboss.as.process.ProcessManagerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessManagerServerHandler.java:160)
at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239)
at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method) [:1.6.0_22]
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) [:1.6.0_22]
at java.lang.ProcessImpl.start(ProcessImpl.java:91) [:1.6.0_22]
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) [:1.6.0_22]
... 9 more
If I there is no JAVA_HOME I see the following error and more importantly - the server freezes and can not be stopped unlesss I manually kill -9 the process. Same happens on HEAD.
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1
JAVA: java
JAVA_OPTS:
=========================================================================
Cannot run Java in 64 bit mode. Continuing in 32 bit mode.
16:22:08,757 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta11
16:22:09,203 INFO [org.jboss.as.process.Server Manager.status] (main) Starting process 'Server Manager'
[Server Manager] Cannot run Java in 64 bit mode. Continuing in 32 bit mode.
[Server Manager] 16:22:09,589 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta11
[Server Manager] 16:22:10,258 INFO [org.jboss.as.domain.controller] (Thread-3) Starting Domain Controller
[Server Manager] 16:22:10,322 INFO [org.jboss.as.domain.controller] (Thread-3) Parsing Domain Configuration
[Server Manager] 16:22:11,165 INFO [org.jboss.as.server.manager] (Thread-3) Starting server server-three
16:22:11,260 INFO [org.jboss.as.process.Server:server-three.status] (pool-2-thread-2) Starting process 'Server:server-three'
16:22:11,279 ERROR [org.jboss.as.process.Server:server-three.status] (pool-2-thread-2) Failed to start process 'Server:server-three': java.io.IOException: Cannot run program "/Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1/java" (in directory "/Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) [:1.6.0_22]
at org.jboss.as.process.ManagedProcess.doStart(ManagedProcess.java:151)
at org.jboss.as.process.ManagedProcess.start(ManagedProcess.java:129)
at org.jboss.as.process.ProcessManager.startProcess(ProcessManager.java:143)
at org.jboss.as.process.ProcessManagerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessManagerServerHandler.java:160)
at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239)
at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method) [:1.6.0_22]
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) [:1.6.0_22]
at java.lang.ProcessImpl.start(ProcessImpl.java:91) [:1.6.0_22]
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) [:1.6.0_22]
... 9 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577759#577759]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
[View Less]
14 years, 2 months