Weblogic 6.1 and Resin Problems

I am having trouble with Weblogic 6.1 and Resin. I have a simple .jsp
          page that calls an entity bean I have created and deployed with
          Weblogic.
          The key aspects of the JSP are as follows:
                    Context jndiContext = new InitialContext();
                    Object ref = ic.lookup("java:comp/env/CustomerHomeRemote");
                    CustomerHomeRemote home = (CustomerHomeRemote)
                         PortableRemoteObject.narrow(ref,CustomerHomeRemote.class);
                    Integer pk = new Integer(1002);
                    CustomerRemote customer = home.findByPrimaryKey(pk);
                    out.print(customer.getFirstname() +"<br>");
                    out.print(customer.getLastname() +"<br>");
          My resin.conf is the same as the default with the following added:
          <classpath id='c:\Smartix-Apps\lib\smartixejb.jar' />
          <classpath id='c:\Smartix-Apps\classes' />
          <classpath id='c:\temp\caucho' />
          <classpath id='c:\Smartix-Apps\lib\resin.jar' />
          <classpath id='C:\Programs\bea\wlserver6.1\lib\weblogic.jar' />
          <jndi-link>
          <jndi-name>java:comp/env/CustomerHomeRemote</jndi-name>
          <jndi-factory>weblogic.jndi.WLInitialContextFactory</jndi-factory>
          <init-param java.naming.provider.url="t3://localhost:7001"/>
          <jndi-lookup>CustomerHomeRemote</jndi-lookup>
          </jndi-link>
          smartixejb.jar contains the CustomerEJB and \classes has all the class
          files.
          The error I am getting is:
          500 Servlet Exception
          java.lang.ClassCastException:
          com.caucho.server.http.ApplicationAdapter
               at com.caucho.jsp.PageManager.<init>(PageManager.java:83)
               at com.caucho.jsp.JspManager.<init>(JspManager.java:75)
               at com.caucho.jsp.JspServlet.init(JspServlet.java:74)
               at com.caucho.server.http.Application.createServlet(Application.java:2755)
               at com.caucho.server.http.Application.loadServlet(Application.java:2711)
               at com.caucho.server.http.Application.getFilterChainServlet(Application.java:2478)
               at com.caucho.server.http.Application.buildFilterChain(Application.java:2445)
               at com.caucho.server.http.Invocation.service(Invocation.java:276)
               at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:129)
               at com.caucho.server.http.RunnerRequest.handleRequest(RunnerRequest.java:338)
               at com.caucho.server.http.RunnerRequest.handleConnection(RunnerRequest.java:270)
               at com.caucho.server.TcpConnection.run(TcpConnection.java:140)
               at java.lang.Thread.run(Thread.java:484)
          Can anyone help me???
          Thanks in advance!
          

Remove <classpath id='c:\Smartix-Apps\lib\resin.jar' /> from
          your resin.conf.
          Matt Koidin <[email protected]> wrote:
          > I am having trouble with Weblogic 6.1 and Resin. I have a simple .jsp
          > page that calls an entity bean I have created and deployed with
          > Weblogic.
          > The key aspects of the JSP are as follows:
          >           Context jndiContext = new InitialContext();
          >           Object ref = ic.lookup("java:comp/env/CustomerHomeRemote");
          >           CustomerHomeRemote home = (CustomerHomeRemote)
          >                PortableRemoteObject.narrow(ref,CustomerHomeRemote.class);
          >           Integer pk = new Integer(1002);
          >           CustomerRemote customer = home.findByPrimaryKey(pk);
          >           out.print(customer.getFirstname() +"<br>");
          >           out.print(customer.getLastname() +"<br>");
          > My resin.conf is the same as the default with the following added:
          > <classpath id='c:\Smartix-Apps\lib\smartixejb.jar' />
          > <classpath id='c:\Smartix-Apps\classes' />
          > <classpath id='c:\temp\caucho' />
          > <classpath id='c:\Smartix-Apps\lib\resin.jar' />
          > <classpath id='C:\Programs\bea\wlserver6.1\lib\weblogic.jar' />
          >
          > <jndi-link>
          > <jndi-name>java:comp/env/CustomerHomeRemote</jndi-name>
          > <jndi-factory>weblogic.jndi.WLInitialContextFactory</jndi-factory>
          > <init-param java.naming.provider.url="t3://localhost:7001"/>
          > <jndi-lookup>CustomerHomeRemote</jndi-lookup>
          > </jndi-link>
          > smartixejb.jar contains the CustomerEJB and \classes has all the class
          > files.
          > The error I am getting is:
          > 500 Servlet Exception
          > java.lang.ClassCastException:
          > com.caucho.server.http.ApplicationAdapter
          >      at com.caucho.jsp.PageManager.<init>(PageManager.java:83)
          >      at com.caucho.jsp.JspManager.<init>(JspManager.java:75)
          >      at com.caucho.jsp.JspServlet.init(JspServlet.java:74)
          >      at com.caucho.server.http.Application.createServlet(Application.java:2755)
          >      at com.caucho.server.http.Application.loadServlet(Application.java:2711)
          >      at com.caucho.server.http.Application.getFilterChainServlet(Application.java:2478)
          >      at com.caucho.server.http.Application.buildFilterChain(Application.java:2445)
          >      at com.caucho.server.http.Invocation.service(Invocation.java:276)
          >      at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:129)
          >      at com.caucho.server.http.RunnerRequest.handleRequest(RunnerRequest.java:338)
          >      at com.caucho.server.http.RunnerRequest.handleConnection(RunnerRequest.java:270)
          >      at com.caucho.server.TcpConnection.run(TcpConnection.java:140)
          >      at java.lang.Thread.run(Thread.java:484)
          > Can anyone help me???
          > Thanks in advance!
          Dimitri
          

Similar Messages

  • Weblogic SAAJ implementation and version problem

    I have a problem with Weblogic 9.0 using its own implementation over the one i provide.
              I have tried putting the saaj-api.jar and saaj-impl.jar in my domains lib/ catalog as well as the domains config/lib/ catalog.
              I also tried PRE_CLASSPATH in setDomainEnv.cmd but it seems the weblogic implementation is being used anyway!
              Any ideas how to solve this?
              Here are a couple of exceptions i get after a context lookup and getConnection of the resource adapter:
              Caused by: javax.xml.soap.SOAPException: Unable to create SOAP connection factory: com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory
                   at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
                                  I also tried adding a property value:
                        System.setProperty("javax.xml.soap.SOAPConnectionFactory", "com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory");
                        in the web app before doing the context lookup, and then i get this exception:
                        java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
              at weblogic.webservice.core.soap.SOAPElementImpl.getElementsByTagNameNS(SOAPElementImpl.java:527)
              

    Was this problem solved in the latest version of Bea Weblogic 9.2?
              I have an issue on soap 1.2 support activation (through Binding.Type.SOAP12):
              java.lang.RuntimeException: weblogic.testclient.WsdlParseFailedException: SOAP 1.2 is not supported by the Test Client
              at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:63)
              at Controller.refreshWsdl(Controller.java:437)
              at Controller.begin(Controller.java:285)
              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:585)
              at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:878)
              at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
              at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
              at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
              at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
              at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
              at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
              at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
              at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
              at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
              at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
              at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
              at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
              at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
              at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
              at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3241)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
              at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
              at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
              at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              Caused by: weblogic.testclient.WsdlParseFailedException: SOAP 1.2 is not supported by the Test Client
              at weblogic.testclient.WsdlOperationParser.createOperation(WsdlOperationParser.java:38)
              at weblogic.testclient.WebService.createOperation(WebService.java:251)
              at weblogic.testclient.WebService.<init>(WebService.java:88)
              at weblogic.testclient.Wsdl.parseWsdl(Wsdl.java:135)
              at weblogic.testclient.Wsdl.<init>(Wsdl.java:60)
              at weblogic.testclient.ConnectionState.createWsdlFromHttpUrl(ConnectionState.java:120)
              at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:54)
              ... 37 more

  • WebLogic 8.1 and Tomcat connection problem

    I am using Tomcat 4.0.6 for my JSPs and WebLogic for my EJBs.
    Everything worked fine under WebLogic 6.1 but I am trying
    to upgrade to WebLogic 8.1 and it is not working.
    I can also connect to WebLogic 8.1 from a standalone class
    but not using Tomcat. What is wrong?
    This is the basic code I am using to connect:
    Hashtable ht = new Hashtable(4);
    ht.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL,"t3://localhost:7009");
    InitialContext ic = new InitialContext(ht);
    Object obj = ic.lookup("NsbInfoHome");
    NsbInfoHome home = ( NsbInfoHome) PortableRemoteObject.
    narrow(obj, NsbInfoHome.class);
    NsbInfo nsbInfo = home.create();
    NsbMemberPrimaryInfo info = nsbInfo.getMemberPrimaryInfo(1);
    And this is the error
    java.lang.NullPointerException
    at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGenerator.java:694)
    at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:666)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:712)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:699)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:76)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:486)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:449)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:345)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:672)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250)
    at javax.naming.InitialContext.init(InitialContext.java:226)
    at javax.naming.InitialContext.<init>(InitialContext.java:202)
    at org.apache.jsp.testWL2$jsp._jspService(testWL2$jsp.java:81)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
    at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
    at java.lang.Thread.run(Thread.java:536)
    --------------- nested within: ------------------
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to
    generate class for weblogic.jndi.internal.ServerNamingNode_WLStub ] -
    with nested exception:
    [java.lang.NullPointerException]
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:716)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:699)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:76)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:486)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:449)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:345)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:672)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250)
    at javax.naming.InitialContext.init(InitialContext.java:226)
    at javax.naming.InitialContext.<init>(InitialContext.java:202)
    at org.apache.jsp.testWL2$jsp._jspService(testWL2$jsp.java:81)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
    at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
    at java.lang.Thread.run(Thread.java:536)
    Any ideas how to fix this?
    Thanks,
    Dan

    Hi,
    I work under a sligthly different seeting like Dan used (Java Client instead of JSPs, but same context properties), but the problem is exactly the same: weblogic.rmi.internal.StubGenerator.getStubOnClient() results in a NullPointerException.
    What does this method actually do? I provided the weblogic.jar in the client's runtime environment; is it possible that the method asks for something else on the client side that I have to provide (only guessing...)
    PS: I found the error myself. Its the Eclipse 3.0 IDE that won't work together with the factory class of BEA for some obscure reason. Switching to another IDE solved the problem...
    Message was edited by c_web at Dec 1, 2004 6:03 AM

  • WebLogic 9 and Antlr problem with JMS Messages

    Hi all,
    I'm facing a problem and your help would be very appreciated.
    We've got an EAR application deployed on a WebLogic 9.x. As we use Hibernate3, when we put it into WebLogic 10, we needed to add "antlr" library to our "weblogic-application.xml" as "prefer-application-packages" (This is because of the well-known error of ClassNotFoundException of the HqlToken class).
    The version of Antlr we have is 2.7.7, and works perfectly in WebLogic 10.
    Now, we want to have an EAR that can be installed in both WebLogic 9.x and 10. But we're getting a fatal exception when we want to create a JMS consumer with a JMS selector in WebLogic 9.x(this is for listening only for the message we need in the queue).
    So, in WebLogic 10 it works with "antlr" in the prefer-application-packages, but in WebLogic 9.x doesn't. And if we don't put it there, it works in WL 9 but not in WL 10.
    The best would be to have the library in the weblogic-application.xml so WebLogic put our library first in the classpath. But in WL 9 we've got this exception:
    javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:2659)
         at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2432)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2379)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2359)
         at weblogic.jms.client.WLSessionImpl.createConsumer(WLSessionImpl.java:800)
         at crm.appl.cat.CatUtil.enviarMensajeSync(CatUtil.java:244)
         at crm.appl.cat.mar.CatMessageReceiver.receive(CatMessageReceiver.java:571)
         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
         at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at crm.appl.cat.mar.CatServlet.service(CatServlet.java:108)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at crm.appl.cat.mar.CatFilter.doFilter(CatFilter.java:33)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 35 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:255)
         at weblogic.jms.frontend.FESession$2.run(FESession.java:966)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:962)
         at weblogic.jms.frontend.FESession.invoke(FESession.java:2824)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 37 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 44 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.backend.BEQueueImpl.createFilterExpression(BEQueueImpl.java:155)
         at weblogic.jms.backend.BEQueueImpl.createConsumer(BEQueueImpl.java:182)
         at weblogic.jms.backend.BESessionImpl.createBEConsumer(BESessionImpl.java:368)
         at weblogic.jms.backend.BESessionImpl.createConsumer(BESessionImpl.java:378)
         at weblogic.jms.backend.BESessionImpl.invoke(BESessionImpl.java:289)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 46 more
    Check that "invocationId" is a JMS String Property that we're adding in the messages. Our same source code works perfect in WL 9 without "antlr" as an prefered application package. You know that in WL 9, the antlr library was bundled into the weblogic.jar, so WL has it in his System classpath.
    Someone has an idea how we can solve this? The final solution may be having 2 EARs (one for WL 9 and one for WL 10, with the only change of the weblogic-application.xml), but it's not a nice solution.
    Thank you a lot in advance.
    Ariel Cassan
    Argentina

    Hi all,
    I'm facing a problem and your help would be very appreciated.
    We've got an EAR application deployed on a WebLogic 9.x. As we use Hibernate3, when we put it into WebLogic 10, we needed to add "antlr" library to our "weblogic-application.xml" as "prefer-application-packages" (This is because of the well-known error of ClassNotFoundException of the HqlToken class).
    The version of Antlr we have is 2.7.7, and works perfectly in WebLogic 10.
    Now, we want to have an EAR that can be installed in both WebLogic 9.x and 10. But we're getting a fatal exception when we want to create a JMS consumer with a JMS selector in WebLogic 9.x(this is for listening only for the message we need in the queue).
    So, in WebLogic 10 it works with "antlr" in the prefer-application-packages, but in WebLogic 9.x doesn't. And if we don't put it there, it works in WL 9 but not in WL 10.
    The best would be to have the library in the weblogic-application.xml so WebLogic put our library first in the classpath. But in WL 9 we've got this exception:
    javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:2659)
         at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2432)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2379)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2359)
         at weblogic.jms.client.WLSessionImpl.createConsumer(WLSessionImpl.java:800)
         at crm.appl.cat.CatUtil.enviarMensajeSync(CatUtil.java:244)
         at crm.appl.cat.mar.CatMessageReceiver.receive(CatMessageReceiver.java:571)
         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
         at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at crm.appl.cat.mar.CatServlet.service(CatServlet.java:108)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at crm.appl.cat.mar.CatFilter.doFilter(CatFilter.java:33)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 35 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:255)
         at weblogic.jms.frontend.FESession$2.run(FESession.java:966)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:962)
         at weblogic.jms.frontend.FESession.invoke(FESession.java:2824)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 37 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 44 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.backend.BEQueueImpl.createFilterExpression(BEQueueImpl.java:155)
         at weblogic.jms.backend.BEQueueImpl.createConsumer(BEQueueImpl.java:182)
         at weblogic.jms.backend.BESessionImpl.createBEConsumer(BESessionImpl.java:368)
         at weblogic.jms.backend.BESessionImpl.createConsumer(BESessionImpl.java:378)
         at weblogic.jms.backend.BESessionImpl.invoke(BESessionImpl.java:289)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 46 more
    Check that "invocationId" is a JMS String Property that we're adding in the messages. Our same source code works perfect in WL 9 without "antlr" as an prefered application package. You know that in WL 9, the antlr library was bundled into the weblogic.jar, so WL has it in his System classpath.
    Someone has an idea how we can solve this? The final solution may be having 2 EARs (one for WL 9 and one for WL 10, with the only change of the weblogic-application.xml), but it's not a nice solution.
    Thank you a lot in advance.
    Ariel Cassan
    Argentina

  • Weblogic Bridge "failed and will reconnect later"

    The enterprise architecture is as follows:
    1 Physical machine where I have 2 VMs on this machine, and each VM I have 1 domain, 1 Cluster and 1 managed server, and the second VM I have the replicated what I have in first VM.
    In first domain I have the OSB, in the second domain I have SOA.
    What I need ? Send information of queues (topics) of First Domain (OSB) to second domain(SOA).
    At first the only thing I did was:
    In the first domain I created OSB JMS Server, JMS Module, Connection Factory and Queue Topic.
    In the second domain SOA I replied the same thing but with different names.
    Then I created the bridge with configuration default between the first domain and the second domain, the bridge and when active it generates me a message Weblogic Bridge "failed and will reconnect later"
    I did a test on my local machine windows where I created two domains, and the same procedures you did above, but the point was funcinou been activated now for the enterprise environment I'm not managing to make it work, you could tell me what is wrong . in both cases restarted the weblogic server as the machine itself the question that ran on my machine and machine company no.
    If you can give me a light thank.

    This is a bug (6973877, derby only) which has been fixed in 4.5 build14 and 4.4u2p1. Thanks for reporting. The problem is the missing "FOR BIT DATA" in LOG_RECORD column in derby table definition MQTMLRJMSBG41 in broker default.properties file
    - LOG_RECORD VARCHAR(2048) NOT NULL,\
    + LOG_RECORD VARCHAR(2048) FOR BIT DATA NOT NULL,\

  • Weblogic 8.1 and Novell LDAP SSL

    Hi Everyone !
    I'm having problems enabling SSL between Weblogic 8.1 and Novell LDAP. I have
    the non-SSL working. All the BEA documentation I've found indicates that the SSL
    Enabled checkbox needs to be checked and that's all. This can't be all because
    I get the following errors.
    Does anyone know how to solve this ?
    Thanks,
    Eddie
    ####<Oct 1, 2003 12:06:42 PM EDT> <Notice> <Security> <6X19DYSZH1ZV> <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-090169>
    <Loading trusted certificates from the jks keystore file C:\bea8.1\WEBLOG~1\server\lib\DemoTrust.jks.>
    ####<Oct 1, 2003 12:06:42 PM EDT> <Notice> <Security> <6X19DYSZH1ZV> <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-090169>
    <Loading trusted certificates from the jks keystore file C:\bea8.1\JDK141~1\jre\lib\security\cacerts.>
    ####<Oct 1, 2003 12:06:42 PM EDT> <Warning> <Security> <6X19DYSZH1ZV> <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-090476>
    <Invalid/unknown SSL header was received from peer NASTEA02 - 10.4.5.104 during
    SSL handshake.>

    You need to configure the server SSL to trust the identity certificate it receives
    from nastea02.bankofny.com If you want to use the default configuration you could
    simply import the CA certificate that issued that identity certificate to the
    DemoTrust.jks keystore.
    Also, look at Using Host Name Verification here: http://edocs.bea.com/wls/docs81/secmanage/ssl.html#1187786
    because this might be another reason why the certificate is rejected.
    Pavel.
    "Eddie Baue" <[email protected]> wrote:
    >
    Hi Everyone !
    Please ignore the exceptions from my previous posting. I'm getting
    a new exception,
    which I've list below.
    Thanks,
    Eddie
    ####<Oct 1, 2003 2:47:20 PM EDT> <Warning> <Security> <6X19DYSZH1ZV>
    <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>>
    <> <BEA-090477>
    <Certificate chain received from nastea02.bankofny.com - 10.4.5.104 was
    not trusted
    causing SSL handshake failure.>
    "Eddie Baue" <[email protected]> wrote:
    Hi Everyone !
    I'm having problems enabling SSL between Weblogic 8.1 and NovellLDAP.
    I have
    the non-SSL working. All the BEA documentation I've found indicatesthat
    the SSL
    Enabled checkbox needs to be checked and that's all. This can't beall
    because
    I get the following errors.
    Does anyone know how to solve this ?
    Thanks,
    Eddie
    ####<Oct 1, 2003 12:06:42 PM EDT> <Notice> <Security> <6X19DYSZH1ZV>
    <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>>
    <> <BEA-090169>
    <Loading trusted certificates from the jks keystore file C:\bea8.1\WEBLOG~1\server\lib\DemoTrust.jks.>
    ####<Oct 1, 2003 12:06:42 PM EDT> <Notice> <Security> <6X19DYSZH1ZV>
    <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>>
    <> <BEA-090169>
    <Loading trusted certificates from the jks keystore file C:\bea8.1\JDK141~1\jre\lib\security\cacerts.>
    ####<Oct 1, 2003 12:06:42 PM EDT> <Warning> <Security> <6X19DYSZH1ZV>
    <mytest>
    <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>>
    <> <BEA-090476>
    <Invalid/unknown SSL header was received from peer NASTEA02 - 10.4.5.104
    during
    SSL handshake.>

  • Performance of Weblogic 4.03 and Visual Age 2.0

    Hello,
    I am experiencing severe performance problems when running Weblogic 4.03 and
    Visual Age 2.0. The server runs extremely slowly in this environment,
    however, the 3.13 version did not suffer from this. Has anyone else noticed
    this? Is there anything I can do about it?
    -Andrew

    Andrew Sammons wrote:
    I am experiencing severe performance problems when running Weblogic
    4.03 and Visual Age 2.0. The server runs extremely slowly in this
    environment, however, the 3.13 version did not suffer from this.
    Has anyone else noticed this? Is there anything I can do about it?You can set the following undocumented property in weblogic.properties:
    weblogic.system.gc.intervalSecs=5
    There's some kind of bad interaction between Visual Age and WebLogic's
    garbage collection control. Basically, there's a garbage collection
    task that by default runs once a second, and in the Visual Age VM,
    something it's doing takes more than a second.
    The problem only seems to exist in WebLogic 4.0.3. It doesn't happen in
    4.5.x. Also, according to one report I've had, you may need to set the
    property value to more than 5 on slower machines.
    Note that this property is unsupported, and is not guaranteed to even
    exist in any other version of WebLogic.
         -- Jim
    Jim Edwards-Hewitt http://weblogic.beasys.com [email protected]

  • Weblogic 4.5 and Visual Cafe 3.1

    Hi,
    I am having a problem integrating Visual Cafe with Weblogic.
    Specifically, it involves getting the Weblogic classpath modified to support
    setting up a connection pool to an Informix database. If I start the
    Weblogic server manually, I can set the server classpath appropriately to
    find the Informix JDBC driver and my pool is setup properly.
    However with VC, it starts the Weblogic server from the IDE and I have
    not been able to get the addition classpath entries to find the Informix
    driver. Is there a way to add additional classpath entries so that when VC
    starts Weblogic it will find my JDBC driver? Or do I have to start the
    Weblogic server seperately and setup remote debugging manually?
    Thanks
    Carl

    Yes, I am using the symantec debug VM. This is the batch file I use to start WL.
    echo %CLASSPATH%
    set
    CLASSPATH=.;c:\VisualCafe\JAVA\LIB;c:\VisualCafe\JAVA\LIB\SYMCLASS.ZIP;c:\VisualCafe\JAVA\LIB\CLASSES.ZIP;c:\VisualCafe\bin\components\sfc.jar;c:\weblogic\license;%CLASSPATH%
    set PATH=c:\winnt\system32;c:\winnt;c:\VisualCafe\Java\bin;c:\weblogic\bin
    set
    JAVACLASSPATH=%CLASSPATH%;.\classes\boot;.\eval\cloudscape\lib\cloudscape.jar
    set
    WEBLOGICCLASSPATH=.\classes;.\license;.\lib\weblogicaux.jar;c:\code\VisualCafe\Version1
    rem java -ms32m -mx32m -classpath %JAVACLASSPATH%
    -Dweblogic.class.path=%WEBLOGICCLASSPATH% -Djava.security.manager
    -Djava.security.policy==weblogic.policy weblogic.Server
    c:\VisualCafe\java\bin\debugvm -ms32m -mx32m -classpath %JAVACLASSPATH%
    -Dweblogic.class.path=%WEBLOGICCLASSPATH% -Djava.security.manager
    -Djava.security.policy==weblogic.policy weblogic.Server
    If you don'y use the symantec debug VM, it stands to reason that the debug
    environment will not see your process in the VM. I can't help you with why your
    WL crashes when you connect using the debug VM. Perhaps you could post some more
    information?
    -- Jay
    Tamilselvan Ramasamy wrote:
    Hey,
    help please
    You said that you can attach from VC 3.1 to weblogic server 4.5.1 right. How
    did you start the server ? Is it using the symantic debugvm.exe and symantic
    settings? If I start the server with javasoft java.exe then VC is not seeing
    the vm at all. And I tried starting weblogic server using symantic
    debugvm.exe, as soon as a client trying to connect then the server crashes.
    Please post the some instruction how did you do that?
    Thanks
    /selvan
    Jay Baker <[email protected]> wrote in message
    news:[email protected]...
    The latter has been successful with me. I start the WL server manually viaa
    command prompt and then 'attach to process'.
    -- Jay
    Carl Phillips wrote:
    Hi,
    I am having a problem integrating Visual Cafe with Weblogic.
    Specifically, it involves getting the Weblogic classpath modified to
    support
    setting up a connection pool to an Informix database. If I start the
    Weblogic server manually, I can set the server classpath appropriatelyto
    find the Informix JDBC driver and my pool is setup properly.
    However with VC, it starts the Weblogic server from the IDE and Ihave
    not been able to get the addition classpath entries to find the Informix
    driver. Is there a way to add additional classpath entries so that whenVC
    starts Weblogic it will find my JDBC driver? Or do I have to start the
    Weblogic server seperately and setup remote debugging manually?
    Thanks
    Carl

  • Weblogs using IP and not domain

    We figured out how to set up weblog user names and we got a domain set up for the server, but when one of the users puts a category in, it defaults to the internal address. Is there anyway to fix this?

    I am using Xserve. I checked with someone else and they thing it is a domain problem. Here is an example page for you. If you click on a category, you will see it trys to go to an internal address. All of the IPs have domains linked to them, internal and external.
    http://tigers.bcacs.org/weblog/cadams/
    I will look around in the other forum. Don't go by what the thing says for my OS, it doesn't have Xserve on it.

  • Weblogic 5.1 and iPlanet as proxy server

    Hello!
    We are using Weblogic 5.1 and Netscape's iPlanet as a proxy server. Both
    the machines are running of seperate NT boxes with static IP addresses.
    All the changes which need to made on iPlanet side (i.e. copying
    proxy36.dll, modificatiopn of mime types file, changes to the obj.conf
    file etc.) have been made. Howver I am still not able to get the JSP
    forwarded to Weblogic to get them serviced.
    I had this evironment set up pretty quickly when using Weblogic 4.5.1.
    Any ideas? Anything I might have overlooked. I have pretty much follwed
    all the instructions specified by Weblogic to set up Netscape as a proxy
    server.
    ANy help in resolving this problem would be greatly appreciated.
    Thanks.
    Vijay R

    I have the same setup but it's on one NT box and works OK. Make sure you have the proxy36.dll from Weblogic 5.1 Service Pack 6. Release notes say you MUST have SP6 proxy file to work with iPlanet 4.1
    Sam Fowler
    Vijay Raghavacharian <[email protected]> wrote:
    Hello!
    We are using Weblogic 5.1 and Netscape's iPlanet as a proxy server. Both
    the machines are running of seperate NT boxes with static IP addresses.
    All the changes which need to made on iPlanet side (i.e. copying
    proxy36.dll, modificatiopn of mime types file, changes to the obj.conf
    file etc.) have been made. Howver I am still not able to get the JSP
    forwarded to Weblogic to get them serviced.
    When I try to execute a JSP, I get the "Internal Server Error". On
    analyzing the
    error message sin the log files for iPlanet it reports that it is not
    able to connect to
    Weblogic.
    In order to fix this porblem I just copies the proxy36.dll for Weblogic
    version
    4.5.1 and copied it in the required iPlanet directory. This seems to
    have fixed
    the problem of getting the JSP serviced by Weblogic, but I am wary about
    the solution.
    Am I doing something wrong or is there a new files availabel for
    download. I checked
    the website for BEA and did not find any answers.
    I had this evironment set up pretty quickly when using Weblogic 4.5.1.
    Any ideas? Anything I might have overlooked. I have pretty much follwed
    all the instructions specified by Weblogic to set up Netscape as a proxy
    server.
    Any help in resolving this problem would be greatly appreciated.
    Thanks.
    Vijay R

  • Weblogic 8.1SP6 NodeManager Services Problem

    After upgrading to Weblogic 8.1 SP6 from SP3 we had problems starting the Node Manager process as windows, we were able to successfully install it as windows service but when starting Node Manager process it was crashing with below exception in Event Generator log.
    occurred on 05/11/2009 @ 15:00:18.870 The exception generated was 80000007 at address 00000000
    (ntdll!KiFastSystemCallRet)
    The problem is caused because of version of beasvc.exe which is shipped with Weblogic 8.1 SP6. As a work around for this problem we have to make sure that system PATH does not have any spaces in it, which may cause this issue. Clean up the system PATH environment variable so that no spaces exist, and try starting the service. There is patch available on this for weblogic 8.1 SP6.
    - - Tarun
    Edited by: Tarun Boyella on May 13, 2009 11:02 AM

    I did a reinstallation and the problem didnt re-occur. So one neednt work on this problem.
    Priya

  • BPM for WebLogic 10.3 JMS listener problem: SecurityException

    Hi!
    I have a BPM 10.3 engine running on WebLogic 10.3 and a BPM process that uses JMS listener global automatic activity. The JMS queue is located in a WebLogic 8.1 server.
    The global activity receives a message and tries to create a new process instance. At runtime a strange error occurs (see below). If I just log the message and comment the process creation out, the message is successfully consumed, but with the creation part it is not. The process creation itself is not the problem because other message listeners that call other process activities fail with similar errors.
    Btw, it's working in Studio, but not in WL10.
    Could someone explain me what happens and how to fix it?
    Have I misconfigured something?
    Thanks in advance,
    Jaanus
    The BPM engine log:
    The task could not be successfully executed.
    Reason: 'fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
    Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
    Caused by: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
    Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
    Caused by: Process execution engine execution error.
    Caused by: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
    Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
    Caused by: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
    fuego.lang.ComponentExecutionException: The task could not be successfully executed.
    Reason: 'fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
    Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
         at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1094)
         at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
         at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
         at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
         at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:3023)
         at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)
         at fuego.ejbengine.EJBProcessBean.executeTask(EJBProcessBean.java:147)
         at fuego.server.execution.GlobalJMSExecutor.execute(GlobalJMSExecutor.java:105)
         at fuego.ejbengine.EJBGlobalJMSExecutor.access$400(EJBGlobalJMSExecutor.java:43)
         at fuego.ejbengine.EJBGlobalJMSExecutor$JMSExecutorWorker.run(EJBGlobalJMSExecutor.java:213)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
    Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
         at fuego.papi.exception.ActivityFailedException.create(ActivityFailedException.java:66)
         at fuego.server.AbstractProcessBean.createActivityFailedException(AbstractProcessBean.java:3690)
         at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4326)
         at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
         at fuego.components.Process.createInstance(Process.java:106)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
         at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
         at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
         ... 16 more
    Caused by: fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
         at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
         at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
         ... 27 more
    Caused by: class fuego.lang.RuntimeExceptionShell ->> fuego.connector.ConnectorException: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
    Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
         at fuego.server.service.EngineConnectorService.getConnection(EngineConnectorService.java:581)
         at fuego.server.service.EngineConnectorService.getEngineConnection(EngineConnectorService.java:300)
         at fuego.transaction.TransactionAction.getEngineHandle(TransactionAction.java:179)
         at fuego.server.execution.EngineExecutionContext.getEngineHandle(EngineExecutionContext.java:443)
         at fuego.server.AbstractInstanceService.create(AbstractInstanceService.java:302)
         at fuego.server.execution.microactivity.BeginMicroActivity.createInstance(BeginMicroActivity.java:95)
         at fuego.server.AbstractProcessBean$53.execute(AbstractProcessBean.java:3642)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:125)
         at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
         at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
         at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
         at fuego.components.Process.createInstance(Process.java:106)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
         at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
         at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
         at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
         at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
         at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:472)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:125)
         ... 8 more
    Caused by: fuego.connector.ConnectorException: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
    Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
         at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:95)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:324)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:298)
         at fuego.connector.JDBCHelper.getConnection(JDBCHelper.java:41)
         at fuego.server.service.EngineConnectorService.getConnection(EngineConnectorService.java:578)
         at fuego.server.service.EngineConnectorService.getEngineConnection(EngineConnectorService.java:300)
         at fuego.transaction.TransactionAction.getEngineHandle(TransactionAction.java:179)
         at fuego.server.execution.EngineExecutionContext.getEngineHandle(EngineExecutionContext.java:443)
         at fuego.server.AbstractInstanceService.create(AbstractInstanceService.java:302)
         at fuego.server.execution.microactivity.BeginMicroActivity.createInstance(BeginMicroActivity.java:91)
         at fuego.server.AbstractProcessBean$53.execute(AbstractProcessBean.java:3642)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
         at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
         at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
         at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
         at fuego.components.Process.createInstance(Process.java:106)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
         at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
         at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
         at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
         at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
         at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
         at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         ... 8 more
    Caused by: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
         at weblogic.security.service.SecurityServiceManager.seal(Unknown Source)
         at weblogic.security.service.IdentityUtility.authenticatedSubjectToIdentity(Unknown Source)
         at weblogic.security.service.RoleManager.getRoles(Unknown Source)
         at weblogic.security.service.AuthorizationManager.isAccessAllowed(Unknown Source)
         at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:442)
         at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:423)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:180)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at fuego.connector.impl.BaseRemoteConnector.getReferencedObject(BaseRemoteConnector.java:116)
         at fuego.connector.impl.BaseRemoteConnector.getReferencedObject(BaseRemoteConnector.java:107)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:75)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:64)
         at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:147)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:319)
         ... 43 more

    I managed to solve the problem by configuring the domain's security settings on both WebLogic servers as follows:
    *) checked "Anonymous Admin Lookup Enabled",
    *) entered the same value to Advanced->Credential on both WLs.

  • Weblogic 7.0 and Sun's sdk 1.4.1_01

    I'm involved in a project which is composed of Weblogic application server
    and later a rich Java client (Swing).
    I dislike having a lot of Java sdk(s) on multiple places in my computer and
    I wish to use the Java most recent version.
    My questions are:
    - Is Java sdk 1.4 supported on Weblogic 7?
    - If not, do you have any experience/problems with it?
    - In the worst case, I won't upgrade to the most recent Java version on the
    server side.
    What implications, if any, does this have on the rich client?
    Should I use for client side development the same Java version as Weblogic
    does or can I get by with 1.4?

    Why do you recommend 1.3.1_06, not 1.3.1_07? I just tried _07 (on WinXP) and I'm
    not sure but I think the error I'm getting now about "libmuxer not found" didn't
    happen with _06. Is that a known problem?
    -greg.
    "Wayne W. Scott" <[email protected]> wrote:
    Oh Gawd, here we go again. Please don't yell at me like so many others
    have done when
    they get answers that they did not want to hear.
    Java SDK 1.4 has NOT been certified with any BEA product yet. The plans
    are for the
    first one to be the Olympic release, probably to be called WLS 8.1, due
    this Summer.
    AFAIK, the biggest problems have been in the integration of Security
    products with 1.4.
    I do not know all the nitty-gritty details. The latest JDK I would
    use is 1.3.1_06.
    I have no further guidance on other related topics.
    Best Wishes,
    Wayne Scott
    Yonatan Taub wrote:
    I'm involved in a project which is composed of Weblogic applicationserver
    and later a rich Java client (Swing).
    I dislike having a lot of Java sdk(s) on multiple places in my computerand
    I wish to use the Java most recent version.
    My questions are:
    - Is Java sdk 1.4 supported on Weblogic 7?
    - If not, do you have any experience/problems with it?
    - In the worst case, I won't upgrade to the most recent Java versionon the
    server side.
    What implications, if any, does this have on the rich client?
    Should I use for client side development the same Java version asWeblogic
    does or can I get by with 1.4?

  • Help Migrating Java app to Weblogic 9.2 and Workshop -- startup errors

    I need a little help getting my application up and running in Workshop. I recently migrated to Weblogic 9.2. Before I downloaded Workshop, I installed Weblogic 9.3 and have successfully setup and deployed the app on my PC outside of Workshop. The application is packaged as an EAR – I have extracted the war file and other contents from the ear onto my PC in order to do the deployment.
    In Workshop, I have setup the application as a Java project, have pointed to the source code and required libraries, and have been able to successfully compile the application. I have setup a ‘run dialog’ with similar parameters as in the config.xml and other configuration files.
    The problem I am currently having is when I start the application in Workshop, it is asking for a username. I have tried to enter the username that I setup with the original deployment (before I installed Workshop) and it does not accept it – it always shuts down.
    How can I either make it not require a username, or else use (point to) the same startup configuration as my original deployment, from before installing Workshop?

    On Tue, 5 Jun 2007 05:30:09 -0700, Paul Harvey <> wrote:
    I've been unable to find clear, authoritative information on this...
    I have an app which requires Java 1.4.x. Should I be able to deploy
    it on WL 9.2, or does 9.2 only support apps written in 1.5?WL9.2 has a Java 1.5 JVM. That should run Java 1.4 programs just fine.
    Tim Slattery
    MS MVP(DTS)
    [email protected]
    http://members.cox.net/slatteryt

  • How to deploy *.jar in WebLogic by Hudson and WLST

    Hi everybody!
    I have the server (hostname - server0), where:
    1. Developers works. He create the build JAR-files and put this file in special local directory:
    /home/build/test1/jar/ - jar-file for test envorement 1 of weblogic (hostname - server1)
    /home/build/test2/jar/ - jar-file for test envorement 2 of weblogic (hostname - server2)
    2. I have the directories with WLST scripts for deploing the build JAR-files:
    2.1. Script files for deploing the jar-files in test envorement 1 of weblogic (hostname - server1)
    /home/build/test1/scripts/deploy.sh
    /home/build/test1/scripts/deploy.py
    2.2. Script files for deploing the jar-files in test envorement 2 of weblogic (hostname - server2)
    /home/build/test2/scripts/deploy.sh
    /home/build/test2/scripts/deploy.py
    3. Hudson (Hudson ver. 2.1.2) is intsalled.
    Could you please tell me, how to automatic deploy *.jar in WebLogic by Hudson and WLST, if take into consideration the email-notification about problem in deploing?

    I've never used WLST inconjunction with Hudson.
    What I have done is use Maven to do this.
    We have a WebLogic Server Maven Plugin which can perform deployment operations.
    Hudson has support for Maven, so you create a Maven project which does the deployment from the project and configure a job using that on Hudson -- if you can get your developer to upload their artifacts to some form of SCM system so Hudson watches for the changes, grabs the new file and does the deployment, that would work.
    If you want to use your scripts, then you could perhaps use the Hudson SSH plugin which can execute "shell" scripts on a server. Theoretically here you would create wrapper shell scripts for your WLST execution/script, then configure a Hudson job which executes the scripts. I've never used the plugin so not sure how it is activated, but you could configure a job to run on a periodic basis, and have the wrapper script itself do the check to see if the directory contains a jar/ear file to deploy -- if it does, execute the WLST scripts; if not, simply return.
    Let us know how you get on!
    -steve-

Maybe you are looking for

  • Trying to Print - Receiving "Missing USB Class Driver" Error

    Since I upgraded from Tiger to Leopard, I have not been able to print. I have a Lexmark X5470. At first, any application that attempted to print simply crashed. Then, I removed the Lexmark folder from /Library/Printers, and did a custom install of ju

  • Workflow Process Log not displayed on UI

    The client recently performed a upgrade in their development environment from 7.0 to 8.0.0.4 and everything appears to be working properly however, the Workflow Process Logs in the UI under Administration-Business Process\Workflow Process Log is not

  • BWA OS Upgrade Error Shared Storage

    We have recently upgraded our IBM BWA to SUSE Linux 11.1, upgraded the GPFS 3.4.0-7 and recompiled RDAC. Everything seemed to work fine, the queries execute, but when I run the checkBIA, I get these warning/error messages: OK: ====== Shared Storage =

  • SR1 to SP14 Upgrade - Portal Platform Warning

    Hello all, I am upgrading the recently installed SR1 to SP12. I successfully applied the Patch for WEBAS J2EE server. Now I'm trying to apply Portal Platform patches. During the "Deploy EAR Files" phase (6 of 12), it gave a warning Message box saying

  • Session Folders

    I've read posts here and there that lead me to believe the answer will be no, but I thought I'd throw it out there for a definitive answer before I give up.  Is there a way to point your session to a different folder for saving audio files?  I would