[Design of JBoss Profiler] - JBoss Profiler On Solaris
by grdzeli_kaci
hi all,
i am newbie on jboss profiler,
i tried to install jboss profiler and done it step by step,
1.download jboss profiler 1.0.CR4,
2. first step "1. Build using ant. The built files will appear under the build/ directory" does not work it throws an error :
| bash-3.00$ $ANT_HOME/bin/ant compile
| Buildfile: build.xml
| init:
| compile:
| [javac] Compiling 5 source files to /export/home/jboss/jboss-profiler-1.0.CR4/jvmti-src/output/classes
| BUILD FAILED
| /export/home/jboss/jboss-profiler-1.0.CR4/jvmti-src/build.xml:23: /export/home/jboss/jboss-profiler-1.0.CR4/build/jar not found.
|
| Total time: 0 seconds
|
what i did incorrect ???
after this i tried to install without build,
look into the read me file, there is installation steo :
"1.Once built, put jbossInspector.dll in your PATH (if you are using Windows)
or libjbossInspector.so in your LD_LIBRARY_PATH (if you are using Linux/Unix.)"
i have solaris os and export ld_library_path
| LD_LIBRARY_PATH=/export/home/jboss/jboss-profiler-1.0.CR4/jvmpi-src/solaris/bin
| export LD_LIBRARY_PATH
|
also i put it into path
| PATH=$JAVA_HOME:$PATH:/export/home/jboss/jboss-profiler-1.0.CR4/jvmpi-src/solaris/bin
| export PATH
|
after all i changed my run configuration file
| JAVA_OPTS="-server -Xmx3168m -Xms2144m -Xmn1g -Xss256k -d64 -XX:PermSize=128m -XX:MaxPermSize=256m
| -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
| -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
| -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=31 -XX:+AggressiveOpts
| -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution
| -Xloggc:/export/home/jboss/jboss-4.0.4.GA/server/all/log/gc.log
| -XrunjbossInspector:/export/home/jboss/jboss-profiler-1.0.CR4,include=com.magti,start=org.jboss"
|
but i got an error like this:
| Error occurred during initialization of VM
| Could not find agent library on the library path or in the local directory: jbossInspector
|
what i did incorrect ?
regards,
Paata.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043647#4043647
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043647
17 years, 8 months
[Design of JBoss jBPM] - Re: possible bug with JTA transactions
by camunda
I am also a bit puzzled about the following exception, if there are logs to save after a Signal. But why is not the correct current JTATransaction used here? (sorry, I didn't get a exact test case yet)
anonymous wrote :
| ERROR
|
| com.camunda.toolkit.jbpm.service.CommandServiceBean
|
| could not close jbpm context after command org.jbpm.command.SignalCommand
|
| org.hibernate.exception.GenericJDBCException: Cannot open connection
| at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
| at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
| at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426)
| at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
| at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:94)
| at org.hibernate.id.IdentityGenerator$GetGeneratedKeysDelegate.prepare(IdentityGenerator.java:69)
| at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:30)
| at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2158)
| at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2638)
| at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48)
| at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
| at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298)
| at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181)
| at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107)
| at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:187)
| at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
| at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:172)
| at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
| at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70)
| at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:535)
| at org.hibernate.impl.SessionImpl.save(SessionImpl.java:523)
| at org.hibernate.impl.SessionImpl.save(SessionImpl.java:519)
| at org.jbpm.logging.db.DbLoggingService.log(DbLoggingService.java:57)
| at org.jbpm.svc.save.SaveLogsOperation.save(SaveLogsOperation.java:47)
| at org.jbpm.svc.Services.save(Services.java:161)
| at org.jbpm.JbpmContext.save(JbpmContext.java:427)
| at org.jbpm.JbpmContext.autoSave(JbpmContext.java:620)
| at org.jbpm.JbpmContext.close(JbpmContext.java:137)
| at com.camunda.toolkit.jbpm.service.CommandServiceBean.execute(CommandServiceBean.java:90)
| ...
|
| Caused by: org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=titan.computation.de/494320, BranchQual=, localId=494320]; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=titan.computation.de/494320, BranchQual=, localId=494320])
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:94)
| at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
| at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
| ... 61 more
|
| Caused by: javax.resource.ResourceException: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=titan.computation.de/494320, BranchQual=, localId=494320]
| at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:290)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:379)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:812)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
| ... 63 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043645#4043645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043645
17 years, 8 months
[Design of JBoss jBPM] - possible bug with JTA transactions
by camunda
Hi,
I am not yet sure if it is a bug or a missconfiguration from me. But I am nearly convinced that it is a bug ;-)
I use the JtaDbPersistenceServiceFactory for pesisting (transactionEnabled=true, currentSessionEnabled=true). Now I trigger a process with a small action, which queries process name from jbpm (and therefor create a own jbpmContext). My testcode:
| private String testProcess = "<process-definition name='Test'>"
| + "<start-state name='startState'>"
| + " <transition name='startTransactionTest' to='end'>"
| + " <action name='test' class='com.camunda.ccs.process.test.ExecuteJbpmCommand'/>"
| + " </transition>"
| + "</start-state>"
| + "<end-state name='end'/>"
| + "</process-definition>";
|
| public void testHibernateSession() {
| // deploy process
| DeployProcessCommand deployCmd = new DeployProcessCommand();
| deployCmd.setXml( testProcess );
| Tk4jbpmConfiguration.getCommandService().execute(deployCmd);
|
| // now start it
| StartProcessInstanceCommand cmd = new StartProcessInstanceCommand();
| cmd.setProcessName("test");
| ProcessInstance pi = (ProcessInstance) Tk4jbpmConfiguration.getCommandService().execute(cmd);
|
| // process is ended
| assertNotNull(pi.getEnd());
| }
|
(The Tk4jbpmConfiguration.getCommandService() just gets a reference to a EJB-3-ServiceBean, which runs the execute in TransactionAttributeType.REQUIRED).
The aciton is very easy:
| public class ExecuteJbpmCommand implements ActionHandler {
| public void execute(ExecutionContext ctx) throws Exception {
| GetProcessDefinitionCommand cmd = new GetProcessDefinitionCommand();
| Tk4jbpmConfiguration.getCommandService().execute(cmd);
| }
| }
|
Now I get the following problem: The first context starts a transaction (and gets the current user transaction from hibrnate). The second jbpmContext get the same transaction. But it commits & closes it at the end (the commit has of xourse no effect on the JTA-Transaction, but the begun marker of the hibernate JTATransaction is set to false!). After that, we get a Exception while closing the JTATransaction the second time. If we ignore it, everything seems to work fine.
You can also see that in the logs:
anonymous wrote :
| DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@27e905
| DEBUG [com.camunda.toolkit.jbpm.service.CommandServiceBean] executing org.jbpm.command.StartProcessInstanceCommand@336f59...
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] using current hibernate session SessionImpl(...)
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] beginning hibernate transaction
| DEBUG [org.hibernate.transaction.JTATransaction] Looking for UserTransaction under: UserTransaction
| DEBUG [org.hibernate.transaction.JTATransaction] Obtained UserTransaction
| DEBUG [org.hibernate.transaction.JTATransaction] begin
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] begun hibernate transaction org.hibernate.transaction.JTATransaction@d34b8c
|
| DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[message, tx, scheduler, authentication, persistence, logging]'
| DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@12f2476
| DEBUG [com.camunda.toolkit.jbpm.service.CommandServiceBean] executing org.jbpm.command.GetProcessDefinitionCommand@2fe28...
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] using current hibernate session SessionImpl(...)
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] beginning hibernate transaction
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] begun hibernate transaction org.hibernate.transaction.JTATransaction@d34b8c
| DEBUG [com.camunda.toolkit.jbpm.service.CommandServiceBean] ... finished with org.jbpm.command.GetProcessDefinitionCommand@2fe28
| DEBUG [org.jbpm.JbpmContext] closing org.jbpm.JbpmContext@12f2476
| DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@1d6c90d
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] committing hibernate transaction org.hibernate.transaction.JTATransaction@d34b8c
| DEBUG [org.hibernate.transaction.JTATransaction] commit
|
| DEBUG [com.camunda.toolkit.jbpm.service.CommandServiceBean] ... finished with org.jbpm.command.StartProcessInstanceCommand@336f59
| DEBUG [org.jbpm.JbpmContext] closing org.jbpm.JbpmContext@27e905
| DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@383c13
| DEBUG [org.jbpm.persistence.db.DbPersistenceService] committing hibernate transaction org.hibernate.transaction.JTATransaction@d34b8c
| ERROR [org.jbpm.persistence.db.DbPersistenceService] hibernate commit failed
| org.hibernate.TransactionException: Transaction not successfully started
| at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:126)
| at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:255)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:213)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.close(JtaDbPersistenceService.java:34)
| at org.jbpm.svc.Services.close(Services.java:222)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
| at com.camunda.toolkit.jbpm.service.CommandServiceBean.execute(CommandServiceBean.java:91)
|
Now, what is the right way to handle it? I am not completly sure at this point...
Any remarks?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043640#4043640
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043640
17 years, 8 months