SB-Messaging adapter connecting to multiple queues

Is it possible to configure messaging BizTalk adaptor to support connecting to multiple services bus instances on BizTalk 2013?

Hi,
You can make use of ReplyTo property
to get or set the address of the queue dynamically,
Refer the article: How
to integrate BizTalk Server 2013 with Windows Azure Service Bus
Rachit
Please mark as answer or vote as helpful if my reply does

Similar Messages

Sb-messaging adapter connection string

Does sb-Messaging Adapter of BizTalk support connection string that has multiple endpoints appended as shown below?
"Endpoint=sb://computer1/test-namespace,sb://computer2/test-namespace;StsEndpoint=https://computer1:9355/test-namespace,https://computer2:9355/test-namespace;RuntimePort=9354;ManagementPort=9355"
And
if it does, does it actually use it to switch to another endpoint if one fails?
This format is mentioned here:
https://msdn.microsoft.com/en-us/library/jj149830.aspx

And
if it does, does it actually use it to switch to another endpoint if one fails?
This format is mentioned here:
https://msdn.microsoft.com/en-us/library/jj149830.aspx
No, It doesn't work that way in BizTalk. You can specify only 1 endpoint/port.
At receive:
Use this
To do this
Queue or Subscription URL
Specify the URL where the Service Bus queue is deployed. Typically the URL is in the following format:
sb://<namespace>.servicebus.windows.net/<queue_name>
At send:
Destination URL
Specify the URL where the Service Bus queue is deployed. Typically the URL is in the following format:
sb://<namespace>.servicebus.windows.net/<queue_name>
On the receive side, you would need multiple Receive Locations for receiving from multiple queues.
On the send side, you would also need multiple Send Ports, unless you use a Dynamic Send Port.
Rachit
Please mark as answer or vote as helpful if my reply does

Error in disp+work.EXE - Running, Message Server connection ok...

Hello gurus,
System: Solution Manager
OS: Windows 2003 server R2 X32
DB: Microsoft SQL server 2005
I have an error when I tried to start my solution manager system, after having done a kernel upgrade (for the level 201)
I donu00B4t know why but the error (as you see in following image) itu00B4s in the java stack more particularly in disp+work.EXE Dispatcher with the status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable".
http://img6.imageshack.us/img6/7067/solmanj2eeerror.png
Can you help me whatu00B4s the problem here?
This next text itu00B4s a dev_disp log... maybe with this you get the error and the solution for that! :
trc file: "dev_disp", trc level: 1, release: "700"
sysno      01
sid        PSM
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    201
intno      20050900
make:      multithreaded, ASCII, optimized
pid        756
Sun Jul 05 21:08:44 2009
kernel runs with dp version 242(ext=110) (@(#) DPLIB-INT-VERSION-242)
length of sys_adm_ext is 364 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 756) [dpxxdisp.c   1287]
     shared lib "dw_xml.dll" version 201 successfully loaded
     shared lib "dw_xtc.dll" version 201 successfully loaded
     shared lib "dw_stl.dll" version 201 successfully loaded
     shared lib "dw_gui.dll" version 201 successfully loaded
     shared lib "dw_mdm.dll" version 201 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3901
Sun Jul 05 21:08:49 2009
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5518]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >salzburgo_PSM_01                        <
DpShMCreate: sizeof(wp_adm)          16464     (1176)
DpShMCreate: sizeof(tm_adm)          3786880     (18840)
DpShMCreate: sizeof(wp_ca_adm)          18048     (60)
DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)          528048     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1296)
DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 055C0040, size: 4419544)
DpShMCreate: allocated sys_adm at 055C0040
DpShMCreate: allocated wp_adm at 055C1BF8
DpShMCreate: allocated tm_adm_list at 055C5C48
DpShMCreate: allocated tm_adm at 055C5C78
DpShMCreate: allocated wp_ca_adm at 059624F8
DpShMCreate: allocated appc_ca_adm at 05966B78
DpShMCreate: allocated comm_adm at 059682E8
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 059E9198
DpShMCreate: allocated gw_adm at 059E91D8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 059E9208
DpShMCreate: allocated wall_adm at 059E9210
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
J2EE server info
start = TRUE
state = STARTED
pid = 5700
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( salzburgo) [dpxxdisp.c   12527]
DpStartStopMsg: send start message (myname is >salzburgo_PSM_01                        <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 201
Release check o.K.
Sun Jul 05 21:08:55 2009
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Sun Jul 05 21:08:57 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2040) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:09:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:09:49 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2168
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64999
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:09:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1440
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2126) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:10:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:10:29 2009
J2EE server info
start = TRUE
state = STARTED
pid = 5484
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64997
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:10:32 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1532
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2133) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:10:49 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:11:09 2009
J2EE server info
start = TRUE
state = STARTED
pid = 3348
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64996
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:11:12 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1436
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2144) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:11:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:11:49 2009
J2EE server info
start = TRUE
state = STARTED
pid = 1868
argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64995
argv[5] = -DSAPSYSTEM=01
argv[6] = -DSAPSYSTEMNAME=PSM
argv[7] = -DSAPMYNAME=salzburgo_PSM_01
argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jul 05 21:11:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2152) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Sun Jul 05 21:12:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
Sun Jul 05 21:12:29 2009
DpEnvCheckJ2ee: switch off j2ee start flag
Best regards,
Jou00E3o Dimas - Portugal
Edited by: Jou00E3o Dimas on Jul 5, 2009 11:39 PM

Hi uday kumar,
First thank you to tried to help me!
--> So... I have a problem... in that checked that you asked, I donu00B4t have acess to all clients in system... Iu00B4m only able to login to client 000 and 100 and in that clients that two users SAPJSF and J2ee_admin donu00B4t exist!! But maybe in 001... I donu00B4t know!! Itu00B4s any other way to know that? I think through configtool in j2ee directory... but I donu00B4t get that, maybe because I donu00B4t have the JAVA part active!!
--> And other thing, you recommed me to "Check the profile parameters once, try change the JVM setting and check were you able to start the server"... What you want to say with JVM setting.. sorry Iu00B4m still newest in sap world... can you explain me better what you wanted to say..?! Thanks.
--> Other think and the last... I checked the sapstartsrv.log in D:\usr\sap\PSM\SCS00\work directory path and in that it said this:
trc file: "sapstartsrv.log", trc level: 0, release: "700"
Mon Mar 09 11:13:46 2009
<<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND
Can you help me?!... thanks a lot!
Best regards,
Jou00E3o Dimas - Portugal

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

If you want to use JMS with AQ as datastore then there is some configuration you need to do to enable this. This is outside SOA Suite per sa, e.g. no adapter required.
If you want to connect to the AQ direct then use the AQ adapter.
this blog may be of some help understand the configuration
http://biemond.blogspot.com/2008/01/oracle-jms-with-esb-and-bpel.html
cheers
James

Connecting to multiple JMS queues

Hi,
I need to connect to multiple JMS queues that all have different username/passwords however I'm struggling to find where to add these details.
In the past we have used the args -Dtibco.default.user=xyz -Dtibco.default.password=1234 on the Server Start tab when connecting to a single queue.
Clearly this won't work for multiple queues.
I have tried adding the details on the bridge source but it doesn't seem to make any difference. Any ideas?
Thanks
Willy

Hi Willy,
This is definitely the week for interop questions.
There are two opportunities that I know of to pass username and password on a bridge source destination. There are the "username" and "password" attributes, which I assume would work in most cases. Not sure. There are also the JNDI properties, presumably via the standard strings "java.naming.security.principal" and "java.naming.security.credentials".
It would be interesting to see the full stack trace that your getting.
Tom
PS. It's been my experience that many applications don't need to use a bridge for retreiving foreign vendor messages as they can simply receive from foreign vendors directly. For example, via a combination of MDBs and the Foreign JMS facility. For more information see [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E12839_01/web.1111/e13727/interop.htm#JMSPG553 ].

Multiple queue receivers with disjoint message selectors - portable?

Hi all,
I was wondering whether an application that uses multiple queue receivers with disjoint message selectors would be portable across different JMS providers.
I fear it's not - at least the spec clearly states that the implementation of message delivery to multiple receivers is provider specific, and I couldn't find any comment that this would be different with disjoint selectors. But I wanted to check with you - maybe I missed anything?
What could be an alternative then (in case you want to avoid multiple queues)? Using a topic with durable subscribers?
Regards,
Sabine

Hi Nimo,
accepted - as long as the JMS spec requires the JMS provider to support multiple receivers. And that's exactly the point where I'm not sure...
Literally it states:
"For PTP, JMS does not specify the semantics of concurrent QueueReceivers for the same queue; however, JMS does not prohibit a provider from supporting this."
The formulation "does not prohibit" makes me think that JMS allows providers also not to support this, for example, to throw an exception when a second consumer is created for the same queue, or not to serve it at all with messages as long as the first consumer is active. Not that I think it would be a very useful implementation - I just want to know if it would be possible. In that case, the application would not be portable.
Regards,
Sabine

SB-Messaging adapter doesn't work behind firewall

Using BizTalk 2013 and the SB-Messaging adapter to retrieve and send messages from Microsoft Azure Service Bus Queue's and Topics.
The Internet proxy and firewall are blocking all the outgoing TCP Ports but the HTTP (80) and HTTPS (443) port are open.
The SB-Messaging receive location is configured correct but the messages are not being received. There is nog error message in de event log.
The SB-Messaging send port is configuerd correct, but the messages are not being send. This is the error message:
A message sent to adapter "SB-Messaging" on send port "SP_Queue_SB-Messaging" with URI "sb://myesb-o.servicebus.windows.net/testmessagequeue/" is suspended.
Error details: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://myesb-o.servicebus.windows.net:9354/. The connection attempt lasted for a time span of 00:00:20.9927053. TCP error code 10060: A connection attempt failed
because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 65.52.128.246:9354. ---> System.Net.Sockets.SocketException: A connection attempt failed because
the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Why does the SB-Messaging adapter not work over the HTTP(S) connection? Why does it not fall back to the HTTP protocal?

Have you installed Windows Azure SDK v2.2 from the SDK site
here ?
If not try installing it and restart the host instance.
Reference can be taken from
blog post
If above does not resolve your issue,I would also suggest to open ports from range 9350 to 9354 .
Also go through below links to get more understanding.
ConnectivityMode
ConnectivitySettings.Mode
Thanks
Abhishek

Http to Abap Proxy communication with multiple queues generation in Recevr

Dear SDNs,
I need some help in the following scenario, appreciate your suggestions and help .
I am receiving the messages from sender to PI on http posting, from PI I am sending the message to SAP system using receiver xi communication channel ( receiver is abap proxy).
Sender will send the messages in QOS=EOIO, QUEueID=XXXt_100 etc parameters, when large volumes cases, it is getting delayed to process it using a single queue.
We are thinking to dynamically generate multiple queues in PI and send the same queue ids to receiver SAP system to process all the messages quickly in SAP System also.
Help /Clarifications needed:
1. XI receiver communication channel in pi does not provide any options to generate dynamic queue id based on payload content (using dynamic configuration) and sent it to SAP.
2. Module Tab in receiver communication channel also got disabled to add custom adapter modules, can we add custome adapter module on xi receiver channel to generate dynamic queue id ?
Really appreciate your immediate help and suggestions.
Thanks.
Suraj.

Dear Praveen,
Thanks lot for the immediate reply, we need to use EOIO, as the messages need to be processed in the same order we send and receive, there is no flexibility in QOS=EOIO, Appreciate if there is any other thoughts?
Thanks In Advance.
Suraj.

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

PI7.1 JMS Adapter - connect to NW6.40

Hello,
We are facing following problem on SAP PI:
We have a scenario where PI (version 7.1) is connecting to another SAP NetWeaver system (version 6.40). There is an application that reads/puts messages from/to JMS Queues running on this system. PI has to connect the JMS Provider of 6.40 system and read/put these messages from/to these JMS Queues.
This scenario worked fine till we used XI 3.0 (NW6.40). We configured sender JMS channel with link to remote JMS Server and parameter "force_remote".
After installation of new PI7.1 we noticed some issues:
1.the connection is unstable. Sending JMS messages from PI to NW6.40 queue works a while but then we get error like this:
Adapter Framework caught exception: Unable to write new JMS message body for message: 00237d29-13fc-02ed-ba85-01d046631592: ConnectorException: Connector for ConnectionProfile of channel: EON_CC_jms_rcv_omsmessageon node: 922834950 having object id: 70855b1c6c483e869982ea2fe9787b36 was unable to create a new javax.jms.TextMessage message: javax.jms.IllegalStateException: Session is closed.
2. we cannot read messages from JMS Queue of NW6.40 at all. The messages are there in queue, communication channel is running and succesfully connected to queue but no message is processed and no error shows in communication channel monitoring.
Has anybody solve similar problem with connection between 7.1 and 6.40 NetWeaver?
I think the problem can be backward incompatibility of 7.1 SAP JMS libraries against 6.40. If this is true then the question is whether it is possible to deploy old libraries and run them simultaneously with native 7.1 libraries?
Thanks

problem sorted - factory property settings were not configured correctly in JMS Adapter connection pool

Multiple Queues(Content Specific) - Can't get more than two queues

Hi,
I have a ccBPM scenario, which collects messages read by the file adapter and then sends them grouped.
It's working fine in many different configurations, but I'd like to configure it in a way described in the PDF "How Tou2026 Configure Inbound Processing in ccBPM Part II: Queue Assignment", which is using Multiple queues - content specific.
If I put 2 queues (after defining a correlation for a message field batchID), it works fine. The messages with batchID=A are processed by one instance process from queue 001, and the messages with batchID=B are processed by another instance process from queue 002.
But if I put 4 queues (SWF_INB_CONF), all the message still keep going to just 2 queues, and not 4. There is no problem, because still the messages with batchID = X are all processed by the same instance process, but I want to add more parallelization to the process using 4 queues.
I've refreshed cache and reactivated, but it will still work with 2 queues and not 4. I've also made sure that the files read have 4 different batchIDs equally distributed among all the files.
I don't know what I'm missing...
Thanks!

Solved it with SAP help.
It seems that even if you config 4 queues (content-specific) to be used in SWF_INB_CONF, it is normal that not all queues allowed are used at runtime. The messages are distributed to the queues based on the correlation defined for the process, narrowing down the result afterwards to the number of allowed queues using a hash algorithm.
Often it is necessary to specify 50-100% more queues to load the actually intended number of queues with messages.
I could reach 4 queues really used setting the parameter to 10 queues.

Error while connecting to JMS queue of weblogic

Hi
I have a bpel process which connects to weblogic queues and puts a message.
These days am getting the following error randomly
WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_TRX_BEGIN.
CCI Local Transaction BEGIN failed due to: ERRJMS_GET_TRANSACTED_FAIL.
nested exception is:
     ORABPEL-12100
ERRJMS_TRX_BEGIN.
CCI Local Transaction BEGIN failed due to: ERRJMS_GET_TRANSACTED_FAIL.
Session.getTransaction() failed
Please examine the log file to determine the problem.
If i resubmit after some time this error goes away.
Can any one give me some idea on what the root cause of the problem is
Thanks
Vamsi

Hi
Thanks for the reply. I have checked out and we are using weblogic.jms.ConnectionFactory. And XA transaction feature is disabled at the weblogic end.
But still the error persists.
The following entries are in the oc4j-ra.xml file
     <connector-factory location="eis/wljms/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="Sample.QueueConnectionFactory"/>
          <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://<IP address>:7001"/>
          <config-property name="acknowledgeMode" value="CLIENT_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value=""/>
          <config-property name="password" value=""/>
          <connection-pooling use="none">
          </connection-pooling>
          <security-config use="none">
          </security-config>
     </connector-factory>
Any further suggestions pls
Thanks
Vamsi

MMP 5.2p2 'waiting for connection; X on queue' errors, X increasing

Shortly after manually upgrading our standalone POP/IMAP multiplexors to 5.2 Patch 2, we started experiencing problems where the CPU utilization of the AService process would drop to almost nothing, and this message would begin to appear in the logs:
20060328 161950 PopProxyAService.cfg (ldap 0x4bb0d8) (uid=redacted) waiting for connection; 10 on queue
20060328 161952 PopProxyAService.cfg (ldap 0x819c50) (uid=another.redacted) waiting for connection; 11 on queue
20060328 161952 PopProxyAService.cfg (ldap 0x817918) (uid=redacted3) waiting for connection; 12 on queueThis message continues with the value increasing:
20060328 163719 PopProxyAService.cfg (ldap 0xcae928) (uid=redacted4) waiting for connection; 235 on queue
20060328 163733 PopProxyAService.cfg (ldap 0xcb13c8) (uid=redacted5) waiting for connection; 236 on queue
20060328 163809 PopProxyAService.cfg (ldap 0xcb5250) (uid=redacted6) waiting for connection; 237 on queue... until AService is restarted.
At first blush, it looks like something is making the LDAP connection wedge, and it's not timing out for some reason, but that's a guess.
I see that someone on the Info-iMS list had the same problem shortly after installing 6.1 back in September 2004:
http://lists.balius.com/pipermail/info-ims-archive/2004-September/019517.html
Has anyone else seen this or know if this has been identified as a specific bug ... or is a symptom of something else?
Royce

That's the problem. THere IS no timeout for the
situation you've gotten into, where MMP (or messaging
server itself) believes a connection exists, and is
active, but gets no response.That's unfortunate. It sounds like a useful timeout for a number of circumstances.
The solution is to refresh all connections so you
don't get into this situation.Unfortunately, the LdapRefreshInterval doesn't appear to be a documented option for 5.2p2, but only for 6. Can you confirm this?
The overhead of binding and unbinding once every 10
minutes or so is very, very minimal.Fair enough.
The latter, if it exists, would be a much more
precise way of handling our symptom. Well, actually, the real problem is that the
connection between MMP and LDAP is getting silently
severed by the load balancer. That's something
that's BAD for both LDAP and for MMP.
Causes fd leaks in ldap, as it never knows when to
close what it beleives is an active connection. It
will attempt to close, but, since it can never get an
ack back after the load balancer severs the
connection, it can't fully close it.
This is truly a bad situation, and it's easy to fix.
recycle the connections before the LB cuts you off.It looks like our LB has an idle timeout of 1 hour, with any traffic at all resetting the timer. In other words, it doesn't look like the LB that's causing the wedge. There is also no internal LB probing going on.
From ulimit/plimit/pfiles output, I've also learned that the slapd user currently has a 65536 FD cap. I've been monitoring the FD usage of the slapd process for the past couple of days, and our LDAP servers have not been getting above 1000. We've also had multiple lockups in that period of time. So running out of FDs may not be causing our problem.
You're very clear about what you want.
Unfortunately, you are not correct about what is
s possible.Perhaps our definitions of 'possible' need some negotiation. :) You're saying that the MMP can't do this today, which I accept as fact. But the pieces are all there, as far as I can see.
The MMP keep close track of how many queries have been served by a particular LDAP connection, how many are on queue without being serviced, and the age of the existing connection. In other words, the app has all the information necessary to do what I'm describing: notice that a connection hasn't actually gotten a response back in X seconds, and terminate it.
Since the app doesn't support what I'm yearning for, this is academic at this point, so I agree that it's time to take a different tack. I don't want to appear ungrateful for your responses. I appreciate the time you've spent on this issue with me. I'm just trying to understand the underlying issues.
So I find myself in these unfortunate circumstances:
1. 5.2 doesn't lock up.
2. No other applications using our LDAP are experiencing any hung LDAP connections (neither at the TCP level nor at the LDAP application level), even though they're using the same LB front-end.
3. From the output of plimit/pfiles, our LDAP servers are configured to handle far more file descriptors than they're consuming. The FD theory appears to not apply.
4. Our LB is configured to time out after 1 hour of inactivity.
5. It seems unlikely that any of the LDAP connections coming from the MMPs are reaching the 1-hour threshold, considering how high-volume they are for POP, unless they are distributing queries across connections very asymmetrically. Even at 3am, there are enough people who leave their computers on all night who check every 1 minutes that the connections are almost never idle for more than a few tens of seconds.
Based on the above, it's hard for me to not conclude that 5.2.p2 appears to either have a regression bug that's causing the wedge itself, or has changed the way that it handles some types of timeouts.
We cannot use 5.2 because we need a bugfix that is in 5.2p2. We appear to not be able to use 5.2p2 because it has this lockup problem that 5.2 does not.
My 'strings' search for LdapRefreshInterval on the AService binary and Pop/IMAP libraries turns up nothing. Can you confirm that 5.2p2 does or does not support this feature?
If not, and the only solution is to use LdapRefreshInterval, do you know if II can run 6.x MMP on our multiplexor boxes and leave 5.2 running on our back-end systems?

Multiple Queue Assignment for Integration Process - PI 7.11

Hi,
I am trying to configure multiple Queues for an Integration Process.
The Integration Process is straight forward, except for a Asynchronous Request Response pattern with correlation. (A asynch send step - immediately followed by a asynchronous receive step with Correlation)
I have done the following
1) In IR set the Queue as Multiple - Content Specific
2) In SWF_INB_CONF transaction reconfigured Multiple Queues - Content Specific without buffering
But when I trigger the message, the message is not at all triggering/entering the Integration Process. The error message is BPE Internal Failure.
But if I reconfigure the IP as One Configurable Queue & "Without Buffering", it is working. But we want multiple queues assigned to this Process.
Thanks in advance.
Regards,
Sudharshan N A

Bjoern, there are blogs/wikis available which should be searched before a question is asked on forum. The information you need is quite basic one and I will therefore lock this thread.
Regards,
Prateek

I can no longer log into my ichat linked to my gmail. right after opening up ichat, receive the following message: lost connection with jabber. the server has unexpectedly disconnected.

i can no longer log into my ichat linked to my gmail. right after opening up ichat, receive the following message: lost connection with jabber. the server has unexpectedly disconnected. how to troubleshoot? thanks.

Hi,
There can be many reasons why the Login is "up the creek".
Any break in the network at your end whilst logged in will cause an issue.
A sort of discrepancy between what iChat thinks the state should be and what the server thinks.
If they don't agree the server will refuse to accept.
A Crash at the server end which does not log you out properly will also do it.
Any file at any time can be come corrupted.
Luckily with the iChat .plists they are recreated if removed with an iChat Restart.
If it were AIM you can also get your Account Suspended and this will not log you in.
(It tends to happen from Chat rooms where people notify AIM about bad behaviour (as they see it) and you have to apply to get Un-suspended).
Most of the big IM services use multiple servers.
Sometimes these go out of Sync.
In the case of AIM this happens when they remove Old unused Screen Names from people's Buddy List prior to making them available for re-registration. I am not sure if this happens at Google.
You seem to be talking about an account that has worked at Work and having new computer at home.
As I mentioned the Priority thing you have not said that it has coincided with the new computer logging in (this will kick the work Computer out of Google whether you are logged in on the Web Mail page or in iChat)
IN addition to that iChat stays partially logged in for Off Line IMs
This is done in the background by a support app called iChatAgent
If your Computer is ON but ichat is not started people can still send you Messages.
Instead of saving these on the server until you login iChat will start up.
Depending if the home Mac is effecting the Work Login it may be holding sway over your Login.
Using your girlfriend's login may have booted her Off Line where she normally uses the name/login.
The AIM Side can be specifically set to allow Multiple Logins and therefore NOT allow them. If this happens you get a warning and messages to do something about it.
You do not get these in any Jabber or Google Login as the Priority setting is supposed to take care of it.
If the Login works at the Web Mail Login and on one computer then the .plist on the work computer is the most likely issue.
There is a small chance that a Corrupt Buddy Pic (Home Folder/Library/Caches/com.apple.iChat/Pictures) may be the cause.
Set this folder to icon view and also use the Finder's View Menu > Show View Options and select icon view.
This should show all pics as their icon.
Check that all display properly.
At this point I would try a COMBO version update install of the last Update you did over what you have.
This often corrects hard to trace things
The 10.5.8 COMBO is here
11:28 PM Monday; June 20, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.7)
 Mac OS X (10.6.7),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

SB-Messaging adapter connecting to multiple queues

Similar Messages

Maybe you are looking for