[Installation, Configuration & DEPLOYMENT] - Deployment error with JBoss 5.0.1 GA
by -christian-
Hi,
because JBoss 5.0 was filling ../server/default/tmp/vfs-nested.tmp with gigabytes of files, I upgraded to 5.0.1 GA. I'am using Eclipse 3.4.1 (WTP) and with JBoss 5.0 everything worked fine, but after changing to 5.0.1 deployment does not work. I'm quite new to JEE/JBoss so I don't really know what's wrong.
Regards,
Christian
| 14:58:21,046 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
| 14:58:21,468 INFO [JBossASKernel] Created KernelDeployment for: PCareEJB.jar
| 14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3
| 14:58:21,468 INFO [JBossASKernel] with dependencies:
| 14:58:21,468 INFO [JBossASKernel] and demands:
| 14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
| 14:58:21,468 INFO [JBossASKernel] and supplies:
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/ClinicService/remote
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/ClinicService/remote-de.pcare.clinic.ClinicServiceRemote
| 14:58:21,468 INFO [JBossASKernel] Class:de.pcare.clinic.ClinicServiceRemote
| 14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3) to KernelDeployment of: PCareEJB.jar
| 14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3
| 14:58:21,468 INFO [JBossASKernel] with dependencies:
| 14:58:21,468 INFO [JBossASKernel] and demands:
| 14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
| 14:58:21,468 INFO [JBossASKernel] and supplies:
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote-de.pcare.department.DepartmentServiceRemote
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote
| 14:58:21,468 INFO [JBossASKernel] Class:de.pcare.department.DepartmentServiceRemote
| 14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3) to KernelDeployment of: PCareEJB.jar
| 14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3
| 14:58:21,468 INFO [JBossASKernel] with dependencies:
| 14:58:21,468 INFO [JBossASKernel] and demands:
| 14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
| 14:58:21,468 INFO [JBossASKernel] and supplies:
| 14:58:21,468 INFO [JBossASKernel] Class:de.pcare.employee.EmployeeServiceRemote
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote
| 14:58:21,468 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote-de.pcare.employee.EmployeeServiceRemote
| 14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3) to KernelDeployment of: PCareEJB.jar
| 14:58:21,875 INFO [TomcatDeployment] deploy, ctxPath=/PCareWeb
| 14:58:22,109 INFO [XmlConfigurationProvider] Parsing configuration file [struts-default.xml]
| 14:58:22,765 INFO [XmlConfigurationProvider] Unable to locate configuration files of the name struts-plugin.xml, skipping
| 14:58:22,765 INFO [XmlConfigurationProvider] Parsing configuration file [struts-plugin.xml]
| 14:58:22,953 INFO [XmlConfigurationProvider] Parsing configuration file [struts.xml]
| 14:58:22,953 INFO [BeanSelectionProvider] Loading global messages from global-messages
| 14:58:23,296 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3" is missing the following dependencies:
| Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
| Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3" is missing the following dependencies:
| Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
| Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3" is missing the following dependencies:
| Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
| Deployment "persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB" is missing the following dependencies:
| Dependency "jboss.jca:name=PCareDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
| Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
| Deployment "jboss.jca:name=PCareDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **
| Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
|
| 14:58:23,296 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
| 14:58:23,343 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
| 14:58:23,359 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 26s:141ms
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216974#4216974
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216974
17 years, 1 month
[JBoss Cache: Core Edition] - Re: Unable To Acquire Lock
by nathanmesser
Have you tried turning on the following log4j logging to see what's happening with the transactions?
org.jboss.cache.interceptors.TxInterceptor=TRACE
(in our properties file that turns into
log4j.logger.org.jboss.cache.interceptors.TxInterceptor=TRACE, JBossAppender)
3.0.2 did have a bug that under certain circumstances the transaction could be rolled back, but not all the locks removed, which would lead to this problem. This was fixed in 3.0.3.
However it could be as simple as GlobalTransaction::4 has modified the node, and hasn't committed yet. Looking at the TxInterceptor logs should tell you when the transaction commits or rolls back.
-Note: I'm not connected with JBossCache development, just a user, and I haven't used JBossCache with Hibernate.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216971#4216971
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216971
17 years, 1 month
[EJB 3.0] - Re: removalTimeoutInSeconds & subsequent removal?
by Protuhj
Ok -- I am getting frustrated over this, I have marked my remove function with @Remove and @PreDestroy and @PrePassivate, idleTimeoutSeconds is 5, removalTimeoutSeconds is 10, my members are transient.
It first times out and passivates, and calls remove on the Proper SFSB. It then tries to remove the bean using @PreDestroy 5 seconds later. When I redeploy my EJB to the app server, it calls my destroy method AGAIN, like it wasn't destroyed properly in the first place.
If I don't have @PrePassivate, it will call my destroy method via the @PreDestroy annotation I guess, but since it was passivated, it is not the correct instance of the bean so it doesn't close the socket. Then when I redeploy the EJB it calls the my remove function on the proper bean. This doesn't seem to be working like it should.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216952#4216952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216952
17 years, 1 month
