Is CSIv2 supported in WLS6.1SP2?

Thanks Andy.
I have some other (different) questions - but I think I should email them. I'll
send via Peter and Jim.
Cheers,
Nick
Andy Piper <[email protected]> wrote:
"Nick Minutello" <[email protected]>
writes:
Is CSIv2 supported in WLS6.1SP2?No. 7.0 only.
andy

Similar Messages

Anyone tried to deploy IBM's Java resource adapter for IMS on WLS6.1sp2?

          Has anyone had success or attempted to deploy the IMS Connector
          for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          use this to connect WebLogic to IMS via IMS Connect 1.2?
          Thanks
          Sam


          "Sam Naylor" <[email protected]> wrote:
          >
          >Has anyone had success or attempted to deploy the IMS Connector
          >for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          >use this to connect WebLogic to IMS via IMS Connect 1.2?
          >
          >Thanks
          >Sam
          Sam,
          I was wondering if you were able to use the IMN Connector RAR file. I was able
          to deploy but that was teh extent of my effort.
          Appreciate you insight!

GC on WLS6.1sp2 and WLS7sp2

Hi All,
Does any find that there is GC problem on WLS6.1sp2? I had an application(web
module) which deployed on both WLS6.1sp2 and WLS7sp2. Both server with same configuration
and initializing min and max heap size to 64m. The occupied memory in heap is
about 20Mb after full GC in both server before the test. When I perform a stress
test on them, I found that garbage collection behavior is different.
In WLS6.1sp2, after running my load test for a period of time, the occupied memory
is about 50Mb after full gabage collection. If I go on stress on the server, OutOfMemoryError
generated. Server has to be restarted. It seems that even full gc, it can't release
all unused objects.
In WLS7sp2, after running my load test for a period of time, the occupied memory
is still 23-25Mb after full gabare collection. There is no problem if I go on
to stress the server.
It seems that the performance of WLS6.1sp2 is not acceptable. It can't release
unused objects. Does any have the same experience on WLS6.1? How can I solve this
problem in WLS6.1? Otherwise, I have to migrate all my program to WLS7. Thx a
lot.
Karen

Karen,
You should try testing weblogic 6.1 with SP4. There are some fixes
related to memory leaks in Wl 6.1 SP3 and SP4.
-Kiran
"Karen Law" <[email protected]> wrote in message news:<3e9d11e1$[email protected]>...
Hi All,
Does any find that there is GC problem on WLS6.1sp2? I had an application(web
module) which deployed on both WLS6.1sp2 and WLS7sp2. Both server with same configuration
and initializing min and max heap size to 64m. The occupied memory in heap is
about 20Mb after full GC in both server before the test. When I perform a stress
test on them, I found that garbage collection behavior is different.
In WLS6.1sp2, after running my load test for a period of time, the occupied memory
is about 50Mb after full gabage collection. If I go on stress on the server, OutOfMemoryError
generated. Server has to be restarted. It seems that even full gc, it can't release
all unused objects.
In WLS7sp2, after running my load test for a period of time, the occupied memory
is still 23-25Mb after full gabare collection. There is no problem if I go on
to stress the server.
It seems that the performance of WLS6.1sp2 is not acceptable. It can't release
unused objects. Does any have the same experience on WLS6.1? How can I solve this
problem in WLS6.1? Otherwise, I have to migrate all my program to WLS7. Thx a
lot.

Where is weblogic_sp.jar in wls6.1sp2??

I download wls6.1sp2,but.
After I install it in win2000,in lib directory weblogic_sp.jar isn't exist!!
why??
help me!!
regds

Hi,
I think the service pack is actually contained in the weblogic.jar file,
so there's no need for a weblogic_sp.jar. The reference to
weblogic_sp.jar in the start script is probably there for old time's
sake :-)
Nils
simon wrote:
>
I download wls6.1sp2,but.
After I install it in win2000,in lib directory weblogic_sp.jar isn't exist!!
why??
help me!!
regds--
============================
[email protected]

Does BEA plan to release a service pack for WLS6.1sp2 to support the 2.3 spec for servelts(final)

The subject line says it all.


Niranjan,
          WLS 7.0 will be the first version that 'officially' supports the final
          JCA 1.0 spec. Currently, there are no plans to have WLS 6.1 officially
          support final JCA 1.0 spec, however, if there is enough customer demand,
          BEA will address.
          Cheers,
          Chris
          Niranjan Perera wrote:
          > The subject line says it all.
          >
          >
          >

JAX-RPC, JAXM, JAXR supported in WLS6.1?

Does wls6.1 support JAX API's? If not, when will they be supported? Thanks much.
Siming

Hi Siming,
The JAX Pack (i.e. JAX-RPC, JAXM, JAXB, JAXR, etc.) are still merely JSRs, with
no "real" consensus on whether they will ever be otherwise. This being the case,
it is unlikely that you will see support for them in WebLogic Server, in the near
future (3 to 6 months). You can always run the Sun RIs (Reference Implementations)
under WebLogic Server (I have done this with both JAXB and JAXM), if you would
like to experiment with these technologies.
Regards,
Mike Wooten
"Siming Mu" <[email protected]> wrote:
>
Does wls6.1 support JAX API's? If not, when will they be supported?
Thanks much.
Siming

SOAP support in WLS6.0

I hear that SOAP support is "built in" to 6.0, but is not yet documented and
won't be documented until February. Does anyone know if this support is the
Apache implementation or something else?

FYI - quoted from the WLS 6.0 FAQ....
Does WebLogic Server 6.0 support SOAP?
WebLogic Server 6.0 does not support SOAP; however, BEA provides an
alpha-quality SOAP implementation at
http://developer.bea.com:80/techtracks/xml/index.jsp.
Alex Thomas <[email protected]> wrote in message
news:3a42444e$[email protected]..
>
Can't see anything in WL6 yet. I heard that a separate, probablyunsupported, SOAP
component would be made available. This is a non-trivial task if oneincludes UDDI,
WSDL etc etc.
cheers
alex
"Robert Cahn" <[email protected]> wrote:
I hear that SOAP support is "built in" to 6.0, but is not yet documented
and
won't be documented until February. Does anyone know if this support is
the
Apache implementation or something else?

Dependency Package in Exploded Application WLS6.1sp2

I am working with the sample application used in Chapter 24 of Professional
Java Server Programming J2EE 1.3 Edition. The application is a test for
displaying ClassLoader information for ejb and web modules and their
associated dependent packages. I am able to deploy the packaged EAR without
a problem under WLS 6.1sp2, but when I attempt to deploy the same
application in exploded format, I am getting a NoClassDefFoundError during
deployment of the ejb module. The manifest files are unchanged and the
dependent jar files are located at the root of the exploded application...
below is a sample of the directory structure.
My question is, where should I put dependent classes and/or packages in an
exploded application and how do I setup the manifest to load them?
Thanks in advance for any help,
Tim Kuntz
\ear_root
Util1.jar
Util3.jar
Util6.jar
Util7.jar
\ejb
\depend1
\META-INF
MANIFEST.MF
Manifest-Version: 1.0
Class-Path: Util1.jar Util3.jar Util6.jar Util7.jar
http://www.theserverside.com/resources/articles/J2EE-Deployment/chapter.html

Here is the answer I received from a BEA Developer Relations Engineer
regarding this...
"When you deploy the EAR file, it is deployed under one classloader. When
you deploy the EAR file in the exploded format, then each EJB jar file is
loaded in a separate classloader. As long as the dependent (helper) classes
are in the classpath, you can always redeploy the EJB jar file, but if you
want to make changes to the dependent class then you have to restart the
WebLogic Server."
"Tim Kuntz" <[email protected]> wrote in message
news:3c616a90$[email protected]..
I am working with the sample application used in Chapter 24 ofProfessional
Java Server Programming J2EE 1.3 Edition. The application is a test for
displaying ClassLoader information for ejb and web modules and their
associated dependent packages. I am able to deploy the packaged EARwithout
a problem under WLS 6.1sp2, but when I attempt to deploy the same
application in exploded format, I am getting a NoClassDefFoundError during
deployment of the ejb module. The manifest files are unchanged and the
dependent jar files are located at the root of the exploded application...
below is a sample of the directory structure.
My question is, where should I put dependent classes and/or packages in an
exploded application and how do I setup the manifest to load them?
Thanks in advance for any help,
Tim Kuntz
\ear_root
Util1.jar
Util3.jar
Util6.jar
Util7.jar
\ejb
\depend1
\META-INF
MANIFEST.MF
Manifest-Version: 1.0
Class-Path: Util1.jar Util3.jar Util6.jar Util7.jar
http://www.theserverside.com/resources/articles/J2EE-Deployment/chapter.html
>
>

JTA to TMS Support for WLS6

Will WLS 6 JTA be able to coordinate with the Tuxedo TMS in WLS6
          GA? CB


Hi Craig.
          Sorry, no, transactional integration between WLS and Tuxedo is planned for a future
          release after WLS 6.0.
          -- Ed Felt, BEA Systems, Inc.

Core dump with WLS6.1SP2 on HP in libjvm.sl

I'm getting the following core dump on HP/UX 11.0. Has anyone seen this before? I'm using the JVM that ships with Weblogic.
Unexpected Signal : 10 occurred at PC=0xc37feb60
Function name=compute_is_subtype_of__13instanceKlassFP12klassOopDesc
Library=/home/darcher/bea/jdk131/jre/bin/../lib/PA_RISC2.0/server/libjvm.sl
Current Java thread:
"ExecuteThread: '11' for queue: 'default'" daemon prio=1 tid=0x00034df8 nid=23 lwp_id=6933 runnable [0x07bf3000..0x07b75478]
at inetsoft.report.internal.Gop.compare(Gop.java:766)
at inetsoft.report.Common.compare(Common.java:610)
at inetsoft.report.filter.DefaultComparer.compare(DefaultComparer.java:36)
at inetsoft.report.filter.SortFilter.compare(SortFilter.java:164)
at inetsoft.report.filter.SortFilter.qsort(SortFilter.java:195)
at inetsoft.report.filter.SortFilter.qsort(SortFilter.java:214)
at inetsoft.report.filter.SortFilter.qsort(SortFilter.java:214)
Thanks,
Dave

I'm getting the following core dump on HP/UX 11.0. Has anyone seen thisbefore? I'm using the JVM that ships with Weblogic.
Turn off the native IO first ... see if that makes a dif.
Then turn off hotspot (or JIT) and see if that makes a dif.
Then call HP (if it's the JIT) or BEA (if it's the native IO).
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"David W. Archer" <[email protected]> wrote in message
news:[email protected]..
>

WLS6.1SP2: "Connections Total" in "Monitoring"

What is meaning of the column "Connections Total" in monitoring page of
the JDBC connection pools?
Is it either
a) The current number of reserved (=in use) connections?
b) The current number of active (=open) connections?
c) The total number of distinct connections which have been created and
also removed in the pool?
I am just wondering this, because we have a connection pool that has a
maximum size of 50 connections. Couple of times this same connection
pool has had a 150 connections in the "Conneections Total" column!!!
BEA version is 6.1 SP2.
Mikko Mäkelä

Mikko,
The Connections Total is the total number of database connections that
have been created so far since the server was last restarted.
What is the value of Initial Capacity of the connection pool? I also
experienced the same problem but by setting the Initial Capacity to
the Maximum Capacity the problem seems to be gone.
Hopes this help,
Leo Fu
Sixth Dimension, Inc.
Mikko Mäkelä <[email protected]> wrote in message news:<[email protected]>...
What is meaning of the column "Connections Total" in monitoring page of
the JDBC connection pools?
Is it either
a) The current number of reserved (=in use) connections?
b) The current number of active (=open) connections?
c) The total number of distinct connections which have been created and
also removed in the pool?
I am just wondering this, because we have a connection pool that has a
maximum size of 50 connections. Couple of times this same connection
pool has had a 150 connections in the "Conneections Total" column!!!
BEA version is 6.1 SP2.
Mikko Mäkelä

Does WLS6.1-sp2 support J2EE-1.3 spec by default?

hi All,
          Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a simple
          Filter servlet, but it didn't work at all.
          I tried to find some docs related to J2EE spec compliance and they say the
          default is J2EE-1.3. Can anyone tell me the default J2EE spec supported by
          WLS6.1-sp2? And how can I check the currently-used J2EE spec in my running
          WLS? How can I switch between J2EE-1.2 and 1.3?
          Thanks
          Liu Yan


I think it is enabled by default. Note that javax.servlet.Filter which is
          shipped with WebLogic is different from one in final Servlet 2.3. Also you
          can search this newsgroup - there are lots of problems with Filters in 6.1.
          If you think that the problem is with your program, try to deploy it on Resin
          or Tomcat to see if it is actually the case.
          Liu Yan <[email protected]> wrote:
          > Thanks for your reply. I found that WLS6.1 DOES support so-called non-final
          > version of J2EE-1.3 spec. And my downloaded version is J2EE-1.3
          > feature-enabled by default. Seems the problem of my filter program.
          > But do you know how to configure J2EE compatibility in admin console? I mean
          > can I switch back and forth between J2EE-1.2 and 1.3?
          > Thanks
          > Liu Yan
          > "Dimitri Rakitine" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
          > :[email protected]...
          >> 6.1 does not support final Servlet 2.3 spec. You can see release notes
          >> for details: http://e-docs.bea.com/wls/docs61/notes/index.html
          >>
          >> Liu Yan <[email protected]> wrote:
          >> > hi All,
          >>
          >> > Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a
          > simple
          >> > Filter servlet, but it didn't work at all.
          >>
          >> > I tried to find some docs related to J2EE spec compliance and they say
          > the
          >> > default is J2EE-1.3. Can anyone tell me the default J2EE spec supported
          > by
          >> > WLS6.1-sp2? And how can I check the currently-used J2EE spec in my
          > running
          >> > WLS? How can I switch between J2EE-1.2 and 1.3?
          >>
          >> > Thanks
          >>
          >> > Liu Yan
          >>
          >>
          >>
          >>
          >> --
          >> Dimitri
          Dimitri

WLS6.1 hanging on Solaris- and SIGQUIT doesn't work

Hi,
We are experiencing a problem that looks like a deadlock when our server is under load (using WLS6.1SP2, Solaris 8 and the 1.3.1 JVM supplied with WLS). After processing many requests, the server hangs and CPU usage drops to 0%. Unfortunately the standard means of getting a thread dump (sending a SIGQUIT with kill -3 or Ctrl-\) does nothing. The problem also occurs if WebLogic is running under debug (using
-Xdebug -Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555) but alas the debugger hangs when trying to pause the server after this deadlock). It appears as though the server is not accepting any requests (including administrative requests from the console) but this doesn't seem to be due to thread starvation as CPU usage is 0%.
The only output we can get is from truss, which seems to indicate no activity at all until the SIGQUIT is received. It seems to register the SIGQUIT but it looks as though it is not being processed.
Does anyone have any ideas?
Kevin.

We found a solution to this problem, relating to the threading model that the JVM
uses.
Have a look at http://java.sun.com/docs/hotspot/threads/threads.html for more
details.
The default threading model on Solaris 8 is many-to-many (threads to LWPs) with
thread-based synchronisation. After playing with various threading models, we
found that the best was one-to-one with the alternate thread library. This is
the default provided by Solaris 9, but you can also tell Java to use this with
older versions of Solaris by putting the following line in your start command
prior to executing WebLogic:
export LD_LIBRARY_PATH=/usr/lib/lwp:$LD_LIBRARY_PATH
Apologies to anyone who was looking for an answer to this beforehand: I should
have replied to this newsgroup back in September!
Kevin Thomas
J2EE Consultant
LogicaCMG
Charlie Therit <[email protected]> wrote:
Kevin,
If you are not able to capture a JVM thread dump, then the next best
thing would be to capture several "/usr/proc/bin/pstack pid" C-level
thread dumps. This information may enable BEA Support to help suggest
potential work arounds. Depending upon the data in the pstack output,
you may also wish to open a support case with Sun.
Sincerely,
Charlie Therit
Developer Relations Engineer
BEA Support
Kevin Thomas wrote:
Hi,
We are experiencing a problem that looks like a deadlock when our serveris under load (using WLS6.1SP2, Solaris 8 and the 1.3.1 JVM supplied
with WLS). After processing many requests, the server hangs and CPU
usage drops to 0%. Unfortunately the standard means of getting a thread
dump (sending a SIGQUIT with kill -3 or Ctrl-\) does nothing. The problem
also occurs if WebLogic is running under debug (using
-Xdebug -Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555)but alas the debugger hangs when trying to pause the server after this
deadlock). It appears as though the server is not accepting any requests
(including administrative requests from the console) but this doesn't
seem to be due to thread starvation as CPU usage is 0%.
The only output we can get is from truss, which seems to indicate noactivity at all until the SIGQUIT is received. It seems to register
the SIGQUIT but it looks as though it is not being processed.
Does anyone have any ideas?
Kevin.

WLS6.1 - to - WLS 6.1 using t3 protocol

Is it possible to make a call using t3 protocol ( without using iiop) from WLS6.1sp2(#1)
to WLS 6.1sp2(#2), which are NOT in cluster
A) servlet on #1 to ejb on #2 B) ejb on #1 to ejb on #2
The WLS to WLS example talks about using iiop for WLS6.1sp2 to WLS5.1 sp11 but it
doesnot talk about wls6.1 to wls6.1

Hi,
We skipped 5.1 and jumped directly from 4.51 to 6.0 so I don't know how
5.1 differs from 6.0 in that respect but the same works in 4.51 and 6.x .
As for the server names -- it is the way the server connection manager
(RMI connections) caches the connections. If your two servers have the
same names one of those connections will be closed and you'll get
exceptions when trying to connect to the other server. It is a 6.1
feature and it shouldn't be that hard to reproduce in your environment.
(There are post for this also in the JMS newsgroup).
--dejan
Harshad Nanal wrote:
Thanks guys for hte info
BUT
I had tried sometime back with WLS5.1 sp6 on both the sides.I was unable to access
the serverWLS#2 from WLS#1 unless both are in clusters. Event the same was confirmed
by BEA support team on EVALNET
Have the things changed with wls5.1 sp11.
In wls6.1 sp2 why servers should have different names when they run on different
IP address
"Vyas" <[email protected]> wrote:
Weblogic has checks between different versions of t3 (t3 version is supposedly
different
from 5.x to 6.x) to disable t3 communication between these versions. One
of way getting
around is to use iiop.
There is no such problem between same versions of WL so no need to do anything
special.
"Harshad Nanal" <[email protected]> wrote:
Is it possible to make a call using t3 protocol ( without using iiop) from
WLS6.1sp2(#1)
to WLS 6.1sp2(#2), which are NOT in cluster
A) servlet on #1 to ejb on #2 B) ejb on #1 to ejb on #2
The WLS to WLS example talks about using iiop for WLS6.1sp2 to WLS5.1 sp11
but it
doesnot talk about wls6.1 to wls6.1

Performance problems using WLS6.1 with the thin driver for Ora9i from OTN

Hello everyone,
Has anyone been experimenting with the thin driver for Oracle 9i under WLS6.1. I got it running, but
I get extremely bad performance when having multiple concurrent accesses. It works more or less in
single user mode. Also it seems not to support XA transactions?
When could we expect the driver from BEA to be out?
Thanks in advance!
Samuel Kounev
TU-Darmstadt, Germany

I had done this from the very beginning, but I was still getting very bad performance under
concurrent accesses. I even followed Sree's instructions and removed the old thin driver from
weblogic.jar, but this didn't help. I am now trying to get the OCI driver for 9i running and hope
this will solve the problem.
Samuel
Tamilselvan Ramasamy wrote:
You have to use Oracle's Oracle 9i thin driver .
put this driver infront of the classpath i.e before weblogic_sp.jar and
weblogic.jar
/selvan
"Sree Bodapati" <[email protected]> wrote in message
news:[email protected]..
The BEA driver is available in WLS6.1SP2 which is GA.
hth
sree
"Samuel Kounev" <[email protected]> wrote in message
news:[email protected]..
Hello everyone,
Has anyone been experimenting with the thin driver for Oracle 9i under
WLS6.1. I got it running, but
I get extremely bad performance when having multiple concurrent accesses.
It
works more or less in
single user mode. Also it seems not to support XA transactions?
When could we expect the driver from BEA to be out?
Thanks in advance!
Samuel Kounev
TU-Darmstadt, Germany

Is CSIv2 supported in WLS6.1SP2?

Similar Messages

Maybe you are looking for