[JBoss JIRA] Created: (JBRULES-3163) Drools does not work with Java7
by Andreas Pieber (JIRA)
Drools does not work with Java7
-------------------------------
Key: JBRULES-3163
URL: https://issues.jboss.org/browse/JBRULES-3163
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.2.0.Final, 5.1.1.FINAL
Reporter: Andreas Pieber
Assignee: Mark Proctor
Fix For: 5.2.1.Final, 5.3.0.Beta1
While there are various places where 1.7 for java source version is already used it seams that there are some places where it simply had been forgotten.
It would be very great if that pull request could make it into a very soon 5.2.1.FINAL release since java7 is released now.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5164) ModuleNotFoundException with OSGi sub deployment
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5164:
-----------------------------------
Summary: ModuleNotFoundException with OSGi sub deployment
Key: AS7-5164
URL: https://issues.jboss.org/browse/AS7-5164
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
{code}
complex.ear
+ complex.war
+ complex-cdi.jar
+ visa-bundle.jar
+ paypal-bundle.jar
{code}
* visa-bundle gets resolved
* complex-cdi bundle gets resolved with a wire to visa-bundle
* complex-cdi gets a dependency added to visa-bundle
* complex-cdi module cannot load
{code}
13:50:40,080 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-3) Resolve: [HostBundleRevision[complex-cdi.jar:0.0.0]], []
13:50:40,082 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-3) Resolution result: 1
13:50:40,082 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-3) HostBundleRevision[complex-cdi.jar:0.0.0]: 2 wires
13:50:40,082 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-3) XPackageRequirement[atts={osgi.wiring.package=org.jboss.as.test.smoke.osgi.bundleB},[complex-cdi.jar:0.0.0]] -> [HostBundleRevision[visa-bundle.jar:0.0.0]]
13:50:40,082 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-3) XPackageRequirement[atts={osgi.wiring.package=javax.annotation},[complex-cdi.jar:0.0.0]] -> [SystemBundleRevision[system.bundle:0.0.0]]
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) Adding integration dependencies: 34
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.ejb-client:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.iiop-client:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.as.ejb3:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on javax.resource.api:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on javaee.api:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.hibernate.validator:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.invocation:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.as.ee:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on javax.persistence.api:main
13:50:40,083 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.javassist:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.weld.core:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.weld.api:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.weld.spi:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.as.weld:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.ws.api:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.ws.spi:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.picketbox:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.as.security:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on javax.xml.bind.api:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on sun.jdk:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on ibm.jdk:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on javax.api:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.logging:main
13:50:40,084 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.vfs:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.apache.commons.logging:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.apache.log4j:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.slf4j:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.logging.jul-to-slf4j-stub:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.osgi.core:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on org.jboss.osgi.resolver:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on deployment.complex.ear:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on deployment.complex.ear.paypal-bundle.jar:main
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) -dependency on deployment.complex.ear.visa-bundle.jar:main (skipped)
13:50:40,085 DEBUG [org.jboss.as.osgi] (MSC service thread 1-3) +dependency on deployment.complex.ear.complex-cdi.jar:main
13:50:40,086 DEBUG [org.jboss.modules] (MSC service thread 1-3) Module deployment.complex.ear.complex-cdi.jar:main defined by Service Module Loader
13:50:40,088 DEBUG [org.jboss.modules] (MSC service thread 1-3) Module deployment.complex.ear:main defined by Service Module Loader
13:50:40,088 DEBUG [org.jboss.as.server.moduleservice] (MSC service thread 1-3) Could not load module 'deployment.complex.ear.paypal-bundle.jar:main' as corresponding module spec service 'deployment.complex.ear.paypal-bundle.jar:main' was not found
13:50:40,093 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) Resolve: [HostBundleRevision[paypal-bundle.jar:0.0.0]], []
13:50:40,097 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) Resolution result: 1
13:50:40,097 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) HostBundleRevision[paypal-bundle.jar:0.0.0]: 2 wires
13:50:40,097 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) XPackageRequirement[atts={osgi.wiring.package=org.jboss.as.test.smoke.osgi.bundleB},[paypal-bundle.jar:0.0.0]] -> [HostBundleRevision[visa-bundle.jar:0.0.0]]
13:50:40,097 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-4) XPackageRequirement[atts={osgi.wiring.package=org.osgi.framework},[paypal-bundle.jar:0.0.0]] -> [SystemBundleRevision[system.bundle:0.0.0]]
13:50:40,099 DEBUG [org.jboss.modules] (MSC service thread 1-4) Module deployment.complex.ear.paypal-bundle.jar:main defined by Service Module Loader
13:50:40,100 DEBUG [org.jboss.modules] (MSC service thread 1-1) Module deployment.complex.ear.complex.war:main defined by Service Module Loader
13:50:40,094 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."complex.ear"."complex-cdi.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."complex.ear"."complex-cdi.jar".CONFIGURE_MODULE: JBAS018733: Failed to process phase CONFIGURE_MODULE of subdeployment "complex-cdi.jar" of deployment "complex.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.complex.ear.complex-cdi.jar:main
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:324)
at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:259)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:153)
at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:82)
at org.jboss.as.osgi.deployment.BundleResolveSubProcessor.deploy(BundleResolveSubProcessor.java:59)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
Caused by: org.jboss.modules.ModuleNotFoundException: deployment.complex.ear.paypal-bundle.jar:main
at org.jboss.modules.Module.addPaths(Module.java:864)
at org.jboss.modules.Module.link(Module.java:1206)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1235)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
at org.jboss.osgi.framework.internal.ModuleManagerPlugin.loadModule(ModuleManagerPlugin.java:595)
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:321)
... 10 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5162) "java.lang.IllegalStateException: Parameters processing failed"
by Mustafa Musaji (JIRA)
Mustafa Musaji created AS7-5162:
-----------------------------------
Summary: "java.lang.IllegalStateException: Parameters processing failed"
Key: AS7-5162
URL: https://issues.jboss.org/browse/AS7-5162
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
Environment: Windows 7 Enterprise Service Pack 1, JDK-1.7.0_05, jboss-as-7.1.1.Final/jboss-eap-6.0.0(Evaluation)
Reporter: Mustafa Musaji
Application throws an exception for IE browser only with "JBoss-as-7.1.1.Final" & "JBoss-eap-6.0.0(Evaluation version)" only, but it is working correctly for Firefox browser.
Note : It is working fine with "jboss-as-7.1.0.Final" version for all browsers.
Exception details :
Unhandled Exception / Error:
Internal Error (757457307) at :: Exception (Parameters processing failed.)
java.lang.IllegalStateException: Parameters processing failed.
at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:407)
at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:229)
at org.apache.catalina.connector.Request.parseParameters(Request.java:2874)
at org.apache.catalina.connector.Request.getParameterNames(Request.java:1333)
at org.apache.catalina.connector.RequestFacade.getParameterNames(RequestFacade.java:379).........................
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-3080) Infinispan CacheManager not available in JNDI at JPA subsystem startup
by Brent Douglas (Created) (JIRA)
Infinispan CacheManager not available in JNDI at JPA subsystem startup
----------------------------------------------------------------------
Key: AS7-3080
URL: https://issues.jboss.org/browse/AS7-3080
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.0.CR1
Reporter: Brent Douglas
Assignee: Scott Marlow
CacheManager is not available in JNDI at JPA subsystem startup. Seems likely to be related to AS7-1656.
Relevant section of startup logs:
10:56:41,036 INFO [org.hibernate.transaction.TransactionFactoryFactory] (MSC service thread 1-1) Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
10:56:41,036 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (MSC service thread 1-1) instantiating TransactionManagerLookup: org.jboss.as.jpa.hibernate3.JBossAppServerJtaPlatform
10:56:41,036 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (MSC service thread 1-1) instantiated TransactionManagerLookup
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Automatic flush during beforeCompletion(): disabled
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Automatic session close at end of transaction: disabled
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) JDBC batch size: 15
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) JDBC batch updates for versioned data: disabled
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Scrollable result sets: enabled
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) JDBC3 getGeneratedKeys(): enabled
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Connection release mode: auto
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Maximum outer join fetch depth: 3
10:56:41,036 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Default batch fetch size: 8
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Generate SQL with comments: disabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Order SQL updates by primary key: disabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Order SQL inserts for batching: disabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
10:56:41,037 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] (MSC service thread 1-1) Using ASTQueryTranslatorFactory
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Query language substitutions: {}
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) JPA-QL strict compliance: enabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Second-level cache: enabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Query cache: enabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Cache region factory : org.hibernate.cache.infinispan.JndiInfinispanRegionFactory
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Optimize cache for minimal puts: enabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Cache region prefix: pluto-resources.ear#PlutoMainPU
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Structured second-level cache entries: enabled
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Query cache factory: org.hibernate.cache.StandardQueryCacheFactory
10:56:41,037 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Statistics: disabled
10:56:41,038 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Deleted entity synthetic identifier rollback: disabled
10:56:41,038 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Default entity-mode: pojo
10:56:41,038 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Named query checking : enabled
10:56:41,038 INFO [org.hibernate.cfg.SettingsFactory] (MSC service thread 1-1) Check Nullability in Core (should be disabled when Bean Validation is on): disabled
10:56:41,285 INFO [org.hibernate.impl.SessionFactoryImpl] (MSC service thread 1-1) building session factory
10:56:41,285 INFO [org.hibernate.type.BasicTypeRegistry] (MSC service thread 1-1) Type registration [materialized_blob] overrides previous : org.hibernate.type.MaterializedBlobType@4863d8a7
10:56:41,286 INFO [org.hibernate.cache.infinispan.JndiInfinispanRegionFactory] (MSC service thread 1-1) Unable to retrieve CacheManager from JNDI [java:jboss/infinispan/hibernate]: javax.naming.NameNotFoundException: Error looking up infinispan/hibernate, service service jboss.naming.context.java.jboss.infinispan.hibernate is not started
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:121) [jboss-as-naming-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) [jboss-as-naming-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) [jboss-as-naming-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:97) [jboss-as-naming-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213) [jboss-as-naming-7.1.0.CR1-SNAPSHOT.jar:]
at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26]
at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.locateCacheManager(JndiInfinispanRegionFactory.java:75) [hibernate-infinispan-3.6.7.Final.jar:]
at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.createCacheManager(JndiInfinispanRegionFactory.java:68) [hibernate-infinispan-3.6.7.Final.jar:]
at org.hibernate.cache.infinispan.InfinispanRegionFactory.start(InfinispanRegionFactory.java:256) [hibernate-infinispan-3.6.7.Final.jar:]
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:238) [hibernate-core-3.6.7.Final.jar:]
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1872) [hibernate-core-3.6.7.Final.jar:]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:906) [hibernate-entitymanager-3.6.7.Final.jar:]
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) [hibernate-entitymanager-3.6.7.Final.jar:]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:149) [jboss-as-jpa-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:79) [jboss-as-jpa-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
10:56:41,287 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."pluto-resources.ear#PlutoMainPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."pluto-resources.ear#PlutoMainPU": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: PlutoMainPU] Unable to build EntityManagerFactory
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:149)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:79)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
... 3 more
Caused by: org.hibernate.cache.CacheException: Unable to retrieve CacheManager from JNDI [java:jboss/infinispan/hibernate]
at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.locateCacheManager(JndiInfinispanRegionFactory.java:79)
at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.createCacheManager(JndiInfinispanRegionFactory.java:68)
at org.hibernate.cache.infinispan.InfinispanRegionFactory.start(InfinispanRegionFactory.java:256)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:238)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1872)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:906)
... 8 more
10:56:41,507 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Deployment of "pluto-resources.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"pluto-resources.ear#PlutoIdentityPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"pluto-resources.ear#PlutoIdentityPU\": Failed to start service","jboss.persistenceunit.\"pluto-resources.ear#PlutoMainPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"pluto-resources.ear#PlutoMainPU\": Failed to start service"}}
10:56:41,738 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Stopped deployment pluto-interop.jar in 237ms
10:56:41,739 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Stopped deployment pluto-framework.jar in 239ms
10:56:41,741 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Stopped deployment pluto-rest.war in 241ms
10:56:41,773 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Stopped deployment pluto-resources.ear in 273ms
10:56:41,775 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.persistenceunit."pluto-resources.ear#PlutoIdentityPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."pluto-resources.ear#PlutoIdentityPU": Failed to start service
service jboss.persistenceunit."pluto-resources.ear#PlutoMainPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."pluto-resources.ear#PlutoMainPU": Failed to start service
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5064) Dependencies auto-activated from persistence.xml cannot be excluded in jboss-deployment-structure.xml
by Craig Ringer (JIRA)
Craig Ringer created AS7-5064:
---------------------------------
Summary: Dependencies auto-activated from persistence.xml cannot be excluded in jboss-deployment-structure.xml
Key: AS7-5064
URL: https://issues.jboss.org/browse/AS7-5064
Project: Application Server 7
Issue Type: Bug
Components: Class Loading, JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: $ java -version
java version "1.7.0_03-icedtea"
OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 17 (Beefy Miracle)
Release: 17
Codename: BeefyMiracle
$ uname -a
Linux thehostname.localdomain 3.4.2-4.fc17.x86_64 #1 SMP Thu Jun 14 22:22:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Craig Ringer
Assignee: David Lloyd
An a dependency added automatically by AS7 using persistence provider detection cannot be excluded using jboss-deployment-structure.xml . The exclusion takes effect but does so incorrectly, producing a non-functional deployment where the persistence provider module still gets activated (if present) but cannot see its own classes via the deployment's classloader.
If the persistence provider module is not present, the deployment will fail with a missing dependency even when the automatic dependency has been excluded.
This behaviour renders it apparently impossible to package a persistence provider in a deployment's /WEB-INF/lib/ directory. If you want to do automated integration testing (say, with Arquillian) that makes it pretty impractical. Additionally, the half-excluded state is clearly just broken.
DETAIL
------
JBoss's module loader automatically adds dependencies on persistence providers declared in <provider/> entries in deployments' persistence.xml files. That's fine if a module for the provider is installed, but it also adds dependencies on modules that are *not* installed.
The mapping from provider to module is in jpa/core/src/main/java/org/jboss/as/jpa/config/Configuration.java and seems to be used by jpa/core/src/main/java/org/jboss/as/jpa/processor/JPADependencyProcessor.java to add the dependency.
If a jboss-deployment-structure.xml excludes the automatically added dependency, AS7 still tries to load the module and use it. If the module isn't present (as many of the persistence provider modules aren't) this will fail the deployment.
If the module *is* present, the exclusion prevents the module from being visible on the deployment's classpath. If the persistence provider ever tries to access its classes via the classloader context of the depoyment (which it will) this will fail with ClassNotFoundException.
I'll add a test case soon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBRULES-2217) Array Index Out of Bounds in ClassFieldInspector with certain method signatures
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/JBRULES-2217?page=com.atlassian.jira.plug... ]
Mario Fusco resolved JBRULES-2217.
----------------------------------
Fix Version/s: 5.4.0.Final
5.3.1.Final
Resolution: Done
> Array Index Out of Bounds in ClassFieldInspector with certain method signatures
> -------------------------------------------------------------------------------
>
> Key: JBRULES-2217
> URL: https://issues.jboss.org/browse/JBRULES-2217
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.0.1.FINAL
> Environment: JBOSS 4.0.5, Windows Server 2003
> Reporter: Justin Waugh
> Assignee: Mario Fusco
> Fix For: 5.4.0.Final, 5.3.1.Final
>
>
> If a class has a method named setXXX but is not a traditional bean method, (particularly that it does not have a single parameter and returns a value) an ArrayOutOfBoundsException will be thrown during class processing from ClassFieldInspector.storeGetterSetter (line 261). This is because in ClassFieldInspector.processClassWithoutByteCode() it improperly detects the method as being a getter, because it does not filter by method name prefix when trying to process get/is methods, but uses the common method ClassFieldInspector.addToMapping() to handle the method.
> an example problem method name would be:
> public boolean setDefaultValueAndCheckValidity();
> Granted, methods like that might not be ideal programming style, but shouldn't break the processor
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBRULES-2217) Array Index Out of Bounds in ClassFieldInspector with certain method signatures
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/JBRULES-2217?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned JBRULES-2217:
------------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Array Index Out of Bounds in ClassFieldInspector with certain method signatures
> -------------------------------------------------------------------------------
>
> Key: JBRULES-2217
> URL: https://issues.jboss.org/browse/JBRULES-2217
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.0.1.FINAL
> Environment: JBOSS 4.0.5, Windows Server 2003
> Reporter: Justin Waugh
> Assignee: Mario Fusco
>
> If a class has a method named setXXX but is not a traditional bean method, (particularly that it does not have a single parameter and returns a value) an ArrayOutOfBoundsException will be thrown during class processing from ClassFieldInspector.storeGetterSetter (line 261). This is because in ClassFieldInspector.processClassWithoutByteCode() it improperly detects the method as being a getter, because it does not filter by method name prefix when trying to process get/is methods, but uses the common method ClassFieldInspector.addToMapping() to handle the method.
> an example problem method name would be:
> public boolean setDefaultValueAndCheckValidity();
> Granted, methods like that might not be ideal programming style, but shouldn't break the processor
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months