Error During SOAP Lookup

Hi,
I'm perforing a SOAP Lookup as explained in the Blog: Webservice Calls From a User Defined Function.
However when i am testing it in Test Tab in message mapping it is showing an error "com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RECV (Party: , Service: AA_BS_RECV, Object ID: 4fb8e1fbeb0e3213a3381de6f63d9542) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out:could be due to invalid address: java.net.SocketException: Connection timed out:could be due to invalid address'. Cause Exception: 'Connection timed out:could be due to invalid address'."
When i test it end to end teh Look up is not returning any Value
Can you please let me know what could be the Error.
Thanks,
Bhargav

Hi Chirag,
I have checked the Target URL and it is correct.
There are no proxy settings so i have not given any authentication details
Thanks,
Bhargav

Similar Messages

Error during JNDI lookup Accessing Remote EJB (access to web service restricted using declarative security model)

Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my web
service with a declarative security model by implementing steps provided in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. When prompted
to accept the digital certificate, click Yes, when prompted for network
authentication information, enter username and password, navigate to the
Test Form tab of Test View, invoke the method by clicking the button and I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I tested my
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order to get
that working. Has anyone seen similar behavior? Is there a known resolution?
Or a suggested way to work around the problem?
Thank you.
Andre

Andre,
It would be best if this issue is handled as an Eval Support case. Please
BEA Customer Support at http://support.beasys.com along with the required
files, and request that an Eval support case be created for this issue.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Anurag,
I removed "t3", still get an error but a different one (Unable to create
InitialContext:null):
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetVisaHistoryTransactions.getVisaHistoryTxn(GetVisaHistoryTransactions
.jws:67) </jwErrorDetail>
</detail>
</error>
Note: inter-domain communication is configured properly. The Web Service to
remote EJB works fine without a declarative security.
Any other ideas?
Thank you for your help.
Andre
"Anurag" <[email protected]> wrote in message
news:[email protected]...
Andre,
It seems you are using the URL
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB
whereas you should not be specifying the "t3:" protocol.
The URL should be like
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB
Please do let me know if you see any issues with this.
Note that this will only allow you to access remote EJBs in the same WLS
domain. For accessing EJBs on another domain, you need to configure
inter-domain communication by
following a few simple steps as mentioned at
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1106135. This link has
been provided in the EJB Control Workshop documentation.
Regards,
Anurag
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Raj,
I tried that before, it didn't help. I got similar error message:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB]</faultstr
ing>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
Anything else should I try?
P.S. AccountDelegatorEJB, the remote EJB my Web Service calls is NOTaccess
restricted.
I hope there is a solution.
Thanks,
Andre
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]...
Andre,
Can you try using the following url with username and password
jndi://username:password@host:7001/my.resource.jndi.object ?
once you add webapp level security, the authenticated is the user who
invokes the EJB.
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/ejb/con
CreatingANewEJBControl.html?skipReload=true
has more info on using remote EJB's.
Hope this helps.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Alla Resnik" <[email protected]> wrote in message
news:[email protected]...
Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my
web
service with a declarative security model by implementing steps
provided
in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. Whenprompted
to accept the digital certificate, click Yes, when prompted for
network
authentication information, enter username and password, navigate tothe
Test Form tab of Test View, invoke the method by clicking the buttonand
I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during
JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookupfailed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260)at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64)</jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I testedmy
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order
to
get
that working. Has anyone seen similar behavior? Is there a knownresolution?
Or a suggested way to work around the problem?
Thank you.
Andre

Prob in IR :Internal error during bean lookup for bean RepObjectAccessBean

Hi,
I am facing the problem in IR .
<b>Internal error during bean lookup for bean RepObjectAccessBean</b>
is the Error window I am getting frequently, After getting this error, It is no allowing to open any of the IR Objects.
Thanks in advance,
Dhanabal T

Hi Dhanabal,
i got the same error. But it is clear.
Please chek once ur configuration part. The error is in configuration part only.
once check all the steps in ur configuration part.
REgards,
chandra.

Error in soap lookup

hi gurus,
i am trying soap lookup and getting the following error.
"Exception during processing the payload.Problem when calling an adapter by using communication channel soap2_chl (Party: , Service: soap2_buss, Object ID: 1ac84b69a3b73e25a0352aab3e1598d4) null" .
but i checked the channel, everything is ok. what may be the problem?
help me.
Thanks in advance.

can you share the code which you are using in the UDF and also the exact names of the business service and communicatio channel. From the error msg looks like XI not able to detect your service or channel.
Cheer's

Error during lookup of remote ejb CaseService - Oracle ACM 12C Standalone

StandAlone Setup:
CD %ORACLE_HOME%\soa\common\bin
set QS_TEMPLATES=%ORACLE_HOME%\soa\common\templates\wls\oracle.soa_template_12.1.3.jar, %ORACLE_HOME%\osb\common\templates\wls\oracle.osb_template_12.1.3.jar
qs_config.cmd
Then ran config.cmd from WLS and extended BPM domain, then was able to see composer app in deployment.
AdminServer Args:
set USER_MEM_ARGS=-Xms512m -Xmx3096m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
Error
====
Error during ejb lookup from bpm services client.
Error during lookup of remote ejb CaseService .
Contact Oracle support if exception can not be fixed.
        at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:86)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
        at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
        at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
        at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
        at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
        at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'ejb.bpm.c
ase.CaseService' didn't find subcontext 'bpm'. Resolved 'ejb'; remaining name 'b
pm/case/CaseService'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:1180)
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
a:265)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
ava:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:21
0)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:22
4)
        at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
ava:253)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
        at javax.naming.InitialContext.lookup(InitialContext.java:411)
        at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:80)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
        at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
        at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
        at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
        at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
        at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
Please help. The problem does not occur with Integrated WLS. I think the config scripts are correctly running from JDev.

Hi,
It's not easy to tell what's wrong with your example.
Maybe you could send me a zip and I'll check when I have some time.
By the way, you're asking a question about the lookup of an EJB3, I wrote an article that covers that topic.
It should give you some interesting input.
http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html
Regards.

SOAP Lookup in PO 7.30 Single Stack.

Hi,
I am creating a scenario from HTTP to File . In between Message Mapping has SOAP Lookup .
But While I executing the Sceanrio, I am facing some error .
Now While reading lots of Blogs over Internet , Some of them pointed towards Creating a Dummy ICO (mandatory in PI 7.30 ) for SOAP Lookup.
So Now my Question are :
1. Why are we creating this Dummy ICO ?? what is the purpose ??
2. How do we create it ?? - Need to know abt Sender Service Interface , Sender Communication channel , Receiver Service Interface ??? What would be these values while creating a Dummy ICO ???
Regards
PS

Hi, the dummy ICO is actually not needed for the lookup, but may fix a bug as stated in your previous thread http://scn.sap.com/message/14054811#14054811 as well as it is meant to test and verify that your SOAP receiver actually works.
Did you follow SAP Help Using the Lookup API in a Message Mapping, especially using a mapping parameter of type Adapter and using the parameter as demonstrated in Implementing Lookups Using SystemAccessor?
I see in your previous thread Error while SOAP LookUp in PI 7.3 Single Stack. that you hardcoded the channel name and business component to retrieve the channel
Channel channel = LookupService.getChannel("BC_Successfactors_Two_D","CC_SOAP_Receive_SessionCreate");
Implement as recommended by SAP Help (above links) may be it solves your problem.

Mail-Adapter Integration Engine Error during parsing of SOAP header

Hello,
we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
pi.RecoverableException: Received HTTP response code 500 : Error during
parsing of SOAP header.
Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
response code 500 : Error during parsing of SOAP header.
Retries exceded, set message
4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
Has somebody else the same problem and solved it or any idea what the matter could be?
Thanks for your help
Christian

Hi Reddy,
We´ve got the following scenario:
Exchange-Server (is always up)
XI Mail-ReceiverAdapter
I use IMAP4 to access the Outlook-Email-Box
Everything works fine. But some Emails aren´t processed.
I think it´s a problem between adapterframework and the integration engine?
There is no difference between the emails?
If you´ll need further informations ask me?
Thanks

Error during parsing of SOAP header

Hi all,
I have configured the j-meter to send an http request to inegration engine of PI.
The request xml that I am sending is as follows:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
<SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
</SOAP:Main>
</SOAP:Header>
<SOAP:Body>
<ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
<Record>
<FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
<BaseUOM>KG</BaseUOM>
<AlternateUOM>GEB</AlternateUOM>
<UnitsInAlternateUOM>100</UnitsInAlternateUOM>
<UnitsInBaseUOM>2268</UnitsInBaseUOM>
<Active_Deleted></Active_Deleted>
</Record>
</ns1:UnitOfMeasure>
</SOAP:Body>
</SOAP:Envelope>
I am getting the following response from the XI:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Any idea as to why PI is not able to parse the request header?
Thanks,
Amit

Hi,
Better to take WSDL from PI(ID window) and try.

Soap lookup error

Hi,
I am trying to use the SOAP lookup within an UDF. The example in Bhavesh blog worked great and when I plug in my web service lookup I have run into all sorts of issues.
My response message from the webservice looks like this:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <GetMappedToValueByIDOutput xmlns:ns1="http://www.abc.com/mappedvalue/output" xmlns=" http://www.abc.com/mappedvalue/output ">
         <ns1:OutputData>
            <ns1:MapValue>This is the mapping lookup result </ns1:MapValue>
            <ns1:MapID/>
         </ns1:OutputData>
      </GetMappedToValueByIDOutput>
   </env:Body>
</env:Envelope>
But I am getting the following error after I plug in the UDF into the message mapping and testing with the integration mapping.
Parsing Error: org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed.'. Cause Exception: 'java.io.IOException: Parsing Error: org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed.'.
Anything that I am missing here?
Teresa

Hi Teresa,
Check this links
http://commons.apache.org/jelly/apidocs/org/apache/commons/jelly/parser/XMLParser.html (for checking your code)
http://wiki.sdn.sap.com/wiki/display/Snippets/JavaSAXParser
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0472795050DB10618552826614657928End?blog=/pub/wlg/9618
Regards
Ramesh

XI SOAP adapter : Error during parsing the SOAP part

Hello experts,
We have several scenarios SOAP to IDocs.
We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
#1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
Many thanks,
Best regards,
Guislain

Hello Michal,
Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
Would you have any other ideas ?
Thanks a lot,
Best regards,
Guislain

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

Error during generation of the WSDL: BUILD FAILED java.lang.NoClassDefFoundError: com/sun/javadoc/Type

When I create an EJB Transport Business Service, after selecting the jar that has the EJB 2.1 artefacts (Remote, Home, etc) the oepe plugin fails and can't continue.
As I understand it seems that there is a problem with the classpath of ant build.xml that oepe creates inside folder /tmp/alsbejbtransport/ to compile the bs and generate the wsdl. I checked if tools.jar is in the classpath (in eclipse) and is included, so I can't figure out wich is the problem.
I found this in Oracle, but not helps solve the problem:
BEA-398120
Error: The WSDL for the typed transport endpoint could not be accessed.
Description
There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration
Action
Contact technical support
This is the the full stacktrace that shows eclipse.
Generate : Error during generation of the WSDL:
BUILD FAILED
java.lang.NoClassDefFoundError: com/sun/javadoc/Type
        at com.bea.util.jam.provider.JamServiceFactoryImpl.createSourceBuilder(JamServiceFactoryImpl.java:205)
        at com.bea.util.jam.provider.JamServiceFactoryImpl.createBuilder(JamServiceFactoryImpl.java:158)
        at com.bea.util.jam.provider.JamServiceFactoryImpl.createClassLoader(JamServiceFactoryImpl.java:137)
        at com.bea.util.jam.provider.JamServiceFactoryImpl.createService(JamServiceFactoryImpl.java:78)
        at weblogic.wsee.util.JamUtil.parseSource(JamUtil.java:152)
        at weblogic.wsee.tools.anttasks.JwsLoader.loadJClasses(JwsLoader.java:186)
        at weblogic.wsee.tools.anttasks.JwsLoader.load(JwsLoader.java:75)
        at weblogic.wsee.tools.anttasks.JwsModule.loadWebServices(JwsModule.java:569)
        at weblogic.wsee.tools.anttasks.JwsModule.generate(JwsModule.java:369)
        at weblogic.wsee.tools.anttasks.JwsModule.build(JwsModule.java:256)
        at weblogic.wsee.tools.anttasks.JwscTask.execute(JwscTask.java:184)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:357)
        at org.apache.tools.ant.Target.performTasks(Target.java:385)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
        at org.apache.tools.ant.Main.runBuild(Main.java:758)
        at org.apache.tools.ant.Main.startAnt(Main.java:217)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.lang.ClassNotFoundException: com.sun.javadoc.Type
        at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1400)
        at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1341)
        at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1088)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
        ... 27 more
Total time: 0 seconds
Eclipse Installation details:
*** System properties:
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=M20110909-1335
eclipse.commands=-os
linux
-ws
gtk
-arch
x86_64
-showsplash
-launcher
{home}/Development/oepe-indigo/eclipse
-name
Eclipse
--launcher.library
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so
-startup
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata
1e418010
-vm
/usr/bin/java
eclipse.home.location=file:{home}/Development/oepe-indigo/
eclipse.launcher={home}/Development/oepe-indigo/eclipse
eclipse.launcher.name=Eclipse
[email protected]/../p2/
eclipse.p2.profile=PlatformProfile
eclipse.product=org.eclipse.platform.ide
eclipse.startTime=1374623921455
eclipse.vm=/usr/bin/java
eclipse.vmargs=-Xms256m
-Xmx768m
-XX:MaxPermSize=512m
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3
-Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
-Dosb.home={home}/Oracle/Middleware/Oracle_OSB1
-Dosgi.bundlefile.limit=750
-Dosgi.nl=en_US
-Dmiddleware.home={home}/Oracle/Middleware
-jar
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
equinox.use.ds=true
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
guice.disable.misplaced.annotation.check=true
harvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
http.nonProxyHosts=localhost
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
java.class.version=50.0
java.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/endorsed
java.ext.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/ext:/usr/java/packages/lib/ext
java.home=/usr/lib/jvm/jdk1.6.0_45/jre
java.io.tmpdir=/tmp
java.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_45/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.protocol.handler.pkgs=null|com.bea.wli.sb.resources.url|com.bea.wli.sb.resources.jca.upgrade.url|weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net|weblogic.net
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_45-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_45
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=20.45-b01
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
jna.platform.library.path=/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator=
middleware.home={home}/Oracle/Middleware
oracle.eclipse.tools.weblogic.ui.isWebLogicServer=true
org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog
org.eclipse.equinox.launcher.splash.location={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
org.eclipse.m2e.log.dir={home}/workspace/pragma/.metadata/.plugins/org.eclipse.m2e.logback.configuration
org.eclipse.update.reconcile=false
org.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6
org.osgi.framework.language=en
org.osgi.framework.os.name=Linux
org.osgi.framework.os.version=3.8.0
org.osgi.framework.processor=x86-64
org.osgi.framework.system.capabilities=osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0, 1.1, 1.2",osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6"
org.osgi.framework.system.packages=javax.accessibility,javax.activation,javax.activity,javax.annotation,javax.annotation.processing,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.jws,javax.jws.soap,javax.lang.model,javax.lang.model.element,javax.lang.model.type,javax.lang.model.util,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.script,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.tools,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters,javax.xml.bind.attachment,javax.xml.bind.helpers,javax.xml.bind.util,javax.xml.crypto,javax.xml.crypto.dom,javax.xml.crypto.dsig,javax.xml.crypto.dsig.dom,javax.xml.crypto.dsig.keyinfo,javax.xml.crypto.dsig.spec,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.soap,javax.xml.stream,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stax,javax.xml.transform.stream,javax.xml.validation,javax.xml.ws,javax.xml.ws.handler,javax.xml.ws.handler.soap,javax.xml.ws.http,javax.xml.ws.soap,javax.xml.ws.spi,javax.xml.ws.wsaddressing,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.css,org.w3c.dom.events,org.w3c.dom.html,org.w3c.dom.ls,org.w3c.dom.ranges,org.w3c.dom.stylesheets,org.w3c.dom.traversal,org.w3c.dom.views,org.w3c.dom.xpath,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers
org.osgi.framework.uuid=901615cd-f3f3-0012-11b6-a3bca4d97ac1
org.osgi.framework.vendor=Eclipse
org.osgi.framework.version=1.6.0
org.osgi.supports.framework.extension=true
org.osgi.supports.framework.fragment=true
org.osgi.supports.framework.requirebundle=true
os.arch=amd64
os.name=Linux
os.version=3.8.0-26-generic
osb.home={home}/Oracle/Middleware/Oracle_OSB1
osgi.arch=x86_64
osgi.bundlefile.limit=750
osgi.bundles=reference:file:javax.transaction_1.1.1.v201105210645.jar,reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110502-1955.jar@1:start
osgi.bundles.defaultStartLevel=4
osgi.bundlestore={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/bundles
osgi.configuration.area=file:{home}/Development/oepe-indigo/configuration/
osgi.framework=file:{home}/Development/oepe-indigo/plugins/org.eclipse.osgi_3.7.1.R37x_v20110808-1106.jar
osgi.framework.extensions=reference:file:javax.transaction_1.1.1.v201105210645.jar
osgi.framework.shape=jar
osgi.framework.version=3.7.1.R37x_v20110808-1106
osgi.frameworkClassPath=., file:{home}/Development/oepe-indigo/plugins/javax.transaction_1.1.1.v201105210645.jar
osgi.install.area=file:{home}/Development/oepe-indigo/
osgi.instance.area=file:{home}/workspace/pragma/
osgi.instance.area.default=file:{home}/workspace/
osgi.logfile={home}/workspace/pragma/.metadata/.log
osgi.manifest.cache={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/manifests
osgi.nl=en_US
osgi.nl.user=en_US
osgi.os=linux
osgi.splashLocation={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
osgi.splashPath=platform:/base/plugins/org.eclipse.platform
osgi.syspath={home}/Development/oepe-indigo/plugins
osgi.tracefile={home}/workspace/pragma/.metadata/trace.log
osgi.ws=gtk
path.separator=:
securerandom.source=file:/dev/./urandom
socksNonProxyHost=localhost
sun.arch.data.model=64
sun.boot.class.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/resources.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/rt.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jsse.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jce.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/charsets.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/jdk1.6.0_45/jre/classes
sun.boot.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64
sun.cpu.endian=little
sun.cpu.isalist=
sun.desktop=gnome
sun.io.unicode.encoding=UnicodeLittle
sun.java.command={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher {home}/Development/oepe-indigo/eclipse -name Eclipse --launcher.library {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so -startup {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1e418010 -vm /usr/bin/java -vmargs -Xms256m -Xmx768m -XX:MaxPermSize=512m -Dsun.lang.ClassLoader.allowArraySyntax=true -Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3 -Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester -Dosb.home={home}/Oracle/Middleware/Oracle_OSB1 -Dosgi.bundlefile.limit=750 -Dosgi.nl=en_US -Dmiddleware.home={home}/Oracle/Middleware -jar {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
sun.java.launcher=SUN_STANDARD
sun.jnu.encoding=UTF-8
sun.lang.ClassLoader.allowArraySyntax=true
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
sun.os.patch.level=unknown
svnkit.http.methods=Basic
svnkit.library.gnome-keyring.enabled=false
user.country=AR
user.dir={home}/Development/oepe-indigo
user.home={home}
user.language=es
user.name={username}
user.timezone=America/Argentina/Buenos_Aires
weblogic.home={home}/Oracle/Middleware/wlserver_10.3
Thanks!!

run this one in command prompt and then convert the applet using converter tool
JC_HOME = C:\java_card_kit-2_2_2\bin\
set CLASSES=%JCHOME%\lib\apduio.jar;%JC_HOME%\lib\apdutool.jar;%JC_HOME%\lib\jcwde.jar;%JC_HOME%\lib\converter.jar;%JC_HOME%\lib\scriptgen.jar;%JC_HOME%\lib\offcardverifier.jar;%JC_HOME%\lib\api.jar;%JC_HOME%\lib\installer.jar;%JC_HOME%\lib\capdump.jar;
D:\NareshPalle\jcardRE\Smart\src>java -classpath %_CLASSES% com.sun.javacard.con
verter.Converter -out EXP JCA CAP -exportpath .\exp -applet 0x0a:0x00:0x00:0x00:0x0e:0x01:0x02:
0x03:0x04:0x05:0x06 PackageName appletName 0x01:0x02:0x03:0x04:0x05:0x0
6:0x07:0x08 1.0
or
go to following directory and run the converter tool in command prompt
step 1: cd C:\java_card_kit-2_2_2\bin\
then run this command under the above directory
step 2:converter -classdir E:\Pathof Your applet class file -out EXP JCA CAP -exportpath E:\path of exp files folder -applet AID PackageName AppletName PackAID major.minor no
For more doubts mail me....
*[removed by moderator]*
Thanks and Regards
NareshPalle
Edited by: EJP on 31/03/2012 20:09: removed your email address. Unless you like spam and unless you think these forums are provided for your personal benefit only, posting an email address here serves no useful purpose whatsoever.

Error in SOAP channel in SAP PI 7.31

Hey Experts,
We have a scenario in which we send IDOCs to our Business Partners via a SOAP channel. It is an asynchronous scenario. However, we are getting the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). Message: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153
If anyone has some information or views to share on this, kindly do so. I have attached a screenshot for your reference.
Regards,
Pritish

Hi Jens,
Thank you very much for your prompt reply to my post. We did go through the note and since we are on Patch 11, we are not sure exactly how relevant it is to us.
However, I would be much obliged if you could clear up one thing. We are using an SOAP adapter to send IDOCs, and the note that you have advocated pertains to an IDOC adapter.
Will the note still be able to help?
Regards,
Pritish

Error During Activation of Web services

When I try to create a web services using RFC and try to complete the steps in the wizard. I am getting error message as "Error during Activation of web services". and also when configure service in wizard, im getting only two profiles as "Basic Authorization: SOAP PROFILE" and "Secure SOAP PROFILE". Kindly do the needful.
Moderator message: please do more research before asking, show what you have done yourself when asking.
Edited by: Thomas Zloch on Aug 8, 2011 1:33 PM

Olivier, thank you so much
SOAMANAGER does not exist in my system (sp level 8), so node "/sap/bc/soap/rfc" should be active. Actually, it is active.
I think the problem is related to user rights/profiles.
I have tried to create another WS after assigning role SAP_BC_WEBSERVICE_ADMIN. The same error when trying to activate it, but now, I can see this WS in SE80 (under "Enterprise Services->Service Definition"). It is not active there and if I try to activate it, a success message appears indicating that user "is not authorized to use function netzwerkadministration". I cannot see any new services in SICF...
Probably the new entry in SICF will be created after activating WS in SE80...
Do u know what user profile should I add in order to properly activate the WS in SE80?
Thank you very much!
Vicente

Error during activation of ExternalWebServiceIntegration

Hi All,
Has anyone got the following error during activation of ExternalWebServiceIntegration?
I am trying to create an ExternalWebServiceIntegration for a SOAP based ERP web service. I am able to create the ExternalWebServiceIntegration using the required WSDL file. But when I try to activate it, I get this error message.
Any idea on what could be causing this?
Thanks,
Sanat

Did you perform a "Check" and see if something's thrown at Output window?
If you don't have enough info to debug, then I suggest you raise an incident.

Error During SOAP Lookup

Similar Messages

Maybe you are looking for