Bug 1044486

Created attachment 838315 [details]
installation log

Created attachment 838316 [details]
standalone config (SQL Server 2008)

Installer can be downloaded from http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0-ER7-2/jboss-fsw-installer-6.0.0.ER7-redhat-2.jar

To create a SQL Server 2008 rdbms test account:

Browse to url:
http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=alloc&label=mssql2008R2&requestee=modeshape-test&expiry=150

The returned page gives database connection credentials.

This will create test account.  To view the status of your test account and to Erase content see:

http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=report

Note: The database accounts tend not to be clear of tables when they get reallocated.  So before an install, be sure to "Erase" the account before installation.

I tried looking at this locally, but I cannot reproduce the issue.

I'm have several other issues:

a) the installer does not install a MS-SQL-2008 driver. I had to manually install /modules/system/layers/base/com/microsoft/sqlserver/main/sqljdbc4.jar. This may or may not be the driver you're testing with; that may have relevance 

b) after installing the above, using the configuration file that is attached to this issue on the dballo00 account, when starting up the server I always get:

11:23:52,948 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 54) MSC000001: Failed to start service jboss.persistenceunit."gadget-web.war#gadget-core": org.jboss.msc.service.StartException in service jboss.persistenceunit."gadget-web.war#gadget-core": javax.persistence.PersistenceException: [PersistenceUnit: gadget-core] Unable to build EntityManagerFactory
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
        at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: gadget-core] Unable to build EntityManagerFactory
        at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:930)
        at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
        at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:92)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
        ... 4 more
Caused by: org.hibernate.HibernateException: Missing table: GS_APP_DATA
        at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1275)
        at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:155)
        at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:508)
        at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1762)
        at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
        at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920)

And I cannot move past this point.

Also, with the exception of the above errors the server does start up and I'm able for example to log into http://localhost:8080/s-ramp-ui/

@stejohns: I was able to reproduce the issue locally using the MS Driver version 3.0.1301.101 and when installing selecting only S-RAMP (the rest of the components are just clutter for this scenario).

The server started up fine the 1st time & I was able to upload an artifact into S-RAMP (via http://localhost:8080/s-ramp-ui). However, upon restart - on a non-clean DB - I was able to reproduce the exception.

As far as I can tell this is caused by the fact that ISPN is configured to use VARCHAR via 

<id-column name="id" type="VARCHAR(500)"/>. 

However, afaik on Ms-SQL Server 2008 this means that the server expects the UCS-2 encoding. However, ModeShape & ISPN use UTF, so changing the column to:

<id-column name="id" type="NVARCHAR(500)"/> 

fixed the issue for me locally.

Can you please validate this fix on your machine (make sure you start with a fresh DB) and if it is correct, this bug needs to be moved to "installer" as it is a configuration issue.

Fix confirmed.  I have a clean server startup.  The CLI configuration for sramp will be updated to reflect this change in fsw.

Verified in CR1.