Error adding other root certs to Weblogic

I am using the trial 30-day version. I wonder whether it has any restrictions which
prevent from adding new root certificates to the ca.pem file. If this is not the
case, I will expose my problem.
I have added a new self-signed root certificate after the one that was contained
in the ca.pem, so there are now two root certificates:
********************** begin of the ca.pem file
-----BEGIN CERTIFICATE-----
MIICQzCCAe2gAwIBAgIBADANBgkqhkiG9w0BAQQFADCBqTELMAkGA1UEBhMCVVMx
EzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBGcmFuY2lzY28xFTAT
BgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJpdHkxIzAhBgNVBAMT
GkRlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5MR4wHAYJKoZIhvcNAQkBFg9zdXBw
b3J0QGJlYS5jb20wHhcNMDAwNTMwMjEzNzQ0WhcNMDQwNTE0MjEzNzQ0WjCBqTEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG
cmFuY2lzY28xFTATBgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJp
dHkxIzAhBgNVBAMTGkRlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5MR4wHAYJKoZI
hvcNAQkBFg9zdXBwb3J0QGJlYS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBIAkEA
3VEoD2Q2ln4PyilUNUyPa9yQxS6YqJk7xwWlAHZ5AAhq7dkosZDCNZYYYTZihpOx
GcgLwqY6gYZCN7pwlk+h/QIDAQABMA0GCSqGSIb3DQEBBAUAA0EAAFsKZZ9dc1na
5lHpO8EL85EPDPRyCJ9lTRw3bPMEqItyBuEAXh8woRgGN5j9KinDoWsmFCBO5MFy
qN5p4APL4w==
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIB6zCCAZWgAwIBAgIBATANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJlczES
MBAGA1UEBxMJQmFyY2Vsb25hMRIwEAYDVQQKEwlTYWZlbGF5ZXIxEjAQBgNVBAsT
CURldmVsb3BlcjENMAsGA1UEAxMEcm9vdDEkMCIGCSqGSIb3DQEJARYVc3VwcG9y
dEBzYWZlbGF5ZXIuY29tMB4XDTk5MTIzMTIzMDAwMFoXDTE5MTIzMTIzMDAwMFow
fjELMAkGA1UEBhMCZXMxEjAQBgNVBAcTCUJhcmNlbG9uYTESMBAGA1UEChMJU2Fm
ZWxheWVyMRIwEAYDVQQLEwlEZXZlbG9wZXIxDTALBgNVBAMTBHJvb3QxJDAiBgkq
hkiG9w0BCQEWFXN1cHBvcnRAc2FmZWxheWVyLmNvbTBcMA0GCSqGSIb3DQEBAQUA
A0sAMEgCQQCg+E0qVGLgZWSjcae1FHMap/8SBlbhQc3GbaL3NxbBDZGeaKZqzlTv
ZhGeWf3zEB17tbHE18hAxro6TA2i8MhVAgMBAAEwDQYJKoZIhvcNAQEEBQADQQAS
E2U64E9eu0dgJYktTK37YcTpyspwSabyeaziAktu99cCOQbCTYXGojouRekbkKAv
u8J28DSM62Me7W5zsPV2
-----END CERTIFICATE-----
********************** end of the ca.pem file
I did not modify the democert.pem or the demokey.pem files, as I want my weblogic
server to continue using the same SSLserver certificate than it was using before.
Then when I try to start the Weblogic server, I got the following error on the
console:
Starting WebLogic Server ....
<24-abr-01 16:21:33 CEST> <Notice> <Management> <Loading configuration file .\co
nfig\examples\config.xml ...>
log file: C:\bea\wlserver6.0sp1\.\config\examples\logs\weblogic.log
<24-abr-01 16:21:37 CEST> <Info> <Logging> <Only log messages of severity "Error
" or worse will be displayed in this window. This can be changed at Admin Consol
e> examples> Servers> examplesServer> Logging> General> Stdout severity threshol
d>
weblogic.security.CipherException: Incorrect encrypted block
at weblogic.security.RSApkcs1.decrypt(RSApkcs1.java:208)
at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:89)
at weblogic.security.X509.verifySignature(X509.java:243)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:440)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:942)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
<24-abr-01 16:21:41 CEST> <Alert> <WebLogicServer> <Inconsistent security config
uration, weblogic.security.AuthenticationException: Incorrect encrypted block
po
ssibly incorrect SSLServerCertificateChainFileName set for this server certifica
te>
weblogic.security.AuthenticationException: Incorrect encrypted block possibly
in
correct SSLServerCertificateChainFileName set for this server certificate
at weblogic.security.X509.verifySignature(X509.java:251)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:440)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:942)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
<24-abr-01 16:21:59 CEST> <Notice> <WebLogicServer> <WebLogic Server started>
<24-abr-01 16:21:59 CEST> <Notice> <WebLogicServer> <ListenThread listening on
p
ort 7001>
I would appreciate any help on this issue. I want to add the new root certificate
because I own a SSLclient certificate in my browser which I want the Weblogic
server to authenticate.
Thank you very much, David.

OK, I finally was able to understand what the error was. The new root certificate
cannot be added to the ca.pem file. You'd better create a new file called ca2.pem
with the new root certificate. Then you have go to SSL configuration section and
edit the 'Trusted CAFile Name' field to point to the ca2.pem file.
Easy but I had trouble to understand it from the documentation.
"David Ruana" <[email protected]> wrote:
>
I am using the trial 30-day version. I wonder whether it has any restrictions
which
prevent from adding new root certificates to the ca.pem file. If this
is not the
case, I will expose my problem.
I have added a new self-signed root certificate after the one that was
contained
in the ca.pem, so there are now two root certificates:
********************** begin of the ca.pem file
-----BEGIN CERTIFICATE-----
MIICQzCCAe2gAwIBAgIBADANBgkqhkiG9w0BAQQFADCBqTELMAkGA1UEBhMCVVMx
EzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBGcmFuY2lzY28xFTAT
BgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJpdHkxIzAhBgNVBAMT
GkRlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5MR4wHAYJKoZIhvcNAQkBFg9zdXBw
b3J0QGJlYS5jb20wHhcNMDAwNTMwMjEzNzQ0WhcNMDQwNTE0MjEzNzQ0WjCBqTEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG
cmFuY2lzY28xFTATBgNVBAoTDEJFQSBXZWJMb2dpYzERMA8GA1UECxMIU2VjdXJp
dHkxIzAhBgNVBAMTGkRlbW8gQ2VydGlmaWNhdGUgQXV0aG9yaXR5MR4wHAYJKoZI
hvcNAQkBFg9zdXBwb3J0QGJlYS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBIAkEA
3VEoD2Q2ln4PyilUNUyPa9yQxS6YqJk7xwWlAHZ5AAhq7dkosZDCNZYYYTZihpOx
GcgLwqY6gYZCN7pwlk+h/QIDAQABMA0GCSqGSIb3DQEBBAUAA0EAAFsKZZ9dc1na
5lHpO8EL85EPDPRyCJ9lTRw3bPMEqItyBuEAXh8woRgGN5j9KinDoWsmFCBO5MFy
qN5p4APL4w==
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIB6zCCAZWgAwIBAgIBATANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJlczES
MBAGA1UEBxMJQmFyY2Vsb25hMRIwEAYDVQQKEwlTYWZlbGF5ZXIxEjAQBgNVBAsT
CURldmVsb3BlcjENMAsGA1UEAxMEcm9vdDEkMCIGCSqGSIb3DQEJARYVc3VwcG9y
dEBzYWZlbGF5ZXIuY29tMB4XDTk5MTIzMTIzMDAwMFoXDTE5MTIzMTIzMDAwMFow
fjELMAkGA1UEBhMCZXMxEjAQBgNVBAcTCUJhcmNlbG9uYTESMBAGA1UEChMJU2Fm
ZWxheWVyMRIwEAYDVQQLEwlEZXZlbG9wZXIxDTALBgNVBAMTBHJvb3QxJDAiBgkq
hkiG9w0BCQEWFXN1cHBvcnRAc2FmZWxheWVyLmNvbTBcMA0GCSqGSIb3DQEBAQUA
A0sAMEgCQQCg+E0qVGLgZWSjcae1FHMap/8SBlbhQc3GbaL3NxbBDZGeaKZqzlTv
ZhGeWf3zEB17tbHE18hAxro6TA2i8MhVAgMBAAEwDQYJKoZIhvcNAQEEBQADQQAS
E2U64E9eu0dgJYktTK37YcTpyspwSabyeaziAktu99cCOQbCTYXGojouRekbkKAv
u8J28DSM62Me7W5zsPV2
-----END CERTIFICATE-----
********************** end of the ca.pem file
I did not modify the democert.pem or the demokey.pem files, as I want
my weblogic
server to continue using the same SSLserver certificate than it was using
before.
Then when I try to start the Weblogic server, I got the following error
on the
console:
Starting WebLogic Server ....
<24-abr-01 16:21:33 CEST> <Notice> <Management> <Loading configuration
file .\co
nfig\examples\config.xml ...>
log file: C:\bea\wlserver6.0sp1\.\config\examples\logs\weblogic.log
<24-abr-01 16:21:37 CEST> <Info> <Logging> <Only log messages of severity
"Error
" or worse will be displayed in this window. This can be changed at Admin
Consol
e> examples> Servers> examplesServer> Logging> General> Stdout severity
threshol
d>
weblogic.security.CipherException: Incorrect encrypted block
at weblogic.security.RSApkcs1.decrypt(RSApkcs1.java:208)
at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:89)
at weblogic.security.X509.verifySignature(X509.java:243)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:440)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:942)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
<24-abr-01 16:21:41 CEST> <Alert> <WebLogicServer> <Inconsistent security
config
uration, weblogic.security.AuthenticationException: Incorrect encrypted
block
po
ssibly incorrect SSLServerCertificateChainFileName set for this server
certifica
te>
weblogic.security.AuthenticationException: Incorrect encrypted block
possibly
in
correct SSLServerCertificateChainFileName set for this server certificate
at weblogic.security.X509.verifySignature(X509.java:251)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:440)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:942)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
<24-abr-01 16:21:59 CEST> <Notice> <WebLogicServer> <WebLogic Server
started>
<24-abr-01 16:21:59 CEST> <Notice> <WebLogicServer> <ListenThread listening
on
p
ort 7001>
I would appreciate any help on this issue. I want to add the new root
certificate
because I own a SSLclient certificate in my browser which I want the
Weblogic
server to authenticate.
Thank you very much, David.

Similar Messages

  • BEA-000802   weblogic.utils.NestedError: Error adding FD to epoll.

    hello,everyone,
    My weblogic have a problem.it often happens.
    <2010-7-14 下午01时15分26秒 CST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
    weblogic.utils.NestedError: Error adding FD to epoll.
    weblogic.utils.NestedError: Error adding FD to epoll
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:86)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1353)
    Truncated. see log file for complete stacktrace
    java.io.IOException: epoll_ctl failed: Bad file descriptor
    at jrockit.ext.epoll.EPoll.epollEnableOneshot(II)V(Unknown Source)
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:72)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    Truncated. see log file for complete stacktrace
    who can help me?
    thanks
    lijun

    hi everyone,
    i am waiting for you answers. is anyone here?
    thanks,
    lijun

  • PSE 9 Organizer Error Adding Keyword Tags and Other Woes

    Hello, everyone.  I am having a ton of problems with PSE 9 Organizer.  The most frustrating and biggest problem is that I believe my catalog has been corrupted beyond repair.  I spent all of yesterday tagging my photos.  I had no problems and everything seemed to be going well until all of the sudden, the organizer suddenly froze up.  I had to use the Windows task manager just to get it to close.  This happened several times.  Finally, the organizer locked up my computer and I had to restart.  I opened the catalog and didn't seem to have any problems at that point.  I was able to view all of the images, video files etc.  I was even able to open the editor from the organizer.  When I tried to add a tag to a photo it gave me an error.  All it said was "error adding keyword tag" then nothing.  I tried to delete the photo and all it said was "error deleting photo".  This "error" shows up any time I try to make any changes to all of the images.  I can't add any new photos, can't delete, or add tags.  I have repaired the catalog several times.  It found errors the first time, but evidently that didn't fix my problem.  I also optimized and deleted my thumbnail cache to see if that was the issue.  Still nothing.  I have other catalogs and they work fine, so it is something to do with this particular catalog.  Any suggestions on what to do next?  Can I move the pictures to a new catalog without losing the tags?  And no, I didn't write the tags to the images because I wasn't done tagging.  Besides, PSE doesn't always write the tags correctly, as you probably know. Next problem.   When I first open PSE and select the organizer, it doesn't alway open.  I can see it on my taskbar (Windows 7 64 bit), but I can't get the window to maximize.  I have to close and open several times to get the window to open.  Sometimes it randomly jumps to my second monitor like it can't decide where to go.  Very frustrating.  I would appreciate any suggestions about what to do.  Thanks.

    Back to the original question, after thinking about this for a couple days I have had two ideas for workarounds:
    1)  Copy my tag names into the photo metadata and create a new catalog to bring all of my images into.  This will allow me to keep all of my existing tags, and it MIGHT solve the tag display problem based on a test with a couple images in a new catalog.  The downsides to this are a) permanently writes my tags into the photo metadata which will be bad if I decide to change something later, b) loses all version sets, and c) loses all albums (although I don't have that many).  I found instructions for this workaround at http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#_Merging_Catalogs.
    2)  Live with the lack of color tag display in Organizer, and use reverse searches to find missing tag categories.  For example, if I want to find all photos that do not have a "Places" tag, I check the box next to the "Places" category (which also selects all sub-categories and tags below this).  Then I go to the Options drop-down in the Find Bar and "Hide best match results" and "Show results that do not match".  This gives me every image in my catalog that does not have a tag from the "Places" category, so I can go through and tag these as appropriate.
    I would have gone with #1 if it weren't for the permanence of the keywords.  I guess I have a commitment problem (or I just haven't got my tag hierarchy figured out yet).  Instead, I am going with #2 which should give me most of what I need for now.  I will still hold out some small glimmer of hope that Adobe manages a fix for this issue down the road.

  • Error Error oracle.iam.platform.context.ContextManager BEA-000000 IAM-0030007 org.xml.sax.SAXParseException: Line 1, Column 1 : XML-20108: (Fatal Error) Start of root element expected. error in oim logs

    Hi ,
    I am getting the below error at times in oim logs not able to find the reason please help.
    <Error> <oracle.iam.platform.context.ContextManager> <BEA-000000> <IAM-0030007
    org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
        at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
        at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
        at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
        at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
        at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
    <XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/bindToInstance encounter some problems: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    oracle.iam.platform.utils.ServiceInitializationException: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
        at oracle.iam.platform.Platform.getService(Platform.java:265)
        at oracle.iam.platform.OIMInternalClient.getService(OIMInternalClient.java:188)
        at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(tcDataBaseClient.java:151)
        at com.thortech.xl.client.dataobj.tcDataBaseClient.recoverConnection(tcDataBaseClient.java:401)
        at com.thortech.xl.client.dataobj.tcDataBaseClient.getInterface(tcDataBaseClient.java:385)
        at com.thortech.xl.dataaccess.tcDataBaseClient.close(tcDataBaseClient.java:349)
        at com.thortech.xl.server.tcDataBaseClient.close(tcDataBaseClient.java:62)
        at com.thortech.xl.server.tcDataBaseClient.finalize(tcDataBaseClient.java:43
    Caused By: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:247)
        at com.sun.naming.internal.VersionHelper12.loadClass(Ve
    <Class/Method: tcDataBaseClient/getInterface encounter some problems: RuntimeException encountered. Reconnecting!
    java.lang.NullPointerException
        at oracle.iam.platform.context.ContextManager.getCounter(ContextManager.java:697)
        at oracle.iam.platform.context.ContextManager.incrementCounter(ContextManager.java:684)
    <Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/close encounter some problems: Bean has been deleted.
    javax.ejb.NoSuchEJBException: Bean has been deleted.
    Thanks,
    Sahana

    hi Antara
    about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
    If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
    So you might get a different parser in a different environment.
    regards
    Jan Vervecken

  • Problem on web app using root context in weblogic 7.0.2

    I got problem on servlet which running on root context "/" in weblogic 7.0.2. I have remove the default web app (which use the root context) before the web app. The web application was deployed without any error. However, when the servlet run to the line calling HttpSession.setAttribute, the following exception occurs. The weblogic server is running on Solaris 8. anyone can help?
              java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
              at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1045)
              at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:477)
              at com.chase.infra.appcontrol.servlet.LoginServlet.doPostHK(Unknown Source)
              at com.chase.infra.appcontrol.servlet.LoginServlet.doPost(Unknown Source)
              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:1058)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
              at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
              at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5451)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              The weblogic.xml is
              <?xml version="1.0" encoding="UTF-8"?>
              <!DOCTYPE weblogic-web-app
              PUBLIC "-//BEA Systems, Inc.//DTD Web Application 7.0//EN"
              "http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd" >
              <weblogic-web-app>
              <context-root>/</context-root>
              </weblogic-web-app>

    Hie,
              We are facing the same problem; i.e. we are getting the same error message when we are trying to run our struts application on Weblogic 7.0.5 using JDK 1.3.1. This problem occured particularly when we tried to do a load testing using approx 20 concurrent users (a lesser load was supported though). Can you please let us know how this problem was sorted out on your end?
              thanks,
              Debanjan

  • XML-20108: (Fatal Error) Start of root element expected. - jdev 11.1.2.3

    Hello:
    I created a simple ADF Fusion Web app using HR schema based on Employees table.
    I am trying to get Contextual Events working and I did the following:
    Created two taskflows: TaskFlowA and TaskFlowB. TaskFlowA has a form based on employees and TaskFlowB has a table based on employees.
    Run the page and everything works.
    Now, in the property inspector based on the submit button, I added a contextual event to publish the event.
    Attempt to run the page again and I receive compile error:
    \WEB-INF\temp\adf\styles\cache\fusionFx-v2-1-desktop-pr245v-ltr-ie-7.0-cmp.css
    Error(1,1): <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    Any ideas to prevent/fix this problem?
    Thanks much
    Edited by: 966952 on Apr 9, 2013 5:51 AM

    As a temporary solution you could add below lines in the xml file
    <?xml version="1.0" encoding="UTF-8" ?>
    <test>
    </test>
    See, the link for more info: http://adfhowto.blogspot.in/2011/05/utility-to-remove-once-and-for-all-rdf.html

  • Can not get application bc4j for adding context root file

    Hi all,
    Can someone help me on this,
    i got this this error while trying to run my web based reporting:
    06/08/21 18:01:04 [SEVERE]: Error instantiating application at file:/C:/Documents and Settings/Bryan1/Desktop/Pattern Maching JSP 2006Feb/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/applications/bc4j.ear: Unable to get ApplicationConfig for bc4j : Error creating deployment directory: IO Error: The system cannot find the path specified.
    06/08/21 18:01:04 [SEVERE]: Error instantiating application at file:/C:/Documents and Settings/Bryan1/Desktop/Pattern Maching JSP May2006/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/applications/ITS.ear: Unable to get ApplicationConfig for ITS : Error creating deployment directory: IO Error: The system cannot find the path specified.
    2006-08-21 18:01:07.265 WARNING J2EE_OJR0007 Can not get application bc4j for adding context root file:/C:/Pattern Maching JSP May2006/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/config/default-web-site.xml
    Ready message received from Oc4jNotifier.
    Embedded OC4J startup time: 5282 ms.
    Target URL -- http://192.168.2.55:8988/Trans-Reporting-context-root/login.jsp
    06/08/21 18:01:07 Oracle Containers for J2EE 10g (10.1.3.0.0) - Developer Preview initializedIF i run http://192.168.2.55:8080/Reporting/login.jsp from web browser then is ok, but cannot straight run from JDeveloper? How to set the path?
    rgds,
    bryan

    Dear Frank,
    Thanks for ur reply but i still failed to access to my login.jsp
    I already select RUN from menu then clean <XXXX.jpr>, then rebuild the project and Run the project but still have the same problem.
    rgds,
    bryan

  • System restarted with messages "Error adding a request to the dispatcher ""

    Hi,
    Today ECC system restarted. The following error messages were found in SM21
    " Error adding a request to the dispatcher queue ( UP2)
    Request (type UP2) cannot be processed "
    I cheched Queue information for this system by navigating to Goto-->Server name --> information -->Queue information
    NOWP     0     21     2,000     25,181,608     25,181,608
    DIA     0     13     2,000     3,384,734     3,384,734
    UPD     0     29     2,000     185,673     185,673
    ENQ     0     69     2,000     18,928,082     18,928,082
    BTC     0     0     2,000     0     0
    SPO     0     3     2,000     5,539     5,539
    UP2     0     2,000     2,000     107,232     107,232
    This is the first time a error of this kind is noticed. Can some tell me what could be the root cause and how to fix this issue?
    Regards,
    Chaitanya.

    hello,
    in the UPD queue you see:
    UP2 0 2,000 2,000 107,232 107,232
    indicating that in a moment there were 2000 records in the dispatcher queue.
    In SM13 you recognize the records which update V2 are not procesed yet, they have the status "V1 processed".
    Are the UP2 work processes occupied?
    kind regards,
    Mercedes

  • Root exception is weblogic.rjvm.PeerGoneException:

    I have a problem doing the Look onto the Weblogic server.
              Here is the code I use in a method for this purpose and call the
              method from main(). I paste the code below (enclosed within "CODE
              BEGINS", "CODE ENDS")
              -----------------CODE BEGINS-----------------------------------------
                   System.out.println("DataCollector : Look up serverHome called");
                   Hashtable props = new Hashtable();
                   props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
                   props.put(Context.PROVIDER_URL, url);
                   props.put(Context.SECURITY_PRINCIPAL, userName);
                   props.put(Context.SECURITY_CREDENTIALS, passWord);
                   System.out.println("Before Inital Context "+props);
                   Context ctx = new InitialContext(props);
                   System.out.println("Initial Context successful");
                   serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
                   System.out.println("Look up successful");
                   ctx.close();
                   System.out.println("Closed context successfully");
              -----------------CODE ENDS-----------------------------------------
              On executing this piece of code, I receive the following Exceptions
              -------------OUTPUT OF CODE BEGINS---------------------
              DataCollector : Look up serverHome called
              Before Inital Context
              {java.naming.provider.url=T3://njecomprod06:10817,
              java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
              java.naming.security.principal=system,
              java.naming.security.credentials=security}
              Initial Context successful
              Exception in thread "main" javax.naming.CommunicationException. Root
              exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
              java.io.EOFException
              java.io.EOFException
              at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
              at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
              at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              -------------OUTPUT OF CODE ENDS---------------------
              This piece of code fails in the line
              serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              The weblogic server is standalone (not on a cluster). All other
              details give for this purpose like port no, username, password etc are
              correct.
              Also, On the WebLogic server prompt, the following stack trace is
              printed. Please let me know what is wrong in this look up code
              element.
              Thanks in advance for your help.
              -------------------------------------------------------EXCEPTION ON
              WEBLOGIC SIDE BEGINS--------------------------
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ] - with nested exception:
              [java.io.EOFException]
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              <Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
              <Uncaught Throwable in processSockets
              java.io.EOFException:
              Start server side stack trace:
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ]
              Start server side stack trace:
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ] - with nested exception:
              [java.io.EOFException]
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              - with nested exception:
              [java.io.EOFException:
              Start server side stack trace:
              java.io.EOFException
                      at java.io.DataInputStream.readInt(DataInputStream.java:343)
                      at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
                      at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
                      at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
                      at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
                      at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
                      at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
                      at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
                      at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
                      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
                      at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
                      at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
                      at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              -------------------------------------------------------EXCEPTION ON
              WEBLOGIC SIDE ENDS--------------------------
              

    You may want to open a support case with BEA to resolve this issue. I
              suspect that you may be using some server patches which have not also
              been applied to your WebLogic client JVMs. If that is the case,
              upgrading to the latest service pack may be the easiest and best remedy.
              Sincerely,
              Charlie Therit
              Developer Relations Engineer
              BEA Support
              Lakshmi Narasimhan wrote:
              >I have a problem doing the Look onto the Weblogic server.
              >
              >Here is the code I use in a method for this purpose and call the
              >method from main(). I paste the code below (enclosed within "CODE
              >BEGINS", "CODE ENDS")
              >
              >
              >-----------------CODE BEGINS-----------------------------------------
              >{
              >     System.out.println("DataCollector : Look up serverHome called");
              >     Hashtable props = new Hashtable();
              >     props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
              >     props.put(Context.PROVIDER_URL, url);
              >     props.put(Context.SECURITY_PRINCIPAL, userName);
              >     props.put(Context.SECURITY_CREDENTIALS, passWord);
              >     System.out.println("Before Inital Context "+props);
              >     Context ctx = new InitialContext(props);
              >     System.out.println("Initial Context successful");
              >     serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              >     System.out.println("Look up successful");
              >     ctx.close();
              >     System.out.println("Closed context successfully");
              >}
              >-----------------CODE ENDS-----------------------------------------
              >
              >On executing this piece of code, I receive the following Exceptions
              >
              >-------------OUTPUT OF CODE BEGINS---------------------
              >DataCollector : Look up serverHome called
              >Before Inital Context
              >{java.naming.provider.url=T3://njecomprod06:10817,
              >java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
              >java.naming.security.principal=system,
              >java.naming.security.credentials=security}
              >Initial Context successful
              >
              >Exception in thread "main" javax.naming.CommunicationException. Root
              >exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
              >java.io.EOFException
              >java.io.EOFException
              > at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
              > at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
              > at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >-------------OUTPUT OF CODE ENDS---------------------
              >
              >This piece of code fails in the line
              >
              >serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              >
              >The weblogic server is standalone (not on a cluster). All other
              >details give for this purpose like port no, username, password etc are
              >correct.
              >
              >Also, On the WebLogic server prompt, the following stack trace is
              >printed. Please let me know what is wrong in this look up code
              >element.
              >
              >Thanks in advance for your help.
              >
              >-------------------------------------------------------EXCEPTION ON
              >WEBLOGIC SIDE BEGINS--------------------------
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ] - with nested exception:
              >[java.io.EOFException]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              ><Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
              ><Uncaught Throwable in processSockets
              >java.io.EOFException:
              >Start server side stack trace:
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End server side stack trace
              >
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ]
              >
              >Start server side stack trace:
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ] - with nested exception:
              >[java.io.EOFException]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End server side stack trace
              > - with nested exception:
              >[java.io.EOFException:
              >Start server side stack trace:
              >java.io.EOFException
              >        at java.io.DataInputStream.readInt(DataInputStream.java:343)
              >        at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              >        at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              >        at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              >        at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              >        at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              >        at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              >        at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              >        at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              >        at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              >        at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              >        at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              >        at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              >        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              >        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End  server side stack trace
              >]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              >
              >-------------------------------------------------------EXCEPTION ON
              >WEBLOGIC SIDE ENDS--------------------------
              >
              >
              [att1.html]
              

  • Getting following error while deploying my webservice on weblogic 10.3

    hi
    I am tring to deploy a webservice (spring + cxf ) in weblogic 10.3
    applicationContext.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:p="http://www.springframework.org/schema/p"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:jee="http://www.springframework.org/schema/jee"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xmlns:jaxws="http://cxf.apache.org/jaxws"
    xsi:schemaLocation="
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
    http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd
    http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
    http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">
    <!-- Scan for both Jersey Rest Annotations a -->
    <import resource="classpath:META-INF/cxf/cxf.xml" />
    <import resource="classpath:META-INF/cxf/cxf-extension-http-binding.xml"/>
    <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
    <context:component-scan base-package="com.persistent.rest"/>
    <context:annotation-config />
    <jaxws:endpoint
    id="accountProcess"
    implementor="com.persistent.rest.GetAccountListImpl"
    address="/"
    bindingUri="http://apache.org/cxf/binding/http" >
    <jaxws:serviceFactory>
    <bean class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">
    <property name="wrapped" value="false" />
    </bean>
    </jaxws:serviceFactory>
    </jaxws:endpoint>
    <bean>...........</bean>
    </beans>
    web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>springCXFWeb</display-name>
    <context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>WEB-INF/applicationContext.xml</param-value>
    </context-param>
    <listener>
    <listener-class>
    org.springframework.web.context.ContextLoaderListener
    </listener-class>
    </listener>
    <servlet>
    <servlet-name>CXFServlet</servlet-name>
    <servlet-class>
    org.apache.cxf.transport.servlet.CXFServlet
    </servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>CXFServlet</servlet-name>
    <url-pattern>/*</url-pattern>
    </servlet-mapping>
    </web-app>
    Getting following error while deploying my webservice on weblogic 10.3
    <Dec 4, 2009 2:04:04 PM PST> <Error> <org.springframework.web.context.ContextLoader> <BEA-000000> <Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers.
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259964185054' for task '2'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'springCXFApp'.>
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'springCXFApp'.>
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    thanks

    hi
    I am tring to deploy a webservice (spring + cxf ) in weblogic 10.3
    applicationContext.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:p="http://www.springframework.org/schema/p"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:jee="http://www.springframework.org/schema/jee"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xmlns:jaxws="http://cxf.apache.org/jaxws"
    xsi:schemaLocation="
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
    http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd
    http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
    http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">
    <!-- Scan for both Jersey Rest Annotations a -->
    <import resource="classpath:META-INF/cxf/cxf.xml" />
    <import resource="classpath:META-INF/cxf/cxf-extension-http-binding.xml"/>
    <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
    <context:component-scan base-package="com.persistent.rest"/>
    <context:annotation-config />
    <jaxws:endpoint
    id="accountProcess"
    implementor="com.persistent.rest.GetAccountListImpl"
    address="/"
    bindingUri="http://apache.org/cxf/binding/http" >
    <jaxws:serviceFactory>
    <bean class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">
    <property name="wrapped" value="false" />
    </bean>
    </jaxws:serviceFactory>
    </jaxws:endpoint>
    <bean>...........</bean>
    </beans>
    web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>springCXFWeb</display-name>
    <context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>WEB-INF/applicationContext.xml</param-value>
    </context-param>
    <listener>
    <listener-class>
    org.springframework.web.context.ContextLoaderListener
    </listener-class>
    </listener>
    <servlet>
    <servlet-name>CXFServlet</servlet-name>
    <servlet-class>
    org.apache.cxf.transport.servlet.CXFServlet
    </servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>CXFServlet</servlet-name>
    <url-pattern>/*</url-pattern>
    </servlet-mapping>
    </web-app>
    Getting following error while deploying my webservice on weblogic 10.3
    <Dec 4, 2009 2:04:04 PM PST> <Error> <org.springframework.web.context.ContextLoader> <BEA-000000> <Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers.
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource http://META-INF/cxf/cxf.xml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.apache.cxf.wsdl11.WSDLManagerImpl: Constructor threw exception; nested exception is java.lang.InternalError: erroneous handlers
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259964185054' for task '2'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    <Dec 4, 2009 2:04:04 PM PST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'springCXFApp'.>
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'springCXFApp'.>
    <Dec 4, 2009 2:04:04 PM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    Truncated. see log file for complete stacktrace
    java.lang.InternalError: erroneous handlers
    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 org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
    Truncated. see log file for complete stacktrace
    thanks

  • Issues in IDoc Sender Scenario:IDoc  with errors added

    Hi all
             Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
    status 56 : External segment name E2KOMG003 cannot be interpreted
    status 60 : Basic IDoc type COND_A03 could not be found.
    And the segments displayed in data record  are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
    Would any one help in resolving the issue.
    Thanks,
    Chilanka

    Hi,
    >>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
    no you cannot create any partner profiles in XI
    for more about IDOC configuration in XI check :
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Error:  The local root folder, ZZZZZZ, does not exist.  Please...

    Dreamweaver newest - Cloud
    Windows 7 Prof 64b SP1
    Everyday now upon firing up Dreamweaver I am getting the same error. As long as I worked on this certain site last the day before, dreamweaver of course tries to load that site upon the next startup.
    The error:  The local root folder, ZZZZZZ, does not exist.  Please choose a new local root folder
    I have typed the path myself and browsed to it many times.  When I go into the Site manager/edit site to correct this, it already has the correct path listed there.  If I just leave what is there and hit save, it doesn't work.  Once re entering is done it allows me to work on the site again. Connecting to remote/upload files and everything works fine.  I can close DW and reopen and all will be fine, for a while.    If I close it and maybe two hours later come back to work on it, DW will report that same error again on startup.
    Other editors of the site with same cloud version of DW and same site settings are not having this error. We've combed for differences.
    I've deleted the site definition altogether and recreated it.  It does not stop the error.
    I found some old references to this issue in the old macromedia forums dealing with Mac and spaces or odd characters being an issue in the local folder path. I'm on windows, but the complaints sounded so similar I decided to try a test suggested there.  Their suggestion was to create a new blank html file, without saving, add some text, select the text, use the link icon in the properties manager to drag a link out to any file in the files panel.  Upon doing so, DW creates a full local path that you can see in your html since you haven't saved the file yet.  The suggestors of this test said you should see if your "mac" and DW was having trouble with spaces or odd characters in the path.   Well the following path shows a PIPE character being created in the path by DW on my test page. 
    file:///W|/private/09 Websites/zzzzzz/index.html
    Could this be showing there is some kind of issue that I need to correct?  Or is this typical?  See the pipe character being listed after the network drive letter of W
    Our local root folder path:
    W:\private\09 Websites\zzzzzz\
    Server Settings:
         Root Directory:
    public_html/zzzzzz.com/
         Web URL:
    HypertextTransferProtocolCOLON//worldwideweb.zzzzzz.commercial/
    Any help or suggestions would be appreciated.

    Sudarshan Thiagarajan wrote:
    remote
    /home/zzzzz/public_html/zzzzz.com
    Is this how your remote setting is defined? If it is, do you have a folder called zzzzz.com on your remote server trailing public_html? Ideally public_html is your website root - index.html resides within that, unless your configuration states otherwise.
    To come to your actual question of the local root folder, yes, your file manager wont show files if the connection fails. However, accessing it depends on the permissions you have on your network drive. Have you checked that?
    I'm not sure why our guy has another folder underneath public_html. My guess is he has some company related hosted test folders for various things under there.  I can see a couple other folders under public_html while checking with filezilla. I suppose he just directed our domain to our web folder under public_html. 
    Again, two others here are using these exact same settings with no root folder errors from DW. We've checked many times and all is the same for them.
      Here are some screen grabs of the settings if this makes it more clear.
    This last one showing the remote connection address under the files/assets panel is the one that looks strange to me.  It shows a home folder / then a folder with our site name / then public_html / then our sitename.com .    Seems convoluted to me.  But it works for everyone else so I'm not sure if this error I'm getting has anything to do with these settings or if there is just some old DW settings file hung up in my system that I need to find and delete or what.
    Thanks for any ideas.

  • Error in using tag library uri='weblogic.tld'

    Hmmm...
    I'm trying to config my userprofile by creating it in the tools application (myserver/tools/index.jsp),
    but when I try to access the Unified Profile Types I get an Error 500 Internal
    Server Error in my webbrowser. The weblogic.log prints out an errormessage that
    sounds something like this:
    ####<30-Aug-01 16:30:14 CEST> <Error> <HTTP> <Ast-WT01> <server01> <ExecuteThread:
    '14' for queue: 'default'> <system> <> <101020> <[WebAppServletContext(3530676,tools)]
    Servlet failed with Exception>
    weblogic.servlet.jsp.JspException: (line 24): Error in using tag library uri='weblogic.tld'
    prefix='wl': For tag 'repeat', cannot load extra info class 'weblogicx.jsp.tags.RepeatTagInfo'
    I'm running weblogic 6.0 and wlcs 3.5. I'm sure of that the tag libraries are
    correct and they are located under tools/web-inf.

    Hmmm...
    I'm trying to config my userprofile by creating it in the tools application (myserver/tools/index.jsp),
    but when I try to access the Unified Profile Types I get an Error 500 Internal
    Server Error in my webbrowser. The weblogic.log prints out an errormessage that
    sounds something like this:
    ####<30-Aug-01 16:30:14 CEST> <Error> <HTTP> <Ast-WT01> <server01> <ExecuteThread:
    '14' for queue: 'default'> <system> <> <101020> <[WebAppServletContext(3530676,tools)]
    Servlet failed with Exception>
    weblogic.servlet.jsp.JspException: (line 24): Error in using tag library uri='weblogic.tld'
    prefix='wl': For tag 'repeat', cannot load extra info class 'weblogicx.jsp.tags.RepeatTagInfo'
    I'm running weblogic 6.0 and wlcs 3.5. I'm sure of that the tag libraries are
    correct and they are located under tools/web-inf.

  • Error in rendering root for dialog

    Hello experts,
    After netweaver 2004 s - SPS 15, we have a
    issue with our planning application (BI-
    integrated planning) / variables. For all our
    planningsfunctions with a VARV command in it, the
    java.lang.NullPointerException occurs.
    SAP Note 1134947 concerns a similar problem, but that
    note is already in SPS 15. Before sps 15 we have'n got a any problems with the planningsfunctions.
    The error occurs in the planningsfunction with VARV in it. For example.
    DATA ZFTE_NEW TYPE F.
    DATA ZMAAND TYPE 0CALMONTH.
    DATA ZMUT TYPE ZMUTATIE.
    DATA ZDATUM TYPE 0CALMONTH.
    DATA KEYFIG TYPE KEYFIGURE_NAME.
    ZFTE_NEW = VARV (ZVARFTE).
    ZDATUM = VARV (ZCALMNTHFR).
    etc...
    Result is the java error and not the variable sceen
    If we change / hard coded the variables
    ZFTE_NEW = 1.
    ZDATUM = '200801'.
    The function results then with no errors, but this is not an option.
    After executing the planningsfunction in the wad the error in rendering root for dialog DLG_VARIABLE occurs.
    Anyone has this problem as well?
    With regards,
    Dennis
    java.lang.NullPointerException
    at
    com.sap.ip.bi.webapplications.ui.dialogs.variab
    lescreen.control.AcVariableScreenControl.getCur
    rentVariantName
    (AcVariableScreenControl.java:641)
    at
    com.sap.ip.bi.webapplications.ui.dialogs.variab
    lescreen.control.AcVariableScreenControl.buildU
    rTree(AcVariableScreenControl.java:206)
    at
    com.sap.ip.bi.webapplications.ui.framework.base
    .impl.CompositeBuildUrTreeTrigger.process
    (CompositeBuildUrTreeTrigger.java:33)
    at
    com.sap.ip.bi.webapplications.ui.unifiedrenderi
    ng.controls.MatrixLayoutCell.iterateOverChildre
    n(MatrixLayoutCell.java:82)
    at
    com.sap.ip.bi.webapplications.ui.framework.base
    .impl.CompositeBuildUrTreeTrigger.process
    (CompositeBuildUrTreeTrigger.java:36)
    Long description of the error:
    com.sap.ip.bi.webapplications.runtime.DialogExc
    eption: Error in rendering root for
    dialog "DLG_VARIABLE"
    at
    com.sap.ip.bi.webapplications.ui.dialogs.framew
    ork.UiDialog.render(UiDialog.java:270)
    at
    com.sap.ip.bi.webapplications.ui.dialogs.framew
    ork.rendering.DialogRenderingRootNode.processRe
    ndering(DialogRenderingRootNode.java:50)

    Dear D.C.M,
    please make shure that the variables are set .e.g by displaying the variables values in a message or by debugging it.
    ZFTE_NEW = VARV (ZVARFTE).
    ZDATUM = VARV (ZCALMNTHFR).
    break-point.
    if zfte_new is initial.
    message .. with zfte_new.
    endif.
    *if ZDATUM is initial.
    message ... with ZDATUM.
    *endif.
    Regards
    Matthias Nutt
    SAP Consulting Switzerland

  • Error adding buffer entry when using Asynchronous mode of JRA and JCO call

    Enviroment: XMII 12.1.4 / CE EhP1 SP03
    When I using SAP JRA Function Call or SAP JCO Funciton Call in transaction, it works well when I choose 'Process Type' as 'Synchronous processing' in 'Data Buffering Configuration' tab. But when I use 'Asynchronouse processing' it doesn't work.
    I check the Netweaver logs, there some logs like following:
    Error adding buffer entry (com.sap.xmii.dataqueue.DataBufferManager)
    Couldn't add buffer entry (com.sap.xmii.dataqueue.DataBufferManager)
    ManagedConnectionImpl.dissociateConnections(), dissociation of a non-cci transaction, H1, C1(com.sap.mw.jco.jra)
    how could I solve this problem?

    Solved after deploy 12.1 SP05 (xMII 12.1.5 build 91)

Maybe you are looking for