[Installation, Configuration & Deployment] - JBOSS on CentOS - Logging Issue
by onizukanne
We've been running an application on liferay 3.6.1, running in JBoss4 on a Windows server.
On migrating the solution to a CentOS server, it appears to run alright at first. However, after about 30mins, we notice serious logging activity resulting in the log files growing to up to 4GB daily. We change the logger from the DailyRollingAppender to the RollingAppender to cut of at 2MB and the server generates about 8 2MB logfiles every second.
This is very strange, since once the problem starts, even after we undeploy all our ears and the liferay ear from the deploy folder, the logging continues. An extract of the logfile is like so:
anonymous wrote : 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,884 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
| 2006-07-29 02:15:52,885 INFO [STDOUT] ?
Notice how many log lines are written every millisecond?
Any one with a similar experience? Any idea what could be responsible? Your ideas are highly welcome, this is really driving us crazy. This is happening on a life system and consumes lots and lots of system resources, causing us to need to restart the service every hour or so. URGENTLY need a solution.
Many thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961674#3961674
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961674
20 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - EntityManager not working correctly
by andydale
Hi,
I am currently experiencing some problems using the that JBoss 4.0.4GA persistence with postgres 8.1.4. I am having lots of trouble reading Entities back out of the database.
The application works as follows, data is received and a new object (Entity) is created and then persisted from within a stateless session bean. The a message is sent to a Message Driven Bean where the entity is then attempted to be read out of the database (with EntityManager.find()) and this is where the problem is. Most of the time the find() method cannot find the Entity even though it has been persisted (verified persistence by viewing the table in pgAdmin) but now this is where it gets interesting, if you code the EntityManager.find() code as so
<object> = EntityManager.find(<object>.class, Integer.valueof(pk))
null is returned most of the time. But if you code the EntityManager.find() like below:
<object> = EntityManager.find(<object>.class, Integer.valueof(pk))
| if(<object> == null){
| try{
| synchronized(this){
| wait(2000);
| }
| <object> = EntityManager.find(<object>.class, Integer.valueof(pk))
| }
| catch(InterruptedException e){
| e.printStackTrace();
| }
| }
the object is always found on the second call of the find method. Has anybody else experienced this strange behaviour ????
Another few things to note are that if i call the find method directly after persisting the Entity in the stateless session bean then is is always found, and in both beans the EntityManager is injected with the @PersistenceContext using the same persistence unit . Also note that the stateless session bean and the message driven bean are in different archives in a .ear file, would this make a difference ??
Thanks,
Andy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961673#3961673
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961673
20 years, 1 month
[JBoss jBPM] - hibernate.LazyInitializationException with jBPM websale exam
by DerJohannes
Hello,
I get the quoted error when I try to access jBPM taskInstances, like "taskInstance.setVariable" or "jbpmContext.save(taskInstance)".
I know that this is due to a closed Hibernate session. But I don't know why the session is closed and how to control that.
The situation is as follows:
I extended the jBPM Starters Kit websale example; the structure of the jsps and the backing beans is still the same.
First, the user is on home.jsp and sees a list of "latest process instances". When he chooses one, the backing bean "HomeBean.java" runs the method "startProcessInstance" before it returns the navigation string "task" to the JavaServer Faces context. In HomeBean.startProcessInstance everything is working fine. The commands
- long processDefinitionId = JsfHelper.getId("processDefinitionId");
- ProcessDefinition processDefinition = graphSession.loadProcessDefinition(processDefinitionId);
- ProcessInstance processInstance = new ProcessInstance(processDefinition);
- TaskInstance taskInstance = processInstance.getTaskMgmtInstance().createStartTaskInstance();
- jbpmContext.save(processInstance);
- taskBean.initialize(taskInstance);
are executed without problems.
On task.jsp, the process graph is correctly displayed by the tag
<jbpm:processimage task="${taskBean.taskInstanceId}" />
As you can see, everthing is okay up to this point.
But...when I hit "Save & Close" now, the TaskBean.saveAndClose method is called (exactly like in the jBPM Starters Kit websale example). TaskBean.saveAndClose calls TaskBean.save and as soon as this method tries to run the command
- taskInstance.setVariable
- or jbpmContext.save(taskInstance),
I get the following error:
09:42:34,441 ERROR [LazyInitializationException] could not initialize proxy - the owning Session was closed
org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed
at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:56)
at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:98)
at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:133)
at org.jbpm.taskmgmt.exe.TaskInstance$$EnhancerByCGLIB$$1cd1f5d7.getTaskMgmtInstance()
at org.jbpm.JbpmContext.save(JbpmContext.java:297)
Can you please tell me what could be the reason for that? Who told Hibernate to close the session? When? Why? How can I prevent Hibernate from closing the session? How can I reopen it? Or could there be another reason for this error?
I am searching for the cause since two days but haven't found it yet; i'm kind of stuck.
Any help would be appreciated,
Johannes
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961671#3961671
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961671
20 years, 1 month