Serialization error using WebLogic generated stubs.

I have written a web service using WL Workshop, and it works fine
in the browser based test environment. When I use the client stubsgenerated by
WL, I get a serialization error:
java.rmi.RemoteException: web service invoke failed; nested exception is:
     javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
did not find needed xsi:type attribute on element <anyType>
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:36)
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:58)
     at datafeed.Client.main(Client.java:19)
Caused by: javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
did not find needed xsi:type attribute on element <anyType>
     at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
     at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:359)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:465)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:359)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:205)
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:33)
     ... 2 more
Caused by: weblogic.xml.schema.binding.DeserializationException: did not find
needed xsi:type attribute on element <anyType>
     at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.extractType(XSDAnyCodec.java:108)
     at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.deserialize(XSDAnyCodec.java:83)
     at weblogic.xml.schema.binding.SequenceCodecBase.deserialize(SequenceCodecBase.java:118)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
     at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
     at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
     at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
     at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
     at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
     at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:266)
     at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:290)
     ... 7 more

Indeed there is a difference in how WLS and Workshop handle
xsd:anyType. Our plan at this point is to fix this to return
javax.xml.soap.SOAPElement when we do not find the xsi:type attribute
-- probably in the next service pack release. We have entered a
change request CR082976 that you can reference with support if you
need a more urgent resolution.
--Scott
In article <[email protected]>,
Neil Hornbeck <[email protected]> wrote:
>
I have written a web service using WL Workshop, and it works fine in
the browser based test environment. When I use the client
stubsgenerated by WL, I get a serialization error:
java.rmi.RemoteException: web service invoke failed; nested exception is:
     javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
did not find needed xsi:type attribute on element <anyType>
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:36)
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:58)
     at datafeed.Client.main(Client.java:19)
Caused by: javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
did not find needed xsi:type attribute on element <anyType>
     at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
     at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:359)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:465)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:359)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:205)
     at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:33)
     ... 2 more
Caused by: weblogic.xml.schema.binding.DeserializationException: did not find
needed xsi:type attribute on element <anyType>
     at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.extractType(XSDAnyCodec.java:108)
     at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.deserialize(XSDAnyCodec.java:83)
     at weblogic.xml.schema.binding.SequenceCodecBase.deserialize(SequenceCodecBase.java:118)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
     at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
     at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
     at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
     at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
     at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
     at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:266)
     at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:290)
     ... 7 more

Similar Messages

Webapp client using weblogic-generated stubs

Hi,
I have a simple webservice that has been tested for a while and works without
any trouble when
accessed from a standalone java client using the weblogic-generated webservice
stubs.
I am trying to code a webapp client (using jsp/struts) using the same stubs, and
seem to keep
getting this error. It appears on the client side, doesn't even reach the server
side.
I am using weblogic 8.1 SP1. (It is interesting that even though everything was
compiled and
deployed with weblogic 8.1, there is some reference to 7.0-- which is not even
installed on the
system, so I don't know where it is coming from.)
<May 7, 2004 12:58:23 PM EDT> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler
threw an exception from its handleResponse method. The exception was:
java.lang.IllegalAccessError: Already connected.>
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception
during processing: java.lang.IllegalAccessError: Already connected (see Fault
Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
</bea_fault:stacktrace>java.lang.IllegalAccessError: Already connected
at weblogic.net.http.HttpURLConnection.setRequestProperty(Ljava.lang.String;Ljava.lang.String;)V(HttpURLConnection.java:570)
at com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry(Ljava.lang.Object;Ljava.lang.Object;Ljava.lang.Object;I)Ljava.lang.Object;(HttpURLConnectionArmInstrumentation.java:98)
at weblogic.net.http.HttpURLConnection.getInputStream()Ljava.io.InputStream;(HttpURLConnection.java:???)
at weblogic.net.http.HttpURLConnection.getHeaderField(Ljava.lang.String;)Ljava.lang.String;(HttpURLConnection.java:542)
at java.net.URLConnection.getContentType()Ljava.lang.String;(URLConnection.java:381)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Ljavax.xml.rpc.handler.MessageContext;)V(Http11ClientBinding.java:202)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(ClientHandler.java:63)
at weblogic.webservice.core.HandlerChainImpl.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(HandlerChainImpl.java:230)
at weblogic.webservice.core.ClientDispatcher.receive(Lweblogic.webservice.WLMessageContext;)Ljava.lang.Object;(ClientDispatcher.java:229)
at weblogic.webservice.core.ClientDispatcher.dispatch([Ljava.lang.Object;)Ljava.lang.Object;(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;Ljava.io.PrintStream;)Ljava.lang.Object;(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;)Ljava.lang.Object;(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(Ljava.lang.String;Ljava.util.Map;)Ljava.lang.Object;(StubImpl.java:270)
Thanks in advance,
E

Hi,
Thanks for your help with this. As it turns out, I received this message from
the weblogic team here:
=======
All,
The J2EE monitoring tool OVTA rolled out to Weblogic Farm Linux QA and Stage environment
had a bug in the instrumentation. The bug induces a java.lang.IllegalAccessError.
A patch as been rolled out to fix this issue.
=======
Once the patch was rolled out and weblogic was restarted, the issue disappeared.
Thanks again for your help!
E
Bruce Stephens <[email protected]> wrote:
Hello,
What is
com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry
at the time of failure?
If you could provide a short reproducer, we could give it a spin; or
open a dialog with our support team.
Thanks,
Bruce
Elisheva G wrote:
Hi, thanks for responding.
I have precisely the same client jsp running without any errors onapache tomcat
accessing
webservices residing in weblogic 8.1 It's only when I try to migratethe client
code from tomcat
to weblogic that I see this "already connected" exception being thrownfrom within
the weblogic-
generated stubs.
I successfully get a port from the service, but when I try to executethe business
method in the
port, that is where the exception is thrown -- consistently.
Any ideas? I am seeing identical behavior on 2 different applications.
Thanks in advance,
E
Bruce Stephens <[email protected]> wrote:
Hello,
The 7.0 reference is a namespace and not a problem and not associated
with your issue. I think you are seeing normal process threading
issues
with jsp sessions. There is an example using a jsp [1] and one with
SSL
[2] that you might want to examine.
HTH,
Bruce
[1]
http://manojc.com/?sample28
[2]
http://webservice.bea.com/clientauth.zip
Elisheva G wrote:
Hi,
I have a simple webservice that has been tested for a while and
works
without
any trouble when
accessed from a standalone java client using the weblogic-generatedwebservice
stubs.
I am trying to code a webapp client (using jsp/struts) using the
same
stubs, and
seem to keep
getting this error. It appears on the client side, doesn't even
reach
the server
side.
I am using weblogic 8.1 SP1. (It is interesting that even though
everything
was
compiled and
deployed with weblogic 8.1, there is some reference to 7.0-- whichis not even
installed on the
system, so I don't know where it is coming from.)
<May 7, 2004 12:58:23 PM EDT> <Info> <WebService> <BEA-220025> <Handlerweblogic.webservice.core.handler.ClientHandler
threw an exception from its handleResponse method. The exception
was:
java.lang.IllegalAccessError: Already connected.>
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException:Exception
during processing: java.lang.IllegalAccessError: Already connected(see Fault
Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
</bea_fault:stacktrace>java.lang.IllegalAccessError: Already connected
at weblogic.net.http.HttpURLConnection.setRequestProperty(Ljava.lang.String;Ljava.lang.String;)V(HttpURLConnection.java:570)
at com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry(Ljava.lang.Object;Ljava.lang.Object;Ljava.lang.Object;I)Ljava.lang.Object;(HttpURLConnectionArmInstrumentation.java:98)
at weblogic.net.http.HttpURLConnection.getInputStream()Ljava.io.InputStream;(HttpURLConnection.java:???)
at weblogic.net.http.HttpURLConnection.getHeaderField(Ljava.lang.String;)Ljava.lang.String;(HttpURLConnection.java:542)
at java.net.URLConnection.getContentType()Ljava.lang.String;(URLConnection.java:381)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Ljavax.xml.rpc.handler.MessageContext;)V(Http11ClientBinding.java:202)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(ClientHandler.java:63)
at weblogic.webservice.core.HandlerChainImpl.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(HandlerChainImpl.java:230)
at weblogic.webservice.core.ClientDispatcher.receive(Lweblogic.webservice.WLMessageContext;)Ljava.lang.Object;(ClientDispatcher.java:229)
at weblogic.webservice.core.ClientDispatcher.dispatch([Ljava.lang.Object;)Ljava.lang.Object;(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;Ljava.io.PrintStream;)Ljava.lang.Object;(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;)Ljava.lang.Object;(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(Ljava.lang.String;Ljava.util.Map;)Ljava.lang.Object;(StubImpl.java:270)
Thanks in advance,
E

Error while generating stub using ant generate-stubs

I am getting error while running ant "generate-stubs" for generating stub.The details of errors as below:
[exec] error: modeler error: expected root element "definitions" (in namesp
ace "http://schemas.xmlsoap.org/wsdl/"), found element "html" (in namespace "nul
l")
Any help????

Perhaps there is an error while you specified the namespaces. Chk them and try............Hope that helps...............ABHI

Error handling in generated stubs

Hello,
I've been playing around with Flex Builder 3 and WS and I am
puzzled by how one can handle generic SOAP error messages (i.e. not
the service faults, but connection errors, message parsing related
errors, etc.).
Here is what I try:
1 Generate service stubs out of an existing WSDL using Flex
Builder
2 Create a dead simple Flex app that makes a WS call via
stubs
3 Trying to call an unreliable WS, and I get Flash popup
with the stack trace:
quote:
TypeError: Error #1090: XML parser failure: element is
malformed.
at
mx.rpc.soap::SOAPDecoder/decodeResponse()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc \soap\SOAPDecoder.as:234]
at com.ws::BaseLookupService/processResult()[C:\Documents
and Settings\ws\My Documents\Flex Builder
3\FlexClient\services\lookup\com\ws\BaseLookupService.as:237]
at
mx.rpc::AsyncResponder/result()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncResp onder.as:84]
at
mx.rpc::AsyncRequest/acknowledge()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncR equest.as:74]
at
DirectHTTPMessageResponder/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\ messaging\channels\DirectHTTPChannel.as:381]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
It looks like neither registering fault handler nor adding
event listener to the AsyncToken catches this error.
Does anyone know if I should I be modifying the generated
stubs to catch this kind of errors or there is a more elegant
approach to fix this? Thanks.

Hello,
I've been playing around with Flex Builder 3 and WS and I am
puzzled by how one can handle generic SOAP error messages (i.e. not
the service faults, but connection errors, message parsing related
errors, etc.).
Here is what I try:
1 Generate service stubs out of an existing WSDL using Flex
Builder
2 Create a dead simple Flex app that makes a WS call via
stubs
3 Trying to call an unreliable WS, and I get Flash popup
with the stack trace:
quote:
TypeError: Error #1090: XML parser failure: element is
malformed.
at
mx.rpc.soap::SOAPDecoder/decodeResponse()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc \soap\SOAPDecoder.as:234]
at com.ws::BaseLookupService/processResult()[C:\Documents
and Settings\ws\My Documents\Flex Builder
3\FlexClient\services\lookup\com\ws\BaseLookupService.as:237]
at
mx.rpc::AsyncResponder/result()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncResp onder.as:84]
at
mx.rpc::AsyncRequest/acknowledge()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncR equest.as:74]
at
DirectHTTPMessageResponder/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\ messaging\channels\DirectHTTPChannel.as:381]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
It looks like neither registering fault handler nor adding
event listener to the AsyncToken catches this error.
Does anyone know if I should I be modifying the generated
stubs to catch this kind of errors or there is a more elegant
approach to fix this? Thanks.

Error Using weblogic.jspc --- java.lang.ExceptionInInitializerError

Hi,
          I am trying to use the weblogic.jspc compiler to pre-compile my jsp
          files so that I can verify that they compile w/o having to visit the
          page. I am using Weblogic 4.5.1. I am encountering the following
          error:
          java.lang.ExceptionInInitializerError
          at java.lang.Throwable.<init>(Compiled Code)
          at java.lang.Error.<init>(Compiled Code)
          at java.lang.LinkageError.<init>(Compiled Code)
          at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
          at java.beans.Beans.instantiate(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
          at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
          at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
          at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
          at weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled
          Code)
          at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
          at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
          at weblogic.jhtmlc.runBody(Compiled Code)
          at weblogic.jspc.runBody(Compiled Code)
          at weblogic.utils.compiler.Tool.run(Compiled Code)
          at weblogic.jspc.main(Compiled Code)
          Have any of you seen this? Can you tell me what I am doing wrong
          (Classpath, etc.)?
          Any and all help would be greatly appreciated.
          The command line I am using is:
          java -verbose -classpath
          $CLASSPATH:/apps/weblogic/license:/apps/weblogic/classes:/apps/weblogic/lib/weblogicaux.jar
          weblogic.jspc -d $HOME/weblogic/myserver/classfiles/examples
          100-Welcome.jsp
          Regards,
          Richard


Fixed with a patch CR0737797 and CR062538 for the 6.1 sp3 source line
          Prasanna Yalam

Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

          Hi,
          I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
          to use Container Managed Transaction through a Session Bean.
          Connection Pool Settings: -------------------------
          Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
          TXDataSource Settings : -----------------------
          Name - myXADS
          JNDIName - myXADS
          PoolName - myXAPool
          Everything works fine but once in a while I get the following exception:
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start() failed on resource 'myXAPool' Unexpected error
          during start for XAResource 'myXAPool': null
          The connection pool size is 30 and the number connections high reached was 5,
          which means there are enough connections in the pool available at all time.
          It would be really great if you can help me out.
          Thanks in Advance, Sudhir.


Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

XA error: using Weblogic 6.1 and Oracle 8.1.6

Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
in the transaction branch start() failed on resource 'myXAPool' Unexpected error
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reached was 5,
which means there are enough connections in the pool available at all time.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Receiving ERRORS using WEBLOGIC.DEPLOY

Hi everybody,
I am getting strange errors when using the weblogic.deploy command-line
function. I am using WL6.0 on W2000.
Deploy/Update
command: java weblogic.deploy -port 7001 -host localhost update
beapasword MyWebApplication stage\MyWebApplication.war
error: java.lang.NullPointerException
at
weblogic.deploy.deployApplication(deploy.java:383)
at weblogic.deploy.deploy(deploy.java:340)
at weblogic.deploy.runBody(deploy.java:219)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.deploy.main(deploy.java:954)
Undeploy
Command: java weblogic.deploy -port 7001 -host localhost undeploy
beapasword MyWebApplication
error: giving up after two minutes
And it looks that just a Update doens't work. I have to undeploy first and
the do a update to see the changes I've made in my file.
Any suggestions....
M-

Hi.
WLS version and service pack level? Please post the entire weblogic.deploy command along
with the exception that follows.
Thanks,
Michael
Harjeet Singh wrote:
I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
on 7001. When I try to run it gives me following error:
[java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
as: system: password
system password is correct. I have tried http://localhost:7001 to but doesen't seem
to work.
Any ideas.
HS--
Michael Young
Developer Relations Engineer
BEA Support

Errors using weblogic sql driver: "No JDBC connection can be made because the transaction state is marked rollback"

One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
     at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
     at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
     at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
     at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

Joseph Weinstein <[email protected]> wrote:
>
>
YuanHui Liu wrote:
Joe,
We got the exact same error message. The error came after we got theJDBC connection,
and trying to create statement off it.
It occurs intermitently when we are running another standalone JAVAapp to do
some end of day work, which results in the DB Server being very busy(90+%CPU
usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
pool. This would sometimes result in all our subsequent DB requeststo fail and
lead to a crash.
We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
connection timeout that caused this(rather it is the end effect).
Can you give us a more detailed explanation? Is there a miscommunicationbetween
our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
it's when the server is
gettng the pool connection. For performance/synchronization reasons we
do a clever
delay: When your code asks for a pool connection we quickly give you
the pool wrapper,
but we delay actually reserving the real underlying DBMS connection until
your first
real need for a connection, at your first JDBC call, such as createStatement()
etc.
It is while waiting for a pool connection long enough for the transaction
coordinator
to have timed you out before you ever get a chance. It's nothing to do
with the
DBMS or even JDBC, I believe. I think the weblogic server either has
too few execute-threads
and/or too few CPU cycles to do the work load.
Okay, so there's a lazy initialization of the connection.
From reading our log I believe our failur is immediate rather
than waiting for 30+ seconds(the default setting) from the DB,
the timeout occurred later as a result. At the time either because the DB Server
is very busy.
Since we are running WLS6.0 we have only one connection pool,
we have defined a max of 150 threads in the pool. While this
is happening the DB Server is being pinned by an overnight job,
but the WLS Server is not busy at all. The DB and WLS resides
on different physical boxes.
We also have a thread dump from the WLS console when we rebooted the server, it
showed that we are hanging on to the thread & jdbc
connections after these exceptions has occurred instead of releasing them, note
"16083"(~4.5 hours) seconds has passed:
142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
Scheduled Trigger
So I would argue this problem actually chewed up resources on the WLS server.
-Yuanhui Liu
>>
>>
Thanks.
-YuanHui Liu
Joseph Weinstein <[email protected]> wrote:
lixin wrote:
One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
load
issue. What is
happening is that the transaction is started, and times out beforethe
SSB even gets to
the first JDBC work. I would first verify that the customer is using
the very latest JVM
available for the machine.
Joe Weinstein
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

Assertion error using weblogic.ejbc20

I'm getting the following error message generating the jar file for my BimPspsAdjApp
WL bean:
[java] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Couldn't
find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Exception in thread "main" weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Couldn't find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Java Result: 1
My Ant command is:
<target name = "intBimPsp">
     <mkdir dir="${ejbjartmp.dir}/webserviceBim/META-INF"/>
     <mkdir dir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp"/>
     <copy file="${descriptors.dir}/BimPspAdjApp-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/ejb-jar.xml"/>
     <copy file="${descriptors.dir}/BimPspAdjApp-weblogic-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/weblogic-ejb-jar.xml"/>
<copy todir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp/">
<fileset dir="${build.dir}/fastway/runtime/intBimPsp/"/>
</copy>
     <jar jarfile="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"
     basedir="${ejbjartmp.dir}/webserviceBim"/>
<java classname="weblogic.ejbc20" fork="yes" dir="${ejbjartmp.dir}">
     <arg line="$pre_BimPspAdjApp.jar $BimPspAdjApp.jar"/>
          <classpath>
               <pathelement location="/apps/bea/wlserver6.1/lib/weblogic.jar"/>
               <pathelement location="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
          </classpath>
     </java>
<delete dir="${ejbjartmp.dir}/webserviceBim/"/>
     <delete file="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</target>
Why does this assertion error occur?
Thanks

Are you trying to run a EJB 2.0 bean using a EJB 1.1 DTD?
Gabriela Gonzalez wrote:
I'm getting the following error message generating the jar file for my BimPspsAdjApp
WL bean:
[java] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Couldn't
find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Exception in thread "main" weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Couldn't find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Java Result: 1
My Ant command is:
<target name = "intBimPsp">
<mkdir dir="${ejbjartmp.dir}/webserviceBim/META-INF"/>
<mkdir dir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp"/>
<copy file="${descriptors.dir}/BimPspAdjApp-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/ejb-jar.xml"/>
<copy file="${descriptors.dir}/BimPspAdjApp-weblogic-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/weblogic-ejb-jar.xml"/>
<copy todir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp/">
<fileset dir="${build.dir}/fastway/runtime/intBimPsp/"/>
</copy>
<jar jarfile="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"
basedir="${ejbjartmp.dir}/webserviceBim"/>
<java classname="weblogic.ejbc20" fork="yes" dir="${ejbjartmp.dir}">
<arg line="$pre_BimPspAdjApp.jar $BimPspAdjApp.jar"/>
<classpath>
<pathelement location="/apps/bea/wlserver6.1/lib/weblogic.jar"/>
<pathelement location="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</classpath>
</java>
<delete dir="${ejbjartmp.dir}/webserviceBim/"/>
<delete file="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</target>
Why does this assertion error occur?
Thanks--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Serialization error in Weblogic

Hi,
We are having a strange problem with serialization and Weblogic cluster.
Some of our JSPs display this error in the log:
<Error> <Cluster> <All session objects should be serializable to replicate. Please check the objects in your session. Failed to replicate non serializable object>
The BEA documentation says that this is because all user-defined objects in the session have to be serializable so that they can be replicated across nodes in the cluster.
Now, we figured that this meant we had some user-defined objects that weren't serialized, and so we added some code to the offending JSPs to:
(a) Get all the objects from the session.
(b) Test them using instance of java.io.Serializable.
(c) Print out all those that weren't serialized.
We caught a few classes with this and fixed them. Now, the number of locations that cause this error have come down to 4. However, these 4 are proving really hard to crack!
As per our diagnostic output, everything in the session is serializable, yet Weblogic insists that something isn't serializable. The BEA documentation isn't much help; it basically recommends we add the "implements java.io.Serializable" to every file in sight.
Has anyone come up against this kind of problem before with Weblogic? Or are we missing something fundamental in serialization itself here?
Thanks in advance.
Ta ta,
Jagan.

Has anyone come up against this kind of problem before
with Weblogic? Or are we missing something fundamental
in serialization itself here?Hi Jagan,
I've had similar problems, but only with much older Weblogic versions.
What I did to find out the problem was to manually take the session object and serialize it. Then, the error output is more specific -- it tells you the exact object type that is the offender. That's better than WL's vague error messages.
It turned out that a) we had objects that were serializable, but had references to non-serializable classes (remember that the entire graph is serialized, not just the object(s) bound to the session) and b) a third-party class was serializable, but it maintained a reference to a non-serializable class from time to time.
The latter problem was a pain to diagnose.
Hope it helps,
Garrett Smith

Error using weblogic.deploy tool, while deploying a war

          Hi all, I'm trying to deploy a war with the follw command:
          java weblogic.deploy -host localhost -port 7001 -component NewScreenWar:BEAserver
          deploy beasystem NewScreenWar d:\newsscreen\weblogic\NewScreenWar.war
          It gives me following error:
          weblogic.j2ee.DeploymentException: Application NewScreenWar does not contain com
          ponent NewScreenWar at weblogic.deploy.deploy(deploy.java:668) at weblogic.deploy.runBody(deploy.java:358)
          at weblogic.utils.compiler.Tool.run(Tool.java:79) at weblogic.deploy.main(deploy.java:1601)
          Application NewScreenWar does not contain component NewScreenWar
          how do I resolve this...??
          thanx --anjaly


Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org

Hyperion Workspace error , using weblogic as application server.

HI Experts !
I have Hyperion 9.3.0 environment and
I m using web logic 8.1 and facing problem in starting workspace .
configuration with weblogic is successful but still error while open workspace :
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Please help me..
Thank you

Hello,
Were you able to find any solutions to this problem. We are experiencing the same issue now.
Thanks
Srikanth

Is anyone has already had the following error using PDF Generator?

Hello,
I try to convert some documents (.doc, .ppt, ...) into .pdf using the PDF Generator.
And sometimes, I hava the following error in a .log file (in the out directory):
Failed to process job DDLaunchObject-2006-08-08 13-22-40.102.doc
Error Code: 1,011
Reason: The BMC reported failure in converting the document.
Is anyone has already had that error? What do I have to do?
Please, could you help me?
Thanks a lot!

I have seen this error when trying to convert a certain Word document. The Word document itself when i opened it in Word resulted in a warning message that it needed to install a language pack, once i installed this language pack, the conversion in PDFG worked.
PDFG uses the native process in the background to convert the files. That means for Word docs it actually uses msword.exe to read the document. If opening the document in Word results in any kind of error or user dialog, then this could be what causes the PDFG server to fail, as the server cannot respond to the error/dialog that occurs.
hope that helps.
David.

Finder error in WL generated Stub code for a BMP Entity Bean

Hi,
I have a group finder error in a BMP I am writing in WL 6.1 sp3.... The
group finder is...
public Collection ejbFindByDocumentKey(DocumentPK docKey) {.....
.... // get a record set of all the interesting keys....
ArrayList retVal = new ArrayList();
while(rs.next()) {
int subDocNum = rs.getInt(1);
SubDocPK subDocPK = new SubDocPK(subDocNum);
retVal.add(subDocPK);
return retVal;
..... // Exception handling
Which works fine in the debugger, but in the session facade when I get an
Iterator on the Collection and cast the result to a SubDocPK I get a
ClassCastException. When I look at the type of the class in the Collection
returned by the container it is SubDocBean_mjdk3_EOimpl (I cannot remember
the exact name as it was at work and I am now at home)
Has anyone else found this problem or a way around, or should I just write a
DAO and get the collection myself?
Yours
Paul Brennan

Right, this is how finders work in BMP.
The ejbFindXXX implementation returns a collection of primary keys. The
container then takes this and returns a collection of remote or local
references.
-- Rob
Paul Brennan wrote:
Hi all,
Just got into work and I want to add that the class inside the collection is a
cdcp.ejb.cdcp.SubDocPK
as below; and when I look in the session bean I get a type
cdcp.ejb.cdcp.SubDocBean_jktqi5_ELOImpl
I have an EAR file I am willing to share....
Any comments or suggestions are welcom
"Paul Brennan" <[email protected]> wrote:
Hi,
I have a group finder error in a BMP I am writing in WL 6.1 sp3....
The
group finder is...
public Collection ejbFindByDocumentKey(DocumentPK docKey) {.....
.... // get a record set of all the interesting keys....
ArrayList retVal = new ArrayList();
while(rs.next()) {
int subDocNum = rs.getInt(1);
SubDocPK subDocPK = new SubDocPK(subDocNum);
retVal.add(subDocPK);
return retVal;
..... // Exception handling
Which works fine in the debugger, but in the session facade when I get
an
Iterator on the Collection and cast the result to a SubDocPK I get a
ClassCastException. When I look at the type of the class in the Collection
returned by the container it is SubDocBean_mjdk3_EOimpl (I cannot remember
the exact name as it was at work and I am now at home)
Has anyone else found this problem or a way around, or should I just
write a
DAO and get the collection myself?
Yours
Paul Brennan

Serialization error using WebLogic generated stubs.

Similar Messages

Maybe you are looking for