[Datasource Configuration] - unable to setup mysql database on JBoss 5.1.0GA
by Ralph Soika
Ralph Soika [http://community.jboss.org/people/rsoika] created the discussion
"unable to setup mysql database on JBoss 5.1.0GA"
To view the discussion, visit: http://community.jboss.org/message/549799#549799
--------------------------------------------------------------
Hi,
I need some help to setup a mysql database.
I followed this wiki
http://community.jboss.org/wiki/SetUpAMySQLDatasource http://community.jboss.org/wiki/SetUpAMySQLDatasource
So after configuration I see in the JBoss Web console now two "Local Tx Datasources"
The DefaultDS and a new one named "jdbc/workflow-db"
The DefaultDS shows the Status "UP" but my new datasource shows the status "DOWN"
In the log file I got error messages like this:
10:53:51,772 ERROR [InventoryManager] Call to getAvailablity() on ResourceComponent for Resource[id=-9, type=Local Tx Datasource, key=DataSource:LocalTx:jdbc/workflow-db, name=jdbc/workflow-db, parent=JBoss AS 5 (imixs), version=?] failed.
java.lang.IllegalStateException: Failed to find [ComponentType{type=DataSource, subtype=LocalTx}] ManagedComponent named [jdbc/workflow-db].
at org.rhq.plugins.jbossas5.ManagedComponentComponent.getManagedComponent(ManagedComponentComponent.java:340)
I am using mysql-connector-java-5.1.7-bin.jar and my database is up and running.
I checked everything more than once.
My mysql-ds.xml file looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>jdbc/workflow-db</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/jboss_test</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>xxx</user-name>
<password>yyy</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>mySQL</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
Can any body give me a hint what I did wrong?
Thanks for any help
Ralph
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549799#549799]
Start a new discussion in Datasource Configuration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[jBPM] - JBPM 4.4 Snapshot: timer expression does not accept EL that return a duration string value
by Nugroho Saputro
Nugroho Saputro [http://community.jboss.org/people/nsaputro] created the discussion
"JBPM 4.4 Snapshot: timer expression does not accept EL that return a duration string value"
To view the discussion, visit: http://community.jboss.org/message/549798#549798
--------------------------------------------------------------
HI All,
I have a problem when running timer with EL expression on JBPM 4.4 snapshot. I use an EL expression #{provisioningService.checkStatusDelay} that return a duration string like "2 minutes"
Previously on JBPM 4.3, the EL gets evaluated correctly and timer works as expected but now I get the following error on 4.4 snapshot.
>
> 09:15:26,535 ERROR [ExecuteJobCmd:42] exception while executing 'ExecuteActivityMessage[59]'
>
> org.jbpm.api.JbpmException: Invalid basedate type: #{provisioningService.checkStatusDelay} is of type java.lang.String. Only Date and Calendar are supported
>
> at org.jbpm.pvm.internal.cal.Duration.calculateDueDate(Duration.java:131)
>
> at org.jbpm.pvm.internal.job.TimerImpl.setDueDateDescription(TimerImpl.java:75)
>
> at org.jbpm.pvm.internal.model.ScopeInstanceImpl.createTimer(ScopeInstanceImpl.java:305)
>
> at org.jbpm.pvm.internal.model.ScopeInstanceImpl.initializeTimers(ScopeInstanceImpl.java:334)
>
> at org.jbpm.pvm.internal.model.ExecutionImpl.createScope(ExecutionImpl.java:264)
>
> at org.jbpm.pvm.internal.model.op.TransitionStartActivity.perform(TransitionStartActivity.java:82)
>
> at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:671)
>
> at org.jbpm.pvm.internal.model.op.ExecuteActivityMessage.execute(ExecuteActivityMessage.java:46)
>
> at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:76)
>
> at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:42)
>
>
>
>
Is this a bug or the expected behavior?
Thank you.
Regards,
Nugroho
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549798#549798]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
Re: [jboss-user] [JBoss Microcontainer Development] - VFS3 and symlinks
by Marko Strukelj
Marko Strukelj [http://community.jboss.org/people/mstruk] replied to the discussion
"VFS3 and symlinks"
To view the discussion, visit: http://community.jboss.org/message/549790#549790
--------------------------------------------------------------
I don't think we have any performance tests in VFS yet. I'm also not aware of any JBoss projects performance testing how-to.
So here are a few things you want to have in mind specifically for testing symlink impact on performance.
First, you'll need to create a lot of symlinks, it's best they point to different files (to avoid filesystem caches) - so maybe create one directory with randomly named files and one directory with corresponding symlinks. Put a filename as content of each file.
Then use VFS on directory containing symlinks and visitor to iterate over them, read each virtual file - check that the content matches the name.
To compare the result, test nonsymlink access - delete the temp dirs and recreate just the files again using random names. Use VFS on directory containing files.
So ... the important thing is to try and neutralize the effect of filesystem caches, although in real life situations there will be a filesystem cache so does it really make sense to avoid it while testing? It depends on what you want to measure really.
The question is how realistic scenario the described test would be - having tons of symlinks. It's actually quite unrealistic as you typically don't go create symlinks for individual files, but for whole directories, so a test where the symlinks directory is actually a symlink to files directory is more realistic, but in this case again you benefit from filesystem caches.
I'd say - just cover all the scenarios :)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549790#549790]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months