Error with JMS adapter
We are using a JMS adapter with XML input files and we are getting the following error:
:#1.#00144F80C55600310000001A00001BC700DD9B18A4E85181#1288983973313#com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer##com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer.handleRetriesOnException(MessagingException, QueueMessage, MessageController)#J2EE_GUEST#223963##<applicationserver_hostname>_<SID>_623765##8bfba530dea111dfbf9b00144f80c556#MS Queue Worker [JMS_http://sap.com/xi/XI/SystemSend]##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#JMS_http://sap.com/xi/XI/System#com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server#http://<hostname>:50000/sap/xi/engine?type=entry#
One that is interesting is that these errors are occurring on application servers only. Could it be that the Integration Server URL is not fully qualified. In the SLD it's just <hostname>, not <hostname>.test.com (as an example).
Any help is greatly appreciated.
Dear George,
Concerning the issue, in the Integration Engine please try increasing the value of the parameter :
- icm/HTTP/max_request_size_KB
from the default size of 100MB to e.g., 2GB.
Kindly go through the following link :
- http://help.sap.com/saphelp_nwpi71/helpdata/en/58/108b02102344069e4a31758bc2c810/frameset.htm
for details.
Additionally, it is recommended to setup a large message queue,
i.e.,
add an entry and appropriate value (e.g., 20480 KB) for the TUNING parameter : 'EO_MSG_SIZE_LIMIT'
using
TCODE
sxmb_adm
Integration Engine Configuration
Select Edit mode and Add the TUNING parameter
I Hope this helps.
Best Regards
Nishwanth
Similar Messages
-
Error in JMS Adapter while communicating with WebSphere MQ 7.5
Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.Problem solved after removing j2ee.jar file from classpath !
-
Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the
connection factory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
ThanksHave you tried cross-domain security or domain trust?
-
Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21 Error MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21 Error Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22 Success The message status set to WAIT.
2010-09-09 11:45:22 Success The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciatedXI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
SAP XI JMS Adapter/ConvertJMSMessageToBinary
SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
SAP XI JMS Adapter/ConvertMessageToBinary
SAP XI JMS Adapter/SendBinarytoXIJMSService -
Hi,
We are connecting to Websphere MQ using the JMS adapter.
The message coming from MQ is a flat structure. So we have configured the Message Transform Bean to do the conversion from plain to xml structure according to
http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter
But when we test a message we end up with this error:
TransportException: No MIME header found at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
I'm not sure if this is related to the content conversion or general settings in the JMS adapter.
Any inputs are highly appreciated.
Thanks
ShakthiHi Shakthi,
Actually, it is the error that tells you where the error took place:
com.sap.aii._adapter.jms_.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
You might also want to refer to this thread: Error in JMS Sender Adpater for a few ideas to solve your problem. In general, it is connected to your adapter configuration. Please review it once again ang you should have the problem fixed.
Hope this helps,
Greg -
Problem with JMS Adapter after upgrade to 7.1
Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PMdoes following JAR files in place in aii_af_jmsproviderlib.sda.
● com.ibm.mq.jar
● com.ibm.mqbind.jar
● com.ibm.mqjms.jar
● connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag -
Error in JMS Adapter Configuration.
Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info
-
Error with jms receiver communication channel
I am new to jms adapter
I am getting ERROR:"Error connection due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure that all needed resources are present in the JMS provider library: com.sap.aii.adapter.lib.sda".
How to resolve this issue?
Please help to me
Thanks
SwathiHi,
Check all the jar files in aii_af_jmsproviderlib.sda
See the list of files from below link
http://help.sap.com/saphelp_nw70/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
or install the drives again i suppose som of jar files are missing on PI box or not deployed correctly.
chirag -
XI 3.0: Preserve trailer spaces with JMS Adapter
Hi everybody
Does anybody knows how it is possible to preserve the trailing spaces in a message coming from JMS adapter?
I have a fixed-length field that is filled with a left space trailer, but the space is removed by (i think) the adapter.
Does exists something similar to "whitespace=preserve" for the datatypes???
Thanks in advance.If somebody is interested, just add the
xml.<structname>.fieldContentFormatting = nothing to the module configuration params.
I derived this one from the configuration guide of the File Adapter -
Error in JMS Adapter Configuration...Pls help..
Hi,
My scenario is that FTP->MQ Queue->Local JMS Queue->XI.
MQ Queue has successfully picked up the files from FTP and posted successfully into Local JMS Queue. But XI is unable to pick them up from Local JMS Queue.
It is giving the following error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '153.88.140.28:ESEALMW303'
Here are the details what I enetered in the Sender JMS Adapter Configuration:-
Transport Protocol-> WebsphereMQ(Non JMS)
QueueConnection Factory Java Class-> com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class->com.ibm.mq.jms.MQQueue
IP address: 153.88.140.28
Server port: 1414
Queue Mgr name ESEALMW303
Channel name MQMA_ESEALMW303_1
JMS queue EAB_MDMTOCBS_LQ01
Any help would be appreciatedSoumya,
Refer Abhy's reply in the below thread
XI JMS error MQJMS2005 : failled to create MQQueuemanager for ....
raj. -
JCA Binding error with FTP Adapter on put operation
Hi
I am facing a problem with put operation with ftp adapter. my soa service will get file from the 1st ftp server (Unix) as attachment and is putting the file on another ftp serve(Unix)r. the put operation is failing with the below error:-
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server. Error sending file to FTP Server. Unable to send file to server. Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Unexpected termination: Socket closed</detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>
this is a SFTP server and the corressponding property is set to true on the configuration. I had also recreated the jndi again & also increased the max connections to 700, but still facing the same issue. Also i am able to ftp the files to this location through filezilla. Also i continously getting the below errors in soa_server1.out:-
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <Unhandled exception for ComponentDN=default/NShoreAccrualConcService!1.0*soa_9113be23-2e93-4e54-9987-2e8ae5a4b2e6/ProcessNShoreAccurals CompositeInstanceId=330020 ComponentInstanceId=330018>
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause :
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server.
Error sending file to FTP Server.
Unable to send file to server.
Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>Unexpected termination: Socket closed</detail>
,code=<code>null</code>}
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:338)
at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:555)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
at sun.reflect.GeneratedMethodAccessor1687.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor1119.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy277.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
>
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <failed to handle message
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server.
Error sending file to FTP Server.
Unable to send file to server.
Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>Error itself indicates the potential issues -
Please ensure
1. Specified remote output Dir has write permission
2. Output filename has not exceeded the max chararters allowed by the OS and
3. Remote File System has enough spaceRegards,
Anuj -
Error with JMS receiver channel
Hi,
We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
After the restart of JMS, we are facing issues with JMS receiver channel.
Some of the responses are delivered, and for few we have the error as described below.
Also, one of the cluster node of the JMS receiver channel has the below error.
Please anybody throw some light on this.
Error description:
" Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.. "
Thanks in advance.
Regards
Bhanu Tiruveedula.Hello Bhanu,
we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
regards,
Ratna -
BPEL: invalid namespace error with DB adapter polling and java embedding
Hello
I'm using bpel 10.1.3.1.0, and I'm experiencing the following problem: I'm am not able to use the SetTitle() function in a process which polls for records using the db adapter.
Steps to reproduce the problem:
- I create a very simple bpel process which poll for records in a table.
- I deploy it, write manually a record in the polled table and the process start.
- I can see the record picked up through the visual flow in the console
- everything looks ok and the process ends correctly
- now I add a java embedding activities just after the receive
- I set the instance title like this: setTitle("Go");
- redeploy, write a record in the polled table and the process start.
- but the process ends in error with the following message "XMLDOMException has been thrown. invalid namespace for prefix xmlns"
And there is no way to make it work. Consider:
If I put the same java embedding activity in another process, for example a simple asynchronous process which just copy the input to the output, and I run from the console, the instance title is set as I want ("Go")
If I remove the three lines from the polling process
<bpelx:exec name="Java_Embedding_1" language="java" version="1.3">
<![CDATA[setTitle("Go");]]>
</bpelx:exec>
then the process is executed correctly again. I add them again and then namespace error.
Whatever statement I put in the java embedding activity (for example a string concatenation or even just a comment I have the same result: invalid namespace for prefix xmlns.
Does anybody has a suggestion to evercome the problem? I need to set the title because its a mess to find out which instance processed a specific record.
Thanks by
PaoloI made a lot of further tests, and I can say the problem is related only to the database adapter polling mechanism.
If I create an asynchronous process, with any kind of database activity (for example select) I can set the title normally.
If I create a process which start with database table polling, then I cannot use the java embedding.
try this:
- create BPEL empty project
- drop a database adapter service and follow the wizard:
- select a connection (I tried both oracle or sqlserver connection)
- select "poll for new or changed record"
- select any table empty or with few record inside (1 or 2)
- press next 4 times
- chose delete record after read (press next)
- chose order by "no ordering" in polling options (press next 2 times)
- now drop a receive activity on the process, and connect with the polling partner link
- drop a java embedding and write any valid java statement
- deploy; if the table is empty, write a recod in the table
- the process is instantiated, but the it fails in the --> receive <-- activity with "invalid namespace" error -
Esb parallel processing problems with jms adapter and bpel
Hi,
I have esb project which dequeues from a jms adapter and then the esb router calls a bpel process. This bpel process takes about 10 seconds. The first step this bpel does is to return true ( to the client) to the esb router so the ESB thinks he is ready. This does not work.
Now if I use in the esb router asyn routing rule to the bpel ws then the esb dequeus all the messages from the queue. All the esb entries are green. But the esb starts one for one the bpel process and then updates the esb entry with a new start time ( very strange) .
If I use a sync routing rule then it dequeues and call the bpel process one for one.
How I can parallel proces the jms messages ,because I have 2 quad cores cpu's . Async routing rules looks like the solution.
How can the esb detects the bpel is still running even with the first action in bpel is to return true. I expected when the esb retrieves true from the bpel ws it ends the current esb entry and goes on with the next. So the total esb time takes a few seconds and not so long as the last the bpel proces finishes.
And why is he updating the starting time.
Thanks Edwin
Message was edited by:
biemondI have esb project which dequeues from a jms adapter
and then the esb router calls a bpel process. This
bpel process takes about 10 seconds. The first step
this bpel does is to return true ( to the client) to
the esb router so the ESB thinks he is ready. This
does not work. I am not sure if it can ever work, if you reply and then still proceed with your BPEL process.
Here is something I would like to suggest:
Can you try ESB -- (sync) --> BPEL, where BPEL process itself is Async. In that case, esb will consume all the messages very fast and BPEL will get that message and put in Delivery Queue and reply back to ESB. Now BPEL will process them simultaniously based Receiver/Worker threads defined in your env.
HTH,
Chintan -
Unable to get BPEL composite with JMS Adapter running.
Hello All,
I have tried to build a BPEL Composite to use JMS Adapter, by following the link http://blogs.sun.com/malkit/entry/oracle_soa_suite_bpel_to
Steps in WebLogic console:
1. Created a new JMS Server JMSServer-0 (file persistent store) this is targeted to AdminServer
1. Created a new JMS Module SystemModule-0
3. Created a connection factory in this module JNDI jms/SendRecvConnectionFactory
4. Created a queue in this module JNDI jms/ReceiveQueue
5. Created a SubDeployment Subdeployment0 for these two components.
6. Created a new JMSAdapter connection pool JNDI eis/tst/TestJMSConn and set the ConnectionFactoryLocation property to jms/SendRecvConnectionFactory
Next, I created a simple Java client and tested the JMS Queue to work fine. This went well.
Next, used JDeveloper to create a BPEL Composite to use JMSAdapater, and followed the guidelines given in the above URL to create the JCA file.
While deploying this BPEL composite, I hit a warning in SOA diagnostic server:
JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'
As a result of this warning, the BPEL Composite instances do not get created when I send a message from the test client.
Please find herewith the log details.
I am using JDeveloper Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923 and FMW 11g R1 PS3 RC11.
Any help here?
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] BPEL Component "default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess" successfully loaded.
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.deploy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] [Deployment] Component: JMSampleProcess was successfully deployed to service engine:implementation.bpel, for composite:JMSSampleProj
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Initializing OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> OutBound JCAEndpointInteraction::initInteraction - Activating Endpoint Interaction, Endpoint Id='OutBound
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Successfully initialized OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] EventBus not null
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] component : Component Name: JMSampleProcess[[
implementation: oracle.fabric.composite.component.implementation.BPELImplementation@51db9e4
oracle.fabric.composite.model.ComponentTypeModel@51db9e6
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CubeServiceEngine=> initing default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess
[2011-04-20T08:33:12.458-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Loading InBound_jms.jca ..
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing JCAEndpointActivation::prepareActivation for {PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Locating JCA Binding Component instance: SCA_AS11R1
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:[[
endpoint='InBound'
WSDL location='oramds:/deployed-composites/default/JMSSampleProj_rev1.0/InBound.wsdl'
portType='Consume_Message_ptt'
operation='Consume_Message'
activation properties={PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating endpoint (0) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Done preparing JCAEndpointActivation for Service 'InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Successfully loaded InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Initializing InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::performActivation - Performing JCA Endpoint Activation, Endpoint Id='InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing endpoint activation (1) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj Creating new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - starting Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_start: Jms Adapter started
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_endpointActivation: Activating endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_start: Starting endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_run: Calling register...
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - successfully completed endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Successfully initialized InBound_jms.jca
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> :defaultRevisionChanged - updated default revision to default/JMSSampleProj!1.0 for default/JMSSampleProj
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21538] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] Removing temporary directory: C:\DOCUME~1\abhatika\LOCALS~1\Temp\1\sar_base_dir_1303306387379.
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21557] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CompositeDeploymentServlet-----> completed deploying sca_JMSSampleProj_rev1.0.jar successfully. Time spent: 5.188 sec.
[2011-04-20T08:33:13.036-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041fd,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'. Resolved 'jms'Hi,
Try targetting it to soa_server1 instead of admin server.
Maybe you are looking for
-
Need to add horsepower to Power PC G5 (can't afford an Intel one yet)
Hello all. In the ideal world I would buy a new Intel based Mac. Right now I can't afford it nor the cost of replacing all the software. So I must make do with what I have. However, I would like to get the most out of it and so I'm wondering of the g
-
I want to increase my warranty period for another 2 or 3 years in either through online or in near by stores. please guide me.
-
I'm looking for a backup fire wire drive for G3 iBook. I've come across the IOmega 320 eGo. Any comments or suggestions greatly appreciated. Will it work? Which SW? Tx J Aronson
-
Hi guys. I made a video in the standard widescreen dimensions. I then imported the video into flashand reduced the size to 75%. The new dimensions are now set to 540 x 432. Now this should be still a nice widescreen shape but it looks like 4x3 dimens
-
How to create tab in two lines
Greetings, Created set of tabs. but they are displaying in a single line e.g Orientation Sales Day. it is apperaing in a single line and i want to display in two lines like "Orientation Sales Day" How i will achive this target ? Guide pls