Hi Amos,

No I did not use Hibernate at all. I used straight jdbc. See the following

private JdbcTemplate jdbcTemplateObject;

    private DataSource   dataSource;

    @Override

    public void setDataSource(DataSource dataSource) {

        this.dataSource = dataSource;

        this.jdbcTemplateObject = new JdbcTemplate(dataSource);

    }

    @Override

    @Transactional(propagation = Propagation.REQUIRED, readOnly = false)

    public void create(User user) {

        String SQL = "insert into users(id,name,email) values (?,?,?)";

        jdbcTemplateObject.update(SQL, user.getId(), user.getName(), user.getEmail());

        System.out.println("Inserted into Customer Table Successfully");

        System.out.println("Create new user = " + user.getName());

        SQL = "insert into Address(id,address,country) values (?,?,?)";

        jdbcTemplateObject.update(SQL, user.getAddress().getId(), user.getAddress().getAddress(),

                user.getAddress().getCountry());

        System.out.println("Inserted into Address Table Successfully");

    }

    @Override

    public User getUser(String name) {

        String SQL = "select * from users where name = '?'";

        User user = jdbcTemplateObject.queryForObject(SQL, new Object[] { name }, new UserMapper());

        return user;

    }

    @Override

    public List<User> getUsers() {

        String SQL = "select * from users";

        List<User> users = jdbcTemplateObject.query(SQL, new UserMapper());

        return users;

    }

}

Hi Tom,

I tried using a name service(NS.bat) with Jacorb but I dont think I have the jacorb configuration correct between Narayana, the Jacorb Name Server, and the Spring application. I think that's the final piece I have missing. According to the Spring documentation a Transaction Manager *should* be an easily plug in via configuration, so just trying to get there. I assumed with the configuration file I have in Spring, that Narayana would just link up and semi-automatically work.

This might just be my lack of knowledge in Jacorb at this point. I am still investigating.

I ran the name server using: ns -Djacorb.naming.ior_filename=d:/IR_Ref -DOAPort=38693

I ran nmg and am able to connect to the name server using nmg -ORBInitRef.NameService=file:///d:/IR_Ref

However I dont know the correct way to get the transaction manager to connect to the nameserver.

Ive tried adding the following to the end of the command in "start-transaction-server.bat":

-Djacorb.naming.ior_filename=d:/IR_Ref

-ORBInitRef.NameService=file:///d:/IR_Ref

@Amos Feng

I switched out the data source to use an actual MySql instance:

<bean name="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">

    <property name="driverClassName" value="com.mysql.jdbc.Driver" />

    <property name="url" value="jdbc:mysql://localhost:3306/test_spring" />

    <property name="username" value="root" />

    <property name="password" value="password" />

</bean>

but that didnt change anything as the output from my spring program was still:

-ORBInitRef.NameService=file:///d:/IR_Ref

May 03, 2017 12:08:22 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh

INFO: Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@6442b0a6: startup date [Wed May 03 12:08:22 PDT 2017]; root of context hierarchy

May 03, 2017 12:08:22 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from class path resource [Beans.xml]

May 03, 2017 12:08:22 PM org.springframework.jdbc.datasource.DriverManagerDataSource setDriverClassName

INFO: Loaded JDBC driver: com.mysql.jdbc.Driver

May 03, 2017 12:08:22 PM org.springframework.transaction.jta.JtaTransactionManager checkUserTransactionAndTransactionManager

INFO: Using JTA UserTransaction: org.springframework.transaction.jta.UserTransactionAdapter@5cee5251

May 03, 2017 12:08:22 PM org.springframework.transaction.jta.JtaTransactionManager checkUserTransactionAndTransactionManager

INFO: Using JTA TransactionManager: com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple@433d61fb

May 03, 2017 12:08:22 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start

INFO: ARJUNA012170: TransactionStatusManager started on port 56989 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService

My expectation is that there is some configuration that needs to be done in the spring application that tells it where the name server is. After the nameserver is connected to the transaction service is linked up with the spring application. But up to this point I am having a problem having anyone connect to the Jacorb name server besides nmg.

Thanks,

Mina

Well from my understanding (which I may be very wrong). JTA is when you use transactions within a container such as JBoss, EJB, etc.. What i am looking to do is have a distributed system where various regular old java programs are modifying databases at the same time and needed a global transaction solution to coordinate this. My assumption was that using Spring and annotations and defining a transaction manager(JTS) that adhered to JTA that it would be wired up to work correctly.

Also I am able to get the JTS to connect to the jacorb nameserver now by changing the jbossts-properties.xml to be

<entry key="OrbPortabilityEnvironmentBean.bindMechanism">NAME_SERVICE</entry>

and including running the start-transaction-service.bat as follows:

"%JAVA_HOME%\bin\java"  com.arjuna.ats.jts.TransactionServer -ORBInitRef.NameService=file:///d:/IR_Ref

So the only last piece seems to be to get the spring app to talk to both...

Hi Tom,

Thank you for your reply. I think that might have been my confusion. To be more exact there are going to be multiple instances of a java program that will need to do multiple updates within a transaction on the same database. So more concretely

Instance 1:on different jvm or server

Begin Transaction

Update table 1

Update table 2

Update table 3

End Transaction

Instance 2:on different jvm or server

Begin Transaction

Update table 1

Update table 2

Update table 3

End Transaction

So its not many programs participating in the same transaction rather its many concurrent transactions on the same tables within different JVM/Servers.

So being able to have the N instances running in a distributed environment and not have them step on each others transaction is what I was hoping to achieve. So i assumed I had to have the transaction propagate to a transaction management solution so that it could see the transaction status and coordinate them. And none of the applications are within an application server, you can think of them as distributed workers on a big data system. So would SimpleJTA work in this case? Or im thinking this is more of a general architecture issue I need to resolve.

Thanks,

Mina