Transaction Notification with DI Server

Hello
I am developing a Web Site with the DI Server, when I have validations in the Transaction Procedure the error message is incorrect.
Message: Could not commit transaction.
Transaction Notification
set @error='10'
set @error_message = 'SP: 123'
-- Select the return values
select @error, @error_message
end
I made the test with the DI - API and the message is correct.
Exists a workaround for this problem???
Thanks
Regrats
Edited by: Andres Naranjo on Sep 1, 2010 1:25 AM

Hello
This problem was solved in SAP Business One 8.8 PL20.
Regards

Similar Messages

Transaction control with DI Server and B1WS

Hi everyone,
recentily I started working with DI server and B1WS, and talking with friends and with a brief research in the foruns Its seens to be impossible to have a Rollback in database transactions performed with DI server and B1WS.
Its really true? I mean, I receive the Session ID when I use the login service, it shouldn't be so difficult to have a rollback function with this info...

Really? Anyone knows?

DeadLocks on Query Notifications with SQL Server 2008 SP3

Hello,
according to this article https://support.microsoft.com/kb/975090 the issue with deadlocks on query notifications should be fixed with SQL Server 2008 SP3 (10.0.5500.0). But we still get deadlocks in the following manner:
<resource-list>
<keylock hobtid="72057598393909248" dbid="5" objectname="MyDB.sys.query_notification_1411013420" indexname="cidx" id="lock1731c1f00" mode="RangeX-X" associatedObjectId="72057598393909248">
<owner-list>
<owner id="process573dc8" mode="RangeX-X"/>
</owner-list>
<waiter-list>
<waiter id="process58ddc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
<keylock hobtid="72057598372872192" dbid="5" objectname="MyDB.sys.query_notification_253437289" indexname="cidx" id="lock800c8780" mode="RangeS-U" associatedObjectId="72057598372872192">
<owner-list>
<owner id="process58ddc8" mode="RangeS-U"/>
</owner-list>
<waiter-list>
<waiter id="process573dc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
</resource-list>
Is there any need to install another fix?
Thanks in Advance!

Hello,
SQL Server 2008 SP4 and all cumulative updates of SP3 do not have fixes related to deadlocks.
Maybe the following workarounds and solutions can help in your scenario.
http://stackoverflow.com/questions/3707137/understanding-deadlocks-with-sql-server-query-notifications
Deadlock Prevention. In case you need to lock multiple conversation groups in a transaction, you need to take the same order to lock the different conversation groups in all transactions, otherwise you will have a deadlock issues.
Source:
http://blogs.msdn.com/b/kangmo/archive/2008/12/17/a-brief-guide-on-sql-server-service-broker.aspx
Try to may transactions more simple and shorter.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Transaction Notification with Addon

Hi guys,
I want to be able to get a transaction notification whenever a sales order is added in SAP B1. I want to retrieve the document entry of the sales order in an Addon that uses only the DI API. I have a lot of experience in building addons, but have no experience with transaction notification. How can this be done?
Thanks,
Costas

Hi Costas
Is your customer a new one? I mean:
Pricing is only applicable to new customers with a contract date after July 15th 2013.
Take into account that in case you only want to be able to get new SO from B1 system you would probably need to buy only one license which suggested price is 750 EUR. I know it is certainly not nothing but still it is not that much.
As for your question regarding TN I'd do it like this:
use PostTransactionNotice procedure to grab a DocEntry of new SO and insert it into your own log table; you can also write a trigger on ORDR table to achieve it
create CLR procedure to do something with logged DocEntry from your table using DotNet; you probably want to be able to pass a parameter to this procedure and get some output after its execution
use a SQL job to grab only new records from your log table and execute a CLR against each one; update status in your log table; write down error, error message and so on...
If have never done any CLR before check this link to learn how easily it can be done to use regex within SQL Server:
http://www.sqllion.com/2010/12/pattern-matching-regex-in-t-sql/
Kind regards,
Radek

Email notification with exchange server

Is there a way to configure bpel to email a notification through microsoft's exchange server?

ok, I'm not sure if this was a smart move or not...
I tried to telnet with what I think is the name of the server, and it didn't do anything. When I ran the process, it faulted.
So in some advanced tab of my network settings, I chose to have an smtp server running on my network. I changed the ns_email.xml file again to have that server's name. When I run the process, it still faults, but the error message has changed to
<faultInfo>Invalid Addresses; nested exception is: javax.mail.SendFailedException: 550 5.7.1 Unable to relay for [email protected]</faultInfo>
</part>
[email protected] is actually filled with my real email address.
any thoughts?

Push notification with ical server to known Attendees of the OD

Hello Apple-Community.
I have a Problem with the Push-Invitations of my Mac Server.
Here´s my background:
- MAC OS X 10.6.4 as Mail-Server, Ical-Server, OD-Master
- Ical and Thunderbird Lightning 1.02b as Calendar-Clients
My Problem:
Every Attendee in my Calender-System with an E-Mail, listet in the OD under the field "mail" eg. "EMailAddress" doesn´t get any Invites via E-Mail. If I delete the EMailAdress in my OD, the user gets an E-Mail-Invitation.
My target:
I want modify the System. The Push-Notification-Server shall send always an E-Mail to every Attendee of an appointment.
I would modify the appropriate configuration file but I have really no idea, where I can search.
I hope, that someone can help me.
Best regards.
Ornaminer

I have a very similar configuration with all PC Thunderbird/Lightning clients. I need the same resolution, but think that an add-on to Thunderbird/Lightning that would accept the event push notifications and allow a response is also a solution. Is there anyone how can develop such an add-on?
Cheers,
Steve

MQSeries as a Transactional Resource Manager with Weblogic Server

          I am trying to setup the example given in the BEA white paper:
          Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          Version 1.
          October 25, 2001.
          I followed the instructions given in the documents, but when i run client program
          >java MQClient t3://localhost:7001 "MQSeries test"
          I received the following exception below. Does anyone how what is the reason for
          this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
          6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
          for java and the MQSeries classes for Java Message Service on the weblogic
          server machine.
          sending: "MQSEries test"
          Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
          sted exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          at $Proxy1.bridgeWLS2MQS(Unknown Source)
          at MQClient.main(MQClient.java:54)


The point is that over TCPIP the MQ XA connection factory is not available.
          The MQ shared memory/JNI driver is required to access it, which limits
          access to those processes that are on the same box as the MQ q manager.
          This is an MQ series limitation.
          Douglas WF Acheson wrote:
          > Hello,
          >
          > If memory server me correct, default connection to MQ Series is through
          > JNI calls and shared memory. You have to change the protocol to TCPIP when
          > connection to the queue manager on another box (do not know much about XA
          > with MQ Series); that is when you connect to MQ Series vi JMS on another
          > box you must do something like the following:
          >
          > qcf = new MQQueueConnectionFactory() ;
          > qcf.setHostName(hostName) ;
          > qcf.setPort(port) ;
          > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
          > qcf.setQueueManager(qManagerName) ;
          >
          > Then when you create you queues, sesions etc. you are point at the correct Q
          > manager.
          >
          > Hope this helps ...
          >
          > Douglas WF Acheson
          >
          > "Raja Mukherjee" <[email protected]> wrote in message
          > news:[email protected]...
          > > On a closer look at the original post (sorry for missing that, it was
          > early
          > > in the morning), you would not be able to use XA if your QM and WLS are in
          > > different boxes. Check on this newsgroup, there are several posts on this
          > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
          > on
          > > the sames box. This is a MQSeries limitation not WLS.
          > >
          > > .raja
          > >
          > >
          > > "ibrahim Nehme" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > I am trying to setup the example given in the BEA white paper:
          > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          > > > Version 1.
          > > > October 25, 2001.
          > > > I followed the instructions given in the documents, but when i run
          > client
          > > program
          > > >
          > > > >java MQClient t3://localhost:7001 "MQSeries test"
          > > > I received the following exception below. Does anyone how what is the
          > > reason for
          > > >
          > > > this exception(s) and how i can solve the problem? My MQSeries Server
          > and
          > > Weblogic
          > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
          > > classes
          > > > for java and the MQSeries classes for Java Message Service on the
          > weblogic
          > > > server machine.
          > > > ---------------------------------------
          > > > sending: "MQSEries test"
          > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
          > > server; ne
          > > > sted exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > <<no stack trace available>>
          > > > --------------- nested within: ------------------
          > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ]
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
          > > > at MQClient.main(MQClient.java:54)
          > >
          > >

SQL Server 2012 Transactional Replication with updateable subscriptioins

Hi All,
It is heard that Transactional Replication with Updateable Subscriptions
is
deprecated in SQL 2012 so it is not possible to configure through the wizards but
we can still configure it by using T-SQL Script. Would you please share that script if possible to configure the same in SQL Server 2012. Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----

Thanks for the information,
I understand that you have got the answer yourself and post it, Therefor I mark your answer. If this is still open question please inform us.
[Personal Site] [Blog] [Facebook]

Transaction with Sunapplication server

Dear All,
I am working on some project with sun application server. The project was done in weblogic and it was working fine. Now our management decided move the working version to sunapplication server. I am having big trouble in finding when does server commits the transaction. Is there any indiaction in the log file and any information that we can trace for transactions that are being commited or rolledback. / any thing to indiacte in the sun-ejb-jar.xml
the flow is like main application conatct session bean which generates event, once event is generated the application generates other 4 records related different persons(insert 4 records into 4 diff tables).
in 5th step program retrieves the values from tables based on what they inserted in previous steps.
session bean which initiates applications generated event and use hybernate to store record, the other 4 recordes are created using entity beans.
I am able to populate the beans(for storing) and retrieve the information from beans. but the actual values are not in the database.
If some one can help that would be great help.
thanks
Srini

To find out what each transaction ended with you have to change your instance's Log Level for JTA and JTS from default INFO to FINE or FINEST. You could also throw in FINE for EJB Container if you need to check what your EJBs are up to.
You can chenge Log Level setting via admin console:
instance-config --> Logger Settings --> Log Levels tab
Once you change the logger settings rerun your test and loads of info would be printed into instance's server.log.

Transaction with the server failed error 405

HI,
Thanks in advance.
We are working on the MDM service provided by apple using the iPCU and have configured the server with valid certificate. But still we notice some other error. Please help us to resolve this.
Error:
(Error) MDM: Cannot Authenticate. Error: NSError:
Desc   : A transaction with the server at failed with the status 405.
US Desc: A transaction with the server at has failed with the status 405.
Domain : MCHTTPTransactionErrorDomainCode   : 23001
Type   : MCFatalErrorParams : ("https://xxxxx.xxx.com/Checkin.aspx",    405)
(Error) MC: Cannot install MDM com.xxx.mdm.mdm3. Error: NSError:
Desc   : The payload com.xxx.mdm.mdm3 could not be installed.
Sugg   : A transaction with the server at https://xxxx.xxx.com/Checkin.aspx has failed with the status 405.
US Desc: The payload com.xxx.mdm.mdm3 could not be installed.
US Sugg: A transaction with the server at https://xxxx.xxx.com/Checkin.aspx has failed with the status 405.
Domain : MCInstallationErrorDomainCode   : 4001
Type   : MCFatalErrorParams : (    "com.xxx.mdm.mdm3")...Underlying error:NSError:
Desc   : A transaction with the server at https://xxxxx.xxx.com/Checkin.aspx has failed with the status 405.
US Desc: A transaction with the server at https://xxxxx.xxx.com/Checkin.aspx has failed with the status 405.
Domain : MCHTTPTransactionErrorDomainCode   : 23001
Type   : MCFatalErrorParams : (    "https://xxxxx.xxx.com/Checkin.aspx",    405)

But in 2005 B I did the same without using license file.
Moreover, I can access the other machine's(Server) Companies from different SAP B1 server by using change Server on Choose Company Screen.
But If I install the client on a system, I am not able to access the companies.
Is it mandatory to have License to install the Client of a server?
Is it new guideline in 2007 or was it already exist in previous versions.

How to set up SAPconnect with email server

Hi,
Does any one know <b>how to set up SAPconnect with email server</b>
We are using workflow and when it fails it we are sending the notification mail to the user on his company mail id, i.e. [email protected]
This is working in the current production system. We are doing the new development which will replace the current production system. The existing Basis team does not know how it was setup in production system and how to set it up in the new system.
When we send any mail notification from workflow we can see the mail in SCOT transaction but it is not received at the specified mail address.
Can any one provide the configuration steps or any document for this.
Thanks in advance..
Pratik

Hi Pratik,
Check the following link:-
/people/thomas.jung3/blog/2004/09/08/sending-e-mail-from-abap--version-610-and-higher--bcs-interface
http://help.sap.com/saphelp_nw04/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/frameset.htm
these link will help u to config SMTP.
And one more thing u have to do..
Go to SE11 n open Table sxnodes in change mode.
And change F_ESMTP field to false i.e. BLANK for the Field NODE = SMTP.
Hope this will work For U.
Regards
Sachin Dhingra

Connectivity with sql server

Dear community members;
I am using Oracle 10g DB. Now I want to connect with SQL Server 2005. Is there any possiblity for connectivity. Because we have to pick some data from sqlserver on online transaction entry time.
Waiting for usefull response.
Thanks
Shahab Ahmed Khan

I am using oracle 11gR1 on windows 2003.
This is my initaccessdb.ora(Path HS/ADMIN)
HS_FDS_CONNECT_INFO = ACCESSDB
HS_FDS_TRACE_LEVEL = OFF
Listner File
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = APPSERVER)(PORT = 1521))
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=PLSExtProc)
(ORACLE_HOME=E:\app\Administrator\product\11.1.0\db_1)
(PROGRAM=extproc)
     (SID_DESC =
     (SID_NAME = accessdb)
(ORACLE_HOME = E:\app\Administrator\product\11.1.0\db_1)
(PROGRAM = ACCESSDB)
     (ENVS=LD_LIBRARY_PATH=D:\)
TNSNAME.ORA
ORCL =
(DESCRIPTION =
     (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.0.14)(PORT = 1521))
     (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME= ORCL)
ACCESSDB =
(DESCRIPTION=
     (ADDRESS =(PROTOCOL = TCP)(HOST=172.16.0.14)(PORT=1521))
          (CONNECT_DATA =
          (SERVICE_NAME=ACCESSDB))
               (HS = OK)
I successfully completed all steps as mentioned in your sending links documents but when i test my dblink query it gives the error message
SQL> conn sys as sysdba
Enter password:
Connected.
SQL> conn ahmed
Enter password:
Connected.
SQL> drop database link test;
Database link dropped.
SQL> create database link test using 'ACCESSDB';
Database link created.
SQL> SELECT * FROM EMPLOYEE@TEST;
SELECT * FROM EMPLOYEE@TEST
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from TEST
Note: Please tell me that should i install ODBC driver ("Microsoft Access Driver *.mdb).If this should be installed then i have done correctly.
Thanks

Updated to 10.6.3, can no longer sync iCal with Exchange Server

My syncing with our exchange server used to work fine. I updated my 3 Macs and now they all have the same issue. They will not sync with the server and they all show 4 notifications that have not yet been responded to. When I view the notifications, they are all for old entries. I accept all 4, but doesn't seem to work - still shows iCal offline. Anyone else having this issue? Any suggestions? I tried removing the calendars cache file and plist files.

I spent an hour on the phone with Apple today, got elevated to an engineer AND talked to a Server Guy at my University.
The cause is still unclear, but the remedy has become painfully clear. To have a working copy of iCal, Mail, and AddressBook, one needs to remove all three accounts from the three client apps, and restart from Mail. This approach is the only way to preserve correct links among the three client apps.
I got iCal working temporarily by deleting my Exchange account and rebuilding it. The problem is that by rebuilding an iCal account, it created duplicate accounts in Mail and AddressBook. Also, the Apple apps autodiscovered slightly different server names, which caused problems sending me and I was getting duplicate email messages as well as contacts and calendar events. I deleted the redundant mail and contact accounts, but continued to have problems with sending mail and I lost my ToDos in Mail. So, I bit the bullet and have blitzed all my exchange accounts on my MBP and am waiting for it to repopulate the 5+ GB of data. Then tomorrow, I will do the same on my iMac.
Sheesh!

The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.

Hello All,
I am getting below error can you please help me
Error:-
The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.

Perhaps this thread will help you out
http://stackoverflow.com/questions/11453066/error-the-transaction-associated-with-the-current-connection-has-completed-but
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Problem with BizTalk server 2013 SFTP adapter on Cloud VM

All,
We have deployed Microsoft Biztalk Server 2013 Enterprise edition on a cloud VM. We are facing an issue with SFTP adapter to receive. Following are the details;
On this VM, we are facing an issue with BizTalk server 2013 SFTP adapter. The SFTP location can receive and send message through SFTP clients and .Net code. But using BizTalk server 2013 SFTP adapter we are only able to send the file on SFTP location but
could not receive the files from same location.
We are getting just one line error in system event log that is :
Event#7011. A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BTSSvc$BizTalkServerApplication service.
Regards,
Shoaib Danish

Hi
BizTalk Server 2013 is available on Windows Azure. BizTalk Server 2013 can be installed locally on your hardware
and in Windows Azure as a virtual machine. Please follow the procedures to check it on your side.
Configuring BizTalk Server 2013 on a Windows Azure VM
Create a BizTalk Virtual Machine in Windows Azure
Create the BizTalk Group Prerequisites
Configure the BizTalk Group
Best regards
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Transaction Notification with DI Server

Similar Messages

Maybe you are looking for