[Beginner's Corner] - Running code after jboss started
by Alessandro Gelormini
Alessandro Gelormini [https://community.jboss.org/people/superalex] created the discussion
"Running code after jboss started"
To view the discussion, visit: https://community.jboss.org/message/736629#736629
--------------------------------------------------------------
hi I have this problem...where I work there is an ear server application runs into jboss 4.2.3 24/7 serving an operations center with some clients which ask for some stuff...now this clients can schedule some reminders on the server which save the details on db and starts some java Timers...these reminders can stay active theoretically forever...the problem is: sometimes jboss has to be restarted after the implementations of new functionalities and clearly the timers are lost...so, through the db information I can reconstruct the state before the server was shutted down; but I want this operation to be performed automatically after the server has been restarted...jboss should read the active timer from db, restart them in the right way and let them available for manipulation from the client (deleting,modifying,ecc)...how can I get this??? Be aware that I cant upgrade the server and use ejb 3.1 functionalities like @Startup and @PostConstruct...
thanks in advance
Alex
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/736629#736629]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 10 months
[JBoss Microcontainer] - Overriding server libs in an EJB inside an EAR - 5.1.0.GA
by Rodrigo Uchoa
Rodrigo Uchoa [https://community.jboss.org/people/rodrigo.uchoa] created the discussion
"Overriding server libs in an EJB inside an EAR - 5.1.0.GA"
To view the discussion, visit: https://community.jboss.org/message/737773#737773
--------------------------------------------------------------
Hi everyone!
This is something I've been struggling for quite some time. That is, how to change the classloader behavior in an EAR deploy. I've read a lot of posts and docs around the internet, but nothing seems to be exactly my case.
It all started with the need to update Hibernate libs in JBoss 5.1.0.GA (from the bundled 3.2.4 to 3.3.1). Using the jboss-classloading.xml file it worked fine when we use a standalone .WAR deploy with the hibernate libs inside "WEB-INF/lib" directory. When we switched to an .EAR deploy, it stopped working. Our .EAR structure looks like this:
EAR
|
|---- lib //all libs, including hibernate's, are here
|
|---- META-INF
| |---- jboss-classloading.xml
|
|---- EJB_Module //persistence-unit defined here, along with EJB business classes
|
|---- WAR_Module
|---- WEB-INF
|---- jboss-classloading.xml
The EAR jboss-classloading.xml:
<classloading xmlns="urn:jboss:classloading:1.0"
domain="app.ear"
export-all="NON_EMPTY"
import-all="true"
parent-first="false">
</classloading>
The WAR's jboss-classloading.xml:
<classloading xmlns="urn:jboss:classloading:1.0"
domain="app.war"
parent-domain="app.ear"
export-all="NON_EMPTY"
import-all="true">
</classloading>
Now to the problem... Let's suppose I have two different .EAR projects with the exact same structure described above. When I deploy both of them to the same JBoss AS instance, one of them always have classloading issues with the hibernate libs when server is starting up. More specifically, we get "ClassCastException" with a hibernate interceptor we have:
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: sinpi-pu] Interceptor class does not implement Interceptor interface: br.gov.dpf.sinpi.core.util.HistoricoInterceptor
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:811)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:191)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:253)
at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:125)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at org.jboss.seam.persistence.EntityManagerFactory.createEntityManagerFactory(EntityManagerFactory.java:85)
at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144)
at org.jboss.seam.Component.callComponentMethod(Component.java:2283)
at org.jboss.seam.Component.callCreateMethod(Component.java:2198)
at org.jboss.seam.Component.newInstance(Component.java:2158)
... 75 more
Caused by: java.lang.ClassCastException: br.gov.dpf.sinpi.core.util.HistoricoInterceptor
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:793)
My assumption is that different "org.hibernate.Interceptor" classes loaded by different classloaders are causing this mess. This problem only occurs when we deploy two EAR's at the same time. I even tried to change the "ear-deployer-jboss-beans.xml" isolated configuration, but it didn't work. What I need is that both EAR's use the newer hibernate libs bundled inside each "ear/lib" directory.
Any ideas would be appreciated.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/737773#737773]
Start a new discussion in JBoss Microcontainer at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 10 months
[jBPM] - Issue with BPMN2.0 Editor
by Bhaskaran Venkataraman
Bhaskaran Venkataraman [https://community.jboss.org/people/bhaskarven] created the discussion
"Issue with BPMN2.0 Editor"
To view the discussion, visit: https://community.jboss.org/message/737610#737610
--------------------------------------------------------------
I was trying to run some tutorial by creating the process model in BPMN2.0 editor. I am facing the following issues :
1. I tried modifying an existing bpmn file according to my requirement. The moment I saved the changes there is a pop-up
saying "The user operation is waiting for building workspace". Then when I run the program I get a bunch of schema errors
which I have reproduced below. I am not able to make even a minor change such as moving a node or editing a property
of a node. I tried creating a new BPMN diagram and that is also does not work. But I am able to compile and run demo
programs.
(null: 8, 96): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 17, 79): src-resolve: Cannot resolve the name 'bpmndi:BPMNDiagram' to a(n) 'element declaration' component.
(null: 22, 52): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 22, 52): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmndi:BPMNDiagram'. One of '{" http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg.org/spec/BPMN/20100524/MODEL":rootElement, " http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg.org/spec/BPMN/20100524/MODEL":relationship}' is expected.
(null: 23, 92): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 24, 54): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 25, 67): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 27, 54): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 28, 66): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 30, 54): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 31, 67): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 33, 123): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 34, 61): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 34, 61): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 34, 61): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 35, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 35, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 35, 62): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 37, 123): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 38, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 38, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 38, 62): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 39, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 39, 62): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 39, 62): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
Hello World
2. The properties panel for the script task is somewhat different from what it is in the tutorial. The Action property is missing and hence I cannot
open the "Action Editor" for writing custom java code or importing Jar files. Also some other properties such as "variables" are missing in the
process properties panel.
I installed the graphiti & BPMN editor plug-in as described in the User Guide. The only change being the one shown below due to
compatibility issues.
As per User Guide => Graphiti 0.7.1 and Codehoop (BPMN) => 2.0
My installation => Graphiti 0.8.0 and Codehoop (BPMN) => 2.0
Please find attached snapshots of the script node properties panel and the process properties panel
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/737610#737610]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 10 months
[jBPM] - jbpm 5.3 - groups
by Chris Melas
Chris Melas [https://community.jboss.org/people/melc] created the discussion
"jbpm 5.3 - groups"
To view the discussion, visit: https://community.jboss.org/message/738279#738279
--------------------------------------------------------------
Hello,
I've noticed in 3 different computer systems (centos, win xp, win vista) that when creating a process with a human task that only has a groupId specified (i.e. https://community.jboss.org/servlet/JiveServlet/showImage/2-738279-18646/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-738279-18... ), the following exception is thrown when reaching the point of the human task.
*6:01:28,031 ERROR [stderr] (Thread-13) java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [userId]*
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:206)
*16:01:28,031 ERROR [stderr] (Thread-13) at org.jbpm.task.service.TaskServiceSession.getTasksAssignedAsPotentialOwnerByStatusByGroup(TaskServiceSession.java:1011)*
16:01:28,031 ERROR [stderr] (Thread-13) at org.jbpm.task.service.TaskServerHandler.messageReceived(TaskServerHandler.java:356)
16:01:28,031 ERROR [stderr] (Thread-13) at org.jbpm.task.service.hornetq.HornetQTaskServerHandler.messageReceived(HornetQTaskServerHandler.java:44)
16:01:28,031 ERROR [stderr] (Thread-13) at org.jbpm.task.service.hornetq.BaseHornetQTaskServer.run(BaseHornetQTaskServer.java:85)
16:01:28,031 ERROR [stderr] (Thread-13) at java.lang.Thread.run(Thread.java:662)
16:01:28,031 ERROR [stderr] (Thread-13) Caused by: org.hibernate.QueryParameterException: could not locate named parameter [userId]
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.engine.query.ParameterMetadata.getNamedParameterDescriptor(ParameterMetadata.java:99)
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.engine.query.ParameterMetadata.getNamedParameterExpectedType(ParameterMetadata.java:105)
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:437)
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:407)
16:01:28,031 ERROR [stderr] (Thread-13) at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:201)
16:01:28,031 ERROR [stderr] (Thread-13) ... 5 more
16:01:28,031 ERROR [stderr] (Thread-33) Exception in thread "Thread-33" java.lang.RuntimeException: Client Exception with class class org.jbpm.task.service.hornetq.HornetQTaskClientConnector$1 using port 5445
16:01:28,046 ERROR [stderr] (Thread-33) at org.jbpm.task.service.hornetq.HornetQTaskClientConnector$1.run(HornetQTaskClientConnector.java:134)
16:01:28,046 ERROR [stderr] (Thread-33) at java.lang.Thread.run(Thread.java:662)
16:01:28,046 ERROR [stderr] (Thread-33) Caused by: java.lang.NullPointerException
16:01:28,046 ERROR [stderr] (Thread-33) at org.jbpm.task.service.TaskClientHandler.messageReceived(TaskClientHandler.java:62)
16:01:28,046 ERROR [stderr] (Thread-33) at org.jbpm.task.service.hornetq.HornetQTaskClientHandler.messageReceived(HornetQTaskClientHandler.java:56)
16:01:28,046 ERROR [stderr] (Thread-33) at org.jbpm.task.service.hornetq.HornetQTaskClientConnector$1.run(HornetQTaskClientConnector.java:120)
16:01:28,046 ERROR [stderr] (Thread-33) ... 1 more
16:01:48,031 ERROR [stderr] (http-localhost-127.0.0.1-8080-3) java.lang.RuntimeException: Timeout : unable to retrieve results
16:01:48,031 ERROR [stderr] (http-localhost-127.0.0.1-8080-3) at org.jbpm.task.service.responsehandlers.BlockingTaskSummaryResponseHandler.getResults(BlockingTaskSummaryResponseHandler.java:41)
16:01:48,031 ERROR [stderr] (http-localhost-127.0.0.1-8080-3) at
...............
...............
By checking out the code of *org.jbpm.task.service.**TaskServiceSession* at line *1011* a named query is called as follows,
Query query = tpm.createQuery("TasksAssignedAsPotentialOwnerByStatusByGroup")
.setParameter("userId", userId)
.setParameter("groupIds", groupIds)
.setParameter("language", language)
.setParameter("status", status);
However as seen in Taskorm.xml inside jbpm-human-task-core-5.3.0.Final.jar/META-INF, indeed the named query has no userId parameter
+<named-query name="TasksAssignedAsPotentialOwnerByStatusByGroup">+
+ <query>+
+select+
+ new org.jbpm.task.query.TaskSummary(+
+ t.id,+
+ t.taskData.processInstanceId,+
+ name.text,+
+ subject.text,+
+ description.text,+
+ t.taskData.status,+
+ t.priority,+
+ t.taskData.skipable,+
+ t.taskData.actualOwner,+
+ t.taskData.createdBy,+
+ t.taskData.createdOn,+
+ t.taskData.activationTime,+
+ t.taskData.expirationTime,+
+ t.taskData.processId,+
+ t.taskData.processSessionId)+
+from+
+ Task t+
+ left join t.taskData.createdBy+
+ left join t.taskData.actualOwner+
+ left join t.subjects as subject+
+ left join t.descriptions as description+
+ left join t.names as name,+
+ OrganizationalEntity potentialOwners+
+where+
+ t.archived = 0 and+
+ potentialOwners.id = :groupId and+
+ potentialOwners in elements ( t.peopleAssignments.potentialOwners ) and+
+ (+
+ name.language = :language+
+ or t.names.size = 0+
+ ) and+
+ (+
+ subject.language = :language+
+ or t.subjects.size = 0+
+ ) and+
+ (+
+ description.language = :language+
+ or t.descriptions.size = 0+
+ ) and+
+ t.taskData.status in (:status) and+
+ t.taskData.expirationTime is null+
+ </query>+
+ <!-- hint name="org.hibernate.timeout" value="200"/ -->+
+ </named-query>+
Is this the case or am i missing something??
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/738279#738279]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 10 months
