Issue of Using Generic Methods in EJB 3 on Oracle WebLogic 10gR3 - WebLogic Server - EJB

Hi, I have developed a EJB 3 and deploy on Server 1 (Oralce WebLogic 10gR3)。The EJB interface is as follow:
package test;
import java.util.List;
public interface HelloWorld {
public String hello(String name);
public List getUsers();
public List<User> getGenericUsers();
}
And develop another web app and deploy on Server 2(Oracle WebLogic 10gR3)。
There are 5 scenarios:
1. Invoke EJB public List getUsers() method from index.jsp of web app, it will throws exception
like:
java.lang.reflect.UndeclaredThrowableException
at $Proxy59.getUsers(Unknown Source)
at jsp_servlet.__index._jspService(__index.java:90)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
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:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3504)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NoSuchMethodException: test.HelloWorldBean_kap09s_HelloWorldImpl_1030_WLStub.getUsers()
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:162)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:53)
... 17 more
2. Invoke EJB public List<User> getGenericUsers() method from index.jsp of web app, it will throws exception like:
####<2008/12/17 上午09時36分21秒 CST> <Error> <HTTP> <developer> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1229477781453> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext#f5df37 - appName: 'HelloWeb', name: 'HelloWeb.war', context-path: '/HelloWeb', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl#1f203e[
GET /HelloWeb/index.jsp HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*
Accept-Language: zh-tw
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
Connection: Keep-Alive
]] Root cause of ServletException.
java.lang.AssertionError: Can not find generic method public abstract java.util.List<test.User> getGenericUsers() in EJB Object
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:159)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:53)
at $Proxy79.getGenericUsers(Unknown Source)
at jsp_servlet.__index._jspService(__index.java:90)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
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:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3504)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
3. If I remove public List<User> getGenericUsers() from EJB Interface of EJB Project and web app project, and repeat scenario 1, It can successfully execute without errors.
4. And If I use java stand-alone app to invokie EJB, all of scenario will successfully execute without errors.
5. And if EJB project and web app project are deployed on the same Oracle WebLogic 10gR3, scenario 1, 2, 3 can successfully execute without errors.
Is there anyone encountered the same issue?

i have the same problem,
Generics is not working with 10gR3.
this is very bad.
any idea will be appreciated.
_________________________
Regards,
Paata Lominadze
Magticom LTD. 

We, also, 're facing exactly the same problem. 

Same problem..
Anyone found a solution by now? 

Hi,
Unfortunately, it appears as though you've found a bug in WLS. I would suggest contacting support so they can work to get you a patch. I'm sorry for the inconvenience.
http://www.oracle.com/support/index.html
- Matt 

I have the same problem,
Generics is not working with 10gR3.
Anybody can help me resolve this?
Thanks!!!! 

I have a customer that has this problem.
We wrote me that:
we got a java.lang.NoSuchMethodException while the method exist even in the generated (by WLS) stub.
when we change the interface by putting a "list" instead of list <> then it works.
hope it can help, but should be great know why.
Regards
Marco
글 수정: user10649412 

Is this the case? If so, then Weblogic should not be considered an EJB3 / JEE5 application server.
How is anyone to know what is - and what is not - supported by Weblogic when we can develop our applications they work perfectly in Glassfish and JBoss, to name a couple? 

Is there a patch / workaround available just in case you need to use Generics in EJB 3.0 ? 

Hi,
WLS doesn't fully support generics yet but the problem in the first post should be fixed already. Please contact Oracle support for information. http://www.oracle.com/support/index.html
A full support to generics is under evaluation and will be released soon. Sorry for inconvenience.
Thanks,
Amy 

any body resolve this issue? 

Please refer section Using Generics in EJBs
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/ejb30/implementing.html 

Hi,
Please refer to: http://middlewaremagic.com/weblogic/?p=1927
.
.
Thanks
Jay Sensharma
http://middlewaremagic.com/weblogic/?p=1927(Middleware magic Is Here)

Related

WLS 8.1.2 : unsupported encoding: 'UTF-8, UTF-16'

Hello,
We are porting a web service from WLS 7.0.4 to WLS 8.1.2.0.
It is a stateless session bean, we use "servicegen" to generate the WS deployment
descriptor and the client is PocketSoap 1.5
This web service worked fine with WLS 7.0.4, but with WLS 8.1.2.0, the server
can't build the HTTP response. It seems it doesn't understand the "Accept-Charset:
UTF-8, UTF-16" included in the HTTP request generated by PocketSOAP.
Is there some extra configuration parameter on the server since v8 to handle this,
or is it a regression ?
Here is the HTTP request :
===================
POST /ws-powertest/powertest HTTP/1.1
Host: diffool:82
Accept-Charset: UTF-8, UTF-16;q=0.8, iso-8859-1;q=0.8
Accept-Encoding: deflate, gzip
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: PocketSOAP/1.5.b1/PocketHTTP/1.1
Content-Length: 412
Authorization: Basic ZXJlbmF1ZDoxMjM0NTY3OA==
<S:Envelope
     xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:a="http://www.bnpparibas.com/eqd/powertest"
     xmlns:XS="http://www.w3.org/2001/XMLSchema"
     xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"><S:Body><a:getPositionAuthenticated
S:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><string XI:type="XS:string">IXOEURWLD</string></a:getPositionAuthenticated></S:Body></S:Envelope>
And the server-side stack trace :
=======================
java.lang.IllegalArgumentException: unsupported encoding: 'UTF-8, UTF-16': java.io.UnsupportedEncodingException:
UTF-8, UTF-16
     at weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:865)
     at weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:674)
     at weblogic.servlet.internal.ServletResponseImpl.setContentType(ServletResponseImpl.java:269)
     at weblogic.webservice.binding.soap.HttpServerBinding.send(HttpServerBinding.java:131)
     at weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:105)
     at weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:98)
     at weblogic.webservice.server.servlet.ServletSecurityHelper$3.run(ServletSecurityHelper.java:173)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.webservice.server.servlet.ServletSecurityHelper.authenticatedPortInvoke(ServletSecurityHelper.java:170)
     at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:302)
     at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:485)
     at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:268)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
thanx for your help,
Emmanuel.
Hi Emmanuel,
Did you already try setting the -Dweblogic.webservice.i18n.charset Java system
property, on the command-line that starts the WLS instance, hosting the WebLogic
Web Service?
-Dweblogic.webservice.i18n.charset=utf-16
This sets the Accept-Charset for all WebLogic Web Services, so you probably want
to just set it in the web-services.xml, for powertest. I don't know what this
currently looks like, but you want to edit it (there is not servicegen option
to set it) to look something like:
<web-services>
<web-service
name="powertest"
targetNamespace="http://www.bnpparibas.com/eqd/powertest"
uri="/ws-powertest/powertest"
charset="UTF-16"
>
...
</web-service>
</web-services>
Refer to http://e-docs.bea.com/wls/docs81/webserv/i18n.html
HTH,
Mike Wooten
"Emmanuel Renaud" <emmanuel.renaud#bnpparibas.com> wrote:
>
Hello,
We are porting a web service from WLS 7.0.4 to WLS 8.1.2.0.
It is a stateless session bean, we use "servicegen" to generate the WS
deployment
descriptor and the client is PocketSoap 1.5
This web service worked fine with WLS 7.0.4, but with WLS 8.1.2.0, the
server
can't build the HTTP response. It seems it doesn't understand the "Accept-Charset:
UTF-8, UTF-16" included in the HTTP request generated by PocketSOAP.
Is there some extra configuration parameter on the server since v8 to
handle this,
or is it a regression ?
Here is the HTTP request :
===================
POST /ws-powertest/powertest HTTP/1.1
Host: diffool:82
Accept-Charset: UTF-8, UTF-16;q=0.8, iso-8859-1;q=0.8
Accept-Encoding: deflate, gzip
SOAPAction: ""
User-Agent: PocketSOAP/1.5.b1/PocketHTTP/1.1
Content-Length: 412
Authorization: Basic ZXJlbmF1ZDoxMjM0NTY3OA==
<S:Envelope
     xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:a="http://www.bnpparibas.com/eqd/powertest"
     xmlns:XS="http://www.w3.org/2001/XMLSchema"
     xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"><S:Body><a:getPositionAuthenticated
S:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><string XI:type="XS:string">IXOEURWLD</string></a:getPositionAuthenticated></S:Body></S:Envelope>
And the server-side stack trace :
=======================
java.lang.IllegalArgumentException: unsupported encoding: 'UTF-8, UTF-16':
java.io.UnsupportedEncodingException:
UTF-8, UTF-16
     at weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:865)
     at weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:674)
     at weblogic.servlet.internal.ServletResponseImpl.setContentType(ServletResponseImpl.java:269)
     at weblogic.webservice.binding.soap.HttpServerBinding.send(HttpServerBinding.java:131)
     at weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:105)
     at weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:98)
     at weblogic.webservice.server.servlet.ServletSecurityHelper$3.run(ServletSecurityHelper.java:173)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.webservice.server.servlet.ServletSecurityHelper.authenticatedPortInvoke(ServletSecurityHelper.java:170)
     at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:302)
     at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:485)
     at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:268)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
thanx for your help,
Emmanuel.
"Michael Wooten" <wooten_michael#hotmail.com> wrote:
Did you already try setting the -Dweblogic.webservice.i18n.charset Java
system property, on the command-line that starts the WLS instance, hosting the
WebLogic Web Service?
-Dweblogic.webservice.i18n.charset=utf-16thanx Michael for the tip, but unfortunately it doesn't solve the pb.
It seems the web service generated by WL 8.1.2 can't handle an HTTP request containing
"Accept-Charset" in its header. I'm waiting for an answer of the bea support about
this assumption.
Emmanuel.
I'm wondering if a solution to this problem was ever found..
I'm having a similar issue. I'm currently evaluating Macromedia Flex, and I have
a simple Flex application that is trying to call a web service running on
weblogic 8.1 sp2.
This works great in Internet Explorer. But, when I run the application in
Firefox, I get the following exception:
java.lang.IllegalArgumentException: unsupported encoding: 'ISO-8859-1,utf-8':
java.io.UnsupportedEncodingException: ISO-8859-1,utf-8
at
weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:865)
at
weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:674)
...
Snooping around the SOAP messages that are sent back and forth, I can see the
HTTP Headers that are sent by each client. This is what is sent by firefox
(notice the accept-charset header):
<HTTPHeaders>
<user-agent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8</user-agent>
<accept>application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1</accept>
<accept-language>en-us,en;q=0.5</accept-language>
<accept-charset>ISO-8859-1,utf-8;q=0.7,*;q=0.7</accept-charset>
<keep-alive>300</keep-alive>
<connection>keep-alive</connection>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
And this is what is sent by Internet Explorer.
<HTTPHeaders>
<accept>*/*</accept>
<x-flash-version>7,0,14,0</x-flash-version>
<user-agent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
1.1.4322)</user-agent>
<connection>Keep-Alive</connection>
<cache-control>no-cache</cache-control>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
Does anybody know how to fix, or work around this problem?
emmanuel renaud wrote:
"Michael Wooten" <wooten_michael#hotmail.com> wrote:
Did you already try setting the -Dweblogic.webservice.i18n.charset Java
system property, on the command-line that starts the WLS instance, hosting the
WebLogic Web Service?
-Dweblogic.webservice.i18n.charset=utf-16thanx Michael for the tip, but unfortunately it doesn't solve the pb.
It seems the web service generated by WL 8.1.2 can't handle an HTTP request containing
"Accept-Charset" in its header. I'm waiting for an answer of the bea support about
this assumption.
Emmanuel.
Nevermind. I set the charset attribute in the web-service.xml file to UTF-8, and
it is working for now. Is this the only way to force the encoding? I tried
setting the environment variable mentioned in the other post first, but that
didn't do the trick.
Jeff Poetker wrote:
I'm wondering if a solution to this problem was ever found..
I'm having a similar issue. I'm currently evaluating Macromedia Flex,
and I have a simple Flex application that is trying to call a web
service running on weblogic 8.1 sp2.
This works great in Internet Explorer. But, when I run the application
in Firefox, I get the following exception:
java.lang.IllegalArgumentException: unsupported encoding:
'ISO-8859-1,utf-8': java.io.UnsupportedEncodingException: ISO-8859-1,utf-8
at
weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:865)
at
weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:674)
...
Snooping around the SOAP messages that are sent back and forth, I can
see the HTTP Headers that are sent by each client. This is what is sent
by firefox (notice the accept-charset header):
<HTTPHeaders>
<user-agent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8</user-agent>
<accept>application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1</accept>
<accept-language>en-us,en;q=0.5</accept-language>
<accept-charset>ISO-8859-1,utf-8;q=0.7,*;q=0.7</accept-charset>
<keep-alive>300</keep-alive>
<connection>keep-alive</connection>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
And this is what is sent by Internet Explorer.
<HTTPHeaders>
<accept>*/*</accept>
<x-flash-version>7,0,14,0</x-flash-version>
<user-agent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
1.1.4322)</user-agent>
<connection>Keep-Alive</connection>
<cache-control>no-cache</cache-control>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
Does anybody know how to fix, or work around this problem?
emmanuel renaud wrote:
"Michael Wooten" <wooten_michael#hotmail.com> wrote:
Did you already try setting the -Dweblogic.webservice.i18n.charset Java
system property, on the command-line that starts the WLS instance,
hosting the
WebLogic Web Service?
-Dweblogic.webservice.i18n.charset=utf-16thanx Michael for the tip, but unfortunately it doesn't solve the pb.
It seems the web service generated by WL 8.1.2 can't handle an HTTP
request containing
"Accept-Charset" in its header. I'm waiting for an answer of the bea
support about
this assumption.
Emmanuel.
Hi Jeff,
This is really a bug in WLS 8.1.2 for which we received a patch.
The correction should be shipped in the next service pack, or you may ask the
Bea support if you need it.
Emmanuel.
Jeff Poetker <jeff.poetker#medplus.com> wrote:
Nevermind. I set the charset attribute in the web-service.xml file to
UTF-8, and
it is working for now. Is this the only way to force the encoding? I
tried
setting the environment variable mentioned in the other post first, but
that
didn't do the trick.
Jeff Poetker wrote:
I'm wondering if a solution to this problem was ever found..
I'm having a similar issue. I'm currently evaluating Macromedia Flex,and I have a simple Flex application that is trying to call a web
service running on weblogic 8.1 sp2.
This works great in Internet Explorer. But, when I run the applicationin Firefox, I get the following exception:
java.lang.IllegalArgumentException: unsupported encoding:
'ISO-8859-1,utf-8': java.io.UnsupportedEncodingException: ISO-8859-1,utf-8
at
weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:865)at
weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:674)...
Snooping around the SOAP messages that are sent back and forth, I cansee the HTTP Headers that are sent by each client. This is what issent
by firefox (notice the accept-charset header):
<HTTPHeaders>
<user-agent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)Gecko/20040206 Firefox/0.8</user-agent>
<accept>application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1</accept><accept-language>en-us,en;q=0.5</accept-language>
<accept-charset>ISO-8859-1,utf-8;q=0.7,*;q=0.7</accept-charset>
<keep-alive>300</keep-alive>
<connection>keep-alive</connection>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
And this is what is sent by Internet Explorer.
<HTTPHeaders>
<accept>*/*</accept>
<x-flash-version>7,0,14,0</x-flash-version>
<user-agent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NETCLR
1.1.4322)</user-agent>
<connection>Keep-Alive</connection>
<cache-control>no-cache</cache-control>
<content-type>text/xml; charset=utf-8</content-type>
<soapaction>""</soapaction>
<host>jpoetker-ws:9090</host>
<content-length>476</content-length>
</HTTPHeaders>
Does anybody know how to fix, or work around this problem?
emmanuel renaud wrote:
"Michael Wooten" <wooten_michael#hotmail.com> wrote:
Did you already try setting the -Dweblogic.webservice.i18n.charsetJava
system property, on the command-line that starts the WLS instance,hosting the
WebLogic Web Service?
-Dweblogic.webservice.i18n.charset=utf-16thanx Michael for the tip, but unfortunately it doesn't solve thepb.
It seems the web service generated by WL 8.1.2 can't handle an HTTPrequest containing
"Accept-Charset" in its header. I'm waiting for an answer of the beasupport about
this assumption.
Emmanuel.

XmlBeans - ClassCastException - XmlAnyTypeImpl

Hi,
I recently inherited a piece of code that was originally written to use XmlBeans
to construct SOAP requests to Oracle COREid. The code was written to use webLogic 8.1
and uses the following libraries:
weblogic81\server\lib\weblogic.jar
weblogic81\server\lib\xbean.jar
weblogic81\server\lib\wlxbean.jar
weblogic81\server\lib\xqrl.jar
weblogic81\server\lib\xmlx.jar
The XmlBeans were generated using COREid schemas compiled using
com.bea.xbean.tool.XMLBean invoked within an Ant script. The code works fine and
returns the correct results in response to an LDAP query made via the beans.
The application was compiled with JAVA_HOME set to JAVA_HOME=c:\bea\jdk142_05.
I'm currently adding additional queries to the code and need to make it work
for webLogic9.2 and JDK1.5 and I'm having some issues with the beans. In order
to get around ClassCastExceptions I changed the imports to import
org.apache.xmlbeans.XmlCursor and org.apache.xmlbeans.XmlObject rather than the
com.bea.xml varieties. I then hit a ClassCastException when trying to cast the
result of a cursor.getObject() to a bean. Assuming this was because all my beans,
generated at the earlier release were com.bea.xml.XmlObject's I assumed a recompilation
using a tool that create org.apache.xmlbean.XmlObject's would fix the problem. This is
where I am stuck.
I am using the same schemas as in the previous release and have tried the following
ways of generating the beans:
org.apache.xmlbeans.impl.tool.SchemaCompiler invoked from Ant
org.apache.xmlbeans.impl.tool.XMLBean invoked from Ant
scomp from the XmlBeans 2.2.0 distribution invoked from command line
All result in a jar file of different sizes containing org.apache.xmlbeans.XmlObjects.
The problem is that when I incorporate the resultant jar file in my application I'm
getting a ClassCastException because cursor.getObject() appears to be producing a
org.apache.xmlbeans.impl.values.XmlAnyTypeImpl.
I have noted that a number of people have reported problems similar to this on the
forums and in each case the root of the problem seems to be a problem with the schema.
Having had the "easypo" example in the XmlBeans 2.2.0 distribution working previously
I incorporated that schema into my application and tried to obtain a "line-item" using
cursor.getObject() and got a PurchaseOrderDocumentImpl ClassCastException.
I suspect that there is a problem with the way I am generating the beans rather than
with the schemas themselves.
Has anyone got any idea why I may be hitting this problem?
Incidentally, in case it's relevant in the latest version of the application I am
using the following jars:
weblogic92\server\lib\weblogic.jar
weblogic92\server\lib\xbean.jar
weblogic92\common\lib\apache_xbean.jar
weblogic92\server\wlxbean.jar
weblogic92\server\lib\wlxbean81.jar
weblogic92\server\lib\xqrl.jar
weblogic92\server\lib\xmlx.jar
Thanks for any help you can offer,
James 
This has been solved now. I was making a mistake in the build procedure. 
Hi,
We are migrating our application from weblogic8.1SP5 to Weblogic10. We are using old XMLbeans compiled from 8.1 xbeans.jar. We got the following error when generating XML from the xbeans.
<Feb 29, 2008 5:14:16 PM PST> <Debug> <Canine> <BEA-000000> <SQLQuery: BEGIN INSERT INTO tblCnEaiTransactionLog ( queue_
name, external_id, create_datetime) VALUES (?, ?, getDate()) SELECT SCOPE_IDENTITY() END>
java.lang.ClassCastException: com.bea.xbean.values.XmlAnyTypeImpl
at com.aligntech.canine.model.service.eai.xml.CreatePatientAndCaseSetupOrderXmlHelper.populateRequestContent(Cre
atePatientAndCaseSetupOrderXmlHelper.java:48)
at com.aligntech.canine.model.service.eai.xml.EaiServiceRequestXmlHelper.addServiceRequestPayload(EaiServiceRequ
estXmlHelper.java:61)
at com.aligntech.canine.model.service.eai.xml.EaiServiceRequestXmlHelper.getXml(EaiServiceRequestXmlHelper.java:
69)
at com.aligntech.canine.model.service.eai.EaiMessageService.sendPatientAndCaseSetupOrderCreation(EaiMessageServi
ce.java:157)
at com.aligntech.canine.model.service.eai.EaiMessageService.sendPatientAndCaseSetupOrderCreation(EaiMessageServi
ce.java:161)
at com.aligntech.canine.model.service.rxform.RxTreatmentService.createJDEPatientOrder(RxTreatmentService.java:41
7)
at com.aligntech.canine.model.service.rxform.RxTreatmentService.submitTreatment(RxTreatmentService.java:352)
at com.aligntech.canine.controller.action.rxform.RxSummaryAction.authorizedExecute(RxSummaryAction.java:88)
at com.aligntech.canine.controller.action.AuthorizedCanineAction.execute(AuthorizedCanineAction.java:26)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at com.aligntech.canine.system.CanineActionServlet.process(CanineActionServlet.java:27)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogi
c.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2117)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2023)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
[WARN] RequestProcessor - Unhandled Exception thrown: class java.lang.ClassCastException
<Feb 29, 2008 5:14:17 PM PST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext#3b0c3a - appN
ame: '_appsdir_vip_dir', name: 'vip', context-path: '/vip'] Root cause of ServletException.
java.lang.ClassCastException: com.bea.xbean.values.XmlAnyTypeImpl
at com.aligntech.canine.model.service.eai.xml.CreatePatientAndCaseSetupOrderXmlHelper.populateRequestContent(Cre
atePatientAndCaseSetupOrderXmlHelper.java:48)
at com.aligntech.canine.model.service.eai.xml.EaiServiceRequestXmlHelper.addServiceRequestPayload(EaiServiceRequ
estXmlHelper.java:61)
at com.aligntech.canine.model.service.eai.xml.EaiServiceRequestXmlHelper.getXml(EaiServiceRequestXmlHelper.java:
69)
at com.aligntech.canine.model.service.eai.EaiMessageService.sendPatientAndCaseSetupOrderCreation(EaiMessageServi
ce.java:157)
at com.aligntech.canine.model.service.eai.EaiMessageService.sendPatientAndCaseSetupOrderCreation(EaiMessageServi
ce.java:161)
at com.aligntech.canine.model.service.rxform.RxTreatmentService.createJDEPatientOrder(RxTreatmentService.java:41
7)
at com.aligntech.canine.model.service.rxform.RxTreatmentService.submitTreatment(RxTreatmentService.java:352)
at com.aligntech.canine.controller.action.rxform.RxSummaryAction.authorizedExecute(RxSummaryAction.java:88)
at com.aligntech.canine.controller.action.AuthorizedCanineAction.execute(AuthorizedCanineAction.java:26)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at com.aligntech.canine.system.CanineActionServlet.process(CanineActionServlet.java:27)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogi
c.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2117)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2023)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
<Feb 29, 2008 5:14:17 PM PST> <Debug> <Http> <BEA-000000> <weblogic.servlet.internal.WebAppServletContext#3b0c3a - appNa
me: '_appsdir_vip_dir', name: 'vip', context-path: '/vip': servlet found for the url-pattern: /us/en/auth/patient/rxform
/rxSummary.do>
I see that in weblogic 10 there is no xbean.jar.
Thanks,
Amit

Oats installation : problem to run OTM

Hy Everybody !
I've got a problem with my OATS installation.
What I've done :
Install OATS
Start console
Change port
I can connect to :
localhost/console
localhost/admin
localhost/olt
But I've got a problem with
localhost/otm
When i tried to connect nothing happend
Log send me following error :
[ServletContext#39916823[app:oats.ear module:otm path:/otm spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl#2604e66[ GET /otm/logon.jsp HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, / Referer: http://localhost:8188/ Accept-Language: fr UA-CPU: x86 Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729) Connection: Keep-Alive Cookie: JSESSIONID=cJs0Nm2LZpnlNG9PTb8xtkMY8ZCQn2hRlhh36wKbcbfmDh6hyCb4!288839633 ]] Root cause of ServletException. javax.servlet.jsp.JspException: Exception thrown by getter for property dataSources of bean logonForm at org.apache.struts.util.RequestUtils.lookup(RequestUtils.java:964) at org.apache.struts.taglib.bean.DefineTag.doEndTag(DefineTag.java:266) at jsp_servlet.__logon._jspService(__logon.java:552) at weblogic.servlet.jsp.JspBase.service(JspBase.java:35) 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.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at oracle.oats.otm.reports.utils.GZIPFilter.doFilter(GZIPFilter.java:64) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at oracle.oats.otm.reports.utils.AlwaysRevalidateCacheFilter.doFilter(AlwaysRevalidateCacheFilter.java:68) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at oracle.oats.otm.util.RequestEncodingFilter.doFilter(RequestEncodingFilter.java:46) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I understood hat I've got a problem with database connection.
When I check my oracle database i've got only users OATS OLT
I've tried to add OTM via Oracle express but when I use Oracle Testing Application Database Configuration it's impossible to add database even if I use existing schema or if I create a new one.
I've got different error message like:
c:\OracleATS\oxe\app\oracle\product\10.2.0\server\network\admin\tnsnames.ora (Accès refusé)
Sometimes a new pop up ask me Administrator password and OATS but after i've got error telling me user don't have enough right and when I give more rights to my user i've got the following error :
c:\OracleATS\oxe\app\oracle\product\10.2.0\server\network\admin\tnsnames.ora (Accès refusé)
Could you please give an advice ?
What ATS tool should i use to create the user ?
Thank you by advance !
Brice COLSON
Edited by: Brice on 9 mars 2011 01:34 
Any ideas ?
Thank by advance ! 
Hy folks I answer to myself !
The problem came from the installation.
I installed OATS on a VM with win xp and it works correctly.

Newly installed Service Registry gets Error 500 - Updates to config files..

Newly installed Service Registry gets "Error 500--Internal Server Error - Updates to config files not supported" when opening web page http://localhost:7001/registry/uddi/web. Deployment screen in WLS Console has a check mark in the health check column. 
Did you do post install steps after installation i.e.
a) Create JDBC data source with jndi name as jdbc/registryDS in WLS console and point to UDDI schema
b) Add JAAS config in JAVA_OPTIONS in setDomainEnv.sh as follows:
-Djava.security.auth.login.config=/<Oracle_HOME>/registry103/conf/jaas.config
c) Bounce WLS. 
I performed all the post install tasks and discovered that I am getting an error during the completion of WLS initialization. Error is included below.
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.idoox.wsdl.DefinitionImpl.getMessage(Ljavax/xml/namespace/QName;)Ljavax/wsdl/Message;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, com/idoox/wsdl/DefinitionImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for interface javax/wsdl/Definition have different Class objects for the type javax/xml/namespace/QName used in the signature
Notice, two class loaders:
weblogic/utils/classloaders/ChangeAwareClassLoader
sun/misc/Launcher$AppClassLoader
So, like URL (http://stackoverflow.com/questions/244482/how-to-deal-with-linkageerrors-in-java) mentions, if a class is loaded by Class Loader #1 and passed to an object created by Class Loader #2, this exception is going to be thrown.
####<Sep 3, 2009 9:11:43 AM MDT> <Error> <HTTP> <w2wz3lcw05> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251990703468> <BEA-101017> <[ServletContext#5399772[app:registry module:registry.war path:/registry spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl#ab1c28[
GET /registry/uddi/inquiry/wsdl HTTP/1.1
User-Agent: Java1.6.0_11
Accept: text/html, image/gif, image/jpeg, */*; q=.2
Connection: Keep-Alive
]] Root cause of ServletException.
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.idoox.wsdl.DefinitionImpl.getMessage(Ljavax/xml/namespace/QName;)Ljavax/wsdl/Message;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, com/idoox/wsdl/DefinitionImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for interface javax/wsdl/Definition have different Class objects for the type javax/xml/namespace/QName used in the signature
     at com.idoox.wsdl.factory.WSDLFactoryImpl.newDefinition(WSDLFactoryImpl.java:60)
     at com.idoox.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:419)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:309)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:272)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:198)
     at com.idoox.wsdl.util.WSDLUtil.readWSDL(WSDLUtil.java:126)
     at com.systinet.wasp.admin.PackageRepositoryImpl.validateServicesNamespaceAndName(PackageRepositoryImpl.java:885)
     at com.systinet.wasp.admin.PackageRepositoryImpl.registerPackage(PackageRepositoryImpl.java:807)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:611)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:643)
     at com.systinet.wasp.admin.PackageRepositoryImpl.update(PackageRepositoryImpl.java:553)
     at com.systinet.wasp.admin.PackageRepositoryImpl.init(PackageRepositoryImpl.java:242)
     at com.idoox.wasp.ModuleRepository.loadModules(ModuleRepository.java:198)
     at com.systinet.wasp.WaspImpl.boot(WaspImpl.java:383)
     at org.systinet.wasp.Wasp.init(Wasp.java:151)
     at com.systinet.transport.servlet.server.Servlet.init(Unknown Source)
     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(SecurityManager.java:121)
     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.ServletStubImpl.execute(ServletStubImpl.java:235)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) 
Hi timdsmith,
did you find a solution to this? I face the same problem, installed Service Registry 10.3 on WebLogic 10.3.1 & Database 11g with no errors. deployment went fine. When I try to acces console I get the same error message:
Error 500--Internal Server Error
org.idoox.wasp.WaspInternalException: java.lang.RuntimeException: Updates to config files not supported
Thx 
Hi user8631539,
Haven't found a resolution yet. Will post one if I do and you can do the same.
Thanks 
Yes, I have yet another casualty on this. I have seen a few similar topics on this...but they all seem to relate to using OC4J and not WLS. 
The problem was trying to install UDDI Registry in a weblogic container with SOA modules deployes.. If you install the uddi registry in a plain empty weblogic every thing will be ok.. There must be some conflic between soa jar libraries versions.. 
Please do check the following thread for exact behaviour of issue
OSR Installation to weblogic cluster
Any suggestions... i have compatible versions of OSR and Weblogic 11g (11.1.1.2 versions) and dedicated instance and domain for OSR only.
Still it keeps giving me the same error
]] Root cause of ServletException.
java.lang.ExceptionInInitializerError
     at com.systinet.wasp.admin.PackageRepositoryImpl.validateServicesNamespaceAndName(PackageRepositoryImpl.java:885)
     at com.systinet.wasp.admin.PackageRepositoryImpl.registerPackage(PackageRepositoryImpl.java:807)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:611)
Caused By: java.lang.RuntimeException: Cannot instantiate WSDLFactory:WSDLException: faultCode=CONFIGURATION_ERROR: Problem instantiating factory implementation.: com.idoox.wsdl.factory.WSDLFactoryImpl
     at com.idoox.wsdl.util.WSDLUtil.<clinit>(WSDLUtil.java:75)
And upon restart of server and the registry application
]] Root cause of ServletException.
org.idoox.wasp.WaspInternalException: java.lang.RuntimeException: Updates to config files not supported
at com.systinet.wasp.WaspImpl.boot(WaspImpl.java:399)
at org.systinet.wasp.Wasp.init(Wasp.java:151)

Error in server.log , while starting soa managed server - B2B not running

Hi All
After starting SOA managed server , we found following error in the server.log , we are successfully able to access em and admin console , but while trying to access B2B console getting no response.
Please help us in understaning this error.
[ServletContext#15501276[app:b2bui module:/b2bconsole path:/b2bconsole spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl#4e8b8[ GET /b2bconsole/faces/login.jspx HTTP/1.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Referer: http://172.16.130.34:7001/console/console.portal?_pageLabel=WebAppModuleTestingPage&_nfpb=true&WebAppModuleTestingPortletexpandNode=ROOTCHILDNODE1 Cookie: JSESSIONID=8R1ZM24XMQDs1Z22QNJ4YM1cMrGlKbd77nCTLkTW62Bkvw2nG6vx!-1614137459; ADMINCONSOLESESSION=LKZJM23fPzQQsM2GyHDHWtJ2L8nNNzmB3gNQG1n1phMwv41mJMVN!-145877631 ]] Root cause of ServletException. java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.trinidadinternal.convert.ColorConverter at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.faces.application.ApplicationImpl.newConverter(ApplicationImpl.java:1114) at com.sun.faces.application.ApplicationImpl.createConverter(ApplicationImpl.java:770) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.addConverterByTargetClass(ConverterValidatorRegistrationUtils.java:164) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:84) at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:77) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:206) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:329) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:86) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64) at oracle.adfinternal.controller.application.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:56) at oracle.adfinternal.controller.application.model.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:70) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260) 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:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.tip.b2b.ui.util.SessionTimeoutFilter.doFilter(SessionTimeoutFilter.java:240) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:143) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
Satendra Pare 
Which version of weblogic and SOA suite have you installed? Which OS are you using? Check on em whether soa-infra is up?
Regards,
Anuj 
Server details are as follows
soa server : 11.1.1
weblogic server : Version 10.3.2.0
SOAInra : Up and Runnign fine
OS Version: Linux 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
Thanks
Satendra Pare 
Hi Satendra,
Can you try after upgrading your SOA system to PS2 (11.1.1.3.0) and weblogic to 10.3.3
You may refer below blog for your system upgrade -
http://blogs.oracle.com/middleware/2010/05/installing_soa_suite_11113.html
You may skip the OSB part safely if you don't need that.
Regards,
Anuj 
Hi Anuj
Is upgradation the only solution? The Error *"java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.trinidadinternal.convert.ColorConverter"* ponints to some missing jars.
Thanks
Satendra Pare 
Hi Satendra,
Is upgradation the only solution?No, it is one of the better options (and my personal suggestion) as PS2 release is more stable and has many more functionalities and features than PS1. The error which you are getting may be due to a corrupt installation. In case you want to solve this error only and do not want to go for upgrade, then feel free to raise a case with support.
Regards,
Anuj

Categories

Resources