[JBoss JIRA] Created: (JBRULES-2639) Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
by Edson Tirelli (JIRA)
Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
----------------------------------------------------------------------------------------------------------
Key: JBRULES-2639
URL: https://jira.jboss.org/browse/JBRULES-2639
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 5.1.0.FINAL
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: FUTURE
Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (AS7-1288) NPE in thread "vfs-shutdown"
by Juergen Zimmermann (JIRA)
NPE in thread "vfs-shutdown"
-----------------------------
Key: AS7-1288
URL: https://issues.jboss.org/browse/AS7-1288
Project: Application Server 7
Issue Type: Bug
Components: VFS
Affects Versions: 7.0.0.Final
Environment: 7.1.0.Alpha1 Jenkins build 1402
Reporter: Juergen Zimmermann
Assignee: John Bailey
When I shutdown a standalone server I'm getting a NPE. The shutdown command is:
jboss-admin.bat --connect command=:shutdown
Console log:
...
18:24:55,990 INFO [org.jboss.as.logging] Restored bootstrap log handlers
18:24:55,990 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped
18:24:56,075 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-as-osgi-configadmin:7.1.0.Alpha1-SNAPSHOT
18:24:56,125 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.log:1.0.0
18:24:56,230 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
18:24:56,286 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.configadmin:1.2.8
18:24:56,323 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-osgi-logging:1.0.0
18:24:56,330 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
18:24:56,331 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
18:24:56,368 ERROR [stderr] Exception in thread "vfs-shutdown" java.lang.NullPointerException
18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider$DeleteTask.run(TempFileProvider.java:151)
18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider.close(TempFileProvider.java:132)
18:24:56,368 ERROR [stderr] at org.jboss.osgi.vfs30.VirtualFileAdaptor30$2.run(VirtualFileAdaptor30.java:94)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-2941) Problem deploying grails app
by Idar Borlaug (Created) (JIRA)
Problem deploying grails app
----------------------------
Key: AS7-2941
URL: https://issues.jboss.org/browse/AS7-2941
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Beta1
Environment: Grails 1.3.4
Reporter: Idar Borlaug
Trying to deploy a grails 1.3.4 app on jboss 7.1.0.Beta1
The same app works fine on jboss 4.
12:26:44,722 ERROR [byfjell] (Thread-59) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [byfjell:0.1.0]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429)
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[byfjell:0.1.0]: missing requirement [Module[byfjell:0.1.0]] package; (&(package=javax.servlet)(version>=2.4.0)(!(version>=3.0.0)))
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
--
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
14 years
[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
14 years
[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
14 years
[JBoss JIRA] (AS7-3536) Review the inter-module dependencies directly relating to domain security
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-3536:
-------------------------------------
Summary: Review the inter-module dependencies directly relating to domain security
Key: AS7-3536
URL: https://issues.jboss.org/browse/AS7-3536
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
The domain-management module containing a lot of the Remoting/SASL security services was added after a lot of the other inter-module dependencies had been established, now before the next major phase of development need to review the resulting dependencies and clean up.
Most notably the API/SPI aspect of the security classes should be better separated from the domain operations acting on them - there are numerous places where access to the API is required or other services need to implement an SPI interface but the close coupling of management operations causes cyclic dependency issues.
--
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
14 years