[Persistence, JBoss/CMP, Hibernate, Database] - Jboss SQL Error
by new_to_jboss_4
2008-03-07 17:13:37,265 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Exception destroying Man
agedConnection org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@7beded[state=DESTROYED
mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@4163e1 handles=0 lastUse=1204936637404 permit=false tra
ckByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@167a256 context=org.jboss.resou
rce.connectionmanager.InternalManagedConnectionPool@d2ee0f xaResource=org.jboss.resource.connectionmanager.TxConnectionM
anager$LocalXAResource@1045431 txSync=null]
org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLRecoverableException: Io excep
tion: Connection reset)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java
:481)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:206)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.ja
va:550)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.removeTimedOut(InternalManagedConnectionPo
ol.java:415)
at org.jboss.resource.connectionmanager.IdleRemover$1.run(IdleRemover.java:81)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLRecoverableException: Io exception: Connection reset
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:281)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:118)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:224)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:296)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:611)
at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:602)
at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:4783)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:202)
... 4 more
Please guide...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135737#4135737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135737
18 years, 1 month
[JBoss jBPM] - Re: Signalling Option
by victorl
This is process definition:
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="" name="alta">
| <start-state name="iniciar tramite">
| <task name="iniciar tramite alta"></task>
| <transition to="agendar ctrl documentacion" name="tramite iniciado"></transition>
| <event type="node-enter">
| <action name="iniciarTramite" class="ar.com.dsv.saslc.seguimiento.workflow.jbpm.handlers.alta.ControlarDocumentacion"></action>
| </event>
| </start-state>
|
| <task-node name="controlar documentacion">
| <task name="Control de Documentacion" signalling="false">
| <controller>
| <variable access="read,write" name="etiquetaBotones"></variable>
| </controller>
| </task>
| <event type="node-enter">
| <action class="ar.com.dsv.saslc.seguimiento.workflow.jbpm.handlers.alta.ObtenerTransiciones" name="obtenerNombreTransiciones"></action>
| </event>
| <transition to="examen psicofisico" name="Completo"></transition>
| <transition to="agendar ctrl documentacion" name="No Completo"></transition>
| </task-node>
|
| <task-node name="examen psicofisico">
| <task name="Examen PsicofiÃÂsico" signalling="false">
| <controller>
| <variable access="read,write" name="etiquetaBotones"></variable>
| </controller>
| </task>
| <event type="node-enter">
| <action class="ar.com.dsv.saslc.seguimiento.workflow.jbpm.handlers.alta.ObtenerTransiciones" name="obtenerNombreTransiciones"></action>
| </event>
| <transition to="calculo sellado" name="Apto"></transition>
| <transition to="coordinacion psicofisico" name="No Apto"></transition>
| </task-node>
|
| <state name="agendar ctrl documentacion">
| <event type="node-enter">
| <action class="ar.com.dsv.saslc.seguimiento.workflow.jbpm.handlers.alta.AgendarCtrlDocumentacion" name="obtenerActividadesSiguientes"></action>
| </event>
| <transition to="controlar documentacion" name="actividad agendada"></transition>
| </state>
|
| <node name="calculo sellado">
| <transition to="fin tramite" name="licencia otorgada"></transition>
| </node>
|
| <state name="coordinacion psicofisico">
| <transition to="tramite rechazado" name="no apto definitivo"></transition>
| </state>
|
| <end-state name="fin tramite"></end-state>
|
| <end-state name="tramite rechazado"></end-state>
|
| </process-definition>
The following java code calls the ActionHandler:
| public void avanzarProceso(Long idProcessInstance)
| {
| JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
| GraphSession graphSession = jbpmContext.getGraphSession();
|
| try
| {
| ProcessInstance instanciaProceso = graphSession.getProcessInstance(idProcessInstance);
| Token token = instanciaProceso.getRootToken();
| System.out.println("Nodo Actual --> " + token.getNode().getName());
| token.signal();
| System.out.println("Nodo Actual --> " + token.getNode().getName());
| jbpmContext.save(instanciaProceso);
| }
| finally
| {
| jbpmContext.close();
| }
| }
|
And the ActionHandler code is:
| public void execute(ExecutionContext executionContext) throws Exception
| {
| System.out.println("Nodo Actual --> " + executionContext.getNode().getName());
|
| List etiquetas = JBPMUtil.obtenerNombreTransiciones( executionContext.getToken() );
| TaskInstance tarea = executionContext.getProcessInstance().getTaskMgmtInstance().createTaskInstance(executionContext.getTask());
| tarea.setVariable("etiquetaBotones", etiquetas);
| System.out.println("Tarea Nodo --> " + tarea.getName());
| tarea.end();
| }
|
And the problem is mentioned following the url gave in previous message.
If you need more information, please tell me.
Thank you very much.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135731#4135731
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135731
18 years, 1 month
[JBoss jBPM] - Delegation instantiate always parses configuration
by jorgemoralespou_2
I have an application which executes a lot of processes. I have seen that for Delegations (DecisionHandlers, for example) it always parses the configuration xml. Is there a way to avoid this? I mean, having somethig like:
| <handler class="my.decision.impl.MyDecisionHandler">
| <variable>${context.a}</variable>
| <value>1</value>
| </handler>
|
Han having the MyDecisionHandler, when it instantiates, having these resolved to an Expression.
| class MyDecisionHandler{
| ...
| public Expression variable;
| public int value;
| ....
| }
|
This way, when I create my processDefinition, the Delagation should be created and assigned this valuess, and if I want to execute a processInstance of this ProcessDefinition it won`t parse xml again.
Why are instantiated delegations not store within the processDefinition? There could be a way to store some safe delegations instantiated, and others that require to be instantiated at the moment just been done like now.
Just a thought!!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135729#4135729
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135729
18 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - Database connections increasing rapidly and stops applicatio
by jbabuscio
We're running a web app using JBoss 4.0.3 and Oracle 10.2.0.3.
We had an issue last October when we switched from Oracle 9i to 10G that our connections were rapidly increasing causing the system to slow down and eventually stop working.
We followed these wiki entries at that time for cleaning up open connections and correcting the configuration:
http://wiki.jboss.org/wiki/Wiki.jsp?page=WhatDoesTheMessageNoManagedConne...
http://wiki.jboss.org/wiki/Wiki.jsp?page=CanJBossTellMeWhenIDontCloseACon...
Using those, we did close all open connections but eventually the problem was the Oracle database driver we were using with the application. We were still using the 9i driver. When we switched to the 10.2.0.3 driver, it worked well.
Two weeks ago, our DBAs installed the Oracle Critical Patch Update (which wasn't supposed to affect us) and we now have the same problem again. We did the following steps:
1. Turned back on debug mode for open connections but nothing showed up that was helpful
2. Downloaded the newest version of the Oracle jar for our JDK, odjbc5.jar which is for version 11.1.0.6 I believe. I found some sites that said Oracle recommends always using the most updated version of their drivers as long as you're using Oracle version 9.0.1 or higher.
After these steps, the problem is still there and we are dumbfounded. One thing to note is that we're very limited with our environments so production doesn't mimic developement(our client has all control). This makes it harder to load test these things.
Does anyone have any ideas, suggestions, or past issues like this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135726#4135726
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135726
18 years, 1 month
[JBoss jBPM] - configuration for bean managed transaction
by hlins
hi all,
I want to call the jbpm CommandServiceBean in a UserTransaction. But the problem is, jBPM doesn't optain the transaction. So the database values has been changed before the commit.
Here's the code
| UserTransaction transaction = sessionContext.getUserTransaction();
| transaction.begin();
| //JNDI look up the get CommandServiceBean
| // creation of an Command, to create new process instance and start it.
| commandService.execute(command);
| transaction.commit;
|
The jbpm.cfg.xml I use.
| ...
| <jbpm-context>
| <service name="persistence">
| <factory>
| <bean class="org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory">
| <field name="isTransactionEnabled"><false /></field>
| </bean>
| </factory>
| </service>
| ...
| </jbpm-context>
| ...
And the hibernate.cfg.xml
| <!-- JTA transaction properties (begin) -->
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
| <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
| <!-- JTA transaction properties (end) -->
|
I have to admit that I can see the changes in the jbpm database not until the transaction commits. But the changes on the database i call during the workflow are directly persistent.
How can configure jbpm?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135723#4135723
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135723
18 years, 1 month