Upgrade JAX-WS stack inside WebLogic 10.3

I have a question on upgrading the JAX-WS stack that is built inside WebLogic 10.3. WebLogic 10.3 JAX-WS RI's version is Oracle JAX-WS 2.1.3 internally and now that JAX-WS 2.2 is out, I would like to use it for my application development. Is there a recommended best-practice on how to upgrade the built-in copy of JAX-WS inside WebLogic or should I stick with including the new jars in my application with prefer-web-inf enabled inside my weblogic.xml file?
Thanks
--Vinny

Hi Pulkit,
If your WebService is not very complex ...then can you please paste it here ...Or can u describe something about your WebService. Like Which kind of methods are there? And Are u using any Asynchronous feature in it?
If you are not using any Asynchronous feature in your webservice then u can try disabling it by adding "-Dweblogic.wsee.skip.async.response=true"
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

Similar Messages

Problem getting XA Datasources to work with Toplink inside Weblogic

Hello,
I am using POJOs inside weblogic 7.1, and I am having some difficulties. Of picked up a jdbc driver called JSQLConnect and it sets up fine from the Weblogic console. This is the only 3rd party XA driver that I have successfully got working inside weblogic.
I've set up the Weblogic datasource in toplink per the documentation/examples I found. I've included a stack trace of where things blow up. From your source code, it looks like the AbstractSynchronizationListener thinks that the unit of work is not active. Thanks in advance for any assistance. Mike
UnitOfWork(2416860)--release unit of work
UnitOfWork(2416860)--JTS#beforeCompletion()
UnitOfWork(2416860)--JTS#afterCompletion()
UnitOfWork(2416860)--release unit of work
ClientSession(2454268)--client released
<May 14, 2003 3:39:10 PM MDT> <Error> <EJB> <010026> <Exception during commit of transacti
on 12:591b650d7f28edb9: weblogic.transaction.internal.AppSetRollbackOnlyException
at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.j
ava:467)
at oracle.toplink.jts.JTSSynchronizationListener.rollbackGlobalTransaction(Unknown
Source)
at oracle.toplink.jts.AbstractSynchronizationListener.beforeCompletion(Unknown Sou
rce)
at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.j
ava:540)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo
.java:92)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(Ser
verTransactionImpl.java:1044)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTran
sactionImpl.java:1581)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransa
ctionImpl.java:237)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImp
l.java:208)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
at com.icat.server.infrastructure.legacyint.LegacyIntegrationServiceImpl_eayqrf_EO
Impl.transferLegacyData(LegacyIntegrationServiceImpl_eayqrf_EOImpl.java:56)
at com.icat.common.infrastructure.legacyint.LegacyIntegrationTask.execute(LegacyIn
tegrationTask.java:165)
at com.icat.common.infrastructure.scheduling.ScheduledTask.executeMyTask(Scheduled
Task.java:142)
at com.icat.common.infrastructure.scheduling.ScheduledTask.run(ScheduledTask.java:
297)
at java.lang.Thread.run(Thread.java:479)

Hi Michael,
I will have to set things up again to try it. I've been in the middle of doing other development and haven't gotten back to the XA Driver attempts again. Can you send me an email where I can fire a note to you directly once I try this again? I will probably need to send you code, etc. Mine is [email protected]
As for your questions, let me address them below:
How are you using XA (e.g. are you talking to two different databases)? Are you using TopLink any differently (e.g. using SessionBroker)? Is your transaction being propagated to multiple servers? What exactly has changed, or have you simply started using a different driver/data source? (Sorry for all the questions, just want to try to hone in on what components we are looking at).
BTW, do transactions ever get started by the client and span multiple server requests?
1) Yep, I am reading from one database, and writing to the other. So its not a two phase commit right now, but we will have one in the future.
2) I'm not using your session broker. We have a framework, where we can get a client session from a named server session. This works pretty well for us. Right now, we are using the same framework to access two databases. I'm just not setting external tx control, session synchornization,etc
3) I can use the third party jdbc driver in a non-XA transaction. So it doesn't seem to be a property of the JDBC driver alone. It seems to be when I attempt to set things up in XA mode.
4) Transactions are controlled at the Session Bean level. They only last for one bean request.
If you have any cycles, I was wondering if you could try getting the XA transaction to work in your environment? I was using Net-Direct's driver, along with Weblogic 7.1 sp1, and Toplink 9.0.3.3 (Build 430). An example of how you got things to work may point out what is different about my useage....

Catalyst 3750 Software Upgrade in a Stack Configuration

I tryed to upgrade IOS using only copy command into flash: and after my 2nd member of stack didn't up - i got next message=
Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_COPY_SW_INITIATED: Auto-copy-software process initiated for systems[bits: 0x0001]
*Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_COPY_SW:
*Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_COPY_SW: Searching for stack member to act
*Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_COPY_SW: as software donor...
*Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_COPY_SW: Software was not copied
*Mar 1 00:03:31.846: %IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED: Auto-advise-software process initiated for systems[bits: 0x0001]
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW:
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW:
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: Systems with incompatible software have been
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: added to the stack. The storage devices on
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: all of the stack members have been scanned, and
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: the software required to make all stack members
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: with each other was not found. The "archive
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: download-sw" command can be used to install
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW: software off of the network from a tar file.
*Mar 1 00:03:31.921: %IMAGEMGR-6-AUTO_ADVISE_SW:
===============================
Next strange thing - i can't see flash from 2nd switch - i use
3750_Core#dir flash:
Directory of flash:/
2 -rwx 676 Jul 22 2005 12:18:23 vlan.dat
3 drwx 0 Jul 18 2005 10:00:16 crashinfo
4 -rwx 10233 Sep 08 2005 04:21:52 config.text
5 drwx 192 Mar 01 1993 00:03:59 c3750-i9-mz.121.11-AX
22 -rwx 6363373 Sep 07 2005 17:00:27 c3750-i5-mz.122-25.SEA.bin
24 -rwx 27 Sep 07 2005 19:11:24 private-config.text
15998976 bytes total (4237312 bytes free)
3750_Core#dir flash1:
Directory of flash:/
2 -rwx 676 Jul 22 2005 12:18:23 vlan.dat
3 drwx 0 Jul 18 2005 10:00:16 crashinfo
4 -rwx 10233 Sep 08 2005 04:21:52 config.text
5 drwx 192 Mar 01 1993 00:03:59 c3750-i9-mz.121.11-AX
22 -rwx 6363373 Sep 07 2005 17:00:27 c3750-i5-mz.122-25.SEA.bin
24 -rwx 27 Sep 07 2005 19:11:24 private-config.text
15998976 bytes total (4237312 bytes free)
3750_Core#
============================
Is't necessary use archive download-sw for upgrade switches in stack? ( like written here -
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00804799d7.shtml

Hello,
I think the command is 'archive copy-sw' rather than 'archive download-sw', check this link:
Incompatible Software and Stack Member Image Upgrades
http://www.cisco.com/en/US/products/hw/switches/ps5528/prod_release_note09186a008020ba45.html#wp61595
Regards,
GP

Upgrade from support stack 12 to support stack 17

Currently I am on a client that has support stack 12 and needs to upgrade to support stack 17. My only question is what are dependencies that will be needed to be able to upgrade to 12 to 17, because I know this will not be a easy move. Any knowledge would help on this issue. Thanks!

just visit http://service.sap.com/rkt-Solman
select your solman version like 7.0, opt for section 'Technology consultants and System Administrators' and then technology configuration learning map
there you will find two sim files for the usage of Mopz in solman, simple usage and normal usage
and refer this SDN guide
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60d6ce0d-734f-2a10-e596-adbce4df51a8
http://help.sap.com/saphelp_smehp1/helpdata/en/45/56dd10b5f62a50e10000000a11466f/frameset.htm

EHP4 Upgrade ABAP+JAVA stack

Hi SDN Team,
We are in the proceess of EHP4 upgrade,now we are at the road map configuration where we got stuck,I is looking for JAVA sca files in XML file but could not found the same and it throw an error,
Trouble Ticket Log
===============
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: SE1
Hostname...........: NA00SAPSAND02
Install directory..: g:/usr/sap/SE1
Upgrade directory..: G:\EHPI\EHPI\java
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
More information can be found in the log file G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
We have added the system in SMSY and download the stack properly and I could see SCA files listed in XML file but still iam stuck the above error
PREPARE_JSPM_QUEUE_CSZ_02
===========================
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter inputFile=EHPComponents.xml
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jul 27, 2010 3:48:22 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jul 27, 2010 3:48:22 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jul 27, 2010 3:48:22 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
Jul 27, 2010 3:48:22 AM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jul 27, 2010 3:48:22 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.141.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
Not sure what to do now.please advise.
Regards
Uday

Hi Uday,
> Jul 27, 2010 3:48:22 AM [Warning]:    >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Warning]:    >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Info]:                      >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of >stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
> Jul 27, 2010 3:48:22 AM [Error]:                       >com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception >has occurred during the execution of the phase.
> Jul 27, 2010 3:48:22 AM [Error]: >com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) >[Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no >components for this system.
I can see in the log that stack xml you are using is not for the system to whom you are upgrading. That is the reason system is rejecting stack file. Please check above extract of logs.
I would suggest you to please generate stack xml file for this system from MOPZ after correctly configuring SMSY and use it. Then your problem will be resolved.
Thanks
Sunny

FileUpload using JAX-WS webservice on weblogic 10.3.5 is taking long time for files greater than 10MB

I am trying to upload a file using JAX-WS webservice which is deployed on the weblogic 10.3.5 server.Even before the code reaches the Service Endpoint lot of time is being spent at the weblogic layer. for files less than 10MB the performance is good but for files greater than 10 MB it takes around 3 mins to complete the request. I did take thread dumps and I see the thread servicing the requests is taking lot of time when executing SAX2DOMEx.characters it consumes around 80 -85 % of time here. Is there anything that I can do to improve the performance here ?
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=37 idx=0x90 tid=16848 prio=5 alive, suspended, native_blocked, daemon
                at jrockit/vm/Allocator.allocLargeObjectOrArray(JIZ)Ljava/lang/Object;(Native Method)
                at jrockit/vm/Allocator.allocObjectOrArray(Allocator.java:349)[optimized]
                at jrockit/vm/StringMaker.toString(StringMaker.java:188)[inlined]
                at com/sun/org/apache/xerces/internal/dom/CharacterDataImpl.appendData(CharacterDataImpl.java:191)[optimized]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:218)[inlined]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:209)[optimized]
                at com/sun/xml/ws/message/SAX2DOMWriterEx.writeCharacters( .java:108)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.handleCharacters(XMLStreamReaderToXMLStreamWriter.java:153)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.bridge(XMLStreamReaderToXMLStreamWriter.java:114)
                at com/sun/xml/ws/message/stream/StreamMessage.writePayloadTo(StreamMessage.java:313)
                at com/sun/xml/ws/message/stream/StreamMessage.writeEnvelope(StreamMessage.java:343)
                at com/sun/xml/ws/message/stream/StreamMessage.writeTo(StreamMessage.java:321)
                at com/sun/xml/ws/message/AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:226)
                at com/sun/xml/ws/handler/SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:87)
                at weblogic/wsee/jaxws/framework/jaxrpc/SOAPMessageContext.getMessage(SOAPMessageContext.java:252)
                at weblogic/wsee/security/wssp/handlers/WssHandler.getSecurityContext(WssHandler.java:318)
                at weblogic/wsee/security/wssp/handlers/WssHandler.preValidate(WssHandler.java:420)
                at weblogic/wsee/security/wssp/handlers/PreWssServerPolicyHandler.processRequest(PreWssServerPolicyHandler.java:25)
                at weblogic/wsee/security/wssp/handlers/WssHandler.handleRequest(WssHandler.java:112)
                at weblogic/wsee/jaxws/framework/jaxrpc/TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
                at com/sun/xml/ws/api/pipe/Fiber.__doRun(Fiber.java:866)
                at com/sun/xml/ws/api/pipe/Fiber._doRun(Fiber.java:815)
                at com/sun/xml/ws/api/pipe/Fiber.doRun(Fiber.java:778)
                at com/sun/xml/ws/api/pipe/Fiber.runSync(Fiber.java:680)
                ^-- Holding lock: com/sun/xml/ws/api/pipe/Fiber@0x83736a70[biased lock]
                at com/sun/xml/ws/server/WSEndpointImpl$2.process(WSEndpointImpl.java:403)
                at com/sun/xml/ws/transport/http/HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
                at com/sun/xml/ws/transport/http/HttpAdapter.handle(HttpAdapter.java:253)
                at com/sun/xml/ws/transport/http/servlet/ServletAdapter.handle(ServletAdapter.java:140)
                at weblogic/wsee/jaxws/WLSServletAdapter.handle(WLSServletAdapter.java:171)
                at weblogic/wsee/jaxws/HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:146)
                at weblogic/wsee/util/ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
                at weblogic/wsee/jaxws/HttpServletAdapter$3.run(HttpServletAdapter.java:311)
                at weblogic/wsee/jaxws/HttpServletAdapter.post(HttpServletAdapter.java:336)
                at weblogic/wsee/jaxws/VerboseHttpProcessor.post(VerboseHttpProcessor.java:39)
                at weblogic/wsee/jaxws/JAXWSServlet.doRequest(JAXWSServlet.java:98)
                at weblogic/servlet/http/AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
                at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
                at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
                at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:300)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:183)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.wrapRun(Lweblogic/servlet/internal/ServletStubImpl;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Ljava/lang/Object;(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(Unknown Source)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:120)
                at weblogic/servlet/internal/WebAppServletContext.securedExecute(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Z)V(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext.execute(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V(Unknown Source)
                at weblogic/servlet/internal/ServletRequestImpl.run()V(Unknown Source)
                at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209)
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

I am trying to upload a file using JAX-WS webservice which is deployed on the weblogic 10.3.5 server.Even before the code reaches the Service Endpoint lot of time is being spent at the weblogic layer. for files less than 10MB the performance is good but for files greater than 10 MB it takes around 3 mins to complete the request. I did take thread dumps and I see the thread servicing the requests is taking lot of time when executing SAX2DOMEx.characters it consumes around 80 -85 % of time here. Is there anything that I can do to improve the performance here ?
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=37 idx=0x90 tid=16848 prio=5 alive, suspended, native_blocked, daemon
                at jrockit/vm/Allocator.allocLargeObjectOrArray(JIZ)Ljava/lang/Object;(Native Method)
                at jrockit/vm/Allocator.allocObjectOrArray(Allocator.java:349)[optimized]
                at jrockit/vm/StringMaker.toString(StringMaker.java:188)[inlined]
                at com/sun/org/apache/xerces/internal/dom/CharacterDataImpl.appendData(CharacterDataImpl.java:191)[optimized]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:218)[inlined]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:209)[optimized]
                at com/sun/xml/ws/message/SAX2DOMWriterEx.writeCharacters( .java:108)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.handleCharacters(XMLStreamReaderToXMLStreamWriter.java:153)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.bridge(XMLStreamReaderToXMLStreamWriter.java:114)
                at com/sun/xml/ws/message/stream/StreamMessage.writePayloadTo(StreamMessage.java:313)
                at com/sun/xml/ws/message/stream/StreamMessage.writeEnvelope(StreamMessage.java:343)
                at com/sun/xml/ws/message/stream/StreamMessage.writeTo(StreamMessage.java:321)
                at com/sun/xml/ws/message/AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:226)
                at com/sun/xml/ws/handler/SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:87)
                at weblogic/wsee/jaxws/framework/jaxrpc/SOAPMessageContext.getMessage(SOAPMessageContext.java:252)
                at weblogic/wsee/security/wssp/handlers/WssHandler.getSecurityContext(WssHandler.java:318)
                at weblogic/wsee/security/wssp/handlers/WssHandler.preValidate(WssHandler.java:420)
                at weblogic/wsee/security/wssp/handlers/PreWssServerPolicyHandler.processRequest(PreWssServerPolicyHandler.java:25)
                at weblogic/wsee/security/wssp/handlers/WssHandler.handleRequest(WssHandler.java:112)
                at weblogic/wsee/jaxws/framework/jaxrpc/TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
                at com/sun/xml/ws/api/pipe/Fiber.__doRun(Fiber.java:866)
                at com/sun/xml/ws/api/pipe/Fiber._doRun(Fiber.java:815)
                at com/sun/xml/ws/api/pipe/Fiber.doRun(Fiber.java:778)
                at com/sun/xml/ws/api/pipe/Fiber.runSync(Fiber.java:680)
                ^-- Holding lock: com/sun/xml/ws/api/pipe/Fiber@0x83736a70[biased lock]
                at com/sun/xml/ws/server/WSEndpointImpl$2.process(WSEndpointImpl.java:403)
                at com/sun/xml/ws/transport/http/HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
                at com/sun/xml/ws/transport/http/HttpAdapter.handle(HttpAdapter.java:253)
                at com/sun/xml/ws/transport/http/servlet/ServletAdapter.handle(ServletAdapter.java:140)
                at weblogic/wsee/jaxws/WLSServletAdapter.handle(WLSServletAdapter.java:171)
                at weblogic/wsee/jaxws/HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:146)
                at weblogic/wsee/util/ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
                at weblogic/wsee/jaxws/HttpServletAdapter$3.run(HttpServletAdapter.java:311)
                at weblogic/wsee/jaxws/HttpServletAdapter.post(HttpServletAdapter.java:336)
                at weblogic/wsee/jaxws/VerboseHttpProcessor.post(VerboseHttpProcessor.java:39)
                at weblogic/wsee/jaxws/JAXWSServlet.doRequest(JAXWSServlet.java:98)
                at weblogic/servlet/http/AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
                at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
                at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
                at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:300)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:183)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.wrapRun(Lweblogic/servlet/internal/ServletStubImpl;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Ljava/lang/Object;(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(Unknown Source)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:120)
                at weblogic/servlet/internal/WebAppServletContext.securedExecute(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Z)V(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext.execute(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V(Unknown Source)
                at weblogic/servlet/internal/ServletRequestImpl.run()V(Unknown Source)
                at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209)
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

Problems deploying a JAX-WS webservice on Weblogic 10.3

Hello Experts,
I have deveoped a SOAP1.2 over HTTP web service using JAX-WS @WebServiceProvider annotation and am trying to deploy it on Weblogic 10.3
The jwsc task is successful. However, I get the following exception when deploying it on weblogic 10.3:
===========================================================================================
####<Feb 16, 2010 12:35:18 PM PST> <Info> <Deployer> <....> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518172> <BEA-149060> <Module OIMTrustedRecon of application OIMTrustedReconEar successfully transitioned from STATE_PREPARED to STATE_NEW on server WLS_ManagedServer_1.>
####<Feb 16, 2010 12:35:18 PM PST> <Error> <Deployer> <psharma-lap> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518656> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266352473562' for task '10'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.async.AsyncResponseBean" failed to preload on startup in Web application: "OIMTrustedRecon".
com.sun.xml.ws.model.RuntimeModelerException: The web service defined by the class weblogic.wsee.async.AsyncResponseBean does not contain any valid WebMethods.
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:262)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
     at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:510)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:182)
     at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:164)
     at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:51)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:53)
     at javax.servlet.GenericServlet.init(GenericServlet.java:241)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
===========================================================================================
Could you please let know if I have done something wrong or am missing something.
Please let me know if you need more information to help me.
Many Thanks,
Pulkit Sharma

Hi Pulkit,
If your WebService is not very complex ...then can you please paste it here ...Or can u describe something about your WebService. Like Which kind of methods are there? And Are u using any Asynchronous feature in it?
If you are not using any Asynchronous feature in your webservice then u can try disabling it by adding "-Dweblogic.wsee.skip.async.response=true"
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

Syncronized upgrade of double stack BI 7.0

Hi All,
We have successfully upgraded our BWD & BWQ which is ABAP+JAVA stack .
we have followed the process of uninstalling the java stack and removing the j2ee and SDM folder and starting the system for the upgrade.
Tomorrow we are going to start BWP , i found the way to syncronize the upgrade in upgrade manual like starting the SAPjup when upgrade asks for syncronization.
Can any one suggest me the process of starting the SAPjup for sync like already upgrade is running with SAPup and just waiting for SAPjup to sync it's just a norwal way of starting the SAPjup ? or anything.
But i am thinking to go in normal what we followed for the BWD&BWQ.
Please suggest...
Thanks,
Subhash.G

How to start the SAPjup now, is it the normal SAPjup activation process what we do for java systems for upgrade..
There´s a separate Java upgrade guide at httP://service.sap.com/instguides, it´s built the same way the ABAP upgrade guides are done (with PREPARE, BIND of support packages etc.)
The way "how it´s done" depends on the application runinng on the Java stack.
Markus

BRF+ Upgrade from JAVA stack to ABAP stack. Tutorials Required.(Beginer)

Dear All,
We are Proceeding with and Upgrade on our JAVA based Stack to ABAP Stack of EHP6.
The new System extensivly uses BRF+ Techonolgy and SAP Workflows.
Could you please Provide certain Basic links to Start of with it? As of now its totally new CONCEPT to start with in coming time for us.
We have skill set avilable in ABAP developemnt,PI,Worklfows and other ABAP object but not so far in BRF+ concept.
If any Tutorails are avaialble then please share across.
PS: I have not been able to Procure " SAP Press Book Availability (BRFplus - Business Rule Management for ABAP Applications)"
Thanks a lot.
Regards
Vishal

Read the papers etc on the Business Rule Framework plus.
Especially take a look at the online training. But be careful with papers for NW 701. This is an old version and you may find stuff in there that is not relevant for you as you are on a much higher release.
There is also a paper that explains how BRFplus can be used in combination with SAP Business Workflow.
Why can't you get the BRFplus book? On the SAP Press page there is also an online version´

EHP Upgrade Issue - Java Stack

Hi,
Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
Error log:
Sep 9, 2009 10:11:51 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Sep 9, 2009 10:11:51 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
Sep 9, 2009 10:11:51 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
I went through the following link , proceeded with option 2, But still getting same error.
Portal Upgrade Issue
Please advise the resolution for the issue I have.
Thanks in advance
Regards
Srinivas
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM

Issue resolved

Upgrade only Java stack to Ehp1 (SAPehpi)

Hi Gurus,
We are currently on PI 7.1, and is considering to upgrade to Ehp1 (primarily for IDoc packaging feature)
and since the IDoc packaging feature is delivered thru a Sender IDoc adapter, which means this seats on the Adapter Engine already (Java stack)
I saw the document for SAPehpi (Upgrading to Ehp1 for a PI 7.1 system) and if i understand it correctly there are two options,
one ABAP + JAVA upgrade and the other is JAVA only upgrade.
So does that mean I can upgrade my Adapter Engine (AAE) to Ehp1 using the JAVA only upgrade option?
My apologies in advance as i have no experience yet in upgrading 7.1 systems
Thanks

> So with that, if we stay on 7.1, then we don't have an option for IDoc packaging (IDoc package inbound to PI will be split into individual IDocs, then will have to use an integration process Collect to re-package it as 1) ?
Even when you apply EhP1, you can use IDoc packaging only, if your sender system is also on SAP BASIS 7.1 EhP1 or SAP BASIS 7.0 Ehp1.
So you should confirm this first.

Create and deploy jax-rpc ws on weblogic 9.2

I am finding a solution how to build a simple jax rpc web service using weblogic 9.2 ant tasks. I cant find a task which generate war out of my implementation.
It have to be JAX-RPC ws (not JAX-WS).
Please help me, I have been searching for hours yet...(without success)
Edited by julius4 at 04/07/2008 3:58 AM

Hi Carmen,
WLS 8.1 provides a spec compliant, full featured JAX-RPC
implementation. Mixing the impl can cause unpredictable and unexpected
results because they share many of the same upper layers, but under the
covers things can be quite different.
If you are looking for J2EE 1.4 web service features, stay tuned...we
are working at flank speed.
Regards,
Bruce
Carmen wrote:
>
Hi All :
I am a beginner and I need help ...!!
as far as I know , weblogic 8.1 is a J2EE 1.3-compliant application server ..so
does this mean that I can't deploy Sun's jax-rpc webservice (which is a standard
way to develop webservices in j2EE 1.4 ) on weblogic 8.1..?
and If I can't , is there a way to configure weblogic in order to deploy Sun's
jax-rpc webservice..?
would you please help me to find the answers..??
Thanks,

EHP4 upgrade question - ABAP Stack and EA-HR

Hi Experts,
My ABAP stack in the ECC system is at 7.01 SP3.
My EA-HR module is at 600 SP38.
We want to upgrade EA-HR to 604 (EHP4) so that we can benefit from some of the MSS functionality but the question is, what ABAP stack level do I need to be on? Is my current version ok or do I need to upgrade?
Can anyone shed light for me on this matter?
Best,
MM

Hi MM,
You can consult SDN Wiki using the following link:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES
Hope it will be helpful,
Regards
Christine

How to reset java upgrade in dual stack upgrade

Hi,
We are working on dual stack upgrade.Now we are in downtime phase for both the stacks.I have situation to reset upgarde now.
I restored DB before downtime phase and jup for java and upg for abap.I am able to reset abap stack.Could anyone please let me know the process to reset java stack.
Thanks

Hi,
In order to reset Java Part, you need to restore file system of the same time-stamp which you have restored for database. Since you have restored DB, so shadow repository of Java Part is already gone, so only you need to restore file system.
Thanks
Sunny

Upgradation of portal application from weblogic 7 to 10

hi!!!
our application was previouslly built on weblogic 7, its being upgraded to weblogic 10. i'm having difficulty in finding the taglib jars in weblogic 10 those are ehuivalent to below jars,
portal_taglib.jar
portlet_taglib.jar
util_taglib.jar
pls anybody help me.......
Edited by megan.21 at 03/19/2008 10:39 PM

Hello,
the final release for WLP is 10.3.6, running on WebLogic Server 10.3.6.
Emmanuel

Upgrade JAX-WS stack inside WebLogic 10.3

Similar Messages

Maybe you are looking for