Weblogic 12.1.2 - Tibco Client (6.3l) - through MDB - IllegalAccessError

Migrating to Weblogic 12.1.2 . I am having MDB(EJB 2.1) connecting to Foreign Tibco JMS Server .While connecting ,I am getting below java.lang.IllegalAccessError: tried to access class com.tibco.tibjms.TibjmsxSessionImp from class weblogic.deployment.jms.WrappedTransactionalSession_com_tibco_tibjms_TibjmsXAQueueSession. java.lang.IllegalAccessError: tried to access class com.tibco.tibjms.TibjmsxSessionImp from class weblogic.deployment.jms.WrappedTransactionalSession_com_tibco_tibjms_TibjmsXAQueueSession at weblogic.deployment.jms.WrappedTransactionalSession_com_tibco_tibjms_TibjmsXAQueueSession.setMessageListener(Unknown Source) at weblogic.ejb.container.internal.JMSConnectionPoller.disconnect(JMSConnectionPoller.java:887) at weblogic.ejb.container.internal.MDConnectionManager.timerExpired(MDConnectionManager.java:170) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550) java.lang.IllegalAccessError: com/tibco/tibjms/TibjmsxSessionImp. java.lang.IllegalAccessError: com/tibco/tibjms/TibjmsxSessionImp at weblogic.deployment.jms.WrappedTransactionalSession_com_tibco_tibjms_TibjmsXAQueueSession.setMessageListener(Unknown Source) at weblogic.ejb.container.internal.JMSConnectionPoller.disconnect(JMSConnectionPoller.java:887) at weblogic.ejb.container.internal.MDConnectionManager.timerExpired(MDConnectionManager.java:170) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550) Does Weblogic 12.1.2 supports Tibco client 6.3 ? Am I missing something ? Please help.

First of all "I installed 11.1.2.3 in windows 7 ultimate OS", it is not a supported OS so if you want assistance problem solving you should stick with a supported OS.
It also looks like you have installed a whole range of products some requiring additional configuration and the requirement of SOA.
I recommend starting with a support OS and only install products that are required.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

WLS 10.0 Mp1 - Weblogic startup class to initialize client's SSL channels

Hi,
Is it possible to use Weblogic startup class to initialize client's SSL channels?
Any pointers are appreciated.
Thanks in advance.

Hey
If possible can you explain the issue in detail.
What do you mean by “initialize client's SSL channels”
Regards,
Hussain

Authenticating to weblogic web service using a client cert with webserver

I am trying to think of how to authenticate a client to a weblogic web service
using a client certificate. The wrinkle is that a Web Server (iis or whatever)
will be handling the ssl part and forwarding non-secure to weblogic. The cert
will still be accessable in the request using: HttpServletRequest req.getAttribute("javax.net.ssl.peer_certificates).
At this point it is not clear to me what I can do. When does CertAuthenticator
get called? Can I even use it? Will I have to write my own version of the weblogic.soap.server.servlet.StatelessBeanAdapter
class?
Any help will be appreciated, even explaining why it can't be done.
Thanks,
Scott

I am trying to think of how to authenticate a client to a weblogic web service
using a client certificate. The wrinkle is that a Web Server (iis or whatever)
will be handling the ssl part and forwarding non-secure to weblogic. The cert
will still be accessable in the request using: HttpServletRequest req.getAttribute("javax.net.ssl.peer_certificates).
At this point it is not clear to me what I can do. When does CertAuthenticator
get called? Can I even use it? Will I have to write my own version of the weblogic.soap.server.servlet.StatelessBeanAdapter
class?
Any help will be appreciated, even explaining why it can't be done.
Thanks,
Scott

How do I access the remote(requesting) clients IP address through the Portal API?

How can I access the remote(requesting) clients IP address through the Portal API?
On our 4.5 - IIS system, we can acces it using the Request.ServerVariables("Remote_Addr") in the ASP pages.
We are deploying 5.0 on Java Portal and would like to be able to do this through the Portal's API so I can call it in one of our custom login Activity space or control etc.
I have looked documentation for the HTTPServletRequest object. It seems like we should be able to access it through one of the methods getRemoteAddr if we can get a handle to HTTPServletRequest object through the Plumtree's framework.
I think the XPRequest object encapsulates the HTTPServletRequest but I didn't see getRemoteAddr method listed in the Javadocs.
Is there a way to access the client's IP address through the Plumtree's framework?
I need to do this so we know the location of the user and in our business case we have fixed IP adresss which let us identify which location is user accessign the system from. We can't do this through preferences or profile because we have to use generic userid for the specifc group of users.
Any help on this would be appreciated.
Thanks.
Vanita

Hi, Vanita. For now, you can use
stringsClientIP = HttpContext.Current.Request.ServerVariables["REMOTE_ADDR"].ToString();
Hope that helps!
Sarah

Client request walk through ...

Hi,
Interesting to know the client request walk through.
Like what happens from the "*user submits the input URL in the client machine to the user getting the final output*".
Will be nice if full discussion goes on here.
Thanks & Regards,
SaiRam

Hi,
Please see this thread.
Full cycle ...
Re: Full cycle ...
Regards,
Hussein

I want to know the ways of connecting 9iAS to Database and clients to database through 9iAS as middleware.

My question was about the necessity of implementing OID or any other version of LDAP.
We have a new 9iAS and 8.1.7 database implementation and i have a doubt about their networking architecture.
I want to know the ways of connecting 9iAS to Database and clients to database through 9iAS as middleware. We are debating if OID is compulsory or if we can go ahead with this implementation with out OID.
Can you please help me and provide me couple of implementation designs(i.e connecting clients to database through 9iAS). It would be great if any one can provide me the implementation's with and with out OID.
-Thanks

Hi ,
For all delta and full DTP loads you can get information in table RSICCONT .Check table RSMONICDP this will give you detail information .Here you will get all the information with timestamp and request id .
Hope these tables will serve your purpose .
Regards,
Jaya

Problem in invoking a secure weblogic web service from javaws client

Hi all,
the situation is this: there is a secure web service (Wssp1.2-2007-Wss1.1-X509-Basic256.xml policy) which is accessed by a stand-alone remote web service client (swing-enabled) which is initiated via java web start. You'll probably wondering why this is a special case. Let me elaborate...
The first step was to develop the service and the client. This wasn't much of a trouble, since the documentation was very good apart from creating a ClientBSTCredentialProvider object at the client side. The documentation should explicitly state that the sixth argument, that of the server certificate, is required! In any case, the first step was a success and the invocation was encrypted and signed at the message level.
The second step was to create a stand-alone remote client, without any local weblogic installation. That was a bit of a problem, since wlfullclient.jar or wseeclient.jar or weblogic.jar were not enough. I should note that the client was created via netbeans 7.0 and not with the help of weblogic clientgen. So, I had to make a verbose run from netbeans, in order to enumerate the jars which are accessed and gather them into the same directory. That was OK too. The standalone client works just fine.
The third step is to simply (not so simply...) make a java web start version of the client. Since the previous step was a success (having all necessary jars in the same directory) this one should not be a problem. Well... that turned out to be a huge issue. What I get back as the error message (shown in the java web start console) is this:
java.lang.InternalError: error initializing kernel caused by: java.lang.AssertionError: Duplicate initialization of WorkManager
     at weblogic.work.WorkManagerFactory.set(WorkManagerFactory.java:107)
     at weblogic.work.ExecuteQueueFactory.initialize(ExecuteQueueFactory.java:23)
     at weblogic.kernel.Kernel.initialize(Kernel.java:103)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:64)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.ensureInitialized(WLSRJVMEnvironment.java:50)
     at weblogic.protocol.ProtocolManager$DefaultAdminProtocolMaker.<clinit>(ProtocolManager.java:53)
     at weblogic.protocol.ProtocolManager.getDefaultAdminProtocol(ProtocolManager.java:218)
     at weblogic.protocol.ProtocolHandlerAdmin.<clinit>(ProtocolHandlerAdmin.java:23)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.registerRJVMProtocols(WLSRJVMEnvironment.java:120)
     at weblogic.rjvm.RJVMManager.ensureInitialized(RJVMManager.java:87)
     at weblogic.rjvm.RJVMManager.<clinit>(RJVMManager.java:46)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:97)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:28)
     at weblogic.rjvm.LocalRJVM$LocalRJVMMaker.<clinit>(LocalRJVM.java:31)
     at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:72)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:403)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:395)
     at weblogic.xml.crypto.utils.DOMUtils.assignId(DOMUtils.java:374)
     at weblogic.xml.crypto.wss.SecurityBuilderImpl.assignUri(SecurityBuilderImpl.java:148)
     at weblogic.wsee.security.policy.SigningReferencesFactory.getSigningReferences(SigningReferencesFactory.java:100)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:446)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:335)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:574)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:428)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.constructMessage(SecurityMessageArchitect.java:304)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:138)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:121)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processOutbound(SecurityPolicyArchitect.java:225)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processMessagePolicy(SecurityPolicyArchitect.java:123)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:119)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:91)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processOutbound(WssClientHandler.java:117)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processRequest(WssClientHandler.java:69)
     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)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy29.fetchCSD(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy30.fetchCSD(Unknown Source)
     at exchangecsdclient.CSDExchangeClientImpl.fetchCSD(CSDExchangeClientImpl.java:151)
     at pdfutil.PDFUtilApp.initialize(PDFUtilApp.java:55)
     at org.jdesktop.application.Application$1.run(Application.java:170)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:66)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.ensureInitialized(WLSRJVMEnvironment.java:50)
     at weblogic.protocol.ProtocolManager$DefaultAdminProtocolMaker.<clinit>(ProtocolManager.java:53)
     at weblogic.protocol.ProtocolManager.getDefaultAdminProtocol(ProtocolManager.java:218)
     at weblogic.protocol.ProtocolHandlerAdmin.<clinit>(ProtocolHandlerAdmin.java:23)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.registerRJVMProtocols(WLSRJVMEnvironment.java:120)
     at weblogic.rjvm.RJVMManager.ensureInitialized(RJVMManager.java:87)
     at weblogic.rjvm.RJVMManager.<clinit>(RJVMManager.java:46)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:97)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:28)
     at weblogic.rjvm.LocalRJVM$LocalRJVMMaker.<clinit>(LocalRJVM.java:31)
     at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:72)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:403)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:395)
     at weblogic.xml.crypto.utils.DOMUtils.assignId(DOMUtils.java:374)
     at weblogic.xml.crypto.wss.SecurityBuilderImpl.assignUri(SecurityBuilderImpl.java:148)
     at weblogic.wsee.security.policy.SigningReferencesFactory.getSigningReferences(SigningReferencesFactory.java:100)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:446)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:335)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:574)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:428)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.constructMessage(SecurityMessageArchitect.java:304)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:138)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:121)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processOutbound(SecurityPolicyArchitect.java:225)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processMessagePolicy(SecurityPolicyArchitect.java:123)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:119)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:91)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processOutbound(WssClientHandler.java:117)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processRequest(WssClientHandler.java:69)
     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)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy29.fetchCSD(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy30.fetchCSD(Unknown Source)
     at exchangecsdclient.CSDExchangeClientImpl.fetchCSD(CSDExchangeClientImpl.java:151)
     at pdfutil.PDFUtilApp.initialize(PDFUtilApp.java:55)
     at org.jdesktop.application.Application$1.run(Application.java:170)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
The two invocations (one using java and the other using javaws) should obviously have not differences at all since all resources (jars) are the same.
I have tried all client jar combinations (with wlfullclient.jar, wseeclient.jar, weblogic.jar) and the result is the same. One additional piece of information is that when removing all security parameters (message level encryption and signing) from the web service the java web start client works just fine!!!
This is not an issue of additional jars that somehow mess with weblogic jars, since the same error occurs even in the basic hello world web service.
I wonder if someone has faced the same problem. I would really really appreciate any help. Thank you in advance and keep up the good work.
Cheers,
Paul.
Edited by: PaulP on Jan 11, 2012 5:31 AM

Hi Kal,
since we're currently evaluating the software and haven't acquired a license, we cannot contact support.
I only need to know if this is a solved bug or not. Does it have to do with the classloading process (I cannot think of anything else)?
Thank you again very very much!
Cheers,
Paul.

Weblogic 10.3: web service client enable HTTP/HTTPS connection reuse?

hi all,
i am writing an client app to call a web service, through a client proxy generated by jdeveloper/weblogic.
My question is:
for the weblogic web service client proxy, is it possible to enable HTTP/HTTPS connection reuse/pooling?
i see there is many connection created when calling the web service (by command netstat)?
thank you.
lsp

anybody can help?
thanks

Use of WebLogic in a thin hardware client environment?

We are currently evaluating the use of a thin hardware client (something like the Sun Microsystems Sun Ray 2FS - http://www.sun.com/sunray/sunray2fs/) for a new JEE development effort. I was wondering if anyone could share their experiences using WebLogic in this environment with either Solaris or Linux (i.e. problems, lessons learned, configuration, etc...).
Thank You,
--Dan

We are currently evaluating the use of a thin hardware client (something like the Sun Microsystems Sun Ray 2FS - http://www.sun.com/sunray/sunray2fs/) for a new JEE development effort. I was wondering if anyone could share their experiences using WebLogic in this environment with either Solaris or Linux (i.e. problems, lessons learned, configuration, etc...).
Thank You,
--Dan

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

WebLogic 10.0 JMS Thin Client and JVM 1.4

As mentioned in [WebLogic JMS Thin Client|http://download.oracle.com/docs/cd/E11035_01/wls100/client/jms_thin_client.html#wp1026979], it can be used on JVM 1.4 client, but it seems that wljmsclient.jar and wlclient.jar compiled using java 1.5 compiler with no 1.4 compatibility.
Where can I get a 1.4 complied version of this jars for WebLogic 10 ?
Edited by: user10385140 on 02.10.2008 2:32

Hi,
The doc is correct that the 1.4 JVM is supported for thin 10.0 clients, but note that 1.4 is not supported for 10.3 (the latest version). If you confirm that there's a problem, I recommend contacting customer support. Meanwhile, as a work-around, you can use a client jar from an earlier version (such as 9.2 at the latest MP).
The latest updated version of the 10.0 client doc is at http://edocs.bea.com/wls/docs100/client/basics.html, the link you provided points to an older version of the edoc.
You might want to look at using a generated "full client" rather than a thin client unless a smaller jar size is important in your use case. The reasoning is stated in the updated edoc.
Regards,
Tom Barnes
WebLogic JMS Developer Team
Edited by: TomB on Oct 2, 2008 6:52 AM

Weblogic clientgen task generates soap11 client for soap12 wsdl

I am creating a client using the clientgen task on a wsdl that is based on the soap1.2 spec.
When the client invokes the service , the client code throws an exception complaining that the content type is wrong. The client code is using the content type text/xml to communicate with the service however the service is expecting application/soap+xml for communication.
I realise from the specs that text/xml is used by the soap1.1 spec. Is there any additional setting on the client gen task to make it generate a 1.2 client?
The webservice is deployed on weblogic9.2 and the client code is generated using the clientgen task found in 9.2 version of weblogic.

Hi thanks for your reply.
I was using weblogic9.2 when I ran into this issue. Our webapplications run on weblogic9.2.
Subsequently I tried to build the client using the weblogic jar found in the Aqualogic service bus tier which is on weblogic9.2 M2 and the client is able to connect successfully. I guess some fix has been put by weblogic?
When I looked around I could not find any documentation regarding this issue.
Is there a fix for this issue on weblogic9.2 or any relevant documentation highlighting this issue?
Edited by [email protected] at 11/30/2007 5:45 PM

Does the weblogic server supports c++ corba client /IIOP?

hi:)
I have a c++ corba client interacts with WLS using IIOP. I am just wondering
what ORB i need to use 2) trsaction propagation 3 ) security
thankx,
suresh reddy

I suggest trying the RMI IIOP newsgroup. I do not quite understand your
question.
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Sunesh Kumra" <[email protected]> wrote in message
news:[email protected]...
Hi Michael,
Is it allowed to use your own multi-threaded library from within WLS ?Note that
the WLS Beans do not contain the threads, the threading part is in somelibrary
which the WLS Beans communicates with. Can the Helper classes which arepackaged
with the WLS Beans span threads of their own ?
Most importantly, is it allowed to use some vendor's ORB (for exampleOrbixweb)
within WLS because the thread created by the ORB might interfere with WLS
threads ??
Michael Girdley wrote:
2.1) CORBA client initiated transactions will not be supported,
everything else will workYes, that is my understanding.
2.2) None of the EJB security services will be available in EJB
method
called by a CORBA client (i.e. getCallerPrincipal() andisCallerInRole()
will fail)Yes, that is my understanding. I would suggest that you place this onthe
RMI IIOP newsgroup. The developers who write the code for this feature
actually hang out over there.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"<=one way=>" <[email protected]> wrote in message
news:[email protected]...
1) We must support both C++ and Java clients that will be requesting
services from our EJBs running in WLS. The clients are internal appsrunning
in different companies and we would prefer to avoid requiring our
clients
to
use an ORB by a specific vendor. At the same time we do not want to
deal
with potential problems related to the implementation differences by
different ORB vendors. What would be the best way to handle thissituation?
2) WLS documentation has the following paragraph:
"WebLogic RMI over IIOP is the framework for EJB-to-CORBA mapping
support.
Currently, however, a standard for passing user identity -- requiredto
implement EJB-to-CORBA mapping -- does not exist and the requirementfor
transaction propagation from the client is in question. While RMI overIIOP
does allow CORBA clients to access EJBeans, the following services
will
not
be available:
EJB transaction services
EJB security services"
Does this mean that:
2.1) CORBA client initiated transactions will not be supported,
everything else will work
2.2) None of the EJB security services will be available in EJB
method
called by a CORBA client (i.e. getCallerPrincipal() andisCallerInRole()
will fail)
Thanks in advance
"Michael Girdley" <[email protected]> wrote in message
news:[email protected]...
Yes, check out the documentation on the RMI over IIOP on our web
site.
>>>>
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"indham inc" <[email protected]> wrote in message
news:[email protected]...
hi:)
I have a c++ corba client interacts with WLS using IIOP. I am justwondering
what ORB i need to use 2) trsaction propagation 3 ) security
thankx,
suresh reddy

Accessing Coherence Extend* Proxy Deployoed on Weblogic Coherence Cluster from Java Client

Hi,
I am trying to access Extend Proxy through Thick Java Client
Followed steps as per below links and deployed a GAR on 3 Server ( 2 Storage Enabled Coherence Cluster and 1 Coherence Storage Disabled Extend Proxy Enabled). I could see ExtendProxyService using JMX and can see Port running on the System.
Ref :
Setting Up Coherence*Extend - 12c (12.1.2)
http://docs.oracle.com/middleware/1212/coherence/COHAG/deploy_options.htm#CHDJBJDI
Issue :
When I tried to Execute Java Client to Connect to Proxy Server it Connects to Port and then Disconnects with ConnectionException as below.
Observer below Lines in Box is show he Connected Socket with Port 9099 which is Extend Proxy Port
Error Message
2013-11-08 14:55:55.114/1.202 Oracle Coherence GE 12.1.2.0.0 <D5> (thread=TcpClientRemoteService:TcpInitiator, member=n/a): Started: TcpInitiator{Name=TcpClientRemoteService:TcpInitiator, State=(SERVICE_STARTED), ThreadCount=0, Codec=Codec(Format=POF), Serializer=com.tangosol.io.DefaultSerializer, PingInterval=0, PingTimeout=30000, RequestTimeout=30000, ConnectTimeout=10000, SocketProvider=[email protected], RemoteAddresses=WrapperSocketAddressProvider{Providers=[[DTC37446E9C6CBD/127.0.0.0:9099]]}, SocketOptions{LingerTimeout=0, KeepAliveEnabled=true, TcpDelayEnabled=false}}
2013-11-08 14:55:55.146/1.234 Oracle Coherence GE 12.1.2.0.0 <D5> (thread=main, member=n/a): Connecting Socket to 127.0.0.0:9099
2013-11-08 14:55:55.146/1.234 Oracle Coherence GE 12.1.2.0.0 <Info> (thread=main, member=n/a): Connected Socket to 127.0.0.0:9099
2013-11-08 14:55:55.161/1.249 Oracle Coherence GE 12.1.2.0.0 <Info> (thread=main, member=n/a): Error establishing a connection with 127.0.0.0:9099: com.tangosol.net.messaging.ConnectionException: TcpConnection(Id=null, Open=true, LocalAddress=0.0.0.0:54384, RemoteAddress=127.0.0.0:9099)
2013-11-08 14:55:55.161/1.249 Oracle Coherence GE 12.1.2.0.0 <Error> (thread=main, member=n/a): Error while starting service "TcpClientRemoteService": com.tangosol.net.messaging.ConnectionException: could not establish a connection to one of the following addresses: [127.0.0.0:9099]; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator.openConnection(TcpInitiator.CDB:121)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:11)
    at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:7)
    at com.tangosol.coherence.component.net.extend.RemoteService.doStart(RemoteService.CDB:11)
    at com.tangosol.coherence.component.net.extend.RemoteService.start(RemoteService.CDB:5)
    at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:53)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
    at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
    at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.startService(ExtensibleConfigurableCacheFactory.java:681)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.ensureService(ExtensibleConfigurableCacheFactory.java:599)
    at com.tangosol.coherence.config.scheme.AbstractCachingScheme.realizeCache(AbstractCachingScheme.java:50)
    at com.tangosol.coherence.config.scheme.AbstractBundlingScheme.realizeCache(AbstractBundlingScheme.java:31)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.ensureCache(ExtensibleConfigurableCacheFactory.java:254)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:205)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:182)

If this proxy design (not starting up due to a invalid entry in "authroized-hosts") is on-purpose from Coherence Engineers - then it should be re-visited.
I think the PROXY Server should just log a message stating about the invalid DNS entry for the Authorized-host and continue with the startup...Failing to start completely doesn;t make sense since one cannot rely completely on DNS to
say everything should be correct before a server start.
Ofcourse you can overcome by writing your own Custom Filter - but the issue pop's out as with any custom filter(s) is maintaining them along the road (with all minor/major coherence upgrades).
Also - this "Authorized-Hosts" concept should be carefully analyzed particularly for the following issues...
(1) if the client IP is changed in the DNS server - will the proxy-server allow the new Client connection without any issues? when will the PROXY server flush its CLIENT DNS entries or what is the TTL time-limit for a CLIENT cached through Authorized-hosts by the PROXY-SERVER?
(2) Suppose, we have a CLIENT in the "Authroized-Hosts" making a valid connection to the PROXY and putting some cache into the SERVER CACHE through the PROXY....now if the IP-address (DNS being the same) of the CLIENT is changed - can the CLIENT can GET the CACHE it just PUT into the SERVER without any ERRORS?
(3) How often we need to re-start PROXIES? Do we need to re-start them often for the DNS issues (if any) mentioned above?
Looks like the Limited documentation & examples for Coherence*Extend - particularly for .NET & C++ clients & *Extend Proxies is a point of concern.
vk

WebLogic is not responding to client request under heavy load

Under heavy loading, our WLS 6.0 SP2 will be not be responding to client requests
after some time, say, 1 hour. From the administration console, the request throughput
is 0 while request waiting accumulates to over 1,000. Even the clients stop making
request to the server, the request waiting will not drop. It seems that WLS blocked
on some threads and unable to serve the requests (see attached thread dump for
details).
Our configuration is as follow:
OS: SunOS 5.7
Database: MS SQL Server 7.0 running on NT4 Enterprise Edition.
(JDBC Driver is the one bundled with WLS 6.0)
We know that using 'DriverManager.getConnection()' can cause deadlock in number
of cases but we have gone through all the code but all of our Database connections
are obtained through datasource. And the connection is closed properly in finally
block.
Moreover, the application is originally running on WLS 4.51 but no problem is
encountered.
Does any expert know what the problem and solution are?
Thanks!
[session.log]

It appears that some threads were possibly blocked at some jDriver calls
initially (ExecuteThread 0,10,15,23 of the default thread pool). WLS JTA
subsequently timed out and rolled back the transactions asynchronously. The
first rollback attempt was blocked at the jDriver level (ExecuteThread 18 of
the default thread pool). Each subsequent rollback retry blocks an
additional execute thread (due to a JTA bug that is fixed in WLS 6.1, but
not 6.0 SPs) - ExecuteThread 1-9,11-26 of the default thread pool.
Eventually, the server ran out of execute threads and became unresponsive.
It is unclear that whether the initial blocking of threads by the jDriver is
a jDriver issue or an application issue. Please report to BEA support at
[email protected] for further assistance.
Regards,
Priscilla
Gary Mok <[email protected]> wrote in message
news:[email protected]..
>
Under heavy loading, our WLS 6.0 SP2 will be not be responding to clientrequests
after some time, say, 1 hour. From the administration console, the requestthroughput
is 0 while request waiting accumulates to over 1,000. Even the clientsstop making
request to the server, the request waiting will not drop. It seems thatWLS blocked
on some threads and unable to serve the requests (see attached thread dumpfor
details).
Our configuration is as follow:
OS: SunOS 5.7
Database: MS SQL Server 7.0 running on NT4 Enterprise Edition.
(JDBC Driver is the one bundled with WLS 6.0)
We know that using 'DriverManager.getConnection()' can cause deadlock innumber
of cases but we have gone through all the code but all of our Databaseconnections
are obtained through datasource. And the connection is closed properly infinally
block.
Moreover, the application is originally running on WLS 4.51 but no problemis
encountered.
Does any expert know what the problem and solution are?
Thanks!

Weblogic 12.1.2 - Tibco Client (6.3l) - through MDB - IllegalAccessError

Similar Messages

Maybe you are looking for