Recurring errors BEA-101083 and BEA-000403

Hello.
My server configuration is:
Intel(R) Core(TM) i5-3470 3.20 GHz (2 processors)
12 GB RAM
Windows Server 2008 R2 Enterprise
I have Weblogic Server 12C installed on this machine.
When I deploy my ADF application on weblogic server it works normally. But in logs ( in the Enterprise manager - Fusion Middleware Control 12c) I see two errors :
Message ID
BEA-101083
Message Level
7
Relationship ID
0
Component
PortalMS3
Module
HTTP
Host
CSPORTAL
Host IP Address
192.100.100.27
User
<WLS Kernel>
Thread ID
ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'
ECID
6e1a4bf5-904c-4412-b2dc-d778ee30a96f-00000b24
Message
Connection failure. java.io.IOException: Программа на вашем хост-компьютере разорвала установленное подключение
at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225) at sun.nio.ch.IOUtil.read(IOUtil.java:198) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375) at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:747) at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:733) at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:1017) at weblogic.socket.NIOSocketMuxer.readFromSocket(NIOSocketMuxer.java:642) at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:951) at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:928) at weblogic.socket.NIOSocketMuxer.process(NIOSocketMuxer.java:507) at weblogic.socket.NIOSocketMuxer.processSockets(NIOSocketMuxer.java:473) at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)
And
Message ID
BEA-000403
Message Level
7
Relationship ID
0
Component
PortalMS3
Module
Socket
Host
CSPORTAL
Host IP Address
192.100.100.27
User
<WLS Kernel>
Thread ID
ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'
ECID
6e1a4bf5-904c-4412-b2dc-d778ee30a96f-00000b24
Message
IOException occurred on socket: Socket[addr=/192.100.100.27,port=65202,localport=7004] java.io.IOException: Программа на вашем хост-компьютере разорвала установленное подключение. java.io.IOException: Программа на вашем хост-компьютере разорвала установленное подключение
at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225) at sun.nio.ch.IOUtil.read(IOUtil.java:198) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375) at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:747) at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:733) at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:1017) at weblogic.socket.NIOSocketMuxer.readFromSocket(NIOSocketMuxer.java:642) at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:951) at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:928) at weblogic.socket.NIOSocketMuxer.process(NIOSocketMuxer.java:507) at weblogic.socket.NIOSocketMuxer.processSockets(NIOSocketMuxer.java:473) at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)
Russian text is meaning : "Program on your host computer breaked connection"
This errors repeated every minute.

Hi,
This seems to be a known issue with weblogic 12.1.2 (Bug 18073982)
I would recommend you to open a SR with Oracle to check further on this.
Thanks,
Sharmela

Similar Messages

WL 8.1 BEA-101083 error when submitting a form using javascript (IE only)

Hello,
I have a JSP page that is submitting a form with javascript document.form.submit()
after checking the validity of form element values, but I randomly get a BEA-101083
error. The jsp page has worked fine for several year in IPlanet, and Sun One
7 application server, but when ported over to WebLogic 8.1 SP2 the error manifests
itself. Basically, when user submits the form, the next page is displayed with
null values, and soon after the following stack trace appears in the server log.
This error only occurs when the client browser is IE, Netscape works fine.
Thanks,
-Colin
<WLS Kernel>> <> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@9bb9300
- idle tim
eout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period
of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(Lweblogic.time.common.Schedulable;)V(SocketMuxer.java:775)
at weblogic.time.common.internal.ScheduledTrigger.run()Ljava.lang.Object;(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.Privil
egedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.a
cl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic.kernel.ExecuteThread;)V(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(Lweblogic.kernel.ExecuteThread;)V(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)

Checkboxes only submit a value when they are "on"
They submit nothing if they are not selected.
The problem comes - do you interpret no checkbox values as "clear all values" or "leave the values alone"? Struts assumes the latter.
Your form is probably being kept in session?
Try implementing the reset() method of your action form and set its property to be equivalent to no checkboxes selected.

Error BEA-101083 Socket Timeout

Hello, we have a WebLogic Server 8.1 SP2 and we found the following error:
<Dec 12, 2005 3:33:32 AM CET> <Error> <HTTP> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1cc2438 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Any idea?
Thanks

As lot fo people we have the same problem.
But I have still not found a concreate solution.
####<08-May-2006 10:02:36 o'clock CEST> <Error> <HTTP> <quatro> <WlsAdm> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@8db03f0 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
     at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(Lweblogic/time/common/Schedulable;)V(SocketMuxer.java:799)
     at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(ScheduledTrigger.java:243)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
     at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
     at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
     at weblogic.time.server.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:50)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
     at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
>

Question:BEA-101083 error weblogic8.16???

platform:AS5 weblogic8.16
managed server log display error
####<2009-9-7 <Error> <HTTP> <web3> <web03> <ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <BEA-101083> <Connection failure.
java.net.SocketException: Error in poll for fd=47, revents=32
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:131)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
so why display this error?? how can i solve this problem??

是连接池的问题，调整一下试一试

HTTP Error BEA-101083

Hi all.
I am testing in a BEA WebLogic Server 8.1 SP1 an application that uses Struts.
When I open a form, sometimes but not always, I get the following error:
<Jul 6, 2004 3:59:47 PM CEST> <Error> <HTTP> <BEA-101083> <Connection failure.
java.net.SocketException: Error in poll for fd=26, revents=8
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:128)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
This error does not produce any malfunction in the application. On the browser
side, anything strange is detected, but I'd like to know the reason of this in
order to avoid the exception to raise. I have no idea about whether this is related
to the BEA Weblogic configuration, to something in my application, ...
Has someone experienced something similar or knows some possible reason?
Thanks.

Getting same error even in WLI8.5 SP5
BEA-101083
####<Mar 2, 2006 4:26:11 PM EST> <Error> <HTTP> <mariner2.nasaprs.com> <server1> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101083> <Connection failure.
java.net.SocketException: Error in poll for fd=349, revents=32
at weblogic.socket.PosixSocketMuxer.processSockets()V(PosixSocketMuxer.java:131)
at weblogic.socket.SocketReaderRequest.execute(Lweblogic/kernel/ExecuteThread;)V(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
>
If anyone come up with any solution or why it happens, send email.

BEA-101083 error

environment details:
PT 8.49.06
Web server on: Windows 2003
Bea Weblogic: weblogic 9.2 mp1-p2
receiving the error messages in the webserver log file. please see below.
####<May 22, 2008 8:56:17 AM PDT> <Error> <HTTP> <UCBFASP1> <PIA> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1211471777758> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a6be6e:Socket[addr=/10.188.10.156,port=15371,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
     at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:947)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<May 22, 2008 8:56:42 AM PDT> <Error> <HTTP> <UCBFASP1> <PIA> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1211471802758> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@5b669c:Socket[addr=/10.88.10.56,port=22327,localport=7001] - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
     at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:947)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Users are getting disconnected/timedout when working on the application.
This needs to be resolved asap. Please can someone help...

Are you able to reproduce the same behaviour in non-production env ?
I would try to install the WL9.2MP1-patch 4 available here below :
ftp://ftp.peoplesoft.com/outgoing/ptools/weblogic/9.20/mp1/patches/
Is it producing only on workload ? Is it a new behaviour ? Did you change some conf ?
I would advise you, once more, to raise a case to your support.
Nicolas.

BEA-101083 Connection failure

While trying to publish mesaage by MQ 5.3 .I got the following error
Please help.
<Error> <HTTP> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff
3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Hi, we are running WLS 8.1 SP 5 on Linux and are having this problem. It appears to have an impact on our client/GUI in the form of premature session timeout.

SocketException BEA-101083 Weblogic 9.2

Hi,
we are facing a problem in our production environment, we get pratically every minutes the following exception :
<30 juin 2008 10 h 27 CEST> <Error> <HTTP> <BEA-101083> <Connection failure.
java.net.SocketException: Error in poll for fd=287, revents=32
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:133)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
What can be the cause of this ? Our users are telling us that the application goes very slow and this is the only abnormal log that we found.
Thank you,
Quentin Anciaux
<[email protected]>

Hi, the problem happens pratically once or two per minute while the application is in use... when the application is not used, no error happens.
So it happens very often... I thought it could be a problem with a proxy/firewall in the middle, but according to the guys in charge of this, nothing has changed on his side.
I've read things about a possible bug in the nativeIO implementation, would it be safe to deactivate nativeIO to see if this bug arise with pure java socket ?
Also this problem only occurs in our production environment, we have 4 others environment used for testing/training/integration and this error does not occur there.
Thanks for any help,
Quentin Anciaux

BEA-101083 Connection failure.java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@16907c at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger

While trying to publish mesaage by MQ 5.3 .I got the following error
          Please help.
          <Error> <HTTP> <BEA-101083> <Connection failure.
          java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff
          3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
          at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
          at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


Can you help me ? I have the same problem.

Integrate with BEA Portal and Lotus Domino R5.0.12

Deal all:
I got a problem when I integrate with BEA Portal and Lotus Domino R5.0.12.
my environment is below:
- Domain Server :
Lotus Domino Server R5.0.12
BEA Personal Messaging API 4.3
(test successful on local host)
- Application Server:
BEA Weblogic 8.15
BEA Groupware portlets 2.5
I got connection successful message when I using "Domino Service Connection"
but I got "CZ: VERSION CONFLICT" error message when I add a new account by
Compoze_Groupware-Edit Account user interface.
Have anybody met the error message before... and know how to sovle the problem..
I appreciated any suggest or comment~~~
detail error message is below:
portlets.compoze.groupware.exception.ConnectionException: CZ: VERSION CONFLICT at portlets.compoze.groupware.controls.provider.SessionControlImpl.createSession(SessionControlImpl.jcs:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381) at $Proxy19.createSession(Unknown Source) at portlets.compoze.groupware.controls.provider.GroupwareProviderControlImpl.updateAccount(GroupwareProviderControlImpl.jcs:4825) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:249) at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85) at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224) at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:109) at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:207) at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315) at $Proxy11.updateAccount(Unknown Source) at portlets.compoze.content.options.accounts.editAccount.editAccountController.saveChangesAccountAction(editAccountController.jpf:534) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1512) at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1447) at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:778) at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211) at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:608) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1504) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:674) at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527) at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1734) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1754) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:561) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:121) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:150) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:109) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:224) at com.bea.netuix.nf.ControlLifecycle$3.visit(ControlLifecycle.java:171) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:355) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:126) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:173) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:150) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Hi,
The reason why you are seeing this exception is because there is a mismatch between the version of the WLPM API used by the portlets, with the version of the service that you have installed on you Domino server.
To explain a little, there are two sides to the API that is used to communicate with Lotus Domino:
1) the Java API side (used by the portlets that you have installed in the portal)
2) the Domino Service side (installed as a DSAPI filter in the HTTP task of a Domino Server)
Each Java API jar and Domino Service Executable are branded with a version number, which in your case does not match because the portlets came with one version of the Java API, and you have installed a non-matching version of the service on the Domino Service side (you probably extracted the executable for the service installation from the "BEA Personal Messaging API 4.3" bundle or installer).
The solution for this is to:
1) uninstall the Domino Service that you have plugged into the domino service
2) extract the Domino Service installer which was included with the portlet bundle. This is located in the "Program Files\compoze\groupware_portlets_bea-2.5\8.1\service\domino" directory if you ran the portlet installer, or in the "groupware_portlets_bea81-noinstall-25\groupware_portlets_bea-2.5\8.1\service\domino" directory if you used the "no-install" zip file.
As a tip, to quickly check whether the versions of the service and Java APIâ€™s that you are using are matching, perform the following steps:
1) hit the domino server with the following URL and notice the "service version": http://domino_service_url:http_port/compoze.czdo. This should be something like "Service Version: 3.6.102"
2)in your portal application (or in the portlet install bundle), open the harmony_portlets.jar file with winzip, then find the "compoze_products_information.properties" file. In this file, notice the "product.domino" version (e.g. product.domino = 3.6.102)
3) the two versions you have inspected must match in order for the connection between the portlet and service to succeed.
If you have verified that the "service" version and "java API" version (located in %portal_app_dir%/APP-INF/lib/harmony_portlets.jar, and you are still getting the exception, it is likely that there is a "harmony_portlets.jar" that included an old version of the Java API located somewhere in the portal server classpath. In this case, make sure that the only harmony_portlets.jar in the classpath is the one that was included with the portlet bundle that you have installed.
Regards,
Lev

PageFlow Bea 9 and BIRT

hello!
I'm trying to integrate in one project my old bea8 sp5 project updated with the workshop to bea 9.2 AND reports in eclipse BIRT.
i have build a war app with reports in this new bea 9.2, and it works fine, but it needs the
<wls:container-descriptor>
<wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
</wls:container-descriptor>
OR
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
modification into weblogic.xml, to work properly.
in the other hand, i have my old app made in workshop 8 sp5, imported in the new enviroment. It works just fine too.
but, when i try to join both, i need to add the
container-descriptor tag in the updated application (where i am making the mixture) to get access to reports pages, then i have an error:
Module named 'prototipo' failed to deploy.
weblogic.application.ModuleException:
where prototipo is the name of the old app, updated to w9.
the complete stack trace in log file is
####<19-jul-2006 16H27' GMT-03:00> <Error> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254341> <BEA-149265> <Failure occured in the execution of deployment request with ID '1153337225730' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
     at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
     at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
     at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
     at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
     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:494)
     at java.lang.Class.newInstance0(Class.java:350)
     at java.lang.Class.newInstance(Class.java:303)
     at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
     at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
     at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
     at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
     at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254856> <BEA-149004> <Failures were detected while initiating distribute task for application 'prototipo'.>
####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254872> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
     at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
     at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
     at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
     at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
     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:494)
     at java.lang.Class.newInstance0(Class.java:350)
     at java.lang.Class.newInstance(Class.java:303)
     at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
     at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
     at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
     at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
     at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
data that could help
i tried change weblogic.xml with "wls:" form, and without it. i don't understand the difference... but in both cases nothing changed.
i search for LogFactoryImpl class in jar files and i had find one, so i delete it from webcontent/web-inf/lib, but the problem stills goes on.
if all the code and jar files are together but prefer-web-inf-classes tag is not used, i have no deployment error, but i can't view reports, of course.
the application has pageflows, ejb's and controls, from bea products. and when i imported it, i choose use beehive in the options.
BIRT version is 2.1.0
JDK version jdk150_04
weblogic.xml:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:wls="http://www.bea.com/ns/weblogic/90">
     <wls:container-descriptor>
          <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
     </wls:container-descriptor>
     <context-root>procesoIngreso</context-root>
     <wls:library-ref>
          <wls:library-name>jstl</wls:library-name>
          <wls:specification-version>1.1</wls:specification-version>
          <wls:implementation-version>1.1.2</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>beehive-controls-1.0-war</wls:library-name>
          <wls:specification-version>1.0</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>weblogic-controls-1.0-war</wls:library-name>
          <wls:specification-version>1.0</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>struts-1.1</wls:library-name>
          <wls:specification-version>1.1</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>struts-1.2</wls:library-name>
          <wls:specification-version>1.2</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>beehive-netui-resources-1.0</wls:library-name>
          <wls:specification-version>1.0</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
     <wls:library-ref>
          <wls:library-name>beehive-netui-1.0</wls:library-name>
          <wls:specification-version>1.0</wls:specification-version>
          <wls:implementation-version>1.0</wls:implementation-version>
     </wls:library-ref>
</wls:weblogic-web-app>
The original weblogic.xml (when workshop imports the old project) was
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="http://www.bea.com/ns/weblogic/90"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
     <jsp-descriptor>
          <debug>true</debug>
     </jsp-descriptor>
     <url-match-map>
          weblogic.servlet.utils.SimpleApacheURLMatchMap
     </url-match-map>
     <context-root>procesoIngreso</context-root>
     
     <library-ref>
          <library-name>struts-1.1</library-name>
          <specification-version>1.1</specification-version>
          <implementation-version>1.0</implementation-version>
     </library-ref>
     <library-ref>
          <library-name>beehive-netui-resources-1.0</library-name>
          <specification-version>1.0</specification-version>
          <implementation-version>1.0</implementation-version>
     </library-ref>
     <library-ref>
          <library-name>beehive-netui-1.0</library-name>
          <specification-version>1.0</specification-version>
          <implementation-version>1.0</implementation-version>
     </library-ref>
     <library-ref>
          <library-name>jstl</library-name>
          <specification-version>1.1</specification-version>
          <implementation-version>1.1.2</implementation-version>
     </library-ref>
</weblogic-web-app>
procesoIngreso is the name of war module of the j2ee app.
web.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<web-app 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>Workshop Application</display-name>
<description/>
<servlet>
<description/>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
<init-param>
<description/>
<param-name>config</param-name>
<param-value>/_pageflow/struts-config.xml</param-value>
</init-param>
<init-param>
<description/>
<param-name>config/-global</param-name>
<param-value>/_pageflow/struts-config--global.xml</param-value>
</init-param>
<init-param>
<description/>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<description/>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
<error-page>
<error-code>500</error-code>
<location>/error.jsp</location>
</error-page>
<jsp-config>
<taglib>
<taglib-uri>netui-tags-html.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>netui-tags-databinding.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>netui-tags-template.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
</taglib>
</jsp-config>
<filter>
<filter-name>PageFlowJspFilter</filter-name>
<filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
</filter>
<filter>
<filter-name>PageFlowForbiddenFilter</filter-name>
<filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
<init-param>
<param-name>response-code</param-name>
<param-value>404</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>PageFlowJspFilter</filter-name>
<url-pattern>*.jsp</url-pattern>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowJspFilter</filter-name>
<url-pattern>*.jspx</url-pattern>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.java</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.jsfb</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.jpfs</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>/_pageflow/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<listener>
<listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
</listener>
<listener>
<listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
</listener>
<servlet>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.jpf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<url-pattern>*.xhr</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<url-pattern>*.render</url-pattern>
</servlet-mapping>
<-- MENU CONFIGURATION -->
<context-param>
          <param-name>menuConfigLocation</param-name>
          <param-value>/WEB-INF/menu-config.xml</param-value>
     </context-param>
     <listener>
     <listener-class>net.sf.navigator.menu.MenuContextListener</listener-class>
     </listener>
<-- END MENU CONFIGURATION -->
<-- BIRT CONFIGURATION -->
<context-param>
          <param-name>BIRT_VIEWER_LOCALE</param-name>
          <param-value>en-US</param-value>
     </context-param>
     <context-param>
          <param-name>BIRT_VIEWER_REPORT_ROOT</param-name>
          <param-value></param-value>
     </context-param>
     
     <context-param>
          <param-name>BIRT_VIEWER_IMAGE_DIR</param-name>
          <param-value></param-value>
     </context-param>
     
     <context-param>
          <param-name>BIRT_VIEWER_LOG_DIR</param-name>
          <param-value></param-value>
     </context-param>
     <servlet>
          <servlet-name>ViewerServlet</servlet-name>
          <servlet-class>org.eclipse.birt.report.viewer.servlets.ViewerServlet</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>ViewerServlet</servlet-name>
          <url-pattern>/frameset</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewerServlet</servlet-name>
          <url-pattern>/run</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewerServlet</servlet-name>
          <url-pattern>/navigation</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewerServlet</servlet-name>
          <url-pattern>/toolbar</url-pattern>
     </servlet-mapping>
<-- END BIRT CONFIGURATION -->
</web-app>
that's all i think that i cant give you, i guess...
(all xml comments have not the "!" because in preview, those lines are not shown, for example <-- END BIRT CONFIGURATION -->)
can you help me please with this issue?
thank in advance.
best regards
julio

julio,
Hey I'm having the exact same problem when I add
<wls:container-descriptor>
<wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
</wls:container-descriptor>
to my weblogic.xml??? Did you ever get a resolution for this problem if so can you help me out.
Thanks,
Greg

An internal error occurred during: "Starting BEA WebLogic Server v8.1 at lo

Hi,
On "Start the server in debug mode"
file .log
eclipse.buildId=I20090611-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_AR
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.core.jobs 4 2 2009-08-05 12:29:57.060
!MESSAGE An internal error occurred during: "Starting BEA WebLogic Server v8.1 at localhost".
!STACK 0
java.lang.NullPointerException
     at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.findWorkshopJspDebuggerLaunchConfigurationDelegate(GenericWeblogicServerBehaviour.java:477)
     at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.setupLaunch(GenericWeblogicServerBehaviour.java:226)
     at org.eclipse.jst.server.generic.core.internal.ExternalLaunchConfigurationDelegate.launch(ExternalLaunchConfigurationDelegate.java:101)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
     at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3057)
     at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3007)
     at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:294)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
OS= Windows XP SP2
Eclipse Java Version= 1.6.0_13
Workspace Java Version= 1.4.2_08
BEA Weblogic= 8.1.6
Eclipse= 3.5.0
WTP= 3.1.0
Project Facets= Dynamic Web Module 2.3
Java= 1.4
Tanks and sorry my English.
Gustavo

I am also experiencing the same NullPointerException when launching Weblogic 8.1 in debug mode within Eclipse 3.5. Is there any anticipated fix for this issue, or a bugtraq record that we can follow to know when the issue is addressed? I do not expect JSP debugging to work (as it wasn't available with Weblogic 8.1 under Eclipse 3.4 either) - BUT right now I cannot debug ANY server-side code within Weblogic 8.1 in Eclipse 3.5 as the server cannot start in debug mode at all.
Many thanks.

Error:cannot access com.bea.p13n.exceptions.ApplicationException

hello,
I wrote an Input Processor class(named HelloIP.java) which extends InputProcessorSupport class. My class has process method which throws ProcessingException. When I tried to compile the class, I got error:connot access com.bea.p13n.exceptions.ApplicationException. My classpath includes pipeline.jar and webflow_servlet.jar. Are there any other packages that I need to include into my classpath?
Thanks a lot for your help.
Penny

Try adding p13n_system.jar. It contains the exception class you need and should
be in the portal/lib directory.
Penny <[email protected]> wrote:
hello,
I wrote an Input Processor class(named HelloIP.java) which extends InputProcessorSupport
class. My class has process method which throws ProcessingException.
When I tried to compile the class, I got error:connot access com.bea.p13n.exceptions.ApplicationException.
My classpath includes pipeline.jar and webflow_servlet.jar. Are there
any other packages that I need to include into my classpath?
Thanks a lot for your help.
Penny

Oracle ifs and BEA weblogic

Oracle ifs and BEA weblogic
We have one application server with weblogic and and ifs 1.0.9 , and one db server with Oracle 8.1.7.
with the following configuration:
Web server
appl server with weblogic 6.0 and ifs 1.1.9
Oracle 8i Enterprise with interMedia text
We need to use the iFS API call for our application.
As I know, weblogic 6.0 support JDK1.3 but ifs 1.1.9 supports up to JDK1.2.
Is this configuration possible?
Any conflict if two version JDK co-exist inside same machine?
Any suggestion?
If I separate the appl. server into two machines, that is,
one server installed with weblogic, the other one installed with ifs.
How could I make use the ifs API call from appl. server?
Is there any configuration guides for this setting?
Thanks a lot.
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Luis:
The iFS API is 100% pure Java. You can use it from any other Java application, be it JSP, EJB, or a standalone application.
So it really comes down to the CLASSPATH. The iFS API is split among a set of .jar files, and some of the configuration information is stored in .properties files that are outside of these .jar files. All of this stuff needs to be in the CLASSPATH of whatever JVM is calling the iFS API.
The iFS API uses the Oracle JDBC driver to communicate with the Oracle database. This is another requirement. You can't use another JDBC driver; you have to use ours.
So again, it's all about configuration.<HR></BLOCKQUOTE>
Would you mind to share more detail on configurating weblogic to integrate the iFS API?
null

Web Services and BEA

Web Services has all the makings of a home run. As a powerful integration
platfor, it moves the procedural-heavy complexities of builiding distributed
app into the realm of simple declarative transactions, while supporting
location transparency. It is a powerful technology that removes the barrier
erected by the discontinuity of geographic distance and cross-platform
technical mismatches that have until now constrained the plumbing between
heterogeneous networked applications.
Developers who feel lost in the labyrinth of hype can turn to a new site
site., Web Services FAQ http://www.webservicesfaq.com devoted to UDDI,
WSDL, SOAP, ebXML, Best Practices, Intergration issues and so on...
Here they'll learn how, while Web Services complements J2EE and compliant
servers superbly, it is also an excellent integration platform for BEA
technologies, and in fact for the transparent interoperability between the
two, and between any other architectures that support the new Web Services
standards.
Best Regards
Ramene Anthony

You should be able to get the username from the context?
private SessionContext sessionCtx = null;
public void setSessionContext(SessionContext sctx) {
this.sessionCtx = sctx;
public void someMethod() {
String username = sessionCtx.getCallerPrincipal().getName();
-Jesus

Recurring errors BEA-101083 and BEA-000403

Similar Messages

Maybe you are looking for