Hi,

I was having problem to make my MDB (MessageDrivenBean) to listen to Websphere Queue. I have created all jms resources accordingly, but still encountered exception : javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03.

-

#2.0 #2019 10 06 18:52:20:914#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000CA0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt to activate endpoint has failed. Attempt number 0#

#2.0 #2019 10 06 18:52:20:914#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#

com.sap.ASJ.jms.000002#BC-JAS-JMS#jms#C0007F00000101E2000000CC0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

There were problems initializing a Message-Driven Bean (MDB) of application sap.com/CRRSRatingEAR. No messages will be delivered to it. For more details, refer to the trace file.#

#2.0 #2019 10 06 18:52:20:915#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#

#BC-JAS-JMS#jms#C0007F00000101E2000000CD0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

ActivationSpec could not be deployed/started due to internal problem, clean up will be performed, the activation spec was  applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.03,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1

[EXCEPTION]

javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts

     at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:193)

     at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:130)

     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:608)

     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:156)

     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:95)

     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:68)

     at com.sap.engine.services.ejb3.facades.internal.impl.server.MessagingFacadeImpl.activateEndpoint(MessagingFacadeImpl.java:43)

     at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:75)

     at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:84)

     at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:206)

     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:912)

     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:438)

     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)

     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:279)

     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:242)

     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:435)

     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478)

     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesSequentially(ParallelAdapter.java:315)

     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:669)

     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2814)

     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:3191)

     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:3353)

     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2726)

     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:109)

     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:80)

     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:48)

     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)

     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:108)

     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:72)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1138)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1027)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:815)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:450)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:224)

     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:904)

     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)

     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)

     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)

     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)

     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)

     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)

     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)

     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03

     at com.sap.jms.client.session.JMSSession.createConsumer(JMSSession.java:381)

     at com.sap.jms.client.connection.JMSConnectionConsumer.<init>(JMSConnectionConsumer.java:37)

     at com.sap.jms.client.connection.Connection.createConnectionConsumer(Connection.java:170)

     at com.sap.jms.resourceadapter.RaActivation.setUpConnectionConsumer(RaActivation.java:221)

     at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:162)

     ... 44 more

-

After I increased the log level, I noticed there was failure in jndi lookup for the queue and connection factory. I check the jndi lookup from NWA, it is available (eg. jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02)

-

#2.0 #2019 10 06 18:52:20:595#+0800#Info#com.sap.jms.resourceadapter.ResourceAdapterImpl#

#BC-JAS-JMS#jms#C0007F00000101E2000000AE0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Starting activation of JMS resource adapter endpoint factory. ActivationSpec is :  applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.02,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1#

#2.0 #2019 10 06 18:52:20:641#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000AF0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt for lookup of destination failed. That could happen for 6.40 applications without application name.An attempt will be performed without the application name. The JNDI name is : jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02#

#2.0 #2019 10 06 18:52:20:646#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B00000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B10000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

First attempt for lookup failed. That could happen for 6.40 application without application name. We will continue with the fallback chain. The JNDI lookup is : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B20000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_global/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B30000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt for lookup without application name failed. An attempt will be performed to use the default connectionFactory instead of the one supplied during deployment. The JNDI name is : jms_vendor_factory_global/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B40000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Will try to lookup factory with lookupString jmsfactory/default/QueueConnectionFactory#

#2.0 #2019 10 06 18:52:20:653#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B50000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jmsfactory/default/QueueConnectionFactory#

#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B60000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

JMS version is 1.1#

#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B70000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Exception listener was set#

-

I have run out of ideas on what is wrong. Please help.

Thanks.

Hi

The jobs scheduled via DB13 is getting failed to schedule and below is the checkdb job log.

LOG:

BR0801I BRCONNECT 7.20 (32)
BR0805I Start of BRCONNECT processing: celtbtfp.chk 2013-07-29 06.15.49
BR0278E Command output of 'sqlplus /nolog < /dev/null':
sh: sqlplus: not found
BR0280I BRCONNECT time stamp: 2013-07-29 06.15.50
BR0279E Return code from 'sqlplus /nolog < /dev/null': 1
BR0302E SQLPLUS call for database instance XXX failed
BR0303E Determination of Oracle version failed
BR0280I BRCONNECT time stamp: 2013-07-29 06.15.50
BR0301E SQL error -12545 at location db_connect-2, SQL statement:
'CONNECT /'
ORA-12545: Connect failed because target host or object does not exist
BR0310E Connect to database instance XXX failed

BR0806I End of BRCONNECT processing: celtbtfp.chk2013-07-29 06.15.50
BR0280I BRCONNECT time stamp: 2013-07-29 06.15.50
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished

For ORA-12545 error,I checked the node name in tnsnames.ora and its correctly defined.

any suggestion to resolve this issue.

Regards

VC

Hello all!

We have some WDJ applications on SAP NW Java 7.3 which uses webservices from SAP backend system (7.01). These webservices developed by us and based on the Function groups.

After upgrade this backend from 7.01 to 7.31 SP 7 we've faced a problem that some of our web-services can't be run anymore. Logs in the Java side sais that there are issues on the service provider side (in our case it's backend system). In the trace files of the backend system we see logs like this:

<?xml version="1.0" encoding="utf-8"?><asx:abap version="1.0" xmlns:asx="http://www.sap.com/abapxml">    <asx:values>        <TRC_RECS>            <SRT_MONI_STATUS_TRACE>                <TS>20130716054915.086702</TS>                <CLASS_NAME>CL_SOAP_RUNTIME_SERVER</CLASS_NAME>                <METHOD_NAME>EXECUTE_PROCESSING</METHOD_NAME>                <PROCESSORID>SOAP_RUNTIME</PROCESSORID>                <PROCESSORNAME>SOAP Runtime</PROCESSORNAME>                <TRC_LEVEL>1</TRC_LEVEL>                <STATUS>E</STATUS>                <TEXT>A SOAP Runtime Core Exception occurred in method
DETERMINE_OPERATION_NAME of class CL_SRT_WSP_RT_CONFIG
at position id 1 with internal error id 1033 
and error text &lt;no error message available&gt;: 
("Message "ZlibIndReadTblsCommonMass{urn:sap-com:document:sap:soap:functions:mc-style}" 
not supported (interface: "ZLIB_FG_WS" binding key:
"50B1FBB961DA0459E10000000A840FEE")") (fault location is 1  ).</TEXT>                <ISREQUEST>X</ISREQUEST>            </SRT_MONI_STATUS_TRACE>        </TRC_RECS>    </asx:values></asx:abap>  

I tried to find posts with similar problem but found nothing.

How we can fix this issue?

regards,

Lev

Hi everyone,

We are using NW7.4 now, but we can't find a suitable NWDS to develop a process project. Since we can't find a suitable NWDS version for NW7.4, we are now using NWDS 7.3 SP09 PAT0004. But while deploying a process project, there comes error: BPM build version not compatible with the runtime version.

Is there a suitable version of NWDS working with NW7.4?

Where can I find it?

Thank you all.

Dear Experts,

Can anybody clarify the TREX version on AIX OS with 64 bit.

We are about to install and all of sudden it came as a blow that TREX is not available on AIX 64 bit.

If not what is the best alternative without changing the OS.

Best Regards,

Srikanth S

Dear Expert,

I would like to define a HTTP Port on a NW 7.01 AS Java that is only accessible from one specific source IP address. Only that specific IP address should be able to access the AS Java via HTTP. All other clients should access the system via HTTPS.

I searched the SCN, Help and SAP Notes, but I could not find any useful information that it is even possible. I know that for NW7.3 AS Java it is possible, but that's not the version we got.

Do you know how to configure the HTTP port on a NW 7.01 AS Java to only accept calls from one source IP?

Thanks a lot for your help.

BR

Fabian

Dear Experts,

In Tcode SM51- hostname is displaying in Uppercase, but we want to set hostname as lowercase like other sap system Development and Production. Upper case scenario is happened in QA System only. Could you please some one advise?

OS -

HP-UX B.11.31 U ia64

Thanks and Regards

Raja

Hello together,

I am just searching for an easy way to automatically collect the expiry date of all installed licenses within Netweaver AS JAVA systems. Has anybody ever come accross this issue and has a nice solution?

Is there a way to do it on the Operating-system level or from within the database? If not may I use some kind of java-code to request the data using the JMX-interface?

Best Regards and thanks in advance,

Jochen

Hi Everyone,

With respect to the subject above, we planning for migration of SAP systems to new data center. As systems are distributed across multiple network domains, we are planning to bring all the sap systems into a Single network domain in New data center.

In the process, we are moving some of the systems (like QA and Dev) initially to new data center. And after a testing, we will be moving to Production systems later to the new Network domain.

Since Dev and QA belong to Domain A(Network Domain) and Prod belong to Domain B(Network Domain).  But Dev, QA and Prod belong to same transport domain.

Since we have Weekly schedule for Production transports. We expect the intermediate steps in migration should not affect the Weekly transport move.

So please suggest whether prerequistes need to be done before the migration and any precautionary measures as well.

Thanks and Regards
Sudha

Hi Experts,

In recent FILE file toSFTP scenario we are facing an issue at SFPT receiver adapter while delivering file to seeburger as:

Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: putFile: Could not connect to remote host; Reason: Could not change to given base directory: \\XXXXXXXXXXXXXX>> Details: putFile: Could not connect to remote host; Reason: Could not change to given base directory:\\XXXXXXXXXXXXXX>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true, >> Description: putFile: Could not connect to remote host; Reason: Could not change to given base directory: \\XXXXXXXXXXXXXX>>Details: putFile: Could not connect to remote host; Reason: Could not change to given base directory: \\\XXXXXXXXXXXXXX>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true

Thanks in advance.

Venakt.

Dears,

     I've followed all the steps mentioned in http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/804bedee-377e-2e10-0f83-d5b33c743dbc?QuickLink=index&overridelayout=true&51342039453959 to create a custom layout and deployed it successfully to the portal, but when I tried to created a new page using Web Page Composer I could not find my custom layout in the list of available layouts.

Note: The layout is available to be used when I try to create a new page directly from the content administration.

Please help what I might be missing.

Thanks and Regards

Sara Kadry

Hi Guys,

We are using DI to develop DC applications, and we've configured a DC in our system, but can't log on to the Name Server, because the url of the Name server is orginized by computer name, see the screen shot below. Dose anybody knows how to change the link of Name Server for DC from computer name to a domain name?

Hello Gurus,

                 we have installed sap erp 6.0 ehp6.

                in this my SAP HR relase is 600 and i have to get it to 604, how can i update this.

                need some inputs on this

thanks and regards