error when deploying an EJB

Latest response

Hi,

I am trying to deploy an EJB and I amgetting following error, can please somebody help me in this regard ??

17:43:43,390 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named NearestService in deployment unit deployment "NearestService.jar" are as follows:

java:global/NearestService/NearestService!com.aviva.ukhe.service.nearest.NearestService
java:app/NearestService/NearestService!com.aviva.ukhe.service.nearest.NearestService
java:module/NearestService!com.aviva.ukhe.service.nearest.NearestService
java:jboss/exported/NearestService/NearestService!com.aviva.ukhe.service.nearest.NearestService

17:43:43,406 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Server is now live
17:43:43,406 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) HornetQ Server version 2.2.19.SNAPSHOT (HQ_2_2_23_Final, 122) [da84cc12-213b-11e3-b635-0764c307630a]) started
17:43:43,421 INFO [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011907: Register module: Module "deployment.IncentivesLookupService.jar:main" from Service Module Loader
17:43:43,437 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
17:43:43,437 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
17:43:43,468 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 63) trying to deploy queue jms.queue.ukhe.pmi.ecol.apply
17:43:43,468 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/queue/ukhe.pmi.ecol.apply
17:43:43,484 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011907: Register module: Module "deployment.ecol-persistence.jar:main" from Service Module Loader
17:43:43,499 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 66) JBAS011402: Starting Persistence Unit Service 'ecol-persistence.jar#ecolPersistenceUnit'
17:43:43,515 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (ServerService Thread Pool -- 65) trying to deploy queue jms.queue.ukhe.pmi.ecol.fail
17:43:43,515 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/queue/ukhe.pmi.ecol.fail
17:43:43,515 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
17:43:43,608 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-2) Add Service
id=NearestService
address=http://localhost:8080/NearestService/NearestServiceImpl
implementor=com.aviva.ukhe.service.nearest.impl.NearestServiceImpl
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://impl.nearest.service.ukhe.aviva.com/}NearestServiceImplService
portName={http://impl.nearest.service.ukhe.aviva.com/}NearestServiceImplPort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."NearestService.jar".component.NearestService.VIEW."com.aviva.ukhe.service.nearest.impl.NearestServiceImpl".SERVICE_ENDPOINT]
17:43:43,655 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 66) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2}
17:43:43,671 INFO [org.hibernate.Version] (ServerService Thread Pool -- 66) HHH000412: Hibernate Core {4.1.6.Final-redhat-3}
17:43:43,671 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 66) HHH000206: hibernate.properties not found
17:43:43,671 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 66) HHH000021: Bytecode provider name : javassist
17:43:43,686 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 66) HHH000204: Processing PersistenceUnitInfo [
name: ecolPersistenceUnit
...]
17:43:43,874 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 66) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
17:43:43,889 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://impl.nearest.service.ukhe.aviva.com/}NearestServiceImplService from class com.aviva.ukhe.service.nearest.impl.NearestServiceImpl
17:43:43,983 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-6) HornetQ resource adaptor started
17:43:43,983 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
17:43:43,983 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
17:43:43,998 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) JBAS014105: ActivationConfigProperty dLQUser will be ignored since it is not allowed by resource adapter: hornetq-ra
17:43:43,998 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) JBAS014105: ActivationConfigProperty dLQPassword will be ignored since it is not allowed by resource adapter: hornetq-ra
17:43:44,014 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) JBAS014142: Started message driven bean 'ECOLSubmitApp' with 'hornetq-ra' resource adapter
17:43:44,404 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 66) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect
17:43:44,404 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ServerService Thread Pool -- 66) exception trying to create exception sorter (disabling):: java.lang.Exception: Unable to load: org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.loadPlugin(BaseWrapperManagedConnectionFactory.java:1027)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isExceptionFatal(BaseWrapperManagedConnectionFactory.java:1061)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.connectionError(BaseWrapperManagedConnection.java:578)
at org.jboss.jca.adapters.jdbc.WrappedConnection.checkException(WrappedConnection.java:1635)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createClob(WrappedConnection.java:1262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_11]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_11]
at org.hibernate.engine.jdbc.internal.LobCreatorBuilder.useContextualLobCreation(LobCreatorBuilder.java:109) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.engine.jdbc.internal.LobCreatorBuilder.(LobCreatorBuilder.java:61) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:157) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:73) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2279) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2275) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1744) [hibernate-core-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.ejb.EntityManagerFactoryImpl.(EntityManagerFactoryImpl.java:94) [hibernate-entitymanager-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905) [hibernate-entitymanager-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890) [hibernate-entitymanager-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) [hibernate-entitymanager-4.1.6.Final-redhat-3.jar:4.1.6.Final-redhat-3]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:197) [jboss-as-jpa-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$500(PersistenceUnitServiceImpl.java:57) [jboss-as-jpa-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:96) [jboss-as-jpa-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_11]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_11]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)

My Jboss-web.xml is like this ---------------------


"http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">

ecol

<resource-ref>
    <res-ref-name>jms/ConnectionFactory
    </res-ref-name>
    <!-- non HA -->
    <!-- <jndi-name>java:/ConnectionFactory</jndi-name> -->

    <!--
        Use the JMS Resource Adapter, let it deal with knowing where the JMS
        server is
    -->
    <jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>


<resource-ref>
    <res-ref-name>jms/QueueEcolApplication</res-ref-name>

    <!-- non HA -->
    <!-- <jndi-name>java:/queue/ecolApplication</jndi-name> -->

    <!-- Use HA-JNDI so we can find the queue on any node -->
    <jndi-name>java:/queue/ukhe.pmi.ecol.apply
    </jndi-name>
</resource-ref>


<resource-ref>
    <res-ref-name>jms/QueueDLQ</res-ref-name>

    <!-- non HA -->
    <!-- <jndi-name>java:/queue/DLQ</jndi-name> -->

    <!-- Use HA-JNDI so we can find the queue on any node -->
    <jndi-name>java:/queue/ukhe.pmi.ecol.fail
    </jndi-name>
</resource-ref>    

Responses

Hi Abhishek.

You'll need to open a support case so we can analyse and help you with this issue.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.