Weblogic 7.0 workshop problem

"Hi,
I have installed BEA WebLogin on my Unix machine with the directory structure
as given below.
srx8:/export/home/bea (1507> ls
jdk131/ logs/ UpdateLicense.sh utils/
license.bea registry.xml user_domains/ weblogic700b/
and
srx8:/export/home/bea/weblogic700b (1509> ls
common/ samples/ server/ uninstall/ workshop/
in the 'workshop' directory, I am trying to start the workshop with the command
/Workshop.sh, but it gives me the following error.. Can any of you please help
me how to solve this problem. I need to star the SOAP server and do some testing
and programming on it. This is the error, I got..Exception in thread "main" java.lang.NoSuchMethodError
at jellybeans.plaf.JellybeansLookAndFeel.initResourceBundle(JellybeansLookAndFeel.java:2529)
at jellybeans.plaf.JellybeansLookAndFeel.initComponentDefaults(JellybeansLookAndFeel.java:649)
at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:62)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:361)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:388)
at jellybeans.core.ui.mainframe.MainFrame.<init>%2

Similar Messages

Publishing EJBs takes more time in Oracle Weblogic 10.3 workshop

Hi,
We recently migrated from Weblogic 9.2 to Oracle Weblogic 10.3 workshop.
I have a ejb project which has more than 30 ejb's(both entity and session ejbs).
The problem is: whenever I modify the code inside a method and save, it builds the project automatically. After that when I try to publish the module, it takes around 5 - 10 minutes for publishing.
Points to note are : The ejb I am modifying has reference to other (10 - 20) ejbs. Hence it takes more time for even for single ejb change.
however, when i modify an ejb which has no reference to ejb, takes less time to publish.
My question is : is there a way to reduce the publishing time in this scenario.
Thanks in advance!

There is a special forum for Workshop issues:
Workshop
Try there.

Workshop problem in building relationship

Hi there,
It seems that workshop (comes with WebLogic 8.1) has problem building
relationship. It keeps saying that it cannot retrieve column info. from my
data source, when in fact creating entity beans from the exact data
source/table works fine.
Am I miss anything?
Thanks.
Yan

"Byron Foster" <[email protected]> wrote in message
news:[email protected]...
>
Thanks for the assist, your option B was the problem. It appears thatwhen using
the "create entity bean from database table" feature the data-source-nameproperty
is set by workshop to the JNDI data source name, and NOT the NAME. Whenusing
the 'Add Relation' feature the wizard uses this name, which of coursewon't work!
But, it has to be the JNDI name because in weblogic-cmp-rdbms-jar.xml
<weblogic-rdbms-jar>.<weblogic-rdbms-bean>.<data-source-name> has to be JNDI
name. EJBGen puts the name here...
So, I still think it is a bug:( A work-around is to name the NAME and JNDI
Name the same?
>
Now, I'm getting some error about can't find table!!! I guess it doesn'treally
matter since I can just use the "have workshop generate foreign keys"option,
since we don't use the appserver to create the tables. The "query table"option
is just a little more convenient.
Again, thanks for the help!
Michael Kovacs <[email protected]> wrote:
Hi Byron,
The error you're seeing is because the relation wizard
is unable to find your datasource on the server. It does
this by looking up the datasource mbeans on the server.
A couple of things:
A) Make sure that your datasource is created on the server.
There's a couple of different ways you can accomplish this:
1) Use workshop's datasource viewer under Tools->WebLogic
Server->Datasource Viewer...
and make sure you see your datasource.
2) Use the console or weblogic.Admin to make sure that your datasource
exists. In the console you'd look under Servcies->JDBC->Datasources.
With weblogic.Admin the MBean type that you would look for, and that
Workshop looks for, using the command line tool is: JDBCTxDataSource
So a sample command to get these MBean types would be:
java weblogic.Admin -url t3://localhost:7001 -username weblogic
-password weblogic get -type JDBCTxDataSource -pretty
(making sure of course that you have weblogic.jar on your classpath)
If you don't see the JDBCTxDataSource MBean that corresponds to your
datasource then workshop isn't going to find your datasource.
B) Make sure that the datasource NAME that you specify for
your entity beans match what the NAME of the datasource
is on the server. Not the JNDI name but the name of the datasource.
hope this helps,
-Michael
Byron Foster wrote:
I'm using workshop 8.1 SP2, and Adding relationships does NOT workwith the
same symptoms as described below.
Connection Info using DBVisualizer:
Oracle
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Oracle JDBC driver
9.2.0.3.0
Using the same driver through DBVisualizer I'm ablie to browse thecolumn information,
so
that would lead me to believe it is not a driver issue.
"keith shacks" <[email protected]> wrote:
Carl
I have recently used relationships in workshop 8.1 sp2 and it seems
to
work fine.
- Keith
"Carl" <[email protected]> wrote:
Well, I upgraded to SP2. I tried to use the relationships again.
This
time around, they still don't work. I get a message "Unable to
retrieve
column information. Datasource xxx not found.":( Does anybody elsehave
luck creating relationships in Workshop SP2? I will be more than
happy
to
provide an example that illustrates this problem.
"Carl" <[email protected]> wrote in message
news:[email protected]...
>>>>>
I believe you have encountered a bug in workshop. So, I do myrelationships
manually. May be it will be fixed in sp2?
"Yan Zhou" <[email protected]_NoSpam> wrote in message
news:[email protected]...
Hi there,
It seems that workshop (comes with WebLogic 8.1) has problem
building
relationship. It keeps saying that it cannot retrieve column info.from
my
data source, when in fact creating entity beans from the exact data
source/table works fine.
Am I miss anything?
Thanks.
Yan

Weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND

I have a deploy application on the server [Weblogic 10], but when I try to assign a VirtualHost handing me the following error:
          weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
          problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
          problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
          at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
          at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
          at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
          at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
          at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
          Truncated. see log file for complete stacktrace

<?xml version="1.0" encoding="UTF-8"?>
          <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
          <display-name>portalUchileWeb</display-name>
          <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>
          <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>
          <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>action</servlet-name>
          <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
          <init-param>
          <param-name>config</param-name>
          <param-value>/_pageflow/struts-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>debug</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>detail</param-name>
          <param-value>2</param-value>
          </init-param>
          <load-on-startup>2</load-on-startup>
          </servlet>
          <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>
               <jsp-config>
          <taglib>
          <taglib-uri>render.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/render_taglib.jar</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/exesite.tld</taglib-uri>
          <taglib-location>/WEB-INF/exesite.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>netui-tags-template.tld</taglib-uri>
          <taglib-location>/WEB-INF/netui-tags-template.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-html.tld</taglib-uri>
          <taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-adapter-html.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>um.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/um_taglib.jar</taglib-location>
          </taglib>
          </jsp-config>
          </web-app>

Workshop for Weblogic 10.3 shutdown problem.

Hi, i have downloaded latest Weblogic 10.3 edition and using workshop for weblogic. I upgraded my last project and defined weblogic 10.3 server. I could run server but when i
want to stop or restart, workshop cant stop the server. I could see server was stopped message in console, but progress bar was still processing and cant restart.
Thanks.

I found that, issue appears on x64 systems. I tried to start and stop weblogic server on x86 system successfully .
Same issue exists on oepe installed eclipse package.

Weblogic server in workshop not deploying ear automatically

Hi,
I configured a weblogic server in the workshop studio, I added an ear to it and started. but when I try to access the web page of the web module, it says "cannot find the page".
On admin console, it doesn't show any application added to it. Only after I deploy the application manually thru admin console, I am able to run my application, but that doesn't make sense because for evey tiny change, I have to create an .ear, stop the application, deploy and again start it.
Can somebody tell me what is the problem?
Regards,
Sushma

Hi Sushma,
Workshop Studio is a web application development tool. Hence ear deployment isn't supported in the current release.
Please create a dynamic web application and target that tot he server
Please post all Workshop Studio related questions to the bea.workshop.developer.general newsgroup at http://forums.bea.com/bea/forum.jspa?forumID=600000007
cheers
Raj

How Do I create & run a new servlet in the Weblogic 8.1 Workshop?

Using the Workshop environment I added a new Empty Application, then a new Web Project,MyServletPrj,then I added a new Java Class and created a famous HelloWorldServlet class.
Next I built application, started a WebLogic Server and depolyed application to the server.
I checked through the Administrative console that HelloWorldServlet was deployed as a part of my project.
How can I run my servlet?
I tried to run it from the MS Explorer browser
http://localhost:7001/MyServletPrj/servlet/HelloWorldServlet
It doesn't work.
What is the problem?
Thanks,
Irina

hi katzirina ,
To create or import the Servlet in workshop and to run it, we need to follow the
steps in workshop as given below.
1)Create the empty application
2)Create the webproject under the application
3)Right click on the webproject and choose the new -> java Class to write the
servlet in IDE Or choose import option and import the servlet file
4)Start the weblogic server
5)Go to tools menu->choose weblogic server->choose weblogic builder
6) In weblogic builder go to file menu->open your webproject
then it shows servlet ,filter,security Constriant and tag libraries folders in a builder at left side
7)Click on the servlet folder and click on the add button at right pane of the builder then you will give servlet name , servlet class name and url pattern.
After giving the Urlpattern click on the add button which is right to the urlpatern text field.
8)Click on ok button
9)click on the save button
then you will see the servlet mapping elements in web.xml file in workshop IDE what we given in builder.
10)Exit from the weblogic builder
11)Right click on the application and clean the application
12)Build the application
then it compiles the Servlets files automatically.
You can see the those class files in .workshop folder which is located under applicaton folder.
Note :go to the applicaton where it is stored.you should see these files manually because workshop ide shows the navigation from the webproject only. you can't see these files from workshop.
13)Go to tools menu->weblogic server->weblogic console and test the application using the weblogic console.
or Directly opent he internet explorer send a request for particular servlet by giving urlpattern.
--- Anilkumar kari

Weblogic 5.1 installation problem on winNT server4.0

while running weblogic executable file on CD to install weblogic on NT Server4.0, following message is appearing-
"the decompression of %s failed.There may not be enough space in the temp directory."
I tried putting the temp system variable in my own directory with 1 GB space , but to no avail. Plz. help
Thanx
JP

Try out hether u have enough space in ur temp directory. if not try cleaning up ur temp directory. by default it will be c:\temp. if the problem persist. try installing the software frm another CD
ebistro

Weblogic 6.0 installation problems with redhat 7.1

Hi!I need your help, I've been trying to install WebLogic 6.0 on linux, and i'm getting this message"sh /home/curtisf/weblogic600sp1_linux.bin -i consolePreparing to install.../tmp/install.dir.1046/Solaris/resource/jre/jre/bin/java: /usr/bin/cut: Nosuch file or directory/tmp/install.dir.1046/Solaris/resource/jre/jre/bin/i386/native_threads/java:error while loading shared libraries: libjvm.so: cannot load shared objectfile: No such file or directory" please if you have any idea of how to solve this problem, please send a mail to [email protected] or [email protected]

I've had the same problem. I created a softlink to cut in /usr/bin and it still
wouldn't work. The install starts and dies with no message or anything. It just
looks as if it'll run forever, but the process is defunct. Has anyone sucessfully
installed on RedHat 7.1?
Demetrio Cruz <[email protected]> wrote:
Hi!I need your help, I've been trying to install WebLogic 6.0 on linux,
and i'm getting this message"sh /home/curtisf/weblogic600sp1_linux.bin
-i consolePreparing to install.../tmp/install.dir.1046/Solaris/resource/jre/jre/bin/java:
/usr/bin/cut: Nosuch file or directory/tmp/install.dir.1046/Solaris/resource/jre/jre/bin/i386/native_threads/java:error
while loading shared libraries: libjvm.so: cannot load shared objectfile:
No such file or directory" please if you have any idea of how to solve
this
problem, please send a mail to [email protected] or [email protected]

Error starting WebLogic server from Workshop - 2

Sorry forgot to actually include the error:
Unexpected exception:
java.io.IOException: CreateProcess: cmd.exe /C START startWebLogic error=267
     at java.lang.Win32Process.create(Native Method)
     at java.lang.Win32Process.<init>(Win32Process.java:63)
     at java.lang.Runtime.execInternal(Native Method)
     at java.lang.Runtime.exec(Runtime.java:550)
     at jellybeans.util.ServerUtil$StartServerTask.runBackground(ServerUtil.java:363)
     at jellybeans.core.task.TaskThread.execute(TaskThread.java:114)
     at jellybeans.core.task.TaskThread.run(TaskThread.java:55)
Was caught at:
jellybeans.util.AssertionFailureException: Unexpected exception: CreateProcess: cmd.exe
/C START startWebLogic error=267
     at jellybeans.util.AssertUtil.handleUnexpectedException(AssertUtil.java:50)
     at jellybeans.util.ServerUtil$StartServerTask.runBackground(ServerUtil.java:367)
     at jellybeans.core.task.TaskThread.execute(TaskThread.java:114)
     at jellybeans.core.task.TaskThread.run(TaskThread.java:55)

Evelyn,
Can you tell me the operating system on which you are running WebLogic
Workshop.
Thank You,
Raj Alagumalai
WebLogic Workshop Support
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]..
Evelyn,
Are you able to start the server from the command line using
startweblogic.cmd ?
the file can be found under your beahome\weblogic700\samples\workshop
directory.
Did you have the older Beta installed on the same machine prior to
installing Beta2 ?
I'm not sure if you read this before.
The following is the set of steps to install Beta2
Before installing "Beta 2, uninstall your Beta 1 version like this:
1. Run the uninstaller
2. Delete the entire bea_home that housed Beta 1 (restart if necessary)
3. Restart
4. Install Beta 2
Also make sure that there is no .jellybeans or .workshop file in the
C:\Documents and Settings\username before to install Beta2
Thanks
Raj Alagumalai
WebLogic Workshop Support
Evelyn Hobson wrote:
Sorry forgot to actually include the error:
Unexpected exception:
java.io.IOException: CreateProcess: cmd.exe /C START startWebLogic
error=267
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:63)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:550)
atjellybeans.util.ServerUtil$StartServerTask.runBackground(ServerUtil.java:363
at jellybeans.core.task.TaskThread.execute(TaskThread.java:114)
at jellybeans.core.task.TaskThread.run(TaskThread.java:55)
Was caught at:
jellybeans.util.AssertionFailureException: Unexpected exception:CreateProcess: cmd.exe
/C START startWebLogic error=267
atjellybeans.util.AssertUtil.handleUnexpectedException(AssertUtil.java:50)
atjellybeans.util.ServerUtil$StartServerTask.runBackground(ServerUtil.java:367
at jellybeans.core.task.TaskThread.execute(TaskThread.java:114)
at jellybeans.core.task.TaskThread.run(TaskThread.java:55)

Error starting WebLogic Server from Workshop

I get the following error when trying to start WebLogic server
from within Workshop. Any ideas? Also, it looks like the sample
code that came with the first beta is no longer there - is that
supposed to be the case?
Build # 2002.0423.3
Values from Workshop.properties:
#Thu Jun 13 14:34:08 MDT 2002
paths.domain=workshop
paths.serverRoot=localhost
paths.startCmd=startWebLogic
defaultJndiDataSource=cgSampleDataSource
paths.browser=C\:\\Program Files\\Internet Explorer\\IExplore.exe
paths.httpRoot=http\://localhost\:7001
paths.rootDirectory=C\:\\bea7.0beta2\\weblogic700\\samples
paths.stopCmd=stopWebLogic
recent.lastProject=C\:\\bea7.0beta2\\weblogic700\\samples\\workshop\\applications\\samples
paths.classPath=C\:\\bea7.0beta2\\jdk131_02\\jre\\lib\\rt.jar;C\:\\bea7.0beta2\\weblogic700\\workshop\\stdlib.jar;C\:\\bea7.0beta2\\weblogic700\\server\\lib\\weblogic.jar
recent.lastFiles=C\:\\bea7.0beta2\\weblogic700\\samples\\workshop\\applications\\samples\\HelloWorld.jws
controls.applicationView.enabled=0
paths.port=7001

I get the following error when trying to start WebLogic server
from within Workshop. Any ideas? Also, it looks like the sample
code that came with the first beta is no longer there - is that
supposed to be the case?
Build # 2002.0423.3
Values from Workshop.properties:
#Thu Jun 13 14:34:08 MDT 2002
paths.domain=workshop
paths.serverRoot=localhost
paths.startCmd=startWebLogic
defaultJndiDataSource=cgSampleDataSource
paths.browser=C\:\\Program Files\\Internet Explorer\\IExplore.exe
paths.httpRoot=http\://localhost\:7001
paths.rootDirectory=C\:\\bea7.0beta2\\weblogic700\\samples
paths.stopCmd=stopWebLogic
recent.lastProject=C\:\\bea7.0beta2\\weblogic700\\samples\\workshop\\applications\\samples
paths.classPath=C\:\\bea7.0beta2\\jdk131_02\\jre\\lib\\rt.jar;C\:\\bea7.0beta2\\weblogic700\\workshop\\stdlib.jar;C\:\\bea7.0beta2\\weblogic700\\server\\lib\\weblogic.jar
recent.lastFiles=C\:\\bea7.0beta2\\weblogic700\\samples\\workshop\\applications\\samples\\HelloWorld.jws
controls.applicationView.enabled=0
paths.port=7001

Weblogic 5.1 SP9 problems with MAC OS 9 w/ MRJ 2.2.5 [InterruptedIOException]

Hello all,
We're having a problem with one of the beans running on our WebLogic server.
A quick summary:
The application is a standalone java application that
interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
The clients are a mix of Windows machines and Mac OS 9 (with OS X
coming down the line, but that is not feasible at this time
to consider a massive upgrade). Due to the limitations
of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
Mac and JRE 1.1.9 on the Windows machines.
The general flow of data is a request is made from the client app
to the WebLogic bean. The bean calls another class method which
retrieves data from the the backend database (Sybase or SQL Server 2000).
We've verified that the data comes back from the query, is placed
in an array, and is in the same state when the EJB prepares to 'return'
the data to the client. This works as expected on the Windows machines,
however, every so often, the Macs will give an
InterruptedIOException: send timed out error. Once the server times
out (after 240 seconds), the client can continue until the next
error.
A few additional pieces of info.
The data returned is an array, but there isn't any consistancy to the
size of the data set. Some will be single element arrays while others
will have 8-10 elements. The amount of data in each element is only
a string of a couple hundred characters, so it is not a large data
stream. Systems on the same network segment can go for a while (sometimes
going on 10 minutes) before getting this error, while remote offices
going over slower links will get an immediate InteruptedIOException.
We have a process in place that if it catches an InterruptedIOException
it loops and tries the procedure again, however a 4 minute wait
between loops just isn't acceptable. We tried lowering this by
placing the following lines into our weblogic.properties file:
weblogic.system.periodLength=15
weblogic.system.idlePeriodsUntilTimeout=4
However, this has had zero impact on the timeout. Are there programatic
ways of changings these values? Or to force a blocking connection that
will force the data pipe to stay open? Has anyone had any insight into
any similar problems? Unfortunately, due to the size of the company,
the environment is fixed, and no mass upgrades are a vaiable option.
Thanks all!
Cliff

Hi Cliff,
it seems as if we have a similar problem within WLS51sp13 and a Java
Client (Servlet within Tomcat). We found that an EJB Stub within the
Client App has a 180s timeout, if the server socket didn't close
(Network problem or similar). I friend gave me a hint setting this
parameter on both sides, client and Server: It works. It seems as if the
server takes the bigger value of both values set.
Greetings,
schnaggy:-)
Cliff Wagner wrote:
Hello all,
We're having a problem with one of the beans running on our WebLogic server.
A quick summary:
The application is a standalone java application that
interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
The clients are a mix of Windows machines and Mac OS 9 (with OS X
coming down the line, but that is not feasible at this time
to consider a massive upgrade). Due to the limitations
of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
Mac and JRE 1.1.9 on the Windows machines.
The general flow of data is a request is made from the client app
to the WebLogic bean. The bean calls another class method which
retrieves data from the the backend database (Sybase or SQL Server 2000).
We've verified that the data comes back from the query, is placed
in an array, and is in the same state when the EJB prepares to 'return'
the data to the client. This works as expected on the Windows machines,
however, every so often, the Macs will give an
InterruptedIOException: send timed out error. Once the server times
out (after 240 seconds), the client can continue until the next
error.
A few additional pieces of info.
The data returned is an array, but there isn't any consistancy to the
size of the data set. Some will be single element arrays while others
will have 8-10 elements. The amount of data in each element is only
a string of a couple hundred characters, so it is not a large data
stream. Systems on the same network segment can go for a while (sometimes
going on 10 minutes) before getting this error, while remote offices
going over slower links will get an immediate InteruptedIOException.
We have a process in place that if it catches an InterruptedIOException
it loops and tries the procedure again, however a 4 minute wait
between loops just isn't acceptable. We tried lowering this by
placing the following lines into our weblogic.properties file:
weblogic.system.periodLength=15
weblogic.system.idlePeriodsUntilTimeout=4
However, this has had zero impact on the timeout. Are there programatic
ways of changings these values? Or to force a blocking connection that
will force the data pipe to stay open? Has anyone had any insight into
any similar problems? Unfortunately, due to the size of the company,
the environment is fixed, and no mass upgrades are a vaiable option.
Thanks all!
Cliff

Init method in Weblogic 5.1 gives problem

          I have used init method in 4.5
          the same method gives problem in 5.1
          C:\weblogic\myserver\classfiles\jsp_servlet\_addcontract.java:89: The method void init(javax.servlet.ServletConfig) declared in class jsp_servlet._addcontract cannot override the final method of the same signature declared in class weblogic.servlet.jsp.JspBase. Final methods cannot be overridden.
          probably occurred due to an error in /addContract.jsp line 11:


Use jspInit method.
          harish <[email protected]> wrote:
          > I have used init method in 4.5
          > the same method gives problem in 5.1
          > C:\weblogic\myserver\classfiles\jsp_servlet\_addcontract.java:89: The method void init(javax.servlet.ServletConfig) declared in class jsp_servlet._addcontract cannot override the final method of the same signature declared in class weblogic.servlet.jsp.JspBase. Final methods cannot be overridden.
          > probably occurred due to an error in /addContract.jsp line 11:
          Dimitri

Weblogic Integration 2.1 problem

<b>I have installed Oracle 9.X then installed Weblogic 6.1 and then installed Weblogic Integration 2.1
after instalation i have started Weblogic server by clicking wlintegration2.1/config/bpmDomain/startWeblogic.cmd
Then i am getting this problem</b>
java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.getConfiguredPlugins(
PluginManagerCfgImpl.java:749)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.initializePlugins(Plu
ginManagerCfgImpl.java:873)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(PluginManagerCfg
Impl.java:80)
at com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(Pl
uginManagerCfgBean_gebmxi_EOImpl.java:1300)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListe
nerBean.java:153)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Oct 31, 2006 4:49:49 PM IST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "myserver" for domain "bpmdomain" running in Production Mode>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
<b>Please resolve this ASAP</b>.

I'm having this issue as well. Can you tell me how you fixed the problem???
Thanks

WebLogic RMI UNIX Performance problem

Hi.
I'm experiencing problems with the performance of RMI calls from within session
beans to external RMI services. I have a system running 4 RMI services in separate
JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+ Gb of RAM.
The system was developed on NT and deployed to UNIX. A typical request is serviced
in 70-90 ms on the NT development box (Desktop 512Mb RAM) but when deployed to
the UNIX box takes anywhere between 500-4000 ms. Performance metrics in the code
indicate that 'crunch' times are similar but remote RMI calls are orders of magnitude
greater.
Has anybody had similar problems? I have checked the tuning guides wrt TCP/IP
configurations but would not expect such a large difference using the default
Solaris configuration. Memory and CPU utilisation on the SPARC are low as are
I/O and other metrics available from vmstat.
Cheers
Pete

Hi.
The JVMs are running on the same machine thus should be looking in /etc/hosts
and not going via DNS.
I have read there is a performance gain by tying WL to a single CPU, any insight?
Pete
Andy Piper <[email protected]> wrote:
"Pete Harris" <[email protected]> writes:
I'm experiencing problems with the performance of RMI calls from withinsession
beans to external RMI services. I have a system running 4 RMI servicesin separate
JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+Gb of RAM.
The system was developed on NT and deployed to UNIX. A typical requestis serviced
in 70-90 ms on the NT development box (Desktop 512Mb RAM) but whendeployed to
the UNIX box takes anywhere between 500-4000 ms. Performance metricsin the code
indicate that 'crunch' times are similar but remote RMI calls are ordersof magnitude
greater.
Has anybody had similar problems? I have checked the tuning guideswrt TCP/IP
configurations but would not expect such a large difference using thedefault
Solaris configuration. Memory and CPU utilisation on the SPARC arelow as are
I/O and other metrics available from vmstat.Its possible that you are getting a DNS lookup for each request or
worse a reverse lookup. You might want to try using IP addresses in
your config to see if that helps.
andy

Weblogic 7.0 workshop problem

Similar Messages

Maybe you are looking for