Oracle8.0.5 dispatcher server

I am a dba for a larger OLTP database,
In peak workload hours,the dispatcher process
will alway dumped .
The below is context of the dump file :
Dump file /ora_log/log/d015_75146_udb1.trc
Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
With the Partitioning and Objects options
PL/SQL Release 8.0.5.0.0 - Production
ORACLE_HOME = /oracle8
System name: AIX
Release: 3
Version: 4
Redo thread mounted by this instance: 1
Oracle process number: 70
Unix process pid: 75146, image:
*** 2000.11.14.14.36.40.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.41.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.43.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.43.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.46.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.47.000
error 18 creating virtual circuit
*** 2000.11.14.14.36.50.000
error 18 creating virtual circuit
*** 2000.11.14.14.37.37.000
error 18 creating virtual circuit
*** 2000.11.14.14.37.37.000
error 18 creating virtual circuit
What can i do ?
Thanks
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Yingguang Li ([email protected]):
Then can I run XSU12 in the client side of oracle 8.1.6?<HR></BLOCKQUOTE>
Yes, add the files .jar to the client classpath variable and compile or run it.
If you are using Oracle JDeveloper it has a library pointing to the xmlparser.
Best regards, Marcelo.
null

Similar Messages

Starting dispatcher server ....Failed to create logfile:

On a test machine we filled the var partition. Now we get the following error when attempting to start-msg
Starting dispatcher server ....Failed to create logfile: No space left on device
The partition has been clear off and has lots of free space. but still bet the above error.
Any ideas?
Thanks,
Darren

Hi,
You may also want to run ./imsimta cnbuild;./imsimta restart. I have seen cases where full filesystems has lead to corruption of the MTA configuration database -- which lead to all sorts of mess.
And if all that fails, you may want to truss the startup and see what file it tried to create/access when it reported that error.
Regards,
Shane.

Dispatcher/server folders are missing under j2ee\cluster

Hi Experts,
We had one portal system and we found the dispatcher, server0, server1 folder and the instance.properties file were missing from one of the instance server.
Another symptom was that we can not see the instance in the configtool. We did't know what happened, could be deleted by someone accidently.
We had daily backup of the disk drivers, so we could restore the whole folder. My question is, we can not even see the instance in configtool, does it mean the instance was also missing on the database? Could restore the whole cluster folder work in this case?
Thanks,
Jason
Edited by: Jason Wu on Nov 3, 2010 9:14 AM

You won't see any server node in config tool if the configuration files are missing. You should be able to restore the missing folders from your last successful backup. You can check the system logs who has logged on to your system and should be able to trace the culprit.

P4 Connection and Dispatcher/Server Threads...

Hi,
I'd like to know what would be the resource impacts of having P4 connection opened on a server in term of theads.
Here is the scenario:
- A stand alone java application starts on a remote server
- It connects to the Nw04s J2ee Engine using P4 either via the Message Server or the Dispatcher.
- It calls an Engine Service passing a its remote interface.
- The service binds it to the J2ee Engine JNDI.
- The call returns
In the end we have a stub pointing to the remove VM bound in the JNDI tree of the J2ee engine.
What does this imply in term of threads in keeping this connection alive? Does P4 books some threads to send and receive requests in the dispatcher?
The problem is that I have around 30 remote clients bound to the JNDI tree and this consumes lots of threads in the dispatcher (more than 60.)
And when I disconnect them, the dispatcher thread pool goes back to a normal value.
Thanks in advance,
Serge.

Hi,
After having asked to the P4 team (many thanks to Atanassov Ivan), if a remote VM connects to the SAP J2ee Engine using P4, it reaches it via the dispatcher and a System thread is reserved in the disptacher to handle this connection.
This System thread is released only if the connection is closed.
It's closed if the remote VM calls the P4Broker's close() method or if the remote VM crashes.
Regards,
Serge.

While Installing ECC6,J2EE engine, dispatcher & server is not starting up..

Hi All,
J2EE engine is not strating up while installaing ECC6(ABAP + JAVA).
std_server0.out details are given below.
stdout/stderr redirect
node name   : server0
pid         : 14544
system name : C28
system nr. : 06
started at : Tue Nov 11 10:23:10 2008
[Thr 8160] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
Loading: LogManager ... 5820 ms.
Loading: PoolManager ... 600 ms.
Loading: ApplicationThreadManager ... 940 ms.
Loading: ThreadManager ... 390 ms.
Loading: IpVerificationManager ... 150 ms.
Loading: ClassLoaderManager ... 160 ms.
Loading: ClusterManager ... 1300 ms.
Loading: LockingManager ...
Please give me an idea about this.
Thanks & Regards,
Kiran Sathyan.

Hi Karteek,
Thank you for your kind attention.
That issue was solved.
I have just stopped the installation and set the VM parameters properly, then restarted the instance manually in MMC.That was successfull.After that, I could continue the installation and I have completed it successfully.
Regards,
Kiran Sathyan.

Migrate Oracle8i DB to Itanium Server from HP PA-Risk Server 64bit

Hi,
We have our existing application & Oracle 8i Database running on HP- Unix - PA-risk processes based 64 bit architecture.
we are planning to buy new hardware i.e Itanium Server for the above existing long application & Database.
My question is do we need to have seprate licence for Oracle 8i DB for new hardware to migrate existing Oracle 8i DB?
Thanks in advance,

As with all licensing questions, you'd really need to contact your Oracle Sales representative. The answer is likely to depend on your existing license agreement, the number of processes and number of cores involved, your country, your relationship with Oracle, your ability to negotiate, etc.
If you are licensed by Named Users, I'd expect you'd be fine. If you're licensed by CPU, I'd expect that the new server would have more CPUs (remembering that Oracle counts CPUs not by sockets but by cores with a platform-specific core multiplier), so you'd have to buy some additional licenses. I would expect that you'd be able to negotiate with Oracle Sales to be able to run the new and old systems in parallel for a brief period of time, but that's something you'd have to get from Sales.
Justin

Oracle8i on Windows 2000 Server - Oracle Instance don't auto start

I've installed the Oracle 8.1.7 on a Dell Pentium III server running Windows 2000 Server operational system. During the installation the Oracle Instance was started up, but after I reboot the computer, the Oracle Listener service and the Oracle service was started in automatic mode but the Oracle Instance do not started though.
My Oracle DBA teacher ask me to run Oradim and edit the Oracle configuration startup parameters. I did, but it didn't solve the problem. The values on Windows registry of the ORA_<SID>_AUTOSTART key is "true". The Dba Studio also gets information form the Oracle server and all the fields seems to be correct with auto-start option, but it didn't work out.
Can someone point me to any text I can read about installation troubles on Windows 2000 Server ?
Thanks in advance.
Jayme.

Hi
I don't have an 8i db to test on but I think it works the same as on 9i.
Check the following parameters in your registry in the key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0:
ORA_<YOUR_SID>_AUTOSTART=TRUE
ORA_<YOUR_SID>_PFILE=<full path and file name of your init file>

"Dispatcher running, server not found" After installing temporary license

hi all,
we have Xi server at stack 03. As the licence expired, we requested for temporay license from SAP Marketplace and updated the same using Visual admin tool. The new expiry date was reflected in the visual admin tool. But once we restrted the WAS, we are unable to log into the visual admin.
"requested object was not found".
when used the url " http://localhost:50000" , it says
" dispatcher runing, server not found"
If anyone has faced simiplar problems, please let us know with some solution.
Regards,
Siva Maranani.

Your server is not running.
Check two things:
1)run jcmon pf=/usr/sap/..../<instance_profile_here
select 20 and then list process to see what is running.
You should see dispatcher, server and SDM running.
In your case the server will show 0 pid.
2) go to the /usr/sap...../j2ee/cluster/server/log/console_logs (I think this is the path....and then look at the latest error logs....
This should give you an idea why the server is not running...
Hope this helps,
John Ryan

Making Server and Dispatcher as windows services

Hi,
How do I make server and dispatch as a part of windows services. So that they can get start when operating system starts instead of going to the folder and clicking on go.bat. Any documentation?
Thanks in advance.
Maya.

Hi Maya,
here is how to do it:
1. Start the Config-Tool (DRIVE:\usr\sap\<J2EE_SID>\j2ee\j2ee_<INSTANCE_NR>\configtool\configtool.bat)
2. Go to: cluster\dispatcher -> NT Service (Tab)
     choose: Enabled NT Service
3. Go to: cluster\server -> NT Service (Tab)
     choose: Enabled NT Service
3. Go to: cluster\state -> NT Service (Tab)
     choose: Enabled NT Service
4. Go to: cluster\dispatcher -> services -> r3startup
     elements = 0
     -> Add
5. Go to: File -> Aply
6. In a Windows CommandShell (CMD) type: DRIVE:\usr\sap\<J2EE_SID>\j2ee\j2ee_<INSTANCE_NR>\configtool\service -install
7. Now you can start State Controler, Dispatcher, Server & from the windows services (in this sequence).
You can also configure the services to start automatic (at windows startup) or not.
Hope this helps,
Robert
PS: You can also consider installing the startup framework with the Enterprise Portal 6.0 SP2 on J2EE 6.20. It's also installed as a windows service and additionaly takes care of restarting processes, which have died/crashed as well as makes possible to unify the clustermanagement (under different operational systems).

Internal server error - processLoanApp of loanGateway1 example

I am receiving an Internal Server Error while attempting to call the processLoanApp operation on the sample service bus example loanGateway1 proxy service. I generated some code from the wsdl definition. The wsdl for LoanStruct defines NumOfYear as an int while the underlying class defines it as a string. This causes a request to fail when the request includes the type of each attribute as part of the request. For example, the following request will fail:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:processLoanApp soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://example.org">
<loanRequest href="#id0"/>
</ns1:processLoanApp>
<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:LoanStruct" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="java:normal.client">
<Name xsi:type="xsd:string">Tyler Durden</Name>
<SSN xsi:type="xsd:string">111-11-1111</SSN>
<Rate href="#id1"/>
<Amount href="#id2"/>
<NumOfYear xsi:type="xsd:int">45</NumOfYear>
<Notes xsi:type="xsd:string">My Note</Notes>
</multiRef>
<multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:long" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">900000</multiRef>
<multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:double" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">5.0</multiRef>
</soapenv:Body>
</soapenv:Envelope>
But if I remove the types from the attributes the request completes succesfully (you can also change the type of the NumOfYears attribute to string and it will work):
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
          <ns1:processLoanApp soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://example.org">
               <loanRequest href="#id0"/>
          </ns1:processLoanApp>
          <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:LoanStruct" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="java:normal.client">
               <Name>Tyler Durden</Name>
               <SSN>111-11-1111</SSN>
               <Rate href="#id1"/>
               <Amount href="#id2"/>
               <NumOfYear>TEST</NumOfYear>
               <Notes>My Note</Notes>
          </multiRef>
          <multiRef id="id2">900000</multiRef>
          <multiRef id="id1">5.0</multiRef>
     </soapenv:Body>
</soapenv:Envelope>
I receive an internal server error. Below is the stack trace I received running this through the service bus test console:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>
[Server CodecHandler] Failed to decode Failed to decode message
</faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0"/>
weblogic.wsee.codec.CodecException: Failed to decode message
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:142)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: com.bea.xml.XmlException: java.lang.IllegalArgumentException: argument type mismatch
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:52)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:351)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:244)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:114)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:351)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:244)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:114)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
Caused by: com.bea.xml.XmlException: java.lang.IllegalArgumentException: argument type mismatch
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:52)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:351)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:244)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:114)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:351)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:244)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:114)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:351)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:244)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:114)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
</detail>
</soapenv:Fault>
</soapenv:Body>
I was wondering if this was a known issue, a bug, or something I am doing wrong?
Edited by jay.perkins at 12/27/2006 7:14 AM

This is a know issue with the sample application. The message sent contains an incorrect namespace and by removing the attribute types you fixed the sample message :)

JES Messenging Server (v6.0) issues: SMTP Error: 4.0.0

Hi,
We've successfully installed Directory Server 5.2, Indentity Server 6.1, Application Server 7.0 update 1, Web Server 6.1 and Calendar Server 6.0 on a Solaris 8 system.
This system is intended for test purposes, hence all the applications are on one system. The production system will be installed on seperate systems as per Sun's recommendations.
Apropos Messenging Server (v6.0)
When I log into the the Web interface I get:
"Quota root does not exist"
If I try to send a message to a local user from the Web interface I get:
"SMTP Error: 4.0.0 temporary error returned by alias expansion: [email protected]"
I get a similar error if I try to mail a local user from outside:
220 trabant.acc.graddelt.com -- Server ESMTP (Sun ONE Messaging Server 6.0 (built Oct 29 2003))
HELO zen.sys.uea.ac.uk
250 trabant.acc.graddelt.com OK, [192.168.104.92].
MAIL From: <[email protected]>
250 2.5.0 Address Ok.
RCPT To: <[email protected]>
452 4.0.0 temporary error returned by alias expansion: [email protected]
When we installed Messenger Server, we selected Schema v2 from comm_dsetup.pl. We would like to use Messsenger Server with Identity Server.
Any suggestions as to how to overcome this issue would be most welcome.
Thanks
Shaun McCullagh
marviQ
Amsterdam

I am getting this error when I sent a mail from Sun Jav messenger express.
SMTP Error:4.0.0 temprorary error returned by alias expension:
how ever , i am able to receive the mails .
I have created one user [email protected] and configured it's account at MS outlook , this user is able to sent the mails to default account [email protected] ,Also [email protected] is obtaining the mails ,On replying to same mail i am getting SMTP error as given above.
what goes wrong ...? any idea...?
FYI...
root@ultra5c # /opt/SUNWmsgsr/sbin/./start-msg
Connecting to watcher ...
Launching watcher ...
Starting ens server ... 1461
Starting store server ...... 1462
checking store server status ........ ready
imap is running already
pop is running already
Starting http server ............................ 1463
Starting sched server ... 1473
Starting dispatcher server .............. 1475
Starting job_controller server ................ 1479
root@ultra5c # ping 192.168.0.64 110
192.168.0.64 is alive
root@ultra5c # ping 192.168.0.64 25
192.168.0.64 is alive
Rgds
chandan

How can i get jdbc2.0 compatible driver for my oracle 8.1.5 client/server

Hi ,
I am looking for a driver that is jdbc2.0 compatible.Apaprently the oci and thin drvers that are shipped with oracle8.1.5 do no support scrollable and updateable resultsets. Can i download the oracle8.1.6 jdbc2.0 compatible drivers and use them with my oracle8.1.5 client/server. if so how do i install it?
Please let me know ASAP!!
It is relly frustrating to find a compatibler driver for the older versions since oracle does'nt provide them
poornima

Yes. For OCI driver, you will also have to have Oracle 8.1.6 client installed as well. http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#_1_

Why did I fail to configure ODBC cartridge of Oracle Application Server 3.0.1 Advance

Firstly, sorry that I don't know if this question is suit for this forum.
Now I want to query oracle8 database through ODBC cartridge of OWAS. My software environment is: Oracle Application Server 3.0.1 Advanced Version, Oracle8 Enterprise Edition 8.0.4. They are installed in a winNT server.
First I installed oracle8 ODBC on this server and configure it successfully(that means I can query Oracle8 through ODBC). Then I configured ODBC cartridge in application server administration. In this process, I don't configure ODBCCartridge specific parameters because I don't known which parameter need to be configured. Last I restart WRB, LISTENER(Admin). I input the URL in Navigator 4.o as the following: Http://tpdcserver.tpdc:8888/odbc/tableprint?database=oracle8&dsn=oracle_data&username=system&password=manager&sql=select+fromALL_USERS
It displayed no correct page but error information: OWB-02002 Driver Failed.
I don't know why. Please tell me. Thank you very much!
null

I have the same problem!
How can i resolve?
Thanks
Nuno

Redirection in web dispatcher

Dear Experts,
I have ABAP backend system and I need to open it to internet. Doing so, I have implemented web dispatcher that is running in DMZ. Up to this point everything went on as desired, but one thing.
When I call the URL http://teidom.com:60000 then it redirects to the target host with the local address http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui. Hereby this is not possible to call the page from internet. This is working only in local network, not in internet. In order to call and view the page from internet, the address has to be intact with no address redirection.
Just to get you closer to understand the situation, here below I wrote down the parameters which I defined for Web Dispatcher (sapwebdisp.pfl).
SAPGLOBALHOST = WebServerRack
SAPSYSTEM = 02
INSTANCE_NAME = W02
DIR_CT_RUN = C:\WebDisp\NTI3867
DIR_EXECUTABLE = C:\WebDisp\NTI3867
Accesssability of Message Server
rdisp/mshost = backsvr.teidom.local
ms/http_port = 8100
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 5003
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
SAP Web Dispatcher Ports
#icm/server_port_0 = PROT=HTTP,PORT=81$$
icm/server_port_0 = PROT=HTTP,PORT=60001
icm/HTTP/redirect_0= PREFIX=/, PORT=8000, PROT=HTTP, TO=/sap/bc/gui/sap/its/webgui, HOST=backsvr.teidom.local
Kind Regards,
Taner Guler

Hi Matt,
It is very kind of you commenting on the subject.
I just want to be sure of the problem that I am facing. My problem is when I call the URL http://teidom.com:60000 from the internet; it is supposed to view the page (information) from ABAP system. But it couldn't.
Web dispatcher is running on the host named 'webdispsvr'
In the firewall I set port 60000 open from internet to web dispatcher server
And in the other firewall (at the back) I set port 8000 open to R3 ABAP system which supplies information to internet.
After setting up the web dispatcher profile according to (thanks Olivier) instructions from help.sap.com
At next stage I started to test
First I tested it in local by URL http://webdispsvr:60000 it works and web browser views the ABAP login windows. From this point of the subject one thing that took my attention was, after pushing enter button for URL http://webdispsvr:60000 then it directly turns to address URL http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui -- <localhost> is a host of where R3 ABAP system runs on (the address redirects to local address which is not wanted situation in the internet as long as it redirects to local URL address)
Second test was in the internet
Behaviour of the system is same nothing changed
When I call URL http://teidom.com:60000, as it happens in local test, it redirects the URL to http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui for this reason page could not be viewed when it is called from the internet.
I hope above information is clear enough to get you understand how bad situation I am in.
Isnt there a way out of this struggle?
Thanks all of you for your great contribution to the situation.
Regards,
Taner

SOAP Adapter - HTTPS w/ client authentication -SSL termination @ dispatcher

Hi,
We have a SOAP client sending SOAP message over SSL to PI. We are using client cert for authentication, but terminating SSL at web dispatcher. In this scenario, i) do we need to configure security for XISOAPADAPTER in Visual admin on PI and ii) do we need to set HTTPS with client authentication security option in SOAp Sender communication channel?
My understanding is that since we are terminatinating SSL at web dispatcher (Server authentication happens between third-party gateway and our gateway and when web dispatcher terminates SSL, client cert for auth is passed via httpheader to PI where it is mapped to UME user with sufficient authorizations) we don't need to set the XISOAPADAPTER security (if it is end-to-end ssl we would i guess set up in V. Admin>Security provider service>clientcertloginmodule for XISOAPADAPTER) and we don't need to set the sender channel as https with client authentication ( it should just be http in SOAP sender channel).
Is my understanding correct? I will really appreciate any clues?
Thanks,
Saurabh

Hi saurabh
follow these links to SAP note
these will be helpful for you
Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
https://websmp102.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=856597&_NLANG=E
Note 856599 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 Mail Adapter
https://websmp102.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=856599&_NLANG=E
Note 870845 - XI 3.0 SOAP adapter SSL client certificate problem
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=916664&nlang=EN&smpsrv=https%3a%2f%2fwebsmp102%2esap-ag%2ede
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=870845&nlang=EN&smpsrv=https%3a%2f%2fwebsmp102%2esap-ag%2ede
regards
Sandeep
If helpful kindly reward points

Oracle8.0.5 dispatcher server

Similar Messages

Maybe you are looking for