[JBoss JIRA] Created: (JBRULES-3107) java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener
by Vinod Kiran Paidimarry (JIRA)
java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener
----------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3107
URL: https://issues.jboss.org/browse/JBRULES-3107
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.Final
Reporter: Vinod Kiran Paidimarry
Assignee: Mark Proctor
java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener
1. KnowledgeBase kbase = readFromAgent();
2. StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
3. KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory.newFileLogger(ksession, "test");
4. ksession.getAgendaEventListeners().size();
5. ksession.fireAllRules();
6. ksession.dispose();
7. logger.close();
Line 3 causes an class cast exception on line 4.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months
[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ]
Jason Greene reopened AS7-4721:
-------------------------------
> CLONE - Jms client can't authenticate to messaging subsystem
> ------------------------------------------------------------
>
> Key: AS7-4721
> URL: https://issues.jboss.org/browse/AS7-4721
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Fix For: 7.1.2.Final (EAP)
>
>
> Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master.
> Exception:
> {code}
> Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin
> at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280)
> at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
> at testjndi.SecurityClient.getConnection(SecurityClient.java:308)
> at testjndi.SecurityClient.initializeClient(SecurityClient.java:83)
> at testjndi.SecurityClient.main(SecurityClient.java:363)
> Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin]
> ... 9 more
> {code}
> Steps to reproduce:
> 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j...
> 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest
> 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration
> 4. Start server
> 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password)
--
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, 12 months
[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated AS7-4721:
------------------------------
Priority: Blocker (was: Major)
> CLONE - Jms client can't authenticate to messaging subsystem
> ------------------------------------------------------------
>
> Key: AS7-4721
> URL: https://issues.jboss.org/browse/AS7-4721
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 7.1.2.Final (EAP)
>
>
> Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master.
> Exception:
> {code}
> Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin
> at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280)
> at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
> at testjndi.SecurityClient.getConnection(SecurityClient.java:308)
> at testjndi.SecurityClient.initializeClient(SecurityClient.java:83)
> at testjndi.SecurityClient.main(SecurityClient.java:363)
> Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin]
> ... 9 more
> {code}
> Steps to reproduce:
> 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j...
> 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest
> 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration
> 4. Start server
> 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password)
--
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, 12 months
[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ]
Jason Greene commented on AS7-4721:
-----------------------------------
The fix for this ffdef62ce9670d6e4d88869efb4203fd9f331ee8 uncovers a race condition in security realms. This is under investigation.
> CLONE - Jms client can't authenticate to messaging subsystem
> ------------------------------------------------------------
>
> Key: AS7-4721
> URL: https://issues.jboss.org/browse/AS7-4721
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 7.1.2.Final (EAP)
>
>
> Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master.
> Exception:
> {code}
> Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin
> at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280)
> at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
> at testjndi.SecurityClient.getConnection(SecurityClient.java:308)
> at testjndi.SecurityClient.initializeClient(SecurityClient.java:83)
> at testjndi.SecurityClient.main(SecurityClient.java:363)
> Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin]
> ... 9 more
> {code}
> Steps to reproduce:
> 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j...
> 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest
> 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration
> 4. Start server
> 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password)
--
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, 12 months
[JBoss JIRA] (JBJPA-36) JBOSS 7.1 doesn't start when adding JPA facet to the Eclipse JSF project
by Veera Marni (JIRA)
Veera Marni created JBJPA-36:
--------------------------------
Summary: JBOSS 7.1 doesn't start when adding JPA facet to the Eclipse JSF project
Key: JBJPA-36
URL: https://issues.jboss.org/browse/JBJPA-36
Project: JBoss JPA
Issue Type: Bug
Environment: Windows 64bit(Windows 7). JBOSS 7.1, ECLIPSE Indigo Service Release 1
Reporter: Veera Marni
Assignee: Carlo de Wolf
I get the following error when adding JPA facet to my JSF project in eclipse.
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
06:55:23,868 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
06:55:25,565 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
06:55:25,777 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting
06:55:31,261 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
06:55:31,261 INFO [org.xnio] XNIO Version 3.0.3.GA
06:55:31,342 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
06:55:31,413 INFO [org.jboss.remoting] JBoss Remoting version 3.2.2.GA
06:55:31,674 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
06:55:31,680 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
06:55:31,706 INFO [org.jboss.as.security] JBAS013101: Activating Security Subsystem
06:55:31,740 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices Extension
06:55:31,816 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
06:55:32,896 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
06:55:33,010 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
06:55:33,124 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
06:55:35,772 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.1.GA
06:55:36,403 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory Q:\IDE\jboss-as-7.1.0.Final\standalone\deployments
06:55:36,420 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment DatabaseMonitoring.war
06:55:36,501 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015002: Deployment of 'JSFQuiz.war' requested, but the deployment is not present
06:55:36,511 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jobApplication.war in deployment directory. To trigger deployment create a file called jobApplication.war.dodeploy
06:55:36,521 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iceFacesJSF-test.war in deployment directory. To trigger deployment create a file called iceFacesJSF-test.war.dodeploy
06:55:36,541 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found DatabaseMonitoring.war in deployment directory. To trigger deployment create a file called DatabaseMonitoring.war.dodeploy
06:55:37,346 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:4447
06:55:37,346 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
06:55:37,489 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
06:55:38,087 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
06:55:38,217 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "iceFacesJSF-test.war"
06:55:38,230 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "jobApplication.war"
06:55:38,231 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "DatabaseMonitoring.war"
06:55:40,377 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
06:55:40,379 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
06:55:40,385 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
06:55:40,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
06:55:40,464 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for iceFacesJSF-test
06:55:42,386 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
06:55:42,395 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
06:55:42,417 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for jobApplication
06:55:44,893 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'iceFacesJSF-test.war#iceFacesJSF-test'
06:55:45,369 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-7) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
06:55:45,384 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-7) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
06:55:46,038 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-7) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/DatabaseMonitoring'
06:55:46,587 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
06:55:46,620 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
06:55:46,629 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
06:55:46,642 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
06:55:47,261 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011402: Starting Persistence Unit Service 'jobApplication.war#jobApplication'
06:55:47,271 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
name: iceFacesJSF-test
...]
06:55:47,277 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-4) HHH000204: Processing PersistenceUnitInfo [
name: jobApplication
...]
06:55:48,040 WARN [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-1) HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
06:55:48,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."iceFacesJSF-test.war#iceFacesJSF-test": org.jboss.msc.service.StartException in service jboss.persistenceunit."iceFacesJSF-test.war#iceFacesJSF-test": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_25]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: iceFacesJSF-test] Unable to build EntityManagerFactory
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
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]
... 3 more
Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set
at org.hibernate.service.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:97)
at org.hibernate.service.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:67)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:176)
at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:71)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2270)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2266)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1735)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
... 9 more
06:55:48,664 WARN [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-4) HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
06:55:48,822 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.persistenceunit."jobApplication.war#jobApplication": org.jboss.msc.service.StartException in service jboss.persistenceunit."jobApplication.war#jobApplication": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_25]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: jobApplication] Unable to build EntityManagerFactory
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
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]
... 3 more
Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set
at org.hibernate.service.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:97)
at org.hibernate.service.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:67)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:176)
at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:71)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2270)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2266)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1735)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
... 9 more
06:55:50,622 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-7) Hibernate Validator 4.2.0.Final
06:55:52,543 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /DatabaseMonitoring
06:55:52,565 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 29933ms - Started 566 of 895 services (252 services failed or missing dependencies, 76 services are passive or on-demand)
06:55:52,773 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jobApplication.war" was rolled back with no failure message
06:55:52,779 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "iceFacesJSF-test.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"iceFacesJSF-test.war#iceFacesJSF-test\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"iceFacesJSF-test.war#iceFacesJSF-test\": Failed to start service"}}
06:55:52,788 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "DatabaseMonitoring.war" was rolled back with no failure message
06:55:53,012 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment iceFacesJSF-test.war in 222ms
06:55:53,014 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment jobApplication.war in 223ms
06:55:53,023 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment DatabaseMonitoring.war in 232ms
06:55:53,030 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.persistenceunit."jobApplication.war#jobApplication": org.jboss.msc.service.StartException in service jboss.persistenceunit."jobApplication.war#jobApplication": Failed to start service
service jboss.persistenceunit."iceFacesJSF-test.war#iceFacesJSF-test": org.jboss.msc.service.StartException in service jboss.persistenceunit."iceFacesJSF-test.war#iceFacesJSF-test": Failed to start service
06:55:53,045 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
06:55:53,054 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"iceFacesJSF-test.war#iceFacesJSF-test\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"iceFacesJSF-test.war#iceFacesJSF-test\": Failed to start service"}}}}
06:55:53,070 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
--
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, 12 months
[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ]
Jason Greene resolved AS7-4721.
-------------------------------
Fix Version/s: 7.1.2.Final (EAP)
(was: No Release)
Resolution: Done
> CLONE - Jms client can't authenticate to messaging subsystem
> ------------------------------------------------------------
>
> Key: AS7-4721
> URL: https://issues.jboss.org/browse/AS7-4721
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Fix For: 7.1.2.Final (EAP)
>
>
> Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master.
> Exception:
> {code}
> Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin
> at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280)
> at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
> at testjndi.SecurityClient.getConnection(SecurityClient.java:308)
> at testjndi.SecurityClient.initializeClient(SecurityClient.java:83)
> at testjndi.SecurityClient.main(SecurityClient.java:363)
> Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin]
> ... 9 more
> {code}
> Steps to reproduce:
> 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j...
> 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest
> 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration
> 4. Start server
> 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password)
--
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, 12 months
[JBoss JIRA] (AS7-4733) ServiceVerificationHandler does not record failure if service missing dependencies has no immediateUnavailableDependencies
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4733:
-------------------------------------
Summary: ServiceVerificationHandler does not record failure if service missing dependencies has no immediateUnavailableDependencies
Key: AS7-4733
URL: https://issues.jboss.org/browse/AS7-4733
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.2.Final (EAP)
ServiceVerificationHandler will put an OperationContext into rollback only mode if any services it is tracking are failed or are missing dependencies. But, if none are failed, and none have *immediate* unavailable dependencies (ServiceController.getImmediateUnavailableDependencies()) then the context failure description is not set. This combination of rollback-only preventing op completion and no error message causes the OperationContext to treat the op as if context.completeStep() was not called, failing with JBAS014750: Operation handler failed to complete
We need a failure description for this case, even though we don't know what services were missing.
For 7.2 we should also look into how OperationContext treats this situation; i.e. avoid having the presence or absence of a failure description as part of the detection on completeStep() not being called.
--
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, 12 months
[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem
by Justin Bertram (JIRA)
[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ]
Justin Bertram reassigned AS7-4721:
-----------------------------------
Assignee: Jason Greene (was: Justin Bertram)
> CLONE - Jms client can't authenticate to messaging subsystem
> ------------------------------------------------------------
>
> Key: AS7-4721
> URL: https://issues.jboss.org/browse/AS7-4721
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Fix For: No Release
>
>
> Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master.
> Exception:
> {code}
> Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin
> at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781)
> at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280)
> at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
> at testjndi.SecurityClient.getConnection(SecurityClient.java:308)
> at testjndi.SecurityClient.initializeClient(SecurityClient.java:83)
> at testjndi.SecurityClient.main(SecurityClient.java:363)
> Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin]
> ... 9 more
> {code}
> Steps to reproduce:
> 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j...
> 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest
> 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration
> 4. Start server
> 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password)
--
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, 12 months